The deadline for signing off is today, right? Sorry to take it to the last minute....
On Tue, Apr 12, 2016 at 5:29 PM, Henry Saputra <henry.sapu...@gmail.com> wrote: > No need to be curious too much, mea culpa from me for missing signing off > the report :) > > I had the impression I did sign off the report for Mnemonic, sincerely > apologize. > > - Henry > > On Tue, Apr 12, 2016 at 4:38 PM, Wang, Yanping <yanping.w...@intel.com> > wrote: > > > Hi, John > > > > I think our mentors are busy during the day. > > Patrick was on vacation last week. I'd suggest give them a few more hours > > to signoff the report. > > > > Thanks, > > Yanping > > > > -----Original Message----- > > From: John D. Ament [mailto:johndam...@apache.org] > > Sent: Tuesday, April 12, 2016 4:32 PM > > To: general@incubator.apache.org > > Subject: Re: Final draft of the Incubator Board Report - April 2016 > > > > I'm a bit curious about how we should handle Mnemonic. I've received no > > response thus far from the podling. I'd rather not kick them out of the > > monthly report. > > > > John > > > > On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey <mar...@rectangular.com > > > > wrote: > > > > > On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament <johndam...@apache.org> > > > wrote: > > > > > > > Below is the final draft of the board report. > > > > > > The report looks good to me! Comments inline. > > > > > > > - Airflow > > > > - Gearpump > > > > - Mnemonic > > > > - Omid > > > > - Tephra > > > > > > > > * Graduations > > > > > > > > The board has motions for the following: > > > > > > > > - Apex > > > > - Johnzon > > > > - TinkerPop > > > > - AsterixDB > > > > > > What turnover! I see that with the addition of Quickstep that's *six* > > new > > > podlings in one month, which has to be a record. > > > > > > Congrats to all the entrants and graduates! > > > > > > > * Credits > > > > > > > > - Report Manager: > > > > > > I added the credit for this month's erstwhile Report Manager. :) > > > > > > > * Did not report, expected next month > > > > > > > > - Concerted > > > > - OpenAz > > > > - Tephra > > > > > > The OpenAZ report was due in January and is thus 4 months late, which I > > > have > > > now noted on the wiki. OpenAZ's status has been raised on > > > private@incubator > > > and we just have to keep raising it each month until a report gets > filed. > > > > > > > -------------------- > > > > Fineract > > > > > > > > Fineract is an open source system for core banking as a platform. > > > > > > > > Fineract has been incubating since 2015-12-15. > > > > > > > > Three most important issues to address in the move towards > graduation: > > > > > > > > 1. Finalising the initial release > > > > 2. Improve the communication around the differences between the > > > previous > > > > MifosX project and the new Fineract project, especially in the > > > MifosX > > > > community, website etc. > > > > 3. With the first initial release, encourage the community to use > the > > > > proper infastructure (mailing lists, issue tracker) for the > > ongoing > > > > collaboration within the community. > > > > 4. Change management towards less 'key-man' dependency on previous > > > > tech/community leaders from MifosX, more towards community > driven > > > > consensus. > > > > 5. Reduce clutter on mailinglist from JIRA updates etc. > > > > > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > > > aware of? > > > > > > > > On the mailinglist there have been discussions around the lack of > > > traffic > > > > on it. This is part of the switchover from the current MifosX > > community > > > > and mailinglists towards the new Fineract lists. At the same time > the > > > > recent meet-up of Mifosx and Fineract devs and people interested in > > it > > > > (see community development), has also triggered a lot of offline > > > > interaction. > > > > > > > > How has the community developed since the last report? > > > > > > > > While activity on the mailinglist has been pretty low, we've had a > > > great > > > > meet-up in Amsterdam where a nice mix of existing MifosX community > > > members > > > > and a group of new interested people was present. This has boosted > > > > interest in Fineract. > > > > > > > > We have a high level of interest from new contributors throughout > > > Africa - > > > > we are working to properly engage them and guide them to the > correct > > > > collaboration channels in our Fineract community. > > > > > > > > How has the project developed since the last report? > > > > > > > > Individual members of the leading partner organizations building > > > solutions > > > > using the Fineract platform have begun to effectively use the > > Fineract > > > > issue tracker to communicate and track the requirements and > > > enhancements > > > > they're building and contributing to Fineract. These individuals > are > > > > setting a good example that other individuals from our partner > > > community > > > > should follow. > > > > > > > > Date of last release: > > > > > > > > N/A > > > > > > > > When were the last committers or PMC members elected? > > > > > > > > N/A > > > > > > > > Signed-off-by: > > > > > > > > [ ](fineract) Ross Gardler > > > > [ ](fineract) Greg Stein > > > > [X](fineract) Roman Shaposhnik > > > > > > This report provides excellent insight into the challenges and > > > opportunities > > > before the Fineract community. Thank you for a good read, and good > luck! > > > > > > > -------------------- > > > > FreeMarker > > > > > > > How has the project developed since the last report? > > > > > > > > FreeMarker had two public releases: A Release Candidate (so that > > users > > > can > > > > test it), and one final release. Apart from the new features and > > > fixes, we > > > > have adjusted the source code and build process to follow Apache > best > > > > practices more closely, and to be more appealing for contributors > > > > (switching to Java 5, fixing formatting where it didn't fit the > > modern > > > > Java conventions). > > > > > > Those sound like good ideas! There really are a lot of ways to make a > > > project > > > easier to contribute to, but they can be hard to see when you're in the > > > thick > > > of it. > > > > > > > -------------------- > > > > Gearpump > > > > > > > > Gearpump is a reactive real-time streaming engine based on the > > > micro-service > > > > Actor model. > > > > > > > > Gearpump has been incubating since 2016-03-08. > > > > > > > > Three most important issues to address in the move towards > graduation: > > > > > > > > 1. Make initial Apache branded release > > > > 2. Initial community process definition and practice enforcement by > > > > following Apache policies > > > > 3. Build the first Apache branded informative website to make > > Gearpump > > > > contributor and end-user friendly. > > > > > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > > > aware of? > > > > > > > > The rights holder of the Gearpump copyright filed a CCLA including > a > > > > Schedule B granting the Gearpump codebase to the Foundation. We are > > > > awaiting assistance from Infrastructure on INFRA-11435 to perform > the > > > > import. > > > > > > > > How has the community developed since the last report? > > > > > > > > All of the initial committers/PPMC have set up with Apache accounts > > and > > > > Apache JIRA accounts. > > > > > > > > Discussion among developers has started on > > > > d...@gearpump.incubator.apache.org > > > > > > > > How has the project developed since the last report? > > > > > > > > The JIRA for the podling is active at > > > > https://issues.apache.org/jira/browse/GEARPUMP and seeing > activity. > > > > > > > > Date of last release: > > > > > > > > No release yet. > > > > > > > > When were the last committers or PMC members elected? > > > > > > > > No new committers or PMC members elected yet. > > > > > > > > Signed-off-by: > > > > > > > > [X](gearpump) Andrew Purtell > > > > [ ](gearpump) Jarek Jarcec Cecho > > > > [ ](gearpump) Reynold Xin > > > > [ ](gearpump) Todd Lipcon > > > > [ ](gearpump) Xuefu Zhang > > > > > > This is a solid first report from Gearpump. It describes the progress > of > > > getting set up in the Incubator and establishes the routine of > reporting. > > > There may not be too much to say about community interaction at first, > > but > > > that's fine. > > > > > > > -------------------- > > > > iota > > > > > > > > Open source system that enables the orchestration of IoT devices. > > > > > > > > iota has been incubating since 2016-01-20. > > > > > > > > Three most important issues to address in the move towards > graduation: > > > > > > > > 1. Overcome current technical difficulties. You might be asking > what > > is > > > > happening with Apache iota. The initial architecture that we > > wanted > > > to > > > > upload was not as scalable as we required it to be. Rather than > > > upload > > > > an architecture that we wanted to fundamentally change we have > > been > > > > developing a new backend architecture and code based that > > > implements a > > > > significantly more scalable solution using Apache, Spark, Spark > > > > Streaming and Cassandra. We are still using Python and Django > for > > > our > > > > APIs and authentication (session and token based). Consequently, > > you > > > > haven’t seen any activity on the Apache iota site and > repository. > > > This > > > > will be changing soon. Litbit (the contributing company whose > > > business > > > > runs on iota) has been working around the clock to remake the > > > backend > > > > using additional Apache components that makes the solution far > > more > > > > scalable. > > > > 2. Set up web site and import code. We will be setting up the > Apache > > > iota > > > > website to reflect the new architecture and uploading the > initial > > > > source code as quickly as we can. > > > > 3. Promote Iota to a wider user base / grow the community. We are > > > planning > > > > to promoting iota at an upcoming keynote being given by Scott > > > Noteboom > > > > (Litbit's CEO). In addition we will be presenting iota at Apache > > > Con in > > > > May 2016. Our goal in promoting iota will be to start building a > > > > community that will contribute to moving iota to it’s first > > release > > > as > > > > an Apache incubator project > > > > > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > > > aware of? > > > > > > > > * None at this time. > > > > > > > > How has the community developed since the last report? > > > > > > > > * This is the first submitted report > > > > > > > > How has the project developed since the last report? > > > > > > > > * This is the first submitted report > > > > > > > > Date of last release: > > > > > > > > * None > > > > > > > > When were the last committers or PMC members elected? > > > > > > > > > > > > Signed-off-by: > > > > > > > > [ ](iota) Daniel Gruno > > > > [ ](iota) Sterling Hughes > > > > [X](iota) Justin Mclean > > > > [X](iota) Hadrian Zbarcea > > > > > > > > Shepherd/Mentor notes: > > > > > > > > johndament: > > > > Its a bit concerning to see that the project is starting off in a > > > > non-ASF way. Even if the code isn't quite right for donation, > may > > be > > > > better to start off writing new code in the ASF repos. > > > > > > > > jmclean: > > > > I too have concerns about why they are developing outside of the > > ASF. > > > > I've contacted them a few times with a please explain and have > > > > assurances that this will be fixed. I'd suggest placing the > podling > > > on > > > > monthly reports for a few more months. > > > > > > > > drew: > > > > 2 mentors active on the mailing list this month, but little > > activity > > > as > > > > the team has not moved development to ASF. Concur with keeping > > > podling > > > > on monthly reports. > > > > > > I'd just like to say that it can be quite challenging to do fundamental > > > architectural design work under ASF-style collaboration and governance. > > > What > > > we are asking of iota is not an easy task and I don't envy them. > > > > > > > -------------------- > > > > Quarks > > > > > > > How has the community developed since the last report? > > > > > > > > The Quarks community is keeping dev-related conversations on the > > > mailing > > > > list. Because of this, it's allowed for the participation of > > > independent > > > > contributors in mailing list discussions. Although our list of > > > independent > > > > contributors is small, Quarks is still very new as an Apache > project > > > and > > > > we aim to actively grow our list in the near future. > > > > > > Nice -- it's good that Quarks understands the direction to head in. > > > > > > > -------------------- > > > > Rya > > > > > > > How has the community developed since the last report? > > > > > > > > * We have a Rya "office hour" teleconference every other week. We > > had > > > > some technical difficulties with screen sharing, but we had a > > > working > > > > solution for the last meeting. Users and developers can ask > > > questions, > > > > receive answers, discuss ideas for future developments. The > > minutes > > > are > > > > sent to the dev@ list. > > > > * We have more PRs from non-committers which are integrated into > the > > > > repository. We expect some of these non-committers to continue > to > > > > submit PRs and become committers. > > > > * There were several ideas from Rya for Google Summer of Code, > and a > > > few > > > > students expressed interest; one of them submitted a proposal > > > > > > Another very nice community development section. Thanks, Rya! > > > > > > > -------------------- > > > > Sirona > > > > > > > > Monitoring Solution. > > > > > > > > Sirona has been incubating since 2013-10-15. > > > > > > > > Three most important issues to address in the move towards > graduation: > > > > > > > > 1. increase the community > > > > 2. do more releases > > > > 3. make the community more active > > > > > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > > > aware of? > > > > > > > > No > > > > > > > > How has the community developed since the last report? > > > > > > > > No change but some more user feedbacks. > > > > > > > > How has the project developed since the last report? > > > > > > > > Several fixes have been done and enhancements in instrumentation > > side. > > > > > > > > Date of last release: > > > > > > > > 2015-11-18 > > > > > > > > When were the last committers or PMC members elected? > > > > > > > > > > > > > > > > Signed-off-by: > > > > > > > > [X](sirona) Olivier Lamy > > > > [ ](sirona) Henri Gomez > > > > [ ](sirona) Jean-Baptiste Onofre > > > > [ ](sirona) Tammo van Lessen > > > > [ ](sirona) Mark Struberg > > > > [X](sirona) Romain Manni-Bucau > > > > > > The reports from Sirona could stand to be a little fuller. > > > > > > Also, the question about last committers / PMC members really ought to > be > > > filled in. The Board is very persistent about asking TLPs for that > > > information. > > > > > > Marvin Humphrey > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
