I also vote for b) I like the idea of being able to manage the project website together with the source code. For topics that don't follow the software release cycle we anyways have the wiki.
2012/12/11 Sergio Fernández <[email protected]> > Hi, > > one of the initial thing we'd need to setup is a proper website for the > project under the new normative domain under incubator [1]. Before Infra > team would be able to solve INFRA-5664 issue, they are awaiting for a > decision from us. > > Basically we have two options [3]: > > a) CMS-based site [4] > b) svnpubsub-based site [5] > > On the one hand, CMS looks great for maintenance using the bookmarklet, > allowing a more flexible structure far from how code is organized. On the > other hand, besides some bugs I'm pretty sure we can solve, svnpubsub allow > us to use maven site, keeping in that way synchronized public website with > the actual development status. > > So, by vote goes for 'b'. > > Cheers, > > [1] > http://marmotta.incubator.**apache.org<http://marmotta.incubator.apache.org> > [2] > http://issues.apache.org/jira/**browse/INFRA-5624<http://issues.apache.org/jira/browse/INFRA-5624> > [3] > http://www.apache.org/dev/**infra-contact#what-we-need-to-**know<http://www.apache.org/dev/infra-contact#what-we-need-to-know> > [4] http://www.apache.org/dev/cms > [5] > http://www.apache.org/dev/**project-site#intro<http://www.apache.org/dev/project-site#intro> > -- > Sergio Fernández >
