Podling Report Reminder - April 2018
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 18 April 2018, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, April 04). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/April2018 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: [DISCUSS] podling report
Sounds good to me. (I'd remove the speaker names from the report; not necessary.) On Mon, Apr 2, 2018 at 7:24 AM, Nadav Har Tzviwrote: > Hey, > > I don't have confirmation for the SDP yet. It might be deferred to the next > SDP (December 2018 instead of June 2018). > > On 2 April 2018 at 13:45, Yaniv Rodenski wrote: > > > Hi All, > > > > We have two days for submitting this report, and I hope we will have some > > additions but for now, I suggest the following report: > > > > " > > Apache Amaterasu is a framework providing configuration management and > > deployment for Big Data Pipelines. > > > > It provides the following capabilities: > > > > Continuous integration tools to package pipelines and run tests. > > A repository to store those packaged applications: the applications > > repository. > > A repository to store the pipelines, and engine configuration (for > > instance, the location of the Spark master, etc.): per environment - the > > configuration repository. > > A dashboard to monitor the pipelines. > > A DSL and integration hooks allowing third parties to easily integrate. > > > > Amaterasu has been incubating since 2017-09. > > > > Three most important issues to address in the move towards graduation: > > > > 1. Prepare the first release > > 2. Grow up user and contributor communities > > 3. Prepare documentation > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > aware of? > > > > None > > > > How has the community developed since the last report? > > > > * Two conference talks are scheduled in the near future, Voxxed Days > > Melbourne (Yaniv Rodenski) and SDP in Tel-Aviv (Nadav Har-Tzvi) > > > > How has the project developed since the last report? > > > > * since the last report 12 PRs were opened and 11 are merged > > * One additional contributor started contributing to the code base > > * One organization we are aware of have started a POC with Amaterasu > > * We are in the process of automating the release process as > > preparation for the first release in the incubator. > > > > Date of last release: > > > > N/A > > > > When were the last committers or PMC members elected? > > > > N/A > > " > > > > If there are no objections I will update the wiki. > > > > Cheers, > > -- > > Yaniv Rodenski > > > > +61 477 778 405 > > ya...@shinto.io > > > > > > -- > = > Nadav Har Tzvi > Committer@Amaterasu >
Re: Project status
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éwrote: > Agree > > It makes sense. > > Regards > JB > > Le 31 mars 2018 à 02:46, à 02:46, Davor Bonaci 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 > >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 > >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 > >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
[DISCUSS] podling report
Hi All, We have two days for submitting this report, and I hope we will have some additions but for now, I suggest the following report: " Apache Amaterasu is a framework providing configuration management and deployment for Big Data Pipelines. It provides the following capabilities: Continuous integration tools to package pipelines and run tests. A repository to store those packaged applications: the applications repository. A repository to store the pipelines, and engine configuration (for instance, the location of the Spark master, etc.): per environment - the configuration repository. A dashboard to monitor the pipelines. A DSL and integration hooks allowing third parties to easily integrate. Amaterasu has been incubating since 2017-09. Three most important issues to address in the move towards graduation: 1. Prepare the first release 2. Grow up user and contributor communities 3. Prepare documentation Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? * Two conference talks are scheduled in the near future, Voxxed Days Melbourne (Yaniv Rodenski) and SDP in Tel-Aviv (Nadav Har-Tzvi) How has the project developed since the last report? * since the last report 12 PRs were opened and 11 are merged * One additional contributor started contributing to the code base * One organization we are aware of have started a POC with Amaterasu * We are in the process of automating the release process as preparation for the first release in the incubator. Date of last release: N/A When were the last committers or PMC members elected? N/A " If there are no objections I will update the wiki. Cheers, -- Yaniv Rodenski +61 477 778 405 ya...@shinto.io