2010/3/2 John Simons <[email protected]>: > Marcus, Why do you have a namespace specific for contributions (Using: > Documentation contributions ) ? The whole website is a wiki, I would > like to allow users to change any page(except maybe the home page), > this of course is moderated.
I find the separation we have now quite useful. When looking at using-wiki we have now, I find a lot of information that is outdated, some is even plain wrong or proposes solutions that have major drawbacks when used. The official docs (site on SVN) requires authors to be committers or other contributors to have a committer add the contribution, which should have a look upon it before committing it. I want to keep the distinction to separate between official/proofread/supported content and user contributions, with the former being a definitive reference for the end-user. For example, I have created NUnit tests for nearly all code samples I have added to the ActiveRecord-pages I revised, as well as statements I was not 100% sure of. Since editing rights can be set in STW by namespace and namespaces cannot be nested, it is more useful to have namespaces for website, docs and contributions than having namespaces per project. When documentation is contributed as wiki pages, it is possible to migrate a page from using to docs including meta-info like categories and history. Therefore we had a process to proofread contributions and keep the quality level of the documentation. -Markus -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
