Re: [DISCUSS] Flagon Project Report Q4 2019
I hit send too fast. Please review this version of the report. ## Flagon 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 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](https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure) and code base * continued to generate a wide user base * discussing collaborations for R 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 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. * None. Our mentors have been very supportive and responsive. ### Signed-off-by: - [ ] (Flagon) Lewis John McGibbney Comments: - [ ] (Flagon) David Meikle Comments: - [ ] (Flagon) Tim Allison Comments: - [ ] (Flagon) Furkan Kamaci Comments: ### IPMC/Shepherd notes: On 12/30/2019 1:14 AM, Joshua C. Poore wrote: Hi Folks, Sorry about the tight turn on this, but posting for initial review before I post to the Incubator Wiki on the 1st. Please send me any thoughts issues or concerns on or before 2200 hrs, JAN 01 2020. Thnx, J ## Flagon 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 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](https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure) and code base * continued to generate a wide user base * discussing collaborations for R 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 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. * None. Our ### Signed-off-by: - [ ] (Flagon) Lewis John McGibbney Comments: - [ ] (Flagon) David Meikle Comments: - [ ] (Flagon) Tim Allison Comments: - [ ] (Flagon) Furkan Kamaci Comments: ### IPMC/Shepherd notes: On 12/30/2019 12:55 AM, Joshua C Poore wrote: Working on it right now. Should be posted to dev soon On 12/29/2019 1:27 PM, Furkan KAMACI wrote: Hi All, Is there anybody working on report? Let
[DISCUSS] Flagon Project Report Q4 2019
Hi Folks, Sorry about the tight turn on this, but posting for initial review before I post to the Incubator Wiki on the 1st. Please send me any thoughts issues or concerns on or before 2200 hrs, JAN 01 2020. Thnx, J ## Flagon 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 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](https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure) and code base * continued to generate a wide user base * discussing collaborations for R 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 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. * None. Our ### Signed-off-by: - [ ] (Flagon) Lewis John McGibbney Comments: - [ ] (Flagon) David Meikle Comments: - [ ] (Flagon) Tim Allison Comments: - [ ] (Flagon) Furkan Kamaci Comments: ### IPMC/Shepherd notes: On 12/30/2019 12:55 AM, Joshua C Poore wrote: Working on it right now. Should be posted to dev soon On 12/29/2019 1:27 PM, Furkan KAMACI wrote: Hi All, Is there anybody working on report? Let me know if you need help. Kind Regards, Furkan KAMACI On Sat, Dec 28, 2019 at 8:10 AM wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 January 2020, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, January 01). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/January2020 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
