On Jul 18, 2012, at 9:36 AM, Pascal Robert wrote:

> 
> Le 2012-07-18 à 09:22, G Brown a écrit :
> 
>> Do you mean:
>> 
>> 1. A User Manual for all wocommunity, and
>> 
>> 2. A Developer Manual for wocommunity?
> 
> No, I mean one wiki space for people who contribute to Wonder and WOLips (and 
> other related tools), and another space with everything else (e.g. 95% of the 
> content of the current wiki).
> 

That is what I meant by User and Developer.

> So maybe "Documentation", and "Community" would be better names.

[WOCommunity]UserDocumentation - for tool, framework, use documentation--how to 
use the stuff,  

[WOCommunity]Tool&FrameworkDevelopment - for how to develop the tools, and 
frameworks

Prepending "WOCommunity" to wiki names would be a little redundant on the 
WOCommunity website; however, a little redundancy is not always bad for human 
brains.

These wiki names would indicate what kinds of thing were contained in the wiki, 
hopefully clearly as well.  Oui/Non? 

> 
>> Maybe UserManual would be a better name than Wonder? I would think the 
>> Wonder wiki  would cover just Wonder, not WOLips, etc. Historically it 
>> certainly has been true.
>> 
>> Names are important. The name should reflect what it is.
>> 
>> $0.02
>> 
>> 
>> On Jul 17, 2012, at 10:20 PM, Pascal Robert wrote:
>> 
>>> 
>>> We do want to have only two spaces: one for "regular" users one for 
>>> contributors. Check the docs mailing list discussions:
>>> 
>>> https://wocommunity.org:9100/Lists/docs-group/List.html
>>> 
>>> The big, non contributor space, is Wonder, and we wanted to move all 
>>> current stuff from the WO space to Wonder.
>>> 
>>> 
>> 
>> 
>> G Brown
>> [email protected]
>> 
>> 
>> 
>> 
> 


G Brown
[email protected]




 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to