Re: ATTN: MENTORS Re: Podling Flagon Report Reminder - January 2020
I took a shot at that question on incubator page. On 1/2/2020 8:32 AM, Furkan KAMACI wrote: Hi Joshua, That question requires an answer for does any 3rd party incorrectly using the Flagon name/brand and whether podling name search has done or not. Kind Regards, Furkan KAMACI On Thu, Jan 2, 2020 at 4:26 PM Joshua Poore wrote: Sure can. New question, though. Does this mean that the PPMC is filing its own trademarks or pushing it through Apache’s process? Joshua Poore On Jan 2, 2020, at 1:40 AM, Furkan KAMACI wrote: Hi Joshua, Thanks for preparing the report! Could you also answer this question at report: Is the PPMC managing the podling's brand / trademarks? Kind Regards, Furkan KAMACI On Thu, Jan 2, 2020 at 3:18 AM Joshua C. Poore < deeplyscott...@gmail.com> wrote: Hi All, Our Report has been posted to https://cwiki.apache.org/confluence/display/INCUBATOR/January2020 Mentors: please sign our report as soon as you are able. Thanks all. I know it's been quiet lately, but we'll be kicking back into full gear in short order. Best, Josh On 1/1/2020 7:57 AM, Furkan KAMACI wrote: Hi Joshua, Just a kindly reminder, today is due for the report. Kind Regards, Furkan KAMACI On Mon, Dec 30, 2019 at 8: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
ATTN: MENTORS Re: Podling Flagon Report Reminder - January 2020
Hi All, Our Report has been posted to https://cwiki.apache.org/confluence/display/INCUBATOR/January2020 Mentors: please sign our report as soon as you are able. Thanks all. I know it's been quiet lately, but we'll be kicking back into full gear in short order. Best, Josh On 1/1/2020 7:57 AM, Furkan KAMACI wrote: Hi Joshua, Just a kindly reminder, today is due for the report. Kind Regards, Furkan KAMACI On Mon, Dec 30, 2019 at 8: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
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 rep
[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
Re: FLOGOS! Plz review logos
Austin! Thanks so much for the input. #2 is my favorite, too. Flagon is user analysis for the masses. It's open source, scalable business analytics for some. It's usability analysis for others. And, its turning the web into a decision-sciences laboratory for others. We're trying to make user analysis open source and safe for all time. We're trying to up the game, too. Clickstream is dumb, we're about patterns of life and real behavioral science. Check out the website: http://flagon.incubator.apache.org/ As for what the logo has to do with anything about our project: Its all history, just like Apple's Apple, Microsoft's Window, and Google's Wheel. Our first UserALE (our logging service) developer was super into beer. So he named it User-ALE (Analytic Logging Engine). The alcohol reference became a thing for the dev team--we started naming all our apps after booze (ALE, Distill, TAP, STOUT). So, when we changed our name, the name really aligned with the history of the products (e.g., Flagon of ALE) more than the products' scope. So, our logos don't really have to have anything to do with our product, or a Flagon, they just have to be cool, fun, and energize people. If there are better ideas for something that aligns with behavioral logging, or actual Flagons (tough, I tried...), I'm all ears. But, we don't need to constrain ourselves, especially not at the cost of having fun and doing awesome things. I'd rather someone see something and ask, "whats that?" than see something completely obvious and have no motivation to explore. Our logo won't affect hits on Google, it will affect how much people spent time on our website or our booth at the next Apache con... Thoughts? On 9/29/2019 12:42 AM, Austin Bennett wrote: #2 looks super cool; still don't have a great sense of what project is trying to do as to whether sufficiently in-line. On Sat, Sep 28, 2019 at 9:38 PM Joshua C. Poore wrote: Hi Folks, I've been doing some sketches on Flagon logos. Probably we'll want a few for various things, but we need a primary logo to use on Twitter, website, etc., etc. I can't get them to go through unscathed through the dev lists. You can find them at this link: https://cwiki.apache.org/confluence/display/FLAGON/Flagon+Logos These are just sketches I made. I have someone (probably) who can finish them off, touch them up for us and make them web-ready. Of course, if someone from the community would like to do that, I'll take it! Just remember that the final will be copyright ASF. I call the first: FlagLorean. Was inspired by Back to the Future and the old ORION films logo ( https://www.google.com/search?q=orion+pictures=1C1CHBF_enUS863US863=lnms=isch=X=0ahUKEwj-4srQlvXkAhWOdd8KHXWgCfYQ_AUIEygC=1368=770#imgrc=NOPjZ1AuCpmMMM:). I wanted a throwback. I imagine this would have a metallic finish with some color inlets (negotiable). I call the second: FlagonSaveTheQueen. It speaks for itself, but was inspired with by the Pistols and Norse runes. For both, I wanted something that we could crop up and use for a web extension icon, which would be recognizable. I liked the idea of using the "ON" in Flagon as our icon. Both of these logos would give us something interesting to put in people's browsers, in that regard. I'm looking for feedback about what people would like to see on the website, wrt to a Logo. Whether either of these are moving in an interesting direction. Again, we need one primary logo, but a few others for Merch/Giveaways. FlagonSaveTheQueen will make a bad-ass patch, for example. Anyway, open to feedback and any other ideas. The sooner we pick some logos, the sooner we can get some cool shirts made :) Best, Josh
FLOGOS! Plz review logos
Hi Folks, I've been doing some sketches on Flagon logos. Probably we'll want a few for various things, but we need a primary logo to use on Twitter, website, etc., etc. I can't get them to go through unscathed through the dev lists. You can find them at this link: https://cwiki.apache.org/confluence/display/FLAGON/Flagon+Logos These are just sketches I made. I have someone (probably) who can finish them off, touch them up for us and make them web-ready. Of course, if someone from the community would like to do that, I'll take it! Just remember that the final will be copyright ASF. I call the first: FlagLorean. Was inspired by Back to the Future and the old ORION films logo (https://www.google.com/search?q=orion+pictures=1C1CHBF_enUS863US863=lnms=isch=X=0ahUKEwj-4srQlvXkAhWOdd8KHXWgCfYQ_AUIEygC=1368=770#imgrc=NOPjZ1AuCpmMMM:). I wanted a throwback. I imagine this would have a metallic finish with some color inlets (negotiable). I call the second: FlagonSaveTheQueen. It speaks for itself, but was inspired with by the Pistols and Norse runes. For both, I wanted something that we could crop up and use for a web extension icon, which would be recognizable. I liked the idea of using the "ON" in Flagon as our icon. Both of these logos would give us something interesting to put in people's browsers, in that regard. I'm looking for feedback about what people would like to see on the website, wrt to a Logo. Whether either of these are moving in an interesting direction. Again, we need one primary logo, but a few others for Merch/Giveaways. FlagonSaveTheQueen will make a bad-ass patch, for example. Anyway, open to feedback and any other ideas. The sooner we pick some logos, the sooner we can get some cool shirts made :) Best, Josh
Re: 2019 Q3 Flagon Report for Review
Justin, Updates made. I think the updates will be more appropriate. These are all drivers for community growth, which is our top issue to address prior to drafting a resolution. Josh On 9/28/2019 11:13 PM, Justin Mclean wrote: Hi, Thanks for submitting the report. Looking at the report I can see that 2 of the tasks needed (#2 and #3) listed for graduation don't seem to be tasks that the Incubator would expect but seem more technical in nature. It would be better if you could replace them with more suitable tasks. Thanks, Justin
Re: Hacktoberfest 2019
Furkan-- Great idea! We may not be able to "participate"; it looks like the best way to participate (or be discovered by participants) as a project is to tag issues as "Hacktober" in git issues, and our issues are still exclusively housed in JIRA. I've been meaning to push a ticket to INFRA to go forward with the integration. If they can get this done before Oct ends, I'll tag some issues and see what happens. Great Idea and if we miss this one, we'll be prepared for the next. Best, Josh On 9/27/2019 2:34 PM, Furkan KAMACI wrote: Hi, There is an event named as Hacktoberfest https://hacktoberfest.digitalocean.com/ You may consider targeting this event to attract more new committers for the project. Kind Regards, Furkan KAMACI
Re: 2019 Q3 Flagon Report for Review [MENTOR ACTION REQUIRED]
Hi All, Having not received any corrective actions on our quarterly report. I have posted it on the wiki website [1]. Mentors, please jump into the wiki and give sign off. Thanks! Josh [1] https://cwiki.apache.org/confluence/display/INCUBATOR/October2019 On 9/22/2019 11:22 PM, lewis john mcgibbney wrote: +1 on the report. ... honestly Josh, I think it is really time for the Flagon PPMC to consider drafting a graduation resolution. Recent releases prove that the release process and quality of source code artifacts are no longer blocking issues. We just need to following https://incubator.apache.org/guides/graduation.html#the_graduation_process On Sun, Sep 22, 2019 at 20:10 Joshua C. Poore <mailto:poor...@apache.org>> wrote: Hi All, It's that time again. Please review the following Apache Flagon (Incubating) podling report. Please post any comments, concerns in this thread. Reports are due for posting on the IPMC Wiki [1] NLT 2019-10-02. For convenience, I am posting the report as txt pasted below. However, a .md version of the report can be found on our wiki [2]. Please be sure to review 2019_Q3_FLAGON_report.md. Thanks! Josh (Flagon PPMC) [1] https://cwiki.apache.org/confluence/display/INCUBATOR/October2019 [2] https://cwiki.apache.org/confluence/display/FLAGON/Podling+Reports --Report Text (.md)-- #Apache Flagon (Incubating) `Apache Flagon` is a generalized user behavioral logging platform for web pages and thin-client applications `Apache Flagon` (formerly Apache SensSoft) has been incubating since 2016-07-13 Three most important issues to address in the move towards graduation: 1. Grow the`Apache Flagon` Committer/Contributor/Community Base around our core product Apache UserALE.js (Incubating) 2. Refactor core analytic product`Apache Flagon Distill`, as content driver to increase user/committer base 3. Complete the issues highlighted at the`Apache Flagon` Roadmap[1] Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? `Apache Flagon` would like to thank its new Mentors for their enthusiasm and engagement. Where in previous quarters, Flagon had challenges receiving critical mentor guidance through key transitions (e.g., copyright clearance, name change). Our current mentors-`Lewis McGibbney`,`Dave Meikle`,`Tim Allison`,`Furkan Kamaci`-have been extremely helpful in providing guidance, accessible for release review, and in product steerage. How has the community developed since the last report? The community has: * continued improving release processes and code base to expedite future releases[3,4] * continued to generate a wide user base * 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 has begun planning a refactoring of the Distill product which will distribute highly desirable user monitoring content and spur community growth and adoption How has the project developed since the last report? * Completed major updates to website and repositories following name change * 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. * Analytical products are being refactored as of the date of this report 2019-09-22 * Continued attention and improvement in Apache Process and Documentation compliance 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 Apache Flagon UserALE.js (Incubating) 2.0.2 * 2019-07-01 Apache Flagon UserALE.js (Incubating) 2.0.0 * 2019-06-21 Apache 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 or are things falling through the cracks? Things are on track and our community is becoming more self-sufficient. See above comment about improvements in mentorship Signed-off-by: [ ] (flagon)`Lewis John McGibbney` Comments: [ ] (flagon)`Dave Meikle` Comments: [ ] (flagon)`Tim Allison` Comments: [ ] (flagon)`Furkan Kamaci` Comments: [1] https://cwiki.apache.org/confluence/display/FLAGON/Roadmaps [2] https://www.npmjs.com/package/flagon-userale [3] https://dist.apache.org/repos/dist/dev/
Re: Unit Tests Behaving Oddly on new Session Id Storage feature
Hi Rob! Just checking into see if you had a chance to look into the unit testing issue at all, and if you had any findings you can share. I've been doing some stuff with Distill recently, and haven't made any more progress on this issue lately. Let me know! Josh On 9/14/2019 1:29 AM, Joshua C. Poore wrote: Thanks Rob, Much appreciated. If all else fails we can build our own mock, and there are other npm packages that we can try. I started with dom-storage b/c its API suites our needs (has getItem, setItem), and chose v2.0.2 because its about as old as our version of jsdom :). We'll see what happens. The sessionStorage thing is an important add for UserALE.js, it not only resolves some unwanted behavior in logging edge cases (e.g., form submit), but would allow for passing key:value data from sessionStorage to localStorage and thus provide a way to support apps that are designed for multi-tab use, by way of preserving sessionIDs. Its a big, little feature, if you get my meaning. Thanks for the support! Josh On 9/13/2019 9:48 AM, Rob Foley wrote: Seems you are doing the right thing (without having looked at the docs myself). I will try to look at it today/tonight. Not sure about the resource loader thing, could be that our use-case is just a non-issue in the new environment and thus is not possible. Rob On Fri, Sep 13, 2019 at 3:21 AM Joshua C. Poore <mailto:poor...@apache.org>> wrote: Hey Rob, Completely agree. See comments in the ticket: https://issues.apache.org/jira/browse/FLAGON-451 I found one npm package that looks promising for a storage mock: dom-storage (see ticket for links). I took a stab at it last night and the night before with very little luck. Pushed some of my work to Flagon-434 and documented findings in the ticket. Can you take a look--I don't think I'm passing the mocked storage into the jsdom env properly. I also played around with the getSessionId function so that it executes from a variable that's passed into getInitialSettings, rather than executed within getInitialSettings itself. Provides a bit better context in error messages. Its clear that jsdom still can't see the storage mock after passing it into the testing framework. Could really benefit from your expertise. Agree the test refactor can happen later. And agree that we should think about modernizing. I've been looking at Jest too. Seems a bit more intuitive and I'd love some nice tidy test coverage metrics. Also seems like we can preserve Chai tests, and Jest ships with jsdom, so maybe we could preserve a lot of our unit tests and just beef up testUtils. I wasn't clear on this: does Jest require that you create your own jsdom constructors, or have they abstracted it away in their own API? I HATE that new jsdom constructor, it drives me bonkers and I haven't figured out how we would pull our resource loader into their custom resource loader, yet (though, I'm still an amateur). Have tried and failed many, many times. Thanks for the help! Josh On 9/12/2019 9:42 AM, Rob Foley wrote: > So I think the answer here is to get a sessionStorage mock going. We can > either find one and add it to devDependencies or I can whip one up. > Upgrading the testing framework is probably worthwhile, but it may be out > of scope for this effort. We could investigate Jest, as I've had success > with that in the past. Either way, a big test refactor would be in order. > > Rob > > On Thu, Sep 12, 2019 at 1:24 AM Joshua Poore mailto:poor...@apache.org>> wrote: > >> @Rob >> >> Following up: >> >> I think the issue is that jsdom v9 has no concept of sessionStorage, so >> when getInitialSettings runs, we have a complete failure of UserALE.js >> within the jsdom environment. This would affect .options and .log APIs. I >> haven’t pushed more work on this, just have done some experimentation >> locally. But, if you re-work the getSessionId function to work outside of >> the getInitialSettings function and simply pass a variable into it, which >> is super ugly, you’ll get a new test failure error message indicating that >> sessionStorage is undefined. I didn’t push this because its not the best >> implementation that we should be working around. The reason why we’re not >> seeing the same error in the implementation on branch is because the >> getSessionId function is called from within getInitialSettings, so we see a >> report of .options being undefined. >> >> I’ve documented this here: >> https://issues.apache.o
2019 Q3 Flagon Report for Review
Hi All, It's that time again. Please review the following Apache Flagon (Incubating) podling report. Please post any comments, concerns in this thread. Reports are due for posting on the IPMC Wiki [1] NLT 2019-10-02. For convenience, I am posting the report as txt pasted below. However, a .md version of the report can be found on our wiki [2]. Please be sure to review 2019_Q3_FLAGON_report.md. Thanks! Josh (Flagon PPMC) [1] https://cwiki.apache.org/confluence/display/INCUBATOR/October2019 [2] https://cwiki.apache.org/confluence/display/FLAGON/Podling+Reports --Report Text (.md)-- #Apache Flagon (Incubating) `Apache Flagon` is a generalized user behavioral logging platform for web pages and thin-client applications `Apache Flagon` (formerly Apache SensSoft) has been incubating since 2016-07-13 Three most important issues to address in the move towards graduation: 1. Grow the`Apache Flagon` Committer/Contributor/Community Base around our core product Apache UserALE.js (Incubating) 2. Refactor core analytic product`Apache Flagon Distill`, as content driver to increase user/committer base 3. Complete the issues highlighted at the`Apache Flagon` Roadmap[1] Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? `Apache Flagon` would like to thank its new Mentors for their enthusiasm and engagement. Where in previous quarters, Flagon had challenges receiving critical mentor guidance through key transitions (e.g., copyright clearance, name change). Our current mentors-`Lewis McGibbney`,`Dave Meikle`,`Tim Allison`,`Furkan Kamaci`-have been extremely helpful in providing guidance, accessible for release review, and in product steerage. How has the community developed since the last report? The community has: * continued improving release processes and code base to expedite future releases[3,4] * continued to generate a wide user base * 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 has begun planning a refactoring of the Distill product which will distribute highly desirable user monitoring content and spur community growth and adoption How has the project developed since the last report? * Completed major updates to website and repositories following name change * 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. * Analytical products are being refactored as of the date of this report 2019-09-22 * Continued attention and improvement in Apache Process and Documentation compliance 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 Apache Flagon UserALE.js (Incubating) 2.0.2 * 2019-07-01 Apache Flagon UserALE.js (Incubating) 2.0.0 * 2019-06-21 Apache 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 or are things falling through the cracks? Things are on track and our community is becoming more self-sufficient. See above comment about improvements in mentorship Signed-off-by: [ ] (flagon)`Lewis John McGibbney` Comments: [ ] (flagon)`Dave Meikle` Comments: [ ] (flagon)`Tim Allison` Comments: [ ] (flagon)`Furkan Kamaci` Comments: [1] https://cwiki.apache.org/confluence/display/FLAGON/Roadmaps [2] https://www.npmjs.com/package/flagon-userale [3] https://dist.apache.org/repos/dist/dev/incubator/flagon/ [4] https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure
Re: Unit Tests Behaving Oddly on new Session Id Storage feature
Hey Rob, Completely agree. See comments in the ticket: https://issues.apache.org/jira/browse/FLAGON-451 I found one npm package that looks promising for a storage mock: dom-storage (see ticket for links). I took a stab at it last night and the night before with very little luck. Pushed some of my work to Flagon-434 and documented findings in the ticket. Can you take a look--I don't think I'm passing the mocked storage into the jsdom env properly. I also played around with the getSessionId function so that it executes from a variable that's passed into getInitialSettings, rather than executed within getInitialSettings itself. Provides a bit better context in error messages. Its clear that jsdom still can't see the storage mock after passing it into the testing framework. Could really benefit from your expertise. Agree the test refactor can happen later. And agree that we should think about modernizing. I've been looking at Jest too. Seems a bit more intuitive and I'd love some nice tidy test coverage metrics. Also seems like we can preserve Chai tests, and Jest ships with jsdom, so maybe we could preserve a lot of our unit tests and just beef up testUtils. I wasn't clear on this: does Jest require that you create your own jsdom constructors, or have they abstracted it away in their own API? I HATE that new jsdom constructor, it drives me bonkers and I haven't figured out how we would pull our resource loader into their custom resource loader, yet (though, I'm still an amateur). Have tried and failed many, many times. Thanks for the help! Josh On 9/12/2019 9:42 AM, Rob Foley wrote: So I think the answer here is to get a sessionStorage mock going. We can either find one and add it to devDependencies or I can whip one up. Upgrading the testing framework is probably worthwhile, but it may be out of scope for this effort. We could investigate Jest, as I've had success with that in the past. Either way, a big test refactor would be in order. Rob On Thu, Sep 12, 2019 at 1:24 AM Joshua Poore wrote: @Rob Following up: I think the issue is that jsdom v9 has no concept of sessionStorage, so when getInitialSettings runs, we have a complete failure of UserALE.js within the jsdom environment. This would affect .options and .log APIs. I haven’t pushed more work on this, just have done some experimentation locally. But, if you re-work the getSessionId function to work outside of the getInitialSettings function and simply pass a variable into it, which is super ugly, you’ll get a new test failure error message indicating that sessionStorage is undefined. I didn’t push this because its not the best implementation that we should be working around. The reason why we’re not seeing the same error in the implementation on branch is because the getSessionId function is called from within getInitialSettings, so we see a report of .options being undefined. I’ve documented this here: https://issues.apache.org/jira/browse/FLAGON-451 < https://issues.apache.org/jira/browse/FLAGON-451>, which is where I’ve moved comments to from issue: https://issues.apache.org/jira/browse/FLAGON-441 < https://issues.apache.org/jira/browse/FLAGON-441> We have two options: there are some patchy things we can do with other modules (described in the ticket), which are still challenging given how we use jsdom.env, OR we can update our testing framework to jsdom v12 (supports sessionStorage) which is also a lot of work. Rob (+ others) — I’m willing to put in some elbow grease on updating to jsdom v12. We may also need to update chai, but frankly our unit-testing framework is out of date and we’ll be faced with harder updates in the future. If I push some commits on this, will you be able to support? Josh On Aug 12, 2019, at 2:21 PM, Joshua Poore wrote: I did some more testing that I’ll document in the next few days. I think the issue is that JSDOM has no concept of window.sessionStorage. Which ever process calls the function I wrote breaks with a Type Error undefined, but if the function is pulled out of the context of getInitialSettings it looks like we get an error specific to sessionStorage. I’ve tried pulling in some add’l npm packages meant to define storage elements, but haven’t had success yet. Then again, haven’t had bandwidth to try really hard yet. Thanks Rob. More findings soon. Joshua Poore On Aug 12, 2019, at 10:23 AM, Rob Foley wrote: I looked through the branch/issue and tried playing around with the code a bit. It seems like the userale script is not being added to the JSDom environment. Our custom resourceLoader (found in test/testUtils.js) is being ran, and is getting the correct content, however at some point JSDom is not actually putting that content into the page. I tried downgrading JSDom to an earlier version with no luck, so I am not sure if there is something else going on. On Sat, Aug 10, 2019 at 12:47 AM Joshua Poore wrote: Rob (or anyone else): any thoughts?
