Re: [ndoc-devel] Sharing custom tags

[<joh...@co...>]

This sounds like a good solution.
It would also help reduce duplicate functionality.
  ----- Original Message -----=20
  From: Donald Kackman=20
  To: ndo...@li...=20
  Sent: Friday, January 28, 2005 8:24 PM
  Subject: [ndoc-devel] Sharing custom tags


  Since a number of people are starting to implement their own tags via =
the extensibility mechanism, it would be nice if we could all share =
their implementations.

  =20

  For this reason I'd like to propose the following mechanism for =
facilitate the sharing user contributions:

  =20

  Submission

  Contribution would come in the form of an email to one of the admins =
or volunteers from among the active devs (or if there are more active =
contributors, they can become devs themselves). Much like a contribution =
to codeproject, the email should contain the submitter's full name, a =
short description of the tag or template, and a ZIP file containing the =
following:

    a.. An extensibility stylesheet(s) implementing the tag (including =
the submitter's license of choice)=20
    b.. A build-able example, including code, preferably within a VS.NET =
project=20
    c.. An NDoc project that documents the example assembly=20
    d.. An optional readme file that explains the history, usage and =
implementation of the tag=20
  =20

  Validation

  Whoever receives the submission would do a quick smoke test on the =
example project, ensuring that the submission works as advertised. If =
the submission works, it gets committed to CVS (see storage) and one of =
the admins is notified so the web site can be updated (see access). If =
not Whoever received the submission can work with the submitter to =
correct any problems.

  =20

  Storage

  We create a directory structure in CVS for storage of the ZIP files

  ndoc

              \contrib

                          \tags

                          \templates

  =20

  Access

  We'll add a new page to ndoc.sf.net that catalogs the available =
contributions and allows for download of the ZIP file. We can also =
distribute them with the installer and the nightly tar-ball.

  =20

  Let me know if this all sounds good or if there is anything I'm not =
thinking of.

  =20

  don