Good morning all Onami people, thanks a lot for taking participation to this new amazing adventure, we are finally ready to start! I am so glad that something we started just in the spare time, grew-up up as community and became a proper Apache project :)
Anyway, this is just the begin, and a lot of work needs to be done! For new ASF committers, please have a deep read first on the http://www.apache.org/foundation/how-it-works.html page and related links - it is really important to make sure everybody acts according to the same Bushido :) Please take in consideration that all existing site/contents/code... as a temporary PROPOSAL and not as definitive decision - decisions will be taken according to the Apache Way, submitting a vote and getting the required consensus. So, if you already have something to discuss, please open a proper separated thread on dev@ ML. * First, the mailing list: who still hasn't done, please subscribe to the ML, initial committers have to subscribe also to the private@ since they are PPMC members as well [email protected] [email protected] [email protected] [email protected] * the svn repository: svn co https://svn.apache.org/repos/asf/incubator/onami As you can see, there are different sections in our repo: artwork branches committers site tags trunk while there is no need to add any comment on branches, tags and trunk, there are few extra dir: - artwork: it should contain all graphics related to Onami, it contains ATM a logo *proposal* that a friend of mine kindly donated us, according to the Japanese mean of O-Nami - committers: useful resources for committers environment settings, such as mvn/svn/... - site: we are using SvnPubSub to publish the maven generated site, this dir is the target of generated pages * the site: http://onami.incubator.apache.org/ * JIRA: https://issues.apache.org/jira/browse/ONAMI * Jenkins: https://builds.apache.org/view/Onami/?auto_refresh=true * the components: while importing the existing donated codebase, I thought, taking inspiration from Apache-Commons patterns, the following components naming pattern: G-Guava -> onami-guava Guartz -> onami-scheduler GSPI -> onami-spi JUnice -> onami-test Lifegycle -> onami-lifecycle Rocoto -> onami-configuration sli4j -> onami-logging Gache -> onami-cache Autobind -> onami-autobind Again, that are _proposals_ and nothing is definitive, please discuss if you have a proposal otherwise we can go ahead via lazy consensus. I think that is enough to start! WDYT? All the best, have a nice day! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/
