> > The report was made in a rush and a bit from memory as I am traveling.
In such cases, it is totally okay to miss the report and report the following month -- not a big deal. I'd much rather see a good report next month compared to an incorrect report with false data. But, also, the incubation report is not Yaniv's personal responsibility. What about everybody else in the PPMC? > Two new contributors have contributed code that have been merged. > This was from my memory, @Yariv Triffon <yar...@gmail.com> did start > committing (he is working on AMATERASU-54), but also, he helped me and > pushed to by branch during this iteration (@Yariv, correct me if I'm > wrong). It does seem that those changes did not make it at the end (or I > might have redone them manually) but I will remove him from the report. > SG. Also, for all metrics, I'd love to see both absolute numbers and relevant difference from the previous report. For example: *During the past 3 months, there were X pull requests/commits/contributors/dev@ threads/issues opened/resolved, inclusive of X from first-time contributors. This compares to X and X in the previous reporting period, respectively.* > > In addition, we are actively looking for more use cases and organizations > > to use Amaterasu. > This is done by having direct discussions with different organizations, in > fact, most of my efforts in the last months have been around trying to find > use cases for Amaterasu, and I have been spending a lot of time approaching > organizations (with some help from @Kirupagaran Devarajan > <kirupagara...@gmail.com> and @ey...@apache.org <ey...@apache.org>). > > I think this is key to the success of the project no less than the number > of commits, but it takes time, especially for a small project. > So, how many '*yes*'/'*no*'/'*in progress*' are there? What did you learn from every 'no'? Is there any analysis or discussion what can be done to improve things based on that feedback? > if you and the other mentors think we should retire we can discuss that Aside: telling somebody to give up on something should carry extreme responsibility. Whoever tells somebody else to give up should better be extremely confident and understand many of the implications, both personal and professional. Many people easily advise others to give up because they aren't capable of it themselves -- be careful to find your path. But, there are also those who understand what they are saying and why, and you should take them seriously. You are welcome to put me in either bucket; that is up to you. I tried to be clear previously that retirement != failure. Simply put, not all communities are best fitted for the ASF. Joining ASF gives you rights and responsibilities. For some communities, they receive more than they give. For others, it is the other way around and it simply is not the right fit. I am very confident to say Amaterasu is not the right fit, at least for the foreseeable future. You'd be better off as a standalone project on GitHub, or potentially part of Apache Labs [1]. In either case, you wouldn't need to worry about reporting, releasing, growing committers -- all of which is now lacking -- and could focus on what you really need: iterating in understanding and solving user pain. I wanted to know if maybe there are things you and the rest of the mentors > think you can do to help us pass this rough patch and get the project to > the next level > I commented on this many times over: the value proposition is not resonating with users, you need to focus on understanding user pain better and solving it. Incubation mentors cannot do this for you. Davor [1] http://labs.apache.org/
