A bit of elaboration: The two primary uses of your password are (1) svn authentication (over https) and (2) ssh access to people.apache.org.
Some Apache projects build their websites with Confluence, some with the maven site plugin, some with Anakia, and some with all of the above. I recommend against completely dependence on the site plugin; it's fine to publish the reports it produces, but I find the release process implications of using it as the primary driver to be very painful. --benson On Mon, Sep 27, 2010 at 5:01 PM, Mark Struberg <[email protected]> wrote: > Hi Dan! > > See the new-committers FAQ [1] which should answere your questions (I hope > it's accurate). > > 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. > > > LieGrue, > strub > > [1] http://www.apache.org/dev/new-committers-guide.html > > --- On Mon, 9/27/10, Dan Haywood <[email protected]> wrote: > >> From: Dan Haywood <[email protected]> >> Subject: Re: Podling Setup (was: Hello?) >> To: [email protected] >> Date: Monday, September 27, 2010, 8:48 PM >> >> 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 [4] 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 [2] and >> [3], so I need >> > some help from NOF people to start working on that >> ASAP. >> Currently our project website is built using Maven . >> Looking at [3] 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. >> >> > >> > [1] - http://incubator.apache.org/guides/mentor.html#Set+Up+Repository >> > [2] - http://incubator.apache.org/guides/sites.html >> > [3] - http://incubator.apache.org/guides/mentor.html#create-website >> and >> [4] http://incubator.apache.org/projects/isis.html >> >> >> Thanks >> Dan >> >> > > > >
