On Fri, August 4, 2006 6:19 pm, Peter Haumer said: <snip> > In the same call we define a process on how to use the Wiki with the > public,
Is the goal of the Wiki just to be able to gather input from the public from a single source (e.g. we have a Wiki set up on the web which anyone can post to) or is it something that we can publish to (e.g. instead of generating straight HTML pages, we generate Wiki pages). If the latter, it seems to me that we need to be able to support a range of Wikis. > how to harvest feedback, assign responsibilities (e.g. discipline > owners harvest from their disciplines), when and how generate Bugzilla's, > when to upload new versions of OpenUP to the Wiki, etc. Shouldn't the Wiki just link to the current download page to keep it easy? > We write up an introduction page for the public wiki experiment explaining > the scope and communicating the usage model to be posted in the Wiki as > well as EPF homepage. Make sense. > We clean-up the Wiki, upload the latest OpenUP version, and announce the > Wiki experiment to the public The Wiki needs to be as easy to use as possible. If we're only using it to gather feedback, how is this any better than a mailing list? - Scott Practice Leader Agile Development, IBM Rational http://www.ambysoft.com/scottAmbler.html Refactoring Databases ( http://www.ambysoft.com/books/refactoringDatabases.html ) is now available. _______________________________________________ epf-dev mailing list epf-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/epf-dev
