On Thu, Dec 7, 2017 at 11:09 AM, Julian Hyde <[email protected]> wrote:
> Thanks for responding, everyone. > > There’s one really important point I’d like to make about incubation (and > Apache in general) that many people find counter-intuitive. There are 3 > basic things to work on: (a) the code, (b) the incubation tasks (e.g. > trademark search), and (c) the community. > > By far the most important thing is the community. Apache folks often cite > the mantra “community over code”; this means that if you build a healthy > community, the code will look after itself. > > Consider one of the most important “tasks” of incubation, namely producing > releases. The contributors often focus on the code, giving themselves a > very high bar in terms of the number of features to implement and bugs to > fix before producing a release. But it’s much better to just get a release > out there, warts and all. The process of producing the release (testing it, > writing the doc, promoting it) pulls the community together. People will > discover those “warts”, contribute fixes, and you will have your first new > committers. > > The first incubator release always takes WAY longer than you expect, and > not for the reason you expect. It takes a lot of effort to assemble the > release into an acceptable format, checking the licenses of dependencies, > including the necessary LICENSE and NOTICE files, and so forth. I recommend > that you start work on the first release very soon, and resist the > temptation to put lots of features into it. > > If you want to build community (i.e. attract people who don’t work for IBM > or live in Zurich) promotion is essential. An active twitter account, blog > posts, and talks at conferences or meet ups where your potential users are > in attendance. (For example, DataWorks Summit Berlin[1] is in April and CFP > ends in one week. A lot of attendees would be interested in Crail, even at > this early stage.) > > As for tasks, they are listed on the status page [2]. We can burn them > down and update the page over the next couple of months. > > Very well said Julian, +1 I would just reinforce that, on the context of Apache, we are all contributors volunteering to work on the Crail project and you should try to use your "apache hat" much more often then your "employee hat" and really get the word out to create a community around the Crail project which will make it sucessfull. Thanks -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
