History for Requirements

??changed:
-
  This is some content snipped from Jon's email and my comments, this 
  is not refined

  - Synthesize material from the zope lists, guides, howtos, as well
    as from interviews with key zopistas, into a series of
    topically-focused articles.

    MichelP -- So [Articles] will be a key artifact, as well as
    [Interviews] (which may just be a kind of Article).

  - Tag each article with metadata vocabularies (e.g. GeneralTopic:
    ZODB, Activity: backup_and_recovery). Aim to develop these
    vocabularies as general ones that the community would want to use
    to categorize other non-Gazette material.

    MichelP -- We have a general pattern we call [Topics], which we
    have realized in ZTopics (but never released) and I also believe
    is being used in the [PTK].

  - Within articles, develop named components (e.g., DtmlCodeFragment,
    DiscussionPoint, BestPracticesList) which can be reused in other
    contexts.

  MichelP I snipped some stuff here and put them under [Requirements].

  - Use RSS to broadcast the Gazette, possibly not just at the issue
    level (Issue #1) but at the more granular component level (e.g.:
    DiscussionPoint, ZopeTip).

  - Use a simple XHTML-oriented technique for writing, which could
    also enhance the quality and reusability of howtos without raising
    the bar too high for would-be contributors. (In other words,
    people write HTML howtos easily today. Few are likely to write
    DocBook XML howtos. XHTML howtos could be a useful middle ground.)

  - Instrument each article with discussion apparatus. ZDiscussions is
    preferable to ZWiki, and rather than one forum per article, it's
    best to have one forum per high-level topic (e.g. a ZODB forum,
    linked to from multiple articles about ZODB).

  - Aim for these ZDiscussions to become destinations which, over
    time, can supersede non-Zope-based mailing-lists as the locus of
    community discussion. (Is there anyone in the Zope community who
    thinks Zope is *not* the right tool for managing its own
    community's interactions?  Would moving in that direction rub
    people the wrong way? My own suspicion is that mailing lists are
    just a bad habit, but then, I do understand that you muck with
    people's habits at your peril. )

  - Post a draft of each article to a group of reviewers, incorporate
    feedback into the first release of the article, linked to from
    zope.org.