Hey there I was extremely busy with my day-to-day work, but it seems like the clouds are clearing up again, I expect to have more time to work on our project in the upcoming weeks. My current task is the new Amaterasu CLI, which is already mostly implemented and I expect delivery somewhere in the next 2 weeks. I will need to coordinate with Yaniv on the CI efforts, as the e2e tests for the CLI require heavy lifting (as in having a test environment up with the Amaterasu runtime properly deployed)
Another task which goes along the new CLI is new documentation, also on my end. On 31 March 2018 at 08:32, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Agree > > It makes sense. > > Regards > JB > > Le 31 mars 2018 à 02:46, à 02:46, Davor Bonaci <da...@apache.org> a écrit: > >To close the loop on this... > > > >Without going too deep... just two individuals responding on this > >thread in > >10 days is way too little, given 5 PPMC members and 6 months in > >incubation. > > > >One thing worth clarifying -- to succeed as an Apache project, yes, a > >lot > >of change is needed. However, I'm *not* saying that there's anything > >wrong > >with the project. Just I'm not sure that the project and the foundation > >are > >the right fit at this moment. Nothing wrong with that -- there are > >many, > >many ways to succeed as a project. > > > >I continue to be enthusiastic about this space and continue to be happy > >to > >help, as appropriate. That said, I'll revive this thread in 1-2 months > >to > >check on the progress. If there's no evidence of progress, it may be > >best > >to rethink the path forward then. > > > >On Thu, Mar 29, 2018 at 12:42 AM, Eyal Ben-Ivri <eyalbeni...@gmail.com> > >wrote: > > > >> Hi to all, > >> > >> Sorry for not replying sooner, but I have been following the thread > >> closely. > >> > >> It is quite obvious we need to find more people that will be active > >in the > >> Amaterasu project. > >> Yaniv and myself are often communicating through private channels > >(and I > >> believe other developers are doing the same), and as an improvement, > >we > >> need to make Amaterasu related discussions through this mailing list. > >> A lot of the features and milestones discussions (some of them are > >> mentioned here like the Travis build) should be discussed here, and > >that is > >> something all of the active developers of the project should start to > >do, > >> in my opinion. > >> > >> Besides that, i agree with all the points raised here, and do think > >that > >> the main “beyond-the-code” goal should be growing the community > >around > >> Amaterasu. > >> > >> Thank you, > >> Eyal > >> > >> > >> > >> On 27. March 2018 at 07:12:04, Davor Bonaci (da...@apache.org) wrote: > >> > >> Anybody else? > >> > >> On Tue, Mar 20, 2018 at 5:06 PM, Yaniv Rodenski <ya...@shinto.io> > >wrote: > >> > >> > Thanks Davor, > >> > > >> > Points taken, we will learn and improve on those. > >> > > >> > Just one clearification, I was not blaming the mentor I myself was > >more > >> > focused on working with Guy on automating the build than following > >up. > >> > Rereading my own response I can see that was unclear. > >> > > >> > > >> > On Wed, 21 Mar 2018 at 11:02 am, Davor Bonaci <da...@apache.org> > >wrote: > >> > > >> > > 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. > >> > > > >> > -- > >> > Yaniv Rodenski > >> > > >> > +61 477 778 405 > >> > ya...@shinto.io > >> > > >> > -- ===================== Nadav Har Tzvi Committer@Amaterasu