Community-led development "The Apache Way"
This was extracted (@ 2021-04-07 00:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
Flagon is a software tool usability testing platform
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Work with IPMC to approve draft graduation resolution
2. Add DISCLAIMER and make read-only subprojects to be retired (TAP,
STOUT, etc.)
3. Add logo to appropriate Apache outlet (logos.apache.org)
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues at this time.
### How has the community developed since the last report?
Not significantly.
### How has the project developed since the last report?
- We are working towards UserALE release 2.1.1
- We have been actively engaged with an expanding user base
- Core product source code is well maintained
- Preparing to complete outstanding graduation actions
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2020-03-27
### When were the last committers or PPMC members elected?
- Furkan (Mentor) 2019-07-24
- Tim Allison (Mentor) 2019-07-17
- Arthi Vezhavendan (PPMC) 2017-01-24
### Have your mentors been helpful and responsive?
- Our mentors have been very supportive and responsive
- Our mentors have urged us to create a Graduation resolution
### Is the PPMC managing the podling's brand / trademarks?
- To date, there are no known issues of 3rd Party misuse of brand
- 'Flagon' was cleared through the Apache PODLINGNAMESEARCH workflow.
- 'Flagon' branded graphics will conform to Apache's Trademark and
Branding policies.
### Signed-off-by:
- [X] (flagon) Lewis John McGibbney
Comments: Flagon was to do degree blokced from graduating within the
last ~3 months. I personally felt that the IMPC review of the DRAFT
graduation resolution could have been better handled by the IPMC. There
were a number of non-blocking items which were raised and which
eventually
impacted the motivation to graduate. It would be nice if Flagon could
graduate as ther podling has shown excellent underatanding of the
Apache
Way and it's patience to mature as a podling. I will work with the
Flagon
PPMC on the next steps as highlightes in the above report.
- [ ] (flagon) David Meikle
Comments:
- [ ] (flagon) Tim Allison
Comments:
- [X] (flagon) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
Justin Mclean: Looking at the email discussion I can't see how it was
blocked,
a few minor things were raised that were easily fixed. All of the proposed
PMC members have still not signed up the the private list.
Flagon is a software tool usability testing platform
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Work with IPMC to approve draft graduation resolution (blocking)
2. Update release practices to be consistent with NPM, Python registry
(non-blocking)
3. Push new UserALE.js release (non-blocking)
### Are there any issues that the IPMC or ASF Board need to be aware of?
- No major issues at this time.
- However, the community has been affected by COVID impacts on certain
sectors.
### How has the community developed since the last report?
- COVID has affected community engagement and onboarding new committers
- User base remains strong and continues to grow in specific markets
- We continue to train and socialize new committers
### How has the project developed since the last report?
- Project maturity roadmaps & release plans are maintained
- Sub-projects are being migrated to Git Issues
- Core product source code is well maintained
- We continue to develop our analytical produce to expand interest
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2020-03-27
### When were the last committers or PPMC members elected?
- Furkan (Mentor) 2019-07-24
- Tim Allison (Mentor) 2019-07-17
- Arthi Vezhavendan (PPMC) 2017-01-24
### Have your mentors been helpful and responsive?
- Our mentors have been very supportive and responsive
- Our mentors have urged us to create a Graduation resolution
### Is the PPMC managing the podling's brand / trademarks?
- To date, there are no known issues of 3rd Party misuse of brand
- 'Flagon' was cleared through the Apache PODLINGNAMESEARCH workflow.
- 'Flagon' branded graphics will conform to Apache's Trademark and
Branding policies.
### Signed-off-by:
- [X] (flagon) Lewis John McGibbney
Comments: Flagon is very close to graduation. The podling status page
has been
updated to reflect reality
http://incubator.apache.org/projects/flagon.html
This has also been posted to the IMPC general@ channel
https://s.apache.org/q0k3q
- [X] (flagon) David Meikle
Comments:
- [ ] (flagon) Tim Allison
Comments:
- [X] (flagon) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
Flagon is a software tool usability testing platform
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Grow the Flagon Committer/Contributor/Community Base
2. Refine release processes for core analytic product (Distill)
3. Finalize (through vote) Flagon logo, get marketing approvals (e.g swag)
### Are there any issues that the IPMC or ASF Board need to be aware of?
* Despite COVID impacts on our community, Flagon remains active
* No other issues
### How has the community developed since the last report?
* COVID has affected community engagement and onboarding new committers
* User base remains strong
* The community has rallied to participate in ApacheCon@Home
### How has the project developed since the last report?
* Project maturity roadmaps & release plans are maintained
* Sub-projects are being migrated to Git Issues
* Core product source code is well maintained
* The community has begun experimenting with OpenTelemetry to expand
interest
* We continue to develop our analytical produce to expand interest
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-03-17
### When were the last committers or PPMC members elected?
* Furkan (Mentor) 2019-07-24
* Tim Allison (Mentor) 2019-07-17
* Arthi Vezhavendan (PPMC) 2017-01-24
### Have your mentors been helpful and responsive?
* Our mentors have been very supportive and responsive
### Is the PPMC managing the podling's brand / trademarks?
* To date, there are no known issues of 3rd Party misuse of brand
* 'Flagon' was cleared through the Apache PODLINGNAMESEARCH workflow.
* 'Flagon' branded graphics will conform to Apache's Trademark and
Branding policies.
### Signed-off-by:
- [ ] (flagon) Lewis John McGibbney
Comments:
- [ ] (flagon) David Meikle
Comments:
- [ ] (flagon) Tim Allison
Comments:
- [X] (flagon) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
Flagon is a software tool usability testing platform
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Grow the Flagon Committer/Contributor/Community Base
2. Refine release processes for core analytic product (Distill)
3. Finalize (through vote) Flagon logo, get marketing approvals (e.g swag)
### Are there any issues that the IPMC or ASF Board need to be aware of?
* None at this time.
* Flagon will likely draft and vote on a graduation resolution this year.
### How has the community developed since the last report?
1. Continued improving release processes and code base
2. Continued to generate a wide user base
3. Discussing collaborations for R&D applications
4. New potential committers are identified and will be introduced soon
### How has the project developed since the last report?
1. Project maturity roadmaps & release plans are maintained
2. Sub-projects are being migrated to Git Issues
3. Core product source code is well maintained
4. Analytical products are being refactored to grow user base
5. Continued attention and improvement in Apache Process
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-03-17
### When were the last committers or PPMC members elected?
* Furkan (Mentor) 2019-07-24
* Tim Allison (Mentor) 2019-07-17
* Arthi Vezhavendan (PPMC) 2017-01-24
### Have your mentors been helpful and responsive?
* Our mentors have been very supportive and responsive.
### Is the PPMC managing the podling's brand / trademarks?
* To date, there are no known issues of 3rd Party misuse of brand
* 'Flagon' was cleared through the Apache PODLINGNAMESEARCH workflow.
* 'Flagon' branded graphics will conform to Apache's Trademark and
Branding policies.
### Signed-off-by:
- [ ] (flagon) Lewis John McGibbney
Comments:
- [X] (flagon) David Meikle
Comments:
- [ ] (flagon) Tim Allison
Comments:
- [X] (flagon) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
Flagon is a behavioral logging platform for web pages and apps
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Grow the Flagon Committer/Contributor/Community Base
2. Refine release processes for core analytic product (Distill)
3. Finalize (through vote) Flagon logo, get marketing approvals (e.g swag)
### Are there any issues that the IPMC or ASF Board need to be aware of?
* None at this time. Following mentors' comments in last (Q3 2019)
report, Flagon will likely draft and vote on a graduation resolution in
the new year.
### How has the community developed since the last report?
* continued improving release processes and code base
* continued to generate a wide user base
* discussing collaborations for R&D applications
* new potential committers have been identified and will be introduced to
the community in the new year
### How has the project developed since the last report?
* Project maturity roadmaps & release plans (JIRA) are maintained
* JIRA boards continue to be maintained.
* Core product source code is well maintained
* Analytical products are being refactored to grow user base
* Continued attention and improvement in Apache Process
* Expect UserALE.js v 2.1.0 RC in Q1 2020
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
* 2019-08-21 Flagon UserALE.js (Incubating) 2.0.2
### When were the last committers or PPMC members elected?
* Furkan Kamaci (Mentor) 2019-07-24
* Tim Allison (Mentor) 2019-07-17
* Arthi Vezhavendan (PPMC) 2017-01-24
### Have your mentors been helpful and responsive?
* Our mentors have been very supportive and
responsive.
### Is the PPMC managing the podling's brand / trademarks?
* 'Flagon' was cleared through the Apache PODLINGNAMESEARCH
workflow.
* 'Flagon' branded images graphics are under development and
will conform to Apache's Trademark and Branding policies.
### Signed-off-by:
- [ ] (flagon) Lewis John McGibbney
Comments:
- [ ] (flagon) David Meikle
Comments:
- [ ] (flagon) Tim Allison
Comments:
- [X] (flagon) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
Flagon is a behavioral logging platform for web pages and apps
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Grow the Flagon Committer/Contributor/Community Base
2. Refine release processes for core analytic product (Distill)
3. Finalize (through vote) Flagon logo, post name change
### Are there any issues that the IPMC or ASF Board need to be aware of?
* None at this time.
### How has the community developed since the last report?
* continued improving [release
processes](https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Rel
ease+Management+Procedure) and code base
* continued to generate a wide user base
* discussing collaborations for R&D applications
* the community has organically grown with a new contributors
* the community has begun a refactoring of Flagon-Distill
### How has the project developed since the last report?
* Completed major updates to website and repos following name change
* Project maturity roadmaps & release plans (JIRA) are maintained
* JIRA boards continue to be maintained.
* Core product source code is well maintained
* Analytical products are being refactored as of report date
* Continued attention and improvement in Apache Process
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
* 2019-08-21 Flagon UserALE.js (Incubating) 2.0.2
* 2019-07-01 Flagon UserALE.js (Incubating) 2.0.0
* 2019-06-21 Flagon UserALE.js (Incubating) 1.0.0 (ReRelease)
### When were the last committers or PPMC members elected?
* Furkan Kamaci (Mentor) 2019-07-24
* Tim Allison (Mentor) 2019-07-17
### Have your mentors been helpful and responsive?
* Flagon thanks its new Mentors for their engagement this quarter.
### Signed-off-by:
- [X] (Flagon) Lewis John McGibbney
Comments: I think it is nearly time for the Flagon PPMC to draft a
graduation resolution. I've mentioned this on the mailing list and
received feedback on it. Recent releases prove that the release
process and quality of source code artifacts are no longer blocking
issues. I would like to see Flagon graduate in this next quarter.
- [X] (Flagon) David Meikle
Comments: Progress has been made with new mentors engaged and releases
starting to flow.
- [ ] (Flagon) Tim Allison
Comments:
- [X] (Flagon) Furkan Kamaci
Comments: I agree that Apache Flagon is ready for graduation solution
as Lewis mentioned on the mailing list.
### IPMC/Shepherd notes:
Apache Flagon is a generalized user behavioural logging platform for web
pages and thin-client applications
Apache Flagon has been incubating since 2016-07-13; Apache Flagon has
officially changed its name from Apache SensSoft.
### Three most important unfinished issues to address before graduating:
1. Accelerate release frequency and reduce branch complexity in repos to
reduce adoption, contributor disincentives.
2. Grow the Apache Flagon Committer/Contributor/Community Base around our
core product Apache UserALE.js (Incubating)
3. Complete the issues highlighted at the Apache Flagon Roadmap [1]
### Are there any issues that the IPMC or ASF Board need to be aware of?
Apache Flagon is currently suffering from unresponsive mentors:
* Dave Meikle has been active and engaged, aside from a prolonged outage
due to a long-term illness. We are grateful for Dave's help and assistance
since then.
* Lewis McGibbney has been uncharacteristically unresponsive on dev@,
private@, and to PM. Note that Lewis has been a champion for us and have
confidence that he will return to activity.
* Atri Sharma has been wholly inactive. We tried to report this in our
last Q1 report; when posted to dev@ for review, he maintained that he
didn't the ability to cast binding VOTEs as an excuse for
non-engagement. We softened the language in our Q1 report and encouraged
him to participate by providing guidance, mentorship, and engaging in
community VOTEs. We haven't heard from him since despite numerous requests
for help and support posted to private@
As a result of long periods of mentor absence:
* ReRelease of v1.0.0 (at IPMC ) was delayed until mentors (Dave) were
available to guide us through a potential copyright issue (resolved).
* Prolonged the process of our name change as we struggled to explore
Apache documentation and understand what we had to change (in process; HUGE
thanks to INFRA for assisting us with some of the details).
* Is presently impeding our release process (not enough binding VOTES)
after tightening release procedures, and working hard to clean up our
branch structure to increase this cadence.
* We have struggled to get timely IPMC sign-off on REPORTs and have been
unable to post these ourselves to the incubator wiki for lack of permission.
* We have had to abandon our prior NPM distribution as it was released by
a non-responsive mentor on their personal NPM account (we don't have
credentials). [2]
NOTE as of the date of REPORT (6/26/2019) our ReRelease of Apache Flagon
UserALE.js (Incubating) v1.0.0 has been under VOTE on general@ for 9 days
(6/17/2019). After community and PPMC VOTE, we needed +2 binding votes.
We received helpful comments from Justin McLean, but despite numerous
reminders to VOTE, we still have yet to receive the last +1 binding VOTE
from IPMC. We are concerned that without active mentors, our release
cadence will remain slow and unresponsive to user communities.
With Dave Meikle's help, we will be searching for two additional mentors
so that our community is self sufficient. We recommend dropping Atri Sharma
from the project for non-participation.
### How has the community developed since the last report?
The community has:
* improved release processes and code base to expedite future releases
[3,4]
* gathered a wide base of users that are eagerly anticipating UserALE.js
v2.0.0 via NPM (under VOTE within the community as of this date).
* discussed with external parties research applications with university
research labs in machine learning and social computing.
* the community has organically grown with a new contributor, who is
participating in VOTEs
* the community expects to complete major updates to documentation on
website and READMEs, in early JUL 2019. Wiki updates will complete shortly
thereafter.
Despite consistent challenges to our community throughout 2018, we are
showing signs of growth, continue to have a relevant project, and are well
postured to accelerate growth in the coming quarters. We remain committed
to learning and adopting the Apache Way.
### How has the project developed since the last report?
* Completed migration to GitBox Repos
* Project maturity roadmaps (Wiki) and version release plans (JIRA)
continue to be maintained.
* JIRA boards continue to be maintained.
* Core product source code for front-end and back-end assets has been
steadily maintained and modernized.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2018-03-14
### When were the last committers or PPMC members elected?
Arthi Vezhavendan was added to Committer base on 2017-01-24
Dave Meikle was added to PPMC on 2018-11-24
Atri Sharma was added to PPMC on 2018-11-24
### Have your mentors been helpful and responsive or are things falling
through the cracks?
See mentorship issues above.
We are now aware that we can lean on general@ or INFRA for support
without permission and have deepened our knowledge of Apache processes so
that committers are more self-sufficient.
### Signed-off-by:
- [ ] (flagon) Lewis John McGibbney
Comments:
- [X] (flagon) Dave Meikle
Comments: Great to have two releases out post the name change. Now we
need to work on improving the mentor situation and on building the
community.
- [ ] (flagon) Atri Sharma
Comments:
[1] https://cwiki.apache.org/confluence/display/FLAGON/Roadmaps
[2] https://www.npmjs.com/package/useralejs
[3] https://dist.apache.org/repos/dist/dev/incubator/flagon/
[4] https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Manage
ment+Procedure
### IPMC/Shepherd notes:
Justin Mclean: All PPMC members in the roster have permission to edit the
incubator report, you don't need to rely on mentors for that. For extra mentors
please ask on the incubator list.