10,513
edits
Changes
Oversight Board/2011/Meeting Minutes-2011-09-16 (view source)
Revision as of 09:35, 16 September 2011
, 09:35, 16 September 2011→What can Sugar Labs 'central' or the community do to help?
*# 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.