forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs dreams.xml book.xml index.xml
Date Fri, 26 Apr 2002 07:49:44 GMT
crossley    02/04/26 00:49:44

  Modified:    src/documentation/content/xdocs book.xml index.xml
  Added:       src/documentation/content/xdocs dreams.xml
  Log:
  Added new document for Dream List, by harvesting content from forrest-dev.
  
  Revision  Changes    Path
  1.4       +1 -0      xml-forrest/src/documentation/content/xdocs/book.xml
  
  Index: book.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/book.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- book.xml	23 Mar 2002 18:37:55 -0000	1.3
  +++ book.xml	26 Apr 2002 07:49:44 -0000	1.4
  @@ -10,6 +10,7 @@
       <menu-item label="Index" href="index.html"/>
       <menu-item label="License" href="license.html"/>
       <menu-item label="Who we are" href="who.html"/>
  +    <menu-item label="Dream list" href="dreams.html"/>
     </menu>
   
     <menu label="References">
  
  
  
  1.2       +1 -0      xml-forrest/src/documentation/content/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/index.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index.xml	23 Mar 2002 16:10:42 -0000	1.1
  +++ index.xml	26 Apr 2002 07:49:44 -0000	1.2
  @@ -11,6 +11,7 @@
       <s1 title="Introduction">
         <p>Forrest provides a sound technological infrastructure for open software
development for the Apache Software Foundation based on ASF software, ASF practices and experience,
and modern software design principles.</p>
         <p>The Forrest developers - <link href="mailto:forrest-dev@xml.apache.org">forrest-dev@xml.apache.org</link></p>
  +      <p>Please see the fledgling <link href="dreams.html">Dream List</link>.</p>
       </s1>
     </body>
   </document>
  
  
  
  1.1                  xml-forrest/src/documentation/content/xdocs/dreams.xml
  
  Index: dreams.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
  
  <document>
   <header>
    <title>Forrest dream list</title>
    <subtitle>Overview</subtitle>
    <authors>
     <person name="Stefano Mazzocchi" email="stefano@apache.org"/>
     <person name="Steven Noels" email="stevenn@apache.org"/>
     <person name="David Crossley" email="crossley@apache.org"/>
    </authors>
   </header>
  
   <body>
   <s1 title="Introduction">
  
    <p>This is the initial attempt to give focus to the Forrest project. 
     This summary is a loose collection of items from the forrest-dev
     mailing list. Please add and re-arrange so that it can evolve into a
     focus document.
    </p>
  
    <p>These are the email threads and documents that are currently being
     summarised. Please see those documents for further detail.
    </p>
  
    <ul>
     <li>
      [RT] my Forrest dream-list
      Date: Wed, 20 Feb 2002
      http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=101431895118349&amp;w=2
      [done]
     </li>
     <li>
      README 
      [FIXME: not yet started summarising]
     </li>
     <li>
      [phases] Forrest
      Date: Fri, 22 Feb 2002
      http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=101445744931104&amp;w=2
      [FIXME: not yet started summarising]
     </li>
     <li>
      adding to the dream list
      Date: Fri, 15 Mar 2002
      http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=101620970016263&amp;w=2
      [FIXME: not yet started summarising]
     </li>
     <li>
      analysis paralysis :-)
      Date: Mon, 25 Feb 2002
      http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=101465344708301&amp;w=2
      [FIXME: not yet started summarising]
     </li>
     <li>
      documentation architecture?
      Date: Thu, 25 Apr 2002
      http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=101973705501466&amp;w=2
      [FIXME: not yet started summarising]
     </li>
     <li>
      Topic Maps for Forrest ?
      Date: Mon, 18 Mar 2002
      http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=101647290524645&amp;w=2
      [FIXME: not yet started summarising]
     </li>
    </ul>
   </s1>
  
   <s1 title="Draft dream list">
  
   <ul>
    <li>
     Forrest provides a sound technological infrastructure for open software development for
the Apache Software Foundation based on ASF software, ASF practices and experience, and modern
software design principles.
    </li>
   <li>
    a publishing system for documentation
   </li>
   <li>
    a build system for code
   </li>
   <li>
    analysis of logs and publishing of results
   </li>
  
   <li>
  Ok, first of all: "it hurts my spirit" (I should TM this) to see the
  apache web sites with such a *poor* information infrastructure. Just
  look at sourceforge: it's not the best site of the world, but gives you
  lots of tools and information that we currently don't have (or have
  hidden someplace).
   </li>
  
   <li>
  I want Forrest to be the development infrastructure of your dreams,
  something that you'll be proud of showing your boss and say "if only we
  had this in place, we would save big bucks" so...
   </li>
  
   <li>
    Dream #1: Forrest should make Sourceforge look obsolete.
   </li>
  
   <li>
  So, in order for this to happen, it must be dynamic.
  Assumption #1: Forrest is a dynamic site.
  The staticity of apache web sites was mostly due to the quest for heavy
  mirroring, Forrest should allow mirroring, so
   </li>
  
   <li>
    Dream #2: Forrest should reduce xml.apache.org bandwidth use dramatically
   </li>
  
   <li>
    Dream #3: Forrest should automate mirroring in a simple and easy way.
  
  My idea is to use the 'command line' features of Cocoon to generate
  static snapshots of sites and produce mirrors directly using a sort of
  rsync or other mean. Anyway, the goal is to make sure mirroring is as
  easy as possible. No, easier than that.
   </li>
  
   <li>
    coherence: all the site should look coherent, same graphics, same
  look-and-feel, same information in the same locations, coherent and nice URI
  space (build to last! so that broken links are reduced!)
   </li>
  
   <li>
    structure: the site should look professional, the structure should be
  flexible enough to fit every need but solid enough to guide users
  browsing and developers adding resources
   </li>
  
   <li>
    scalability
   </li>
  
   <li>
    functionality: everything you ever wanted to have in your project web site
   </li>
  
   <li>
   logs and community rating: I want to have numbers to judge the value
  of a community/effort
   </li>
  
   <li>
  Downloads, number of commiters, numbers of people subscribed on the users/dev
  list, numbers of mail messages / week on these lists, CVS activity...
  These are the kind of parameters I use to "judge" an Apache project that I
  have not been looking into before.
   </li>
  
   <li>
    Graphs of various statistics.
   </li>
  
   <li>
   Built-in search engine: users much have a simple way to find things.
   Lucene.
   </li>
  
   <li>
   User-writable pages: people should have a way to add things to the pages.
   See the thread for more detail on this.
  FIXME: get MARC ref
   </li>
  
   <li>
   short bios for the project committers, with pictures: gives a better
  sense of community. Having a weblog there would be great.
   </li>
  
   <li>
   news, announcements, events and project calendaring: the news and
  the annoucements will generate a RSS feed, events will be aggregated
  into a project-wide calendar, or an effort-specific calendar, the events
  will also be overwritten on the logs, to indicate how logs were
  influenced by the events (say, a release or a new committer added)
   </li>
  
   <li>
   book-like PDF versions of documentation: easy to print out docs.
   </li>
  
   <li>
    integration with GUMP: dependencies, runs, committer that broke the run
   </li>
  
   <li>
   javadocs seemlessly integrated with the documentation and with the
  search engine.
   http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=101620970016263&amp;w=2
   </li>
   
   <li>
   mail archive seemlessly integrated with the search engine (one should
  look for something and get results from either docs, javadocs or emails
  messages)
   </li>
  
   <li>
    coherent-looking CVS view
   </li>
  
   <li>
    document translation using Google translation services
   </li>
  
   <li>
   Integrated project management, task management, bug tracking, feature requests, process
management. 
  The idea is to integrate Scarab for bug tracking/patches and
  managing/feature requests.
  (As far as team management, this is a serious political issue and I do not
  want to tackle that one yet, not even on the dreamlist.)
   </li>
  
   <li>
    overview doco for all projects ... CVS Usage precis, overview of opensource
    and links to relevant doco
   </li>
  
  </ul>
   </s1>
  
   </body>
  </document>
  
  
  

Mime
View raw message