Difference between revisions of "Oversight Board/2017-2019-candidates"
(deleted the term "entry")
|Line 49:||Line 49:|
After a decade of working on Sugar, I reflecting on we engage learners. programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. to the of Free/Libre Software scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.
Where have we fallen short?
Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex
Revision as of 16:11, 31 August 2017
There are to be four (4) Oversight Board slots to be elected for the 2017-2019 period, currently held by Walter, Adam, Lionel and Sameer.
|Stage I||August 15||Announcement of election date and first call for candidates.|
|Stage II||August 30||Reminder of election date and second call for candidates.|
|Stage III||September 15||Candidates' Wiki submissions deadline.|
|Stage IV||October 1-15||Election.|
Candidates should create a Wiki entry at Candidates' Wiki submissions, one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.
Candidates should read and understand the terms of the Software Freedom Conservancy Fiscal Agreement, because such terms bind our behavior as Sugar Labs Oversight Board and all our internal policies and procedures as a Project and as an organization.
Among other terms, please note the Project Management, Communications and Activities terms in the agreement provide that:
2.1. The Oversight Board Will Manage the Project.
2.2. The Project Will Be Free Software.
6. Representation of the Project in Conservancy: The Representative will have the authority to instruct Conservancy on the Project’s behalf on all matters.
The terms contemplate that the Oversight Board elects a single individual to communicate with Conservancy (the “Representative”) and shall notify Conservancy promptly following the election of a new Representative.
By publishing your candidacy below, you imply that in case you are elected a Sugar Labs Oversight board member you will honor the agreement terms.
Devin Ulibarri is a musician and an educator who became interested in free/libre software in 2014 during research for the Center for Music-in-Education (Boston). Devin pursued research into the implications for "software libre in education" which led him to believe that free/libre software is best for teaching and learning. He was soon introduced to SugarLabs, which both empowers teachers/learners with software freedom as well as offers tools to exercise those freedoms in a community setting.
Since his introduction to the SugarLabs community, Devin has participated heavily in the development of Music Blocks, a programming language for music. Within the SugarLabs community, Devin offers conceptual recommendations, design ideas, mockups, testing, minor patches, and community involvement on GitHub and Sugar's IRC. In his local community, Devin has represented Music Blocks software as a workshop lecturer (Constructionism Conference in Thailand, Canopy of Somerville) as well as a class instructor (YMCA Malden).
As an oversight board member, Devin would bring his insight as an experienced classroom teacher, an artist, and a free/libre software advocate. Devin has been described as "a very patient person", which he hopes would be a contribution to the oversight board if elected.
After a decade of working on Sugar, I am reflecting on how we engage learners. We provide programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. Our adherence to the principles of Free/Libre Software provides scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.
Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex. Apps might be fun, but the hard part of “hard fun” is in reaching towards complexity.
We are going where the learners are: Sugar as a Web app, on Android, or on iOS, (Sugarizer) and, tracking the growth of the Maker Movement, we now support Sugar on Raspbian. “It is said that the best way to learn something is to teach it—and perhaps writing a teaching program is better still in its insistence on forcing one to consider all possible misunderstandings and mistakes.” — Seymour Papert
I have made mistakes, but as part of a learning community we will do better.
“Homework is boring. Looking for bugs is fun.” —Ezequiel Pereira
Let's continue to provide the basis of some fun.