Thanks Henry. Nope we don't need bylaws or a CoC, but I believe they could help attract contributors. We learnt on CouchDB that if you don't have bylaws, nobody really knows how the project works, or what the rolls are, and I think that holds back contribution.
We could copy the CouchDB bylaws, change a few references to MetaModel, and then vote them in. Assuming that the way we do things on CouchDB is compatible with how this community wants to operate. Similarly, I think establishing even a minimal CoC which will be enforced by the PMC opens up this project to contributions from people who might not contribute otherwise. Certainly not graduation blockers. But I consider these to be very important for all ASF projects. On 21 September 2014 00:19, Henry Saputra <[email protected]> wrote: > Thx for input Noah. > > We have twitter account already and had been tweeting news about MM. > Kasper also have blogged about new features in MM. > I think this is why we got some new contributors lately. > > As for website, yes we need to update with ways to contribute evangelize it > more. > > For by laws and conducts, seemed like the last input from IPMCs we don't > need for now. > It could slow down contributions if we don't get it right and many projects > didn't get it right. > > - HS > > On Saturday, September 20, 2014, Noah Slater <[email protected]> wrote: > >> Thanks for the update. >> >> Have you thought about setting up a project blog and tweeting out >> progress, news, things going on in wider ecosystem? Each blog post is >> an opportunity to tweet and to share the link on Reddit, Hacker News, >> and so on. >> >> Same thing with releases. What's the current release cadence like? >> Making regular (even if small) releases serves as a sort of heart beat >> for the project, and can be very useful for drumming up interest. >> >> Basically, we should be looking for opportunities to get the word out >> about the project. >> >> Some comments on the website: >> >> We don't mention "contribution" anywhere. While the website is >> obviously intended for downstream users, we should also be thinking of >> it as an job advertisement. We are looking to recruit people to the >> project. What can we do to make this happen? >> >> cf. http://couchdb.apache.org/#contribute >> >> I'd also suggest we think about establishing some bylaws and a code of >> conduct. >> >> cf. http://couchdb.apache.org/bylaws.html >> cf. http://couchdb.apache.org/conduct.html >> >> Both documents help to make the project more welcoming. >> >> -- >> Noah Slater >> https://twitter.com/nslater >> -- Noah Slater https://twitter.com/nslater
