2,354
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 10:
Line 41: − + Line 101:
Line 132: − + Line 128:
Line 159: + + Line 151:
Line 184: − # Increase L10n recruitment activities through personal or collaborative contacts. This is something to which every Sugar Labs member should contribute, but the Deployment Team (especially OLPC deployment partners) and the Local Labs have particular responsibilities for their native languages.+ − # Infrastructure Team support required for Pootle upgrade.+ − # Activity Team collaboration required to increase i18n of ASLO activities.+ − # Bug Squad could enhance testing of LTR and bidirectional language support. Arabic / Dari or Hebrew testers would be especially useful.+ − # Design Team should keep i18n / L10n issues in mind when making choices, e.g. bolding of text is not ideal for i18n / L10n (depending on the fonts available), whereas color highlighting is language neutral.+ − # There are happily a wealth of materials being developed in local languages by local deployments, unhappily very few of those materials are being upstreamed by re-basing on the most-common English i18n formats. The Education Team and Local Labs should take the lead in identifying suitable materials and advocating for i18n into a format that will work with our existing infrastructure and resources (i.e. English msgids).+ − # The previous point is not anglocentrism, but rather an acknowledgment of the reality that we have a primarily lang-en to lang-XX L10n community. A similar acknowledgment of linguistic reality has caused us to develop materials and methods to facilitate re-basing on Spanish for L10n into indigenous languages. This places a particular urgency on keeping lang-es L10n current at all times to allow lang-es strings to be used as a bridge to indigenous languages.+
Oversight Board/2011/Meeting Minutes-2011-09-16 (view source)
Revision as of 23:07, 16 September 2011
, 23:07, 16 September 2011→Team Reports
In attendance:
SLOB members: walter, cjb, icarto, alsroot, bernie
Community members including: cjl, JT4sugar, wernerio, SeanDaly, garycmartin, raffael
== Agenda ==
# Team Reports
# Local Lab Reports
# Resources discussion
----
'''MOTION''' Keep the GSoC 2010 mentor funds as our general funds, as previously decided, revisiting the decision of whether to give some/all of them to the mentors themselves next time we do a SoC.
Motion passed 4 yes; 1 not voting; 2 not present
----
===Action items===
# follow up meeting to look at content support (including activity output and commentary)
# follow up meeting re content for the new website
# follow up meeting re deployment team <--> local labs
# bernie to put our financial house in order
# walter to report motion to SFC
===Team Reports===
===Team Reports===
[[File:Sugar team and local labs updates sept 2011 som.jpg|thumb|380px|Self-Organizing Map from team and local lab report text.]]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014077.html Activity]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014077.html Activity]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014045.html Infrastructure]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014045.html Infrastructure]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014066.html Marketing]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014066.html Marketing]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014027.html Platform]
* [[Platform_Team/Roadmap|Platform]]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014046.html Translation]
* [http://lists.sugarlabs.org/archive/iaep/2011-September/014046.html Translation]
* [[Wiki_Team/Roadmap|Wiki]]
* [[Wiki_Team/Roadmap|Wiki]]
===Constraints===
===Constraints===
====What does the team see as its constraints from being more successful in its Mission?====
====What does the team see as its constraints from being more successful in its mission?====
''Activity''
''Activity''
* Finding developers willing to maintain activity code over the longer term.
* Finding developers willing to maintain activity code over the longer term.
''Design''
''Design''
* Mining mail lists, wikis, blogs, for any thing that might be appropriate.
* Mining mail lists, wikis, blogs, for any thing that might be appropriate.
''Marketing''
* The marketing challenges can be met. I am however pessimistic concerning the technical orientation of the project. In my view, if teachers had more weight in Sugar Labs, the Marketing Team could spend a lot less time explaining and fighting and more time marketing. However, for this to happen, developers would need to accept teachers' recommendations concerning the project's orientations. FLOSS engineers generally have a healthy aversion to accepting assigned projects such as at classic marketing-run companies like Microsoft or Apple. It is my hope that SL developers (and packagers, etc.) would become motivated to do so through contact with teachers and Learners and reliable feedback concerning Sugar.
''Translation''
''Translation''
* Recruitment of additional localizers.
* Recruitment of additional localizers.
*# Give more governance weight to educators. This could be achieved in several ways, but I believe the best way would be to form an executive committee of team leaders meeting periodically. The marketing strategy could be aligned with the development roadmap for a start, resources allocation could be hashed out, in general more unity of purpose could be achieved. At the same time, I believe it may be beneficial to remake the Oversight Board with allocated seats for educators (under the current conditions they will never be elected). Perhaps candidates could run as either general contributor or educator, and the top two scoring educators could take seats on the Board?
*# Give more governance weight to educators. This could be achieved in several ways, but I believe the best way would be to form an executive committee of team leaders meeting periodically. The marketing strategy could be aligned with the development roadmap for a start, resources allocation could be hashed out, in general more unity of purpose could be achieved. At the same time, I believe it may be beneficial to remake the Oversight Board with allocated seats for educators (under the current conditions they will never be elected). Perhaps candidates could run as either general contributor or educator, and the top two scoring educators could take seats on the Board?
''Translation''
''Translation''
* Increase L10n recruitment activities through personal or collaborative contacts. This is something to which every Sugar Labs member should contribute, but the Deployment Team (especially OLPC deployment partners) and the Local Labs have particular responsibilities for their native languages.
* Infrastructure Team support required for Pootle upgrade.
* Activity Team collaboration required to increase i18n of ASLO activities.
* Bug Squad could enhance testing of LTR and bidirectional language support. Arabic / Dari or Hebrew testers would be especially useful.
* Design Team should keep i18n / L10n issues in mind when making choices, e.g. bolding of text is not ideal for i18n / L10n (depending on the fonts available), whereas color highlighting is language neutral.
* There are happily a wealth of materials being developed in local languages by local deployments, unhappily very few of those materials are being upstreamed by re-basing on the most-common English i18n formats. The Education Team and Local Labs should take the lead in identifying suitable materials and advocating for i18n into a format that will work with our existing infrastructure and resources (i.e. English msgids).
* The previous point is not anglocentrism, but rather an acknowledgment of the reality that we have a primarily lang-en to lang-XX L10n community. A similar acknowledgment of linguistic reality has caused us to develop materials and methods to facilitate re-basing on Spanish for L10n into indigenous languages. This places a particular urgency on keeping lang-es L10n current at all times to allow lang-es strings to be used as a bridge to indigenous languages.
''Wiki''
''Wiki''
* Promote greater documentation and interlinking of information.
* Promote greater documentation and interlinking of information.
* Attract more participants by public discussion.
* Attract more participants by public discussion.