Since the report is due today, I went ahead and updated the wiki https://wiki.apache.org/incubator/April2016. Let me know if anything needs to change while I can still change it :)
Thanks! On Wed, Apr 6, 2016 at 6:01 PM, Swapnil Bawaskar <sbawas...@pivotal.io> wrote: > I have incorporated these suggestions (in bold) > > How has the community developed since the last report? > - We have been able to address the “Three most important issues to move > towards graduation” from the previous report > 1. We had out first public release > 2. We Added 4 new committers, one of which is outside Pivotal > 3. We are about to have a second release, establishing a regular release > cadence > - We had a GeodeSummit http://geodesummit.com/ > - 22 sessions (including Keynote) > - Sessions included current use cases as well as integrations with other > Apache projects > - Over 100 attendees > - *Received project proposal after the summit.* > - The Geode Clubhouse hosted a meeting covering A walk through the > different approaches for caching data in a Spring based application with > Apache Geode by Luke Shannon > - The breakdown of JIRA tickets is the following: > Q3 / 2015 - 65 created, 19 resolved. > Q4 / 2015 - 342 created, 227 resolved. > Q1 / 2016 - 438 created, 362 resolved. > Q2 / 2016 - 8 created, 12 resolved (As of Apr 4th) > - There was a total of 123 pull requests on GitHub with 6 still open. > - The breakdown of the mailing lists messages for January, Feb, March of > 2016: > org.apache.geode.issues 4300 > org.apache.geode.commits 3731 > org.apache.geode.dev 2154 > org.apache.geode.user 294 > - There are now 153 subscribers on the dev and 145 on the user mailing > lists. > - Community events: > - January 2016: > - FOSDEM 2016 in Brussels: > - Taxi trip analysis (DEBS grand-challenge) with Apache Geode > (incubating) > - Big Data meets Fast Data: an scalable hybrid real-time transactional > and analytics solution > - February 2016: > - Seattle Java User’s Group (Talk about Introduction to Apache Geode) > > > > * - March 2016: - Geode Summit in Palo Alto, California - Geode > meetup in Palo Alto > (http://www.meetup.com/Pivotal-Open-Source-Hub/events/228983898/ > <http://www.meetup.com/Pivotal-Open-Source-Hub/events/228983898/>) - > Apache Apex (incubating) meetup featuring Geode integration > (http://www.meetup.com/Apex-Bay-Area-Chapter/events/228593080/ > <http://www.meetup.com/Apex-Bay-Area-Chapter/events/228593080/>)* > > How has the project developed since the last report? > - Had first release, close to the second release (with 134 out of 138 > issues resolved) > > > > > > > *- We elected a release manager for the first release and have rotated > that responsibility for the second release- Had a discussion about how to > number the releases- Voted on the Release candidates, rejected the first > but the second release candidate was voted as the final release- The > community discussed the criteria for becoming a committer and learned the > correct way of nominating new committers.- JIRA components were refined > after a discussion on the mailing list.- Consensus was achieved for the > scope for the releases on the mailing list.- Decision was made not to > rename the command line tool on the mailing list.* > - Each commit and pull request is run through CI using Travis CI > - Removed @author tags > - First release published to maven central > - Javadocs hosted on the project website. > > > On Wed, Apr 6, 2016 at 5:32 PM, Sai Boorlagadda <sai.boorlaga...@gmail.com > > wrote: > >> I think "Pluggable storage" is initiated after Geode Summit. >> >> On Wed, Apr 6, 2016 at 5:27 PM, Roman Shaposhnik <ro...@shaposhnik.org> >> wrote: >> >> > On Wed, Apr 6, 2016 at 5:22 PM, Swapnil Bawaskar <sbawas...@pivotal.io> >> > wrote: >> > > I found the following"Shepherd/Mentor notes" for our previous report >> > > <https://wiki.apache.org/incubator/January2016>: >> > > >> > > For the next report: for me as a mentor (and perhaps for others on >> > IPMC) >> > > it is not very insightful to see the number of pull requests or >> JIRAs >> > > opened. It isn't what "project development" constitutes in my >> mind. I >> > > would like to see more info about how project is getting into >> Apache >> > > Way, >> > > what important discussions are held, what decisions are made >> through >> > > community consensus, etc. >> > >> > That's a good point, but please don't read it as an excuse to drop that >> > first part of the valuable statistics. >> > >> > > Given the above, I was thinking about appending the following to the >> > report: >> > > >> > > - We elected a release manager for the first release and have rotated >> > that >> > > responsibility for the second release >> > > - Had a discussion about how to number the releases >> > > - Voted on the Release candidates, rejected the first but the second >> > > release candidate was voted as the final release >> > > - The community discussed the criteria for becoming a committer and >> > learned >> > > the correct way of nominating new committers. >> > > - JIRA components were refined after a discussion on the mailing list. >> > > - Consensus was achieved for the scope for the releases on the mailing >> > list. >> > > - Decision was made not to rename the command line tool on the mailing >> > list. >> > >> > The above looks very reasonable to me! >> > >> > Also, any insights from community development as a follow up to Geode >> > Summit >> > would be super useful to include in the report. >> > >> > Thanks, >> > Roman. >> > >> > >
