I provided with a patch (AXIS2-4911) to update the axis.apache.org during the last Axis2 Hackathon. Following is a screen shot of the page design. https://issues.apache.org/jira/secure/attachment/12467409/screen.png
If no one disagrees, shall we please update the site in to this? I also submitted patches for [1] Axis2 Java site - http://axis.apache.org/axis2/java/core/ (AXIS2-4912) [2] Apache Rampart - http://axis.apache.org/axis2/java/rampart/ (RAMPART-313) [3] Apache Sandesha - http://axis.apache.org/axis2/java/sandesha/(SANDESHA2-206) thanks, Chanaka On Tue, Dec 28, 2010 at 3:30 PM, Andreas Veithen <[email protected]>wrote: > Yes, > http://axis.apache.org/axis2?/(java|c)/(core|rampart|sandesha|savan|transports) > are generated sites, while the rest (in particular the home page at > http://axis.apache.org) should eventually be published using some > other means. Glen added a static index.html to the root, but this is > not under version control; it only exists at > people.apache.org:/www/axis.apache.org. > > Andreas > > On Tue, Dec 28, 2010 at 05:25, Afkham Azeez <[email protected]> wrote: > > I think we should be able to modify at least certain pages independent of > > the latest release. For example, the home > > page http://axis.apache.org/ looks so dull & incomplete. Chanaka had > > prepared nicer looking pages with the projects logos and so on. We > certainly > > need to update that page at least. > > Thanks > > Azeez > > > > On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen < > [email protected]> > > wrote: > >> > >> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <[email protected]> wrote: > >> > So then updates to the site can only be done on a release boundary? > >> > >> The basic constraint is to maintain consistency between the published > >> site and the site sources. In practice this indeed means that the site > >> is only refreshed during a release. However: > >> > >> * One can do manual edits to the generated site, provided that the > >> site sources are also updated (so that the updates are not lost when > >> the site is regenerated). I did that with the Axis2 site in order to > >> fix a couple of broken links after the 1.5.3 release. Unfortunately > >> people tend to forget to update the site sources, leaving it to other > >> people to clean up the mess when doing a new release (see r1042149 and > >> r1042163). > >> * Technically, nothing would prevent us from republishing the site > >> from the trunk without doing a release. However, this means that the > >> site may contain information (e.g. in the Javadoc) that is not > >> applicable to any release. Also, I don't know any project at the ASF > >> that does this. > >> > >> > If true, that does not seem too flexible, does it? > >> > >> Maven sites are fine for some type of documentation (such as Javadoc, > >> reference documentation or information that doesn't change much), but > >> it is definitely not flexible enough for some type of content (e.g. > >> tutorials). Some time ago there was a discussion about this and the > >> consensus is that we need something else (which would be in addition > >> to the Maven sites, at least during a transition phase) that would > >> allow to publish content with a simpler procedure. At that time, > >> Confluence (with the auto-export plugin) was the only CMS available > >> and I like that system, although it's not perfect. However, the future > >> of this at the ASF is uncertain because the infra team would like to > >> get rid of it in favor of their own custom built solution. > >> > >> > Nadir Amra > >> > > >> > > >> > Andreas Veithen <[email protected]> wrote on 12/27/2010 > 11:04:50 > >> > AM: > >> > > >> >> From: Andreas Veithen <[email protected]> > >> >> To: [email protected] > >> >> Date: 12/27/2010 11:07 AM > >> >> Subject: Re: Axis Website update > >> >> > >> >> The changes for AXIS2-4912 were applied to the site sources in the > >> >> trunk. That was after I prepared the 1.5.4 release. The site > currently > >> >> online is the one generated from the 1.5.4 release and therefore > >> >> doesn't contain these changes. The normal way to get them published > is > >> >> with the next release. If that is 1.6, then the changes will be > >> >> included automatically. If the next release is 1.5.5, then the site > >> >> changes need to be merged to the 1.5 branch first (I did that for > >> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another > >> >> release from the 1.5 branch). > >> >> > >> >> Andreas > >> >> > >> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <[email protected]> > wrote: > >> >> > Chanaka had submitted a few site patches, and I think these have > been > >> >> > committed to the SVN. If so, why hasn't the site > >> >> > http://axis.apache.org > >> >> > still been updated? > >> >> > > >> >> > -- > >> >> > Afkham Azeez > >> >> > Senior Software Architect & Senior Manager; WSO2, > >> >> > Inc.; http://wso2.com, > >> >> > > >> >> > Member; Apache Software Foundation; http://www.apache.org/ > >> >> > email: [email protected] cell: +94 77 3320919 > >> >> > blog: http://blog.afkham.org > >> >> > twitter: http://twitter.com/afkham_azeez > >> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez > >> >> > > >> >> > Lean . Enterprise . Middleware > >> >> > > >> >> > > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: [email protected] > >> >> For additional commands, e-mail: [email protected] > >> >> > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > > > > > -- > > Afkham Azeez > > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > > > > Member; Apache Software Foundation; http://www.apache.org/ > > email: [email protected] cell: +94 77 3320919 > > blog: http://blog.afkham.org > > twitter: http://twitter.com/afkham_azeez > > linked-in: http://lk.linkedin.com/in/afkhamazeez > > > > Lean . Enterprise . Middleware > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
