| --- |
| date: 2015-01 |
| fledgling: |
| - samoa |
| - Corinthia |
| - Kylin |
| - NiFi |
| - taverna |
| - zepplin |
| growth-issues: |
| - Aurora |
| - Brooklyn |
| - Calcite |
| - MRQL |
| - odftoolkit |
| - parquet |
| - ranger |
| - usergrid |
| infrastructure: |
| ip-clearance: |
| - "Corinthia initial source grant" |
| ipmc: |
| entering: |
| - hyunsik |
| leaving: |
| - srowen |
| - marvin |
| legal-trademarks: |
| miscellaneous: |
| - | |
| NPanday community seems to be in agreement that retirement is the best |
| option at this point. The only outstanding issue before formally |
| recommending graduation VOTE is to decide whether there's enough cycles |
| available for one last release before retirement. |
| no-release: |
| - DataFu |
| - HTrace |
| - Ignite |
| - Kalumet |
| - Lens |
| - tamaya |
| no-report: |
| - NPanday |
| - ripple |
| podlings: |
| count: 36 |
| graduating: |
| - samza |
| new: |
| - Corinthia |
| - zeppelin |
| releases: |
| Brooklyn: |
| - |
| date: 2014-12-22 |
| release: 0.7.0-M2-incubating |
| falcon: |
| - |
| date: 2014-12-05 |
| release: 0.6-incubating |
| samza: |
| - |
| date: 2014-12-08 |
| release: 0.8.0-incubating |
| reports: |
| Aurora: |
| board-issues: |
| community-development: | |
| Latest Additions: |
| |
| * PMC addition: |
| * David McLaughlin, 2014-08-20 |
| * Contributor additions: No additional contributors had code committed |
| since the last report, however three new contributors currently have |
| code under review that was submitted within the past 6 weeks. At least |
| one of these contributions is a large feature addition, which is |
| promising. |
| |
| Issue backlog status since last report (Oct 1, 2014): |
| |
| * Created: 212 |
| * Resolved: 177 |
| |
| Mailing list activity since last report: |
| |
| * @dev 480 messages |
| * @issues 1085 messages |
| * @reviews 2235 messages |
| graduation-issues: |
| - "Expanding the community's diversity and adding new committers" |
| - "Third Apache release, progress being tracked in ticket AURORA-872" |
| project-development: | |
| * Increased participation from new contributors within the Aurora core and |
| ecosystem, for example a Chef cookbook and Docker support under |
| development. |
| * Continued to hold weekly IRC meetings, digests sent to dev@ list |
| * Large improvements to project documentation and website. |
| committers: |
| count: 14 |
| entering: |
| leaving: |
| ppmc: |
| count: 14 |
| entering: |
| dmclaughlin: 2014-08-20 |
| leaving: |
| signoff: |
| jfarrell: true |
| benh: false |
| mattmann: true |
| hsaputra: true |
| notes: |
| ptgoetz: | |
| Podling looks very healthy. 3 of 4 mentors engaged since last report. |
| Brooklyn: |
| board-issues: |
| community-development: | |
| Our community continues to grow slowly but surely, and has received |
| interest and contributions from new community members. |
| |
| We had the opportunity to talk about our project at ApacheCon Europe |
| recently, which has introduced Brooklyn to a wider audience within |
| Apache. |
| graduation-issues: |
| - "Grow the community" |
| - "More diversity of the committers/PPMC (currently biased towards employees of a single organization)" |
| - "Following up our first release with further, regular, releases" |
| project-development: | |
| Code continues to be proposed and merged at a high rate. We are |
| satisfied with our technical velocity. |
| |
| We recently completed our first release as an Apache project, and |
| look forward to following this up with regular releases from now on. |
| committers: |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| hogstrom: false |
| akarasulu: false |
| ke4qqq: true |
| marrs: false |
| jbonofre: true |
| olamy: false |
| chipchilders: true |
| asavu: false |
| jzb: true |
| jim: true |
| notes: |
| chipchilders: | |
| The Brooklyn community is doing very well in learning the rules / |
| policies / nuances of working at the ASF. It still needs a bit more time |
| to build up a diverse community IMO, but things are looking good. |
| ke4qqq: | |
| The Brooklyn folks kicked out their first release during this reporting |
| cycle, which is an important milestone. Work still remains in terms of |
| building a diverse community. |
| Calcite: |
| board-issues: |
| community-development: | |
| In December, there were 84 messages on dev@, 45 commits, 50 issues |
| created, 27 issues resolved by 7 contributors. |
| |
| Julian Hyde gave a talk "SQL on everything, in memory" about Calcite |
| at the Strata + Hadoop World conference in October, and held an |
| "office hour" with interested community members. He also spoke at |
| a Hive meet-up in New York and a Kylin meet-up in San Jose about |
| how those projects integrate with Calcite. |
| |
| Collaborations are under way with other Apache projects: with Drill |
| to make implementation convention more neutral; with Hive for join |
| algorithm selection, and leveraging sorted data; and with Phoenix |
| to create a Calcite adapter for Phoenix. |
| graduation-issues: |
| - "Continue to build community" |
| - "Add more committers and PPMC members" |
| - "Demonstrate community robustness by rotating project tasks among multiple project members" |
| project-development: | |
| We have completed the rename from Optiq to Calcite. We have also |
| re-organized the code into the org.apache.calcite namespace. We are |
| planning to make a 1.0 release in January with the re-organized |
| code. |
| committers: |
| count: 5 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| tdunning: true |
| gates: true |
| stevenn: true |
| notes: |
| Corinthia: |
| board-issues: |
| community-development: | |
| This is our first podling report. |
| |
| We have spend a lot of mail on getting acquainted and finding the strength |
| of each other. |
| |
| Now discussion are flowing freely. We have consensus on PPMC == Committer |
| as long as we are in incubator. |
| graduation-issues: |
| - "complete the move to ASF infrastructure" |
| - "Discuss and decide on a medium-term roadmap" |
| - "Grow the community" |
| project-development: | |
| This is our first podling report. |
| |
| We are at work making a stable kernel so we can more easily add more |
| developers. |
| committers: |
| count: 8 |
| entering: |
| pescetti: 2014-12-31 |
| leaving: |
| ppmc: |
| entering: |
| pescetti: 2014-12-31 |
| leaving: |
| signoff: |
| humbedooh: true |
| jani: true |
| notes: |
| DataFu: |
| board-issues: | |
| 1. Has not yet made a release, but is in process of preparing first. |
| 2. Need to dramatically grow the contributor base. |
| community-development: | |
| New committer and PMC member. Several JIRAs filed by new users. |
| graduation-issues: |
| - "Grow user and contributor base." |
| - "Make first release." |
| - "Increase activity for initial committers." |
| project-development: | |
| 1. 16 issues created, several from new contributors. |
| 2. 8 issues closed. |
| 3. Reasonable amount of mailing list traffic. |
| committers: |
| count: 16 |
| entering: |
| rjurney: 2014-11 |
| leaving: |
| ppmc: |
| entering: |
| rjurney: 2014-11 |
| leaving: |
| signoff: |
| hashutosh: false |
| rvs: true |
| tdunning: true |
| notes: |
| HTrace: |
| board-issues: |
| community-development: | |
| * 141 messages on dev@htrace |
| * 42 issues resolved and 11 open |
| graduation-issues: |
| - "Make our first release from incubator" |
| - "Move dependent projects over to the incubator version" |
| - "Continue to grow user and contributor base; i.e. grow the community." |
| project-development: | |
| * This is our first report. |
| * We are fully moved over to Apache Infrastructure now (thanks in |
| particular to Jake Farrell for help here). |
| * We have our first htrace website published. |
| * Development of an easy to deploy htraced trace sink and visualization is |
| moving along nicely. |
| * An htrace receiver for Apache Flume was contributed. |
| * We have put up 5 release candidates for our 1st podling release with a |
| 6th on its way. |
| committers: |
| count: 12 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| jfarrell: true |
| todd: false |
| lewismc: true |
| apurtell: false |
| billie: true |
| stack: true |
| notes: |
| johndament: | |
| The podling is working through its first release slowly. First release |
| is always the hardest. Good activity for a new podling on the lists, |
| still waiting on the board report though. |
| Ignite: |
| board-issues: |
| community-development: | |
| Several contributors expressed interest in contributing. |
| graduation-issues: |
| - "Finish migration to Apache process." |
| - "Grow active and healthy community around Apache Ignite product." |
| - "Get on a stable release schedule and have 3 successful product releases." |
| project-development: | |
| - Started the implementation of JCache (JSR 107) specification. |
| - Integrated JCache (JSR 107) TCK test suite into project lifecycle. |
| - Made significant improvements to Apache Ignite (incubating) website. |
| - Submitted SGA from GridGain to Apache Ignite (incubating) for In-Memory |
| Hadoop Accelerator. |
| committers: |
| count: 15 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| brane: true |
| cos: true |
| hsaputra: true |
| rvs: true |
| stack: true |
| notes: |
| adc: | |
| This podling is off to a great start. Mentors are extremely active |
| participants with most of the non-Jira chatter being between Dmitriy |
| Setrakyan and the mentors; look to the Jira issue to see the rest of the |
| community "getting it done". The "issues to be addressed" section seems |
| reasonable. |
| brane: | |
| I agree with Alan's assessment, but I'd really like to see more |
| activity on the dev@ list; especially more of the initial committers |
| getting involved in discussions there. Whilst Jira notifications are |
| nice, I have a nagging feeling that most of the discussions within |
| the community are happening off-line, which leaves a rather large |
| hole in the community's collective memory (i.e., mail archives). |
| This will have to be addressed before graduation. |
| Kalumet: |
| board-issues: |
| community-development: | |
| Apache Kalumet 0.6-incubating version has been released. However, due to |
| some misunderstanding, the release vote has not been completed by 3 IPMC. |
| Especially, some legal files issues have been raised. |
| |
| We are preparing a 0.6.1-incubating release to fix the legal files and |
| submit to IPMC vote. |
| |
| We are in the way of promoting the documentation on the website. |
| graduation-issues: |
| project-development: | |
| We are preparing the 0.6.1-incubating (plan for December, 27) to fix the |
| legal files issues raised on 0.6-incubating release and have a complete |
| IPMC vote. |
| |
| We are preparing the 0.7-incubating release with the development changes. |
| |
| A new contributor has been identified and started to work on some issues |
| and refactoring of the webconsole (mockup provided using Vaadin). |
| |
| Local branches have been created containing: |
| |
| - new model and REST API |
| - new webconsole (remove of Echo framework) |
| |
| These local branches will be merged on the 0.7-incubating branch (master). |
| |
| Before Graduation: |
| |
| - The documentation has been updated and aligned with the 0.6-incubating |
| release. The documentation will be promoted on the website and "linked" |
| in announcement e-mails as soon as the 0.6.1-incubating release has been |
| voted. |
| - The 0.7-incubating release will fix the graduation issue, especially in |
| term of license (removal of Echo2 framework for the UI). |
| |
| Post Graduation: |
| |
| - Kalumet scripts. It's the extension of the "software" concept globally |
| to all Kalumet resources. It will allow users to create custom |
| deployment/update plan, with a set of fine-grained steps. |
| committers: |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| jim: true |
| hgomez: false |
| jbonofre: true |
| olamy: false |
| notes: |
| Kylin: |
| board-issues: |
| community-development: | |
| The community is growing. Several new members have started actively |
| contributing to the project. New contributors made a significant |
| contribution in develop new feature, fix bugs, refine web experience. The |
| Kylin meetups at Bay Area and Beijing was well attended. Apache Kylin has |
| been presented at Big Data Technology Conference 2014, Beijing which is |
| one of biggest Big Data conference in China. Interest of people during |
| that event was great and engaged a lots of organizations and individuals, |
| many of them started to evaluate and joined Kylin community. |
| graduation-issues: |
| - "Migrate source code and issue tracking from github.com to Apache Git and JIRA" |
| - "Make the first release from apache" |
| - "Make project website available on apache" |
| project-development: | |
| 1. The project setup is going quite well. Initial committers are |
| onboarding, JIRA, mailing list were successfully done, Web content has |
| been migrated to Apache Git but need tuning. Main source code migration |
| will be done in January 2015. |
| 2. Bug fixing, enhancement are happing on current branch which |
| will be the target v1.0 release. |
| 3. Work toward next gen version (supports inverted-index) is |
| progressing substantially. |
| committers: |
| count: 11 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| omalley: true |
| tdunning: true |
| hsaputra: true |
| notes: |
| Lens: |
| board-issues: | |
| We are still waiting for project website creation via |
| https://issues.apache.org/jira/browse/INFRA-8549 |
| community-development: | |
| * Logo of the project has been finalized and published. |
| * Added one new committer/PPMC - Rajat Khandelwal |
| * Had contributor meetup in Bangalore, India |
| * Mailing list subscription (as on 2015-jan-03): |
| * Dev list: 29 members |
| * Commits list: 14 members |
| * User list: 21 members |
| graduation-issues: |
| - "Make the first release from apache" |
| - "Make project website available on apache" |
| - "Reach out to people through presentations and blogs" |
| project-development: | |
| * Main activities include |
| * Podling setup wrt jenkins and pushing docs |
| * Improving documentation |
| * Stabilizing the code for first stable release |
| * Feature additions - Join chains in OLAP cube |
| * Mailing list activity : |
| * Dev via mail-archives.apache.org: |
| * December - 1380 messsages |
| * Commits via mail-archives.apache.org: |
| * December - 50 messages |
| * User mailing list activity - None |
| |
| * Issues 101 created and 62 resolved (via 30 day summary from LENS Jira) |
| committers: |
| count: 14 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| cdouglas: true |
| jghoman: true |
| jbonofre: true |
| notes: |
| adc: | |
| Very good report; an exemplar of how reports should be done. The |
| community seems very active and healthy. IMO, only items 1 & 2 are |
| required for graduation. |
| MRQL: |
| board-issues: | |
| The project is not making much progress on the level of increasing the |
| number of active committers and expanding the users community. |
| |
| This is already being discussed inside the project community and the main |
| active committer asked to give the project more few months as he will try |
| spreading the word more about the project through some public events |
| community-development: |
| graduation-issues: |
| - "Increase the number of active committers" |
| - "Increase adoption, expand user community, and increase user list activity" |
| project-development: | |
| During the last three month, 12 jira issues were reported, from which 10 |
| were fixed. Most of these issues were related to MRQL query evaluation in |
| Flink mode. Finally, we have set up MRQL on ASF Jenkins, which is a CI |
| server that continuously checks the integrity of our builds and validates |
| our tests. |
| committers: |
| count: 12 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| adc: true |
| akarasulu: false |
| mnour: true |
| notes: |
| cos: | |
| Very light email list traffic compare to prev. month. Mentors are |
| active. |
| NiFi: |
| board-issues: |
| community-development: | |
| The dev mailing list has picked up 20 new e-mails since the last report |
| and is now at 62 (commits has grown to 25). |
| |
| At the suggestion of the community we've adopted a review-then-commit |
| strategy which is designed to among other things help with community |
| development. |
| |
| We've received several patches from members outside the initial committer |
| list including changes which dramatically improved our build process and |
| provide new extensions. |
| graduation-issues: |
| - "Produce an initial release." |
| - "Grow our community beyond the initial set of committers." |
| - "Establish rhythm for releases, review processes, and document how to most effectively bring on new committers." |
| project-development: | |
| All of our current infrastructure needs are setup and things are working |
| really well. Our focus now is on working towards our first release which |
| is 0.0.1 and presently comprised of 85 JIRA issues the vast majority of |
| which are resolved. We've conducted a thorough review of all source files |
| to ensure proper license headers/notices/disclaimers are present. We've |
| completed a thorough review and modification of the overall LICENSE and |
| NOTICE files in preparation for release. We've conducted the initial |
| podling name search and submitted the ticket for that analysis to be |
| verified and confirmed. |
| committers: |
| count: 14 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| billie: true |
| arvind: true |
| esteve: false |
| bimargulies: true |
| brock: true |
| drew: false |
| apurtell: true |
| notes: |
| tnachen: | |
| Project is still setting up and in the early phase. Mailing list and commits are fairly active.. |
| NPanday: |
| board-issues: |
| community-development: |
| graduation-issues: |
| project-development: |
| committers: |
| count: 9 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| rbircher: false |
| cos: false |
| notes: |
| ptgoetz: | |
| NPanday has missed the last two reports (last report August 2014). One |
| of two mentors are engaged and encouraging the podling to make a final |
| release before retiring (last release was on 2011-05-17). However, there |
| is little PPMC/Committer involvement with only 2 PPMC members showing |
| involvement on the dev@ list in the past year. Also confirmed that a |
| report reminder email was received by the dev@ list for each of the last |
| missed reporting periods as well at the current period. |
| |
| It's clear that mentors past and present have attempted to help the |
| NPanday project grow to a viable size -- at least enough to approve a |
| release, new Committer/PPMC Member, or even decide to retire -- without |
| success. |
| |
| The main warning signs appear to be: |
| |
| * Inability to reach community consensus (barely 2 acive Committer/PPMC |
| Members, making 3 +1s for any vote very difficult) |
| * Inability to perform releases |
| * Inability to grow the community to a viable size |
| |
| The issues listed above do not indicate a lack of mentor involvement, |
| but rather a community in decline. |
| odftoolkit: |
| board-issues: |
| community-development: | |
| We have made a release but there has been little activity since then. |
| |
| We still need to attract more members and publicizing the project in the |
| ODF. |
| |
| Our validator was used on the ODF Plugfest, ahead a patch was provided by |
| a new contributor. |
| graduation-issues: |
| - "Grow the community in terms of committers" |
| - "Have regular releases" |
| - "Decide if we would like to be a top level project or join an existing project, or move to the attic." |
| project-development: | |
| Update of ODF validator before the ODF Plugfest (London). |
| |
| There have been some user issues reported and responded to. |
| |
| ODF Toolkit part of presentation on the Apache Con Europe. |
| committers: |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| billie: true |
| arvind: true |
| esteve: false |
| bimargulies: true |
| brock: true |
| drew: false |
| apurtell: true |
| notes: |
| robweir: | |
| My concern is the same as before. IMHO we've grown too comfortable |
| being a podling. We're able to do everything we want to do as a |
| podling, have a website, check in code, make releases, etc. I'm not |
| really feeling any urgency from committers or PPMC members to push |
| this project through to the next steps needed for graduation. |
| |
| Advantages of being a Top Level Project at Apache include: |
| |
| 1) Less process overhead for releasing. We still need to check all |
| of the items, but we're then trusted to do this on our own without |
| additional IPMC review. |
| |
| 2) Our releases would no longer have the Incubation disclaimer in the |
| release notes |
| |
| 3) We'd get a top level URL for the website odf@apache.org, and a |
| shortened mailing list address, dev@odf.apache.org. |
| |
| 4) We'd have more freedom to do publicity via press releases, etc. |
| |
| 5) We'd still need to do quarterly reports, but these would go |
| directly to the Apache Board. |
| |
| Although none of these by themselves are huge, take together it is a |
| nice bundle of perks. And it really signifies that, as a community, |
| we understand The Apache Way, the release procedures and are able to |
| sustain the community. |
| |
| In our report this month we list the three most important things to do |
| on the way to graduation: |
| |
| 1. Grow the community in terms of committers |
| |
| 2. Have regular releases |
| |
| 3. Decide if we would like to be a top level project or join an existing |
| project, or move to the attic. |
| |
| |
| Any proposals on what we can do for #1 and #2? For example, do we |
| have any contributed patches we still need to integrate? Are there |
| other ways we could think of for publicizing the project, and |
| attracting additional volunteers? |
| tnachen: | |
| It seems like the project is active in release and code (towards the low activity side). |
| However the mailing list traffic and engagement has decreased overtime and the |
| dev list even with jira notifications is still very low traffic. |
| parquet: |
| board-issues: |
| community-development: | |
| Latest Additions: |
| |
| * PMC addition: None |
| * Contributor addition: Dan Weeks and Alex Levenson |
| |
| Issue backlog status since last report: |
| |
| * Created: 45 |
| * Resolved: 20 |
| |
| Mailing list activity since last report: |
| |
| * dev 310 messages: 90 in Oct, 126 in Nov, and 94 in Dec |
| graduation-issues: |
| - "Expanding the community and adding new committers" |
| - "1st releases toward org.apache Parquet 1.6.0 GA" |
| - "Identifying how to ensure timely code reviews by committers" |
| project-development: | |
| - Completed first release, Apache Parquet Format (incubating) 2.2.0 |
| - Established a by-law for adding committers |
| - Added 2 new committers |
| - Parquet presentation accepted for Strata San Jose |
| committers: |
| count: 19 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| todd: false |
| jfarrell: true |
| mattmann: true |
| rvs: true |
| tomwhite: false |
| notes: |
| cos: | |
| Mailing lists are active; most mentors are active. |
| ranger: |
| board-issues: |
| community-development: | |
| * Added few more contributors |
| * Vote for adding an additional committer is in progress with |
| private@ranger.incubator |
| * Issues (JIRAs) created/resolved since last report (after Oct-01-2014 |
| before Dec-30-2014): |
| Created: 115 |
| Resolved: 100 |
| graduation-issues: |
| - "Increase the Ranger contributors/committers across industry verticals" |
| - "Establish a automated git check-in process to validate the check-in patches for quality control (similar to Hadoop QA)" |
| - "Add more documentation to support new users and contributors." |
| project-development: | |
| * Project Name has been renamed from "Apache Argus” to “Apache Ranger” |
| * Three Release candidates were voted in dev community for Ranger-0.4.0 |
| version and RC3 has been voted to be released in IPMC |
| * First release of Apache Ranger 0.4.0 on Nov-17,2014 |
| * Apache Ranger 0.4.0 Release artifacts are published in |
| official dist directory. |
| * Ranger Documentation wiki Site |
| (https://cwiki.apache.org/confluence/display/RANGER) has been added. |
| * Working on release of Apache 0.4.1 to avoid compilation issues related |
| to SNAPSHOT libraries in HBase and Hive dependencies |
| * Working on adding more security functionalities for the next release, |
| Apache Ranger 0.5.0 |
| committers: |
| count: 12 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| gates: true |
| humbedooh: true |
| ddas: false |
| jghoman: true |
| omalley: true |
| notes: |
| johndament: | |
| Ranger suffered a bit from a renaming issue that came up. Activity on |
| the lists is a little bit lighter since, but I'm sure will bounce back. |
| I'm concerned over inability to access the wiki though, sent a note to |
| the podling to request proper access. |
| ripple: |
| board-issues: |
| community-development: |
| graduation-issues: |
| project-development: |
| committers: |
| count: 11 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| jukka: false |
| grobmeier: false |
| asavory: false |
| samoa: |
| board-issues: |
| community-development: | |
| This is the first report. |
| graduation-issues: |
| - "Get IP clearance (SGA) from Yahoo" |
| - "Move the current code into ASF's git repository" |
| - "Start working as an Apache project" |
| project-development: | |
| This is the first report. |
| committers: |
| count: 11 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| gates: false |
| hashutosh: false |
| enis: false |
| tdunning: true |
| notes: |
| samza: |
| board-issues: |
| community-development: | |
| Continued growth in mailing list, particularly from new users. |
| graduation-issues: |
| project-development: | |
| Released version 0.8. |
| committers: |
| count: 12 |
| entering: |
| - |
| cpsoman: 2014-08-13 |
| leaving: |
| ppmc: |
| entering: |
| - |
| cpsoman: 2014-08-13 |
| leaving: |
| signoff: |
| cdouglas: true |
| acmurthy: false |
| rvs: true |
| notes: |
| tamaya: |
| board-issues: | |
| There are many discussions about how simple the API and or code should be. |
| community-development: | |
| We got a new contributor, Reinhard Sandtner who already shipped a patch |
| and is participating in some discussions. |
| graduation-issues: |
| - "Project web site must be setup (done)." |
| - "Establish a solid code base for a release." |
| - "Continue to grow the community." |
| project-development: | |
| The project setup is going quite well. The initial code donation is under |
| ongoing review. |
| committers: |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| johndament: true |
| struberg: true |
| gpetracek: true |
| dblevins: false |
| notes: |
| johndament: | |
| Podling is struggling a bit with some growing pains. Hope it will |
| straighten out soon. |
| taverna: |
| board-issues: |
| community-development: | |
| Quiet month - dominated by migration issues. |
| |
| Involvement with students who are combining Taverna and Apache Storm. |
| |
| Email traffic December 2014: |
| |
| * dev@taverna: 50 messages |
| * users@taverna: 12 messages |
| graduation-issues: |
| - "IP clearance to be signed by Univ of Manchester" |
| - "Move source code, wiki, issues to apache.org." |
| - "Re-awake community after migration, prepare a release" |
| project-development: | |
| The project is waiting for the Software Grant from Univ of Manchester |
| Solicitor and Contracts Manager as he needed to retrieve the existing CLAs |
| from archive. He has replied (2015-01-05): "They should arrive back from |
| storage this week and we can proceed with the [software grant] transfer" |
| |
| Taverna's WSDL-support modified to work with Apache Woden. |
| |
| About 45% of code base ready to be migrated (moved to slimmer git layout, |
| modified to org.apache.taverna groupId and build). |
| TODO: LICENSE and NOTICE plugins for Maven. |
| |
| Apache Taverna website live at |
| http://taverna.incubator.apache.org/ |
| -- not yet migrating content from |
| http://www.taverna.org.uk/ until IP clearance sorted |
| |
| Discussions around packaging / Debian |
| committers: |
| count: 16 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| andy: true |
| mattmann: true |
| suresh: false |
| smarru: false |
| mpierce: true |
| notes: |
| andy: | |
| Given the podling has not yet got the software grant on ASF file, |
| through no fault of the podling, I suggest keeping reporting Taverna |
| monthly. |
| jmclean: | |
| Off to a good start, with discussions about making builds and assembling |
| LICENSE and NOTICE. Mentors (very) active. |
| usergrid: |
| board-issues: |
| community-development: | |
| We added a couple of new committers: Alex Muramoto, Ryan Bridges and John |
| Ament. We are working on our second release from the Incubator, Usergrid |
| 1.0.1 and are creating release candidates now for voting. |
| graduation-issues: |
| - "Continue to build community" |
| - "Perfect release process" |
| - "Exclude unnecessary dependencies from release" |
| project-development: | |
| Much work has been done in the "two-dot-o" version of Usergrid with a new |
| persistence and query engine. Bugs have been fixed in the master branch |
| and it is now being prepared for a Usergrid 1.0.1 release. |
| committers: |
| count: 10 |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| snoopdave: true |
| jfarrell: true |
| jim: true |
| lewismc: false |
| lresende: false |
| notes: |
| johndament: | |
| The group is still getting accustomed to the Apache Way. Special thanks |
| to those in the incubator who have helped with licensing issues in the |
| current release attempt. |
| zeppelin: |
| board-issues: |
| community-development: | |
| Zeppelin has just entered the ASF Incubator and the onboarding |
| is progressing nicely. All initial committers have been issued |
| ASF accounts and the basic INFRA has been setup. |
| graduation-issues: |
| - "Complete the SGA" |
| - "Migrate to ASF infrastructure" |
| - "Complete PODLINGNAMESEARCH-64" |
| project-development: | |
| This is the first report. |
| committers: |
| entering: |
| leaving: |
| ppmc: |
| entering: |
| leaving: |
| signoff: |
| cos: true |
| hyunsik: true |
| tdunning: true |
| hsaputra: true |
| rvs: true |
| notes: |
| shepherds: |
| Aurora: pgoetz |
| Brooklyn: smarru |
| Calcite: mfranklin |
| Corinthia: rbircher |
| DataFu: drew |
| HTrace: johndament |
| Ignite: adc |
| Kalumet: wave |
| Kylin: asavu |
| Lens: adc |
| MRQL: cos |
| NiFi: tnachen |
| NPanday: pgoetz |
| odftoolkit: tnachen |
| parquet: cos |
| ranger: johndament |
| ripple: rgardler |
| samoa: rbircher |
| samza: mfranklin |
| tamaya: smarru |
| taverna: jmclean |
| usergrid: asavu |
| summary: | |
| IPMC has recognized the need for tightening up mentorship requirements |
| and overall structure of the incubation process. Active discussions |
| on how to this in the best possible way are on going and the recommendation |
| is expected to be available in a few weeks. |
