SpongeDocs Review and Planning

SpongeDocs Review and Planning
@Inscrutable wrote:

http://pastebin.com/rphXA8gH
Hello again, Sponge cosmos.

SpongeDocs has come a long way from it's humble beginnings, and now a plethora of translations have commenced. New PRs are arriving, and we greatly appreciate the contributions from the community. However, as it grows, it becomes more cumbersome to manage. SpongeDocs needs a few more able assistants, if they're out there.

This is addressed in particular to those involved in writing and managing SpongeDocs, and our translation teams working on Crowdin.

Crowdin
There are a lot of people now working on translating the Docs into many languages using our instance at Crowdin. However, there is no organised structure to some of these teams, and this may lead to conflict. We would like to appoint some Reviewers or Team Co-ordinators, to help things along. (Once Docs are Reviewed, they are protected from changes by other translators.) I would appreciate some feedback from the translation teams about this, so we can choose wisely.
--> EDIT: In particular, we need new co-ordinators for Chinese (China), French, Russian and Spanish. There are also six one-man translation teams...

I'd also like to apologise to any translators if it seems your problems haven't been getting much attention. As stated, we're a bit short on managerial staff at Crowdin, so it has been difficult to get around all the issues.

The status of or Translated pages is still a Work-in-Progress. There are plans afoot to make them available on RtD, and to make the pages on Crowdin update regularly from GitHub, but they have not yet been realised.

We Need Developers
Seriously. I may dance a fine dance, but I can't review code examples. We have a few friendly developers who can do this from time to time, but we need more. We need dev input into the structure of the docs (issue: The Grand Scheme) to see what pages may yet be needed. We could also use a whole heap of pages written (for plugins and for Sponge development) that need an experienced devs' eye, but even simply flagging issues as "API needed" would be a useful contribution. If you can spend 5 minutes a day looking at the odd PR or page, and put your comments in #spongedocs , then it will be a great help.

phew That largely covers the issues we currently have on the Docs. Let me again call for volunteers to jump in and assist, the more the merrier. Just ask on #spongedocs and someone can point you to a useful task. Also, please feel free to reply - this is meant to be a discussion, not rules-from-on-high. Let's get something going that works for everyone involved, so we're all on the same page.

EDIT: SpongeDocs now has a sub-forum here. Please try to direct all relevant message traffic that way in future.
​

Posts: 38

Participants: 21

Read full topic