Hello Madhan, This reasoning makes sense. But it is worrying that no new committers are becoming long term contributors to the project. May be there would be more motivation for new committers to continue contributions if there was a definition of what makes a "deserving committer". I am sure it is different in many cases, but just some examples might help? For example, sustained contributions over x months etc. Building up the number of experienced active committers that are progressing to be PMC members would help spread the load of mentoring new contributors and committers as the community grows. This in turn could help accelerate the growth of the community.
All the best Mandy ___________________________________________ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: [email protected] LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - [email protected] From: Madhan Neethiraj <[email protected]> To: "[email protected]" <[email protected]> Date: 14/03/2019 08:18 Subject: Re: [DRAFT] Board report for Apache Atlas: March 2019 Mandy, Consistent contribution over period of time is the key criteria to become a committer and then PMC. As you noted, Atlas PMC has been moving contributors to committers based on their sustained involvement and contributions in the project. While new folks continue to join the community and make awesome contributions, there has been reduced engagement from recent committers; hence no recent additions to PMC. Atlas PMC will continue to look for contributions and engagements, and will offer PMC role to deserving committers. Thanks, Madhan On 3/13/19, 11:58 PM, "Mandy Chessell" <[email protected]> wrote: Dear All, Looking at the reports month by month, the code activity and the growth in the number of contributors/committers is looking very healthy. We can see contributors moving to committer status. However it does look strange that no new committer has been promoted to the PMC for nearly 2 years. The board may see that as a possible problem in the operation of the community? Perhaps it would be helpful to send out some hints to the community on what a committer has to do to be considered for the PMC? All the best Mandy ___________________________________________ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: [email protected] LinkedIn: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_pub_mandy-2Dchessell_22_897_a49&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=DEupm0k8-ppAmw6rImSmuE_tc4KzDG1cSUr7Fo_5T8Q&m=eM0zeUMK6bFkqsyYHusC0ngwXvc8Hq-20ilHH3qg0qo&s=LnLxL1nchbM5UsTaoA4ZbA77oKCZ9N3w79llRs4ATns&e= Assistant: Janet Brooks - [email protected] From: Nixon Rodrigues <[email protected]> To: [email protected] Date: 14/03/2019 05:17 Subject: Re: [DRAFT] Board report for Apache Atlas: March 2019 Madhan thanks for draft, It looks good. Slight correction in needed in 2.0.0 release date. >> 2.0.0 plan to release by 12/31/2018 Nixon On Thu, Mar 14, 2019 at 6:50 AM Madhan Neethiraj <[email protected]> wrote: > Atlas team, > > > > Please review the draft board report below and send your feedback/comments. > > > > Thanks, > > Madhan > > > > > > ## Description: > > Apache Atlas is a scalable and extensible set of core foundational > > governance services that enables enterprises to effectively and > efficiently > > meet their compliance requirements within Hadoop and allows integration > with > > the complete enterprise data ecosystem > > > > ## Issues: > > There are no issues requiring board attention at this time. > > > > ## Activity: > > - significant updates to lineage UI - faster rendering, searchability, > option to hide entities, highlight selected entity path, .. > > - added option to ignore/prune metadata for temporary/staging Hive tables > > - support for custom icons per entity-type > > - significant performance improvements during create/update of entities > > - added support for notifications on relationship changes > > - model updates to remove use of ownedRef/inverseRef constraints > > - enhancements to enable Atlas to be a reference implementation for > Egeria > - working on 2.0.0 release, to support Hadoop 3, HBase 2, Solr 7, Kafka > 2, Hive 3 > > > > ## Health report: > > - 5 new contributors added in last 3 months: Aadarsh, Binit, Le Ma, > Sridhar K, Sridhar S > > > > ## PMC changes: > > - Currently 33 PMC members > > - No new PMC members added in last 3 months > > - Last PMC member addition was on 6/21/2017 > > > > ## Committer base changes: > > - Currently 38 committers > > - No new committers added in last 3 months > > - Last addition to committer role was on 10/15/2018 > > > > ## Releases: > > 2.0.0 plan to release by 12/31/2018 > > 0.8.3 was released on 10/31/2018 > > 1.1.0 was released on 09/17/2018 > > 1.0.0 was released on 06/02/2018 > > 0.8.2 was released on 02/05/2018 > > 1.0.0-alpha was released on 01/25/2018 > > 0.8.1 was released on 08/29/2017 > > 0.8-incubating was released on 03/16/2017 > > 0.7.1-incubating was released on 01/26/2017 > > 0.7-incubating was released on 07/09/2016 > > 0.6-incubating was released on 12/31/2015 > > 0.5-incubating was released on 07/11/2015 > > > > Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
