Patrick Hunt commented on ZOOKEEPER-80:

Ok, based on Jira comments and thread discussion I propose the following:

1) we'll add a new contrib directory as zookeeper/trunk/src/contrib/<module>

this directory will contain user contributions - such as recipes and the 
pending fuse module, ex:
zookeeper/trunk/src/contrib/zkfuse  (see ZOOKEEPER-25)

let's call these sub-dirs "contrib modules"

2) each module will contain readme/build.xml (or autoconf etc...)/ src, docs, 
lib, etc.... subdirectories.
if a module contains more than one lang implemention we would have src/c 
src/java etc...

3) recipes (any contrib module really) will have associated documentation in 
it's contrib/<module>/docs directory.  Note that Hadoop, and ZooKeeper, use 
Apache forrest for their documentation and for generating the ASF 
hadoop.apache.org web site.

4) recipes will have a single source hierarchy:

5) build.xml for recipes will generate a release jar file 
"zookeeper-recipes-<version>.jar", api docs, etc... which will be tar'd and 
included in the ZooKeeper release 

6) recipe users will be encouraged to use the released jar files in their 
client code (no checking out from svn as originally proposed)

7) contrib module issues will be tracked on the zookeeper jira

8) contrib modules are maintained on an "as is, best effort, work in progress" 
basis. The contents of these contrib modules are tagged, versioned, built, and 
released along with the ZooKeeper clients/server release.

Vote early vote often ;-)

> Document process for client recipe contributions
> ------------------------------------------------
>                 Key: ZOOKEEPER-80
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-80
>             Project: Zookeeper
>          Issue Type: Task
>          Components: documentation
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
> Per Doug's suggestion I'll use a link instead of copy/paste:
> http://mail-archives.apache.org/mod_mbox/hadoop-zookeeper-dev/200807.mbox/[EMAIL

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to