On Tue, Mar 5, 2013 at 6:39 AM, Hasan Hasan <[email protected]> wrote:
> Hi Reto > > An excerpt of [2]: > > The infrastructure team currently supports two main mechanisms for > publishing and maintaining project sites: > - svnpubsub, which allows the static contents of a designated svn folder > (example) to automatically published as the project web site at > http://project.apache.org/. The project team can use any site build > mechanism it wants as long as the above requirements are met. > - Apache CMS, which provides a simple browser-based user interface for > editing, staging and publishing site content in Markdown, HTML or any other > source format for which support has been added. See the CMS reference and > adoption for more details. The Apache CMS uses svnpubsub as the underlying > mechanism for publishing a site. > > Some projects still use a deprecated site deployment system based on > periodic synchronization of static files from people.apache.org to the > live > web servers. This mechanism will be discontinued at the end of 2012, by > which time all projects should have migrated to one of the above site > publishing mechanisms. > > -- end of excerpt -- > > Thus, if we don't want to use svnpubsub, we have to use Apache CMS. Or am I > missing something here? > We can't use it for or clerezza based process as described here: http://svn.apache.org/viewvc/clerezza/site/trunk/readme.txt?view=markup Cheers, Reto On Tue, Mar 5, 2013 at 6:07 AM, Reto Bachmann-Gmür <[email protected]> wrote: > Hi Hasan > > I'm not sure about the project layout. But I don't think that a special > casing for the site is needed because we don't use svnpubsub. Also I see no > harm in adding the site as a normal project to the reactor. Especially now > when the reactor is no longer the released unit. > > Cheers, > Reto > > On Mon, Mar 4, 2013 at 11:29 PM, Hasan <[email protected]> wrote: > > > Dear all, > > > > To move from svn to git we should file a ticket on infra mentioning the > > following [1]: > > > > project unix name > > project layout > > portions of svn tree to leave writable (e.g. ASF CMS site sources) > > > > The project unix name would be clerezza. That's clear. > > But how about the project layout and portions of svn tree to leave > > writable? > > Regarding the portions of svn tree to leave writable, would it be > > clerezza/site ? > > > > Note that the infrastructure team currently supports two main mechanisms > > for publishing and maintaining project sites [2]: svnpubsub and Apache > CMS > > According to [1] Git is not supported by svnpubsub. > > > > So please help me with answering the questions above and other tasks for > > moving to git [3]. > > > > [1]: http://www.apache.org/dev/infra-contact#requesting-graduation > > [2]: http://www.apache.org/dev/project-site#intro > > [3]: https://git-wip-us.apache.org/docs/switching-to-git.html > > > > cheers > > hasan > > >
