Hi List, While checking, sorting and refactoring stuff for the new building guide, I also ventured into our CVS/SCM/CWS docs. I merged/renamed some stuff, created redirects and tagged some stuff with categories (mostly development, SVN, SCM, CWS).
However, there are quite some stuff that is really mixed up, for example infos about SCM-tooling, EIS-tooling and basic QA-workflow are distributed and mixed all over these pages (and some more): http://wiki.services.openoffice.org/wiki/CWS http://wiki.services.openoffice.org/wiki/ChildWorkSpace http://wiki.services.openoffice.org/wiki/EIS I think it would make sense to clearly separate: * cws, the command line tool * cws workflow for developers (including how to use EIS) ^- this one should be "further reading" in the "Building Guide" * cws workflow for QAs (inlcuding how to use EIS) (and getting rid of outdated/wrong stuff by the way) Also we need to clean up category:CWS: http://wiki.services.openoffice.org/wiki/Category:CWS Currently, it contains: * SCM tools usage (ok) * QA Policies (ok) * various QA stuff (Gatekeeper, RedTinderboxStatusInEIS) (meh) * QA Status Pages of some cws's (huh?) Im proposing to get rid of the CWS QA states at least (or move them to a new Category:CWSQAStatus). I think these pages (which _should_ be the first thing a contributor reads after having his build enviroment set) should be worth the effort. Comments? Have Fun, Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
