Hi Marco, 2011/4/7 Marco Zaugg <[email protected]>
> > On 07.04.2011, at 07:07, Reto Bachmann-Gmuer wrote: > > Hi Marco, > > Even when you're not a developer you're free to proposes patches to the > website publication process as well as to the website content itself. It is > requirement on a process however that all content is stored in svn, so > simple SFTP isn't an option. > > That already is a NOGO for a non-techie. Storing data in svn, fine. But a > non-techie does not > work with such tools. Actually even SFTP would already be challenging. > That's why wikis and > other CMS should be used in the mid-term. > I think that a Wiki is not an alternative to our website; in my opinion the website should contain project overview, team, how to contribute, 5 minutes tutorials and so on (and I like ours at this stage), then the wiki would contain more detailed information regarding some components, use cases, and so on, also it'd allow non techies to contribute documentation more easily that PMC could eventually find worth bringing into the website. As I can see from the Incubator website [1] we're meant to have a wiki at https://cwiki.apache.org/CLEREZZA/ but it seems it's not there yet (I think we didn't request it). > > > Also keep in mind that documentation should mainly be available in the > documentation both published on the website as well as being available > online on a clerezza instance. So the process should take this into > account. > > Agree with that, I think I'm not writing technical documentation, but > rather the > content around that, be it use cases, solutions that already use Clerezza, > acknowledgments, > non-tech summaries etc. I personally doubt that this type of information is > needed > in a Clerezza instance. > Clerezza provides a /documentation service so it'd be good to let people see how it works, I think that is the main concern about this point so if there isn't a perfect sync I wouldn't see any issue. Regards, Tommaso [1] : http://incubator.apache.org/projects/clerezza.html
