Hi Stephan, Hi Uwe,

Approach:

- Step 1. Separate wiki by community process levels.

- Step 2. Synchronization wiki (documentation) with Zope3 realeases.

Step 1. Separate wiki by process levels.

--------------------------------------------------------------------

In compliance with enterprise lifecycle process model emphasize:

  -- community (enterprise) level

  -- project level

  -- technology level


First sorting attempt. Current wiki tree:

http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/FrontPage/FrontPage/map

Same wiki (nothing deleted), but sorting by lifecycle processes.
(Note: underline logical parts, not underline real wiki headers)

Top-levels:

Community level
===============

  Reglaments (or environment management)
  ---------------------------------------
      Zope3DeveloperInfo

  Lifecycle process management
  ----------------------------
      WikiBadge

Project level
=============
  Project planning and control
  ----------------------------
      VisionStatement
      RoadMap
      SprintSchedule
     Information management
  ---------------------------
      #zope3-dev IRC channel
      NewPagesRSS   (not using from 2004)
      ZWiki
      Zope3Newsletter

Technology level
================
  Stakeholders (requirements definition)
  ---------------------------------------
      UseCases
     Architectural design (Zope3 developers documentation)
  -----------------------------------------------------
      ComponentArchitectureOverview
      Zope3Proposals
      Glossary
          EnglishGlossary (terminology and developer's professional slang)
          FrenchGlossary

  SubProjects developers documentation
  -------------------------------------

  Web developers documentation
  ----------------------------
      FAQ
      WindowsConfigurationDifferences
      Zope3Book
      Zope3Book.it
      InternationalDocumentation

  Implementation
  --------------

      zope3 releases
      ~~~~~~~~~~~~~~
          ZopeX3 seria
          Zope3 seria

      Add-on packages releases (subprojects)
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          AddOnPackages
          PyXML

Outdated and obsolete
=====================
  HistoricalDocuments (outdated)
  ReferenceDocumentation (obsolete)

Archive
=======
ZopeCVSWiki


Full tree here:

http://www.zope.org/Members/netlander/newWikiTree/document_view


Step 2. Synchronization documentation with Zope3 releases.

Badges:

-- outdated – related with previous Zope3 releases

-- current - related with current zope3 releases

-- future – related with next releases

Question:

----------------

Is this approach all right?

What do you think about using enterprise architecture model and enterprise lifecycle model for creation zope3.org?

P.S.

I repeat here all lists and images:
http://www.zope.org/Members/netlander/index.html

--
Regards,
Valeri Lazarev


_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to