Hi John perfect, I was also thinking on bringing that up. I prefer the Wiki way. As you said easier to contribute. This Thursday we have Hackergarten and about 3-4 people are in Zurich and some more in parallel in Basel, so we can just prepare things online then, given we have access to it... >From the initial committers list I would say the following person will probably work on it:
- Anatole Tresch - Andres Almiray - Marco Zurmühle I assume there is somekind of project template, where we can start with, that would be perfect ;) Best, Anatole 2014-11-25 3:04 GMT+01:00 John D. Ament <[email protected]>: > All, > > I'd like to bring up the topic of a website for Tamaya. I'm not sure > if there's an existing source for it, but I did notice that there's > already a lot of asciidoc in the source code, which I'm sure could be > used for a website. > > So, how do we want to build and manage a website for the project? > > Many new projects are managing their sites via their regular source > code, which allows for easier contribution. For java projects, we can > use maven to publish those files to the Apache CMS for staging then > release to production sites. > > You can read more about the Apache CMS at [1]. > > Another way to manage it is as a wiki. This is easier to manage, > doesn't require code changes to publish, but allows for broader > contribution. > > We can also manage HTML directly in CMS. You commit to it using > subversion. > > Once we figure out how to build the website, let's maybe put something > together and have the site be requested. > > John > > [1]: http://www.apache.org/dev/cms.html > -- *Anatole Tresch* Java Engineer & Architect, JSR Spec Lead Glärnischweg 10 CH - 8620 Wetzikon *Switzerland, Europe Zurich, GMT+1* *Twitter: @atsticks* *Blogs: **http://javaremarkables.blogspot.ch/ <http://javaremarkables.blogspot.ch/>* *Google: atsticksMobile +41-76 344 62 79*
