Changes

*# Arrange for a simple and well-documented procedure for these deployments to provide their own translation and to share the results with the community;

*# Arrange for a simple and well-documented procedure for these deployments to provide their own translation and to share the results with the community;

* Report monthly to the Sugar Labs Oversight Board and to the community and to the public on the status of the translations program, preferably by blogging informally (blog posts can be any length) to http://planet.sugarlabs.org using plain language that is understandable to almost all.

* Report monthly to the Sugar Labs Oversight Board and to the community and to the public on the status of the translations program, preferably by blogging informally (blog posts can be any length) to http://planet.sugarlabs.org using plain language that is understandable to almost all.

* Report every 4 months on strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:

* Report every 4 months on tactical/strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:

*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)

*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)

*# What can and should happen over the coming 4-month cycle?  Community workflows are never 100% rational: how do we tactically nurture continuous improvement?

*# What can and should happen over the coming 4-month cycle?  Community workflows are never 100% rational: how do we tactically nurture continuous improvement?

*# Long-term strategic/impact recommendations on an annual basis.  Or optionally more often, if he/she is so inclined.

*# Long-term strategic/impact recommendations on an annual basis.  Or optionally more often, if he/she is so inclined.

* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle.  This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!

* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle.  This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!