|Mohammad Nour El-Din||Sep 21, 2010 7:09 am|
|Mohammad Nour El-Din||Sep 21, 2010 7:37 am|
|Mark Struberg||Sep 21, 2010 10:14 am|
|Mohammad Nour El-Din||Sep 22, 2010 2:01 am|
|Mohammad Nour El-Din||Sep 27, 2010 3:25 am|
|Mohammad Nour El-Din||Sep 27, 2010 3:53 am|
|Dan Haywood||Sep 27, 2010 1:48 pm|
|Mark Struberg||Sep 27, 2010 2:01 pm|
|Benson Margulies||Sep 27, 2010 2:09 pm|
|Dan Haywood||Sep 27, 2010 2:35 pm|
|Benson Margulies||Sep 27, 2010 2:37 pm|
|Mark Struberg||Sep 27, 2010 11:18 pm|
|Kevin Meyer||Sep 27, 2010 11:23 pm|
|Dan Haywood||Sep 28, 2010 12:22 am|
|Subject:||Re: Podling Setup (was: Hello?)|
|From:||Mark Struberg (stru...@yahoo.de)|
|Date:||Sep 27, 2010 2:01:30 pm|
See the new-committers FAQ  which should answere your questions (I hope it's
For the website: usually the version gets added to the base-URL, so for
different version we won't override old pages. In OWB, we did just setup a
redirect to the latest version.
regarding Wiki: we can request a CWIKI area for Isis.
--- On Mon, 9/27/10, Dan Haywood <dkha...@gmail.com> wrote:
On 27/09/2010 11:25, Mohammad Nour El-Din wrote:
Now most of the accounts are
created and we should go forward: I see from  that my login would appear to be 'danhaywood', but where do I login, and what would my password be? Will I receive some sort of password by email?
3- Project Website: 3.1 We need to follow the steps explained in  and , so I need some help from NOF people to start working on that
ASAP. Currently our project website is built using Maven . Looking at  it seems that this is an accepted approach. But (speaking with Rob) we're not sure what this means in practice. Our guess is: a) mvn site-deploy into some high-up directory in our SVN tree, then b) svn add all the files generated.
But how does this work for subsequent releases? Do we do the same and an svn add of everything new? How are we meant to identify files that are removed (eg, for generated javadocs for classes that have moved package)?
4- Project Wiki: 4.1 We should start discussing how documentations are going to be done on Wiki - maybe from the site itself.
A wiki is definitely required to capture input from the community.
That said, my view was to keep the wiki as small as possible, with the committers working to move any valuable content from the wiki and into the formal documentation. Each main module will have its own DocBook XML file (src/docbkx/guide) and this will be the main place for documentation to end up.
I've also suggested that each module has a simple src/site/apt/jottings.apt as a place to jot down any documentation that should be added to the DocBook.
6- Project Apache like Logo: 6.1- For this one I will have my brother make you some, he is a graphics/web designer.
That'd be a good start, thanks.