I am proposing approval of the Guianan Creole 
Wikipedia<https://incubator.wikimedia.org/wiki/Wp/gcr>. It has ticked off all 
the boxes it needs to tick off: active community, interface translation, 
reasonable number of pages.

The one potential problem with this test is that the ratio of articles to stubs 
is low. (That is, it has a lot of stubs, compared to quality articles.) The 
reason for this is that the small, but enthusiastic, team working on the test 
project kept wanting some guidance from LangCom as to how much content was 
needed in order to get an approval. By design, we don't really have a specific 
standard for that. In the absence of that guidance, the team kept creating 
short pages; it took me a long time to convince them to stop, and to focus on 
filling out complete pages instead.

They have now started to do that, and have a core of pages in areas of specific 
interest to the community of Guiane that are filled out and up to quality 
standards. They are continuing to work on that. But enough stubs were created 
early in the game that from a ratio perspective, it would take the team a long 
time to get to what we'd ordinarily prefer to see. Now, I have been working 
with this team regularly for a long while—probably at least two years. They 
feel they have worked hard, but they are getting anxious. I firmly believe that 
if this test is approved, the team will continue to work on the project, and 
will be able to recruit additional contributors. I am concerned that if we say 
no—particularly if I am not able to give specific guidance on how many 
"complete" pages are enough—they are going to give up and walk away.

Let me add: the stubs are not junk. They're just stubs. The team has worked 
hard to do the right thing all along, and their focus is in a good place now. 
Thank you for your consideration.

Steven


Sent from Outlook<http://aka.ms/weboutlook>
_______________________________________________
Langcom mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/langcom

Reply via email to