Thanks for a great response. Some comments inline. * In the last month we have been working on automating the release process > via Travis, we are still trying to enable Travis build for the Amaterasu > repo, which is taking ridiculously long. We need one of the mentors to just > enable it via their account (I've already talked a couple of times to one > of the mentors about it). >
Searching for 'travis' in the mailing list archives doesn't yield any discussion threads. Mentors don't have permission to do this themselves. Infra JIRA is the way to do it, but I couldn't find such JIRA ticket filed. Emailing one mentor directly (or any other community member) isn't a way to build the community. Things need to be discussed in public whenever possible. Given the above, blaming a mentor (whomever you may be referring to) doesn't make sense. * We are ready to release version 0.2.0-incubating, the reason it took us a > month to initiate the process is the above automated build, which I > suggested in prior discussion and had no rejections. We will complete this > once build is enabled. > The release itself is a great milestone, but not the purpose to itself. > * as for community growth, we are working with two organizations on running > POCs (which will hopefully grow the user base) one of them is due to start > very soon. I don't want to name them (first of all it's too early, and also > it is for them to decide if they want to share) but a representative from > at least one of those organisations is on the list and is welcomed to share > :) > Great! > * This year I've seen contributions from 4 contributors (not much more than > 3, I know) but one of them is new (Guy Peleg) and AFAIK additional > longer-term work is done by one more contributor on his local fork (Nadav > Har-Tzvi) > I think this is the crux of the problem. Why is longer-term work going on in a local fork? > * We should be presenting more, and growing the community more which is > hard to do starting out as a tiny community. Any advice given there would > be appreciated. > The first thing has to be do the basics well: on-list communication, open discussions, no side channels, etc.
