Wiki planning

[Markus Zywitza]

Will we use namespaces to partitionate the wiki? If yes,what about the
following structure:

-Main namespace: Website
-Docs: End-User Documentation
-Using: Documentation contributions
-Samples: Sample applications and tutorials
-Develop: Contributor related information (style guides etc.)

I was also thinking about using namespaces by product, but given that
many products will be merged in the near future, I think this
partitioning will be quite unstable over time.

What are your thoughts?

-Markus

[Krzysztof Koźmic]

- I think we can pretty safely assume MonoRail, ActiveRecord and Windsor
can have their own NS
- I don't see any reason to keep docs and using separate, perhaps
samples should be there as well, especially given there aren't too many

Krzysztof

[John Simons]

Even so projects may merge in the near future, I would still use
namespaces.
Regarding structure, Henrik put a screenshot of what a project page
could look like: http://castle-project-devel.googlegroups.com/attach/d25f8dc52124a618/documentation_page.png?view=1&part=2,
I think this may be our starting point?

I was more about grouping things per project, such as:
ProjectA
Samples
Documentation/Tutorials
ProjectB
Samples
Documentation/Tutorials
...
I would then also have the following namespaces:
-Main: default home

-Develop: Contributor related information (style guides etc.)

Also, regarding sponsor logos, do we need to display them on the home
page? Or can they be moved?

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.

Cheers
John

On Mar 3, 4:46 am, Krzysztof Koźmic <krzysztof.koz...@gmail.com>
wrote:

[Markus Zywitza]

2010/3/2 John Simons <johnsi...@yahoo.com.au>:

> 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

[John Simons]

Markus,

As I said before, all submissions will be moderated, so we still have
the last say :)
And because of that, I don't see a reason to have this separation you
are proposing.

I've enable the moderation setting under Administration |
Configuration (Tab) | Security Configuration (settings)
See http://www.screwturn.eu/forum/viewtopic.php?f=17&t=7268

Cheers
John

On Mar 3, 10:56 am, Markus Zywitza <markus.zywi...@gmail.com> wrote:
> 2010/3/2 John Simons <johnsimons...@yahoo.com.au>: