Difference between revisions of "Wiki Team/Wiki Gardening Weekend 2016"
Jump to navigation
Jump to search
m (→Activity Team) |
|||
| Line 9: | Line 9: | ||
== Activity Team== | == Activity Team== | ||
| − | [[Activity_Team]] role needs some love, with the migration off of a centralized git-based repository | + | [[Activity_Team]] role needs some love, with the migration off of a centralized git-based repository [https://git.sugarlabs.org/ Gitorious] to diverse GitHub repos has to some extent decentralized a developer and localizer community that previously had a common point of contact. |
* Who adopts Activities stranded in Gitorious? | * Who adopts Activities stranded in Gitorious? | ||
Revision as of 21:20, 20 April 2016
- Review Wiki_Team/Roadmap
- Review Special:ListUsers/bureaucrat
- Review Activities/Activities_needing_documentation
- Review Activity Team (lots of obsolete references and no JS activity references)
- Review Getting Involved (make it relevant to Sugar in 2016)
- Review Education Team (make it relevant to 2016 realities)
Activity Team
Activity_Team role needs some love, with the migration off of a centralized git-based repository Gitorious to diverse GitHub repos has to some extent decentralized a developer and localizer community that previously had a common point of contact.
- Who adopts Activities stranded in Gitorious?
- How to provide the best linkage for Activity feedback form less sophisticated users back to developers/maintainers?
- Translation_Team needs direct channels and responsive maintainers to advance i18n and L10n.
Translation Team
Chris Leonard User:Cjl would like to respectfuilly request editorial control over the Translation Team Translation_Team branch structure. I have some major work to do and it is going to be easiest to use wiki markup in the editing process. This is a very small portion of over all wiki content.