Hi all, Derick and me just discussed the usage of our Wiki. While a wiki is a cool way for users to contribute docs and I personally see quite some uses for it, Derick objects that wikis tend to get a mess quickly and that we need to watch changes all the time, to avoid having BS in it.
I therefore think, we should restrict access to the wiki in reasonable ways. I imagine to use the wiki for two essential purposes: 1. Develop requirements / design docs for new components (new features) 2. User contributed comments about components Note that this does not mean to migrate our official docs into the wiki in any way. Accepted component / feature proposals will be migrated to corresponding component dirs and official docs will stay where they are. By now, our wiki can only be edited by users of the group zetacomponents-commiters, which is only the PMC so far. My suggestion is to keep this status per default and only allow other users to edit dedicated pages. As there are: - One page per component, where users can provide code snippets, share comments and so on. - One page where proposals (requirements / design) can be maintained. Note that a page in Confluence can have sub-pages, so that does not necessarily mean that only a single page for proposals will exist, but a dedicated name space. If we find more reasonable applications for the wiki, we can open up more areas. What do you think? Regards, Toby -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
