Hi, I've silently followed the discussion in this thread and I'd like to comment on the structure.
On Friday, February 18, 2011 1:37 PM [GMT+1=CET], Paolo Castagna <[email protected]> wrote (with possible deletions): >> Does a consolidated suggestion like this work? >> >> +-- About >> +-- Download >> [Includes Maven] >> +-- Getting started >> [Small number of short guides.] >> +-- Tutorials >> [Would include topic tutorial (such as the existing RDF & >> SPARQL ones) as well as cross-cutting tutorials (such as >> Ian's working with Jena under Eclipse)] >> [I would also put the critical HOW TOs here (IO, Frames, >> Assembler) but they could be in a section under the detailed >> documentation] >> +-- Documentation >> +-- javadoc >> +-- RDF >> +-- Query >> +-- TDB >> +-- SDB >> +-- Serving data (Fuseki) >> +-- Ontology >> +-- Inference >> +-- tools >> +-- extras >> +-- Community >> [Should include roadmap, guidance on patch submission, links >> to trackers etc.] Putting Roadmap below Community is counterintuitive, at best. To most of us it seems clear what a roadmap is about - functions that have been identified and are planned to be implemented in the future. However, in this case some may think "Is this a roadmap about the community?" - certainly not. In my opinion, a roadmap is of top-level interest (provided that it exists). Actually, I often see myself searching for a roadmap when visiting Web sites of projects that I use regularly (and often it does not exist). A good example in this regard is SVN [1]. Regards, Thorsten [1] http://subversion.apache.org >> +-- News
