Re: [REPORT] FLAGON Q2 REPORT FOR REVIEW

OK. Nothing heard. This report has been published to the Board Agenda on schedule for the 4/17 board meeting. Thanks! Josh > On Apr 9, 2024, at 8:44 PM, Joshua Poore wrote: > > For review, Q2 Flagon Quarterly report. I have a draft saved in Whimsey now, > and can make modific

[REPORT] FLAGON Q2 REPORT FOR REVIEW

For review, Q2 Flagon Quarterly report. I have a draft saved in Whimsey now, and can make modifications based on issues, concerns. Let me know if I missed anything. DUE 4/10/2024 V/r Josh ## Description: The mission of Apache Flagon is the creation and maintenance of software related to

Re: [VOTE] Release Apache Flagon UserALEjs 2.4.0

BUMP Hi All, Don’t forget to VOTE for this release! > On Mar 25, 2024, at 10:17 PM, Joshua Poore wrote: > > +1 from me > > Great work everyone! Acceptable release. > > we only need 1 more binding VOTE for a release! > > > [Y] Build and Unit Tests Pass >

Re: [VOTE] Release Apache Flagon UserALEjs 2.4.0-RC02

Updating VOTE subject to RC02 to keep consistency on lists. > On Mar 25, 2024, at 10:17 PM, Joshua Poore wrote: > > +1 from me > > Great work everyone! Acceptable release. > > we only need 1 more binding VOTE for a release! > > > [Y] Build and Unit Tests Pas

Re: [VOTE] Release Apache Flagon Userale 2.4.0-RC01

> Best > > Evan Jones > Website: www.ea-jones.com > > On Thu, Mar 21, 2024 at 9:31 AM Joshua Poore wrote: > >> I wanted to note something here, I should have said yesterday: >> >> You will need to restart the VOTE if you modify source—whe

Re: [VOTE] Release Apache Flagon UserALEjs 2.4.0

+1 from me Great work everyone! Acceptable release. we only need 1 more binding VOTE for a release! [Y] Build and Unit Tests Pass [Y] Integration Tests Pass [Y] Signatures and Hashes Match Keys [Y] LICENSE, and NOTICE Files in Source and Binary Release Packages [Y] LICENSE, and NOTICE are

Re: [VOTE] Release Apache Flagon Userale 2.4.0

are there, not source. PPL can change their votes. New VOTE is cleaner, though. Joshua Poore > On Mar 20, 2024, at 8:30 PM, Joshua Poore wrote: > > Great work folks! Really! Very close… but: > > Currently I’m -1 on this. I see two blocking issues on this, which must

Re: [VOTE] Release Apache Flagon Userale 2.4.0

Great work folks! Really! Very close… but: Currently I’m -1 on this. I see two blocking issues on this, which must be addressed. But, the release is very close. See below for an easy get well plan. Issues: 1. (blocking issue) source distribution (at dist/dev) does not contain all source

Re: [RFC] Consolidation of Apache Flagon Projects into a Monorepo Structure

The idea is growing on me—I’m pretty sure we can generate Pypi and NPM releases from the same repo, different folders. Agree that now is the time to do it before user base on Distill grows. I do think we should run a consensus/community VOTE on this. Let me refresh myself on which ruleset we

Re: Personal feedback while reviewing the projects activity in preparation for the next board meeting

Chris— We interrogated the issue of the ELK license some time ago while we were in the Incubator. Even ELK v 6 raised this question given their introduction of a new license that prohibited CSP’s from distributing. We definitely didn’t want to be confused with a CSP in distributing ELK... Our

[REVIEW] DRAFT Jan 2024 Quarterly Board Report for Review

Hello, Please see the DRAFT Quarterly Board Report for Review and provide any comments by 1700 EST 10 JAN 2024. Thank You! ## Description: The mission of Apache Flagon is the creation and maintenance of software related to thin-client behavioral logging capability useful for business

Re: Updating flagon site with Distill release

Great work on that docker image update, too, Jason! Tests well. PR merged. > On Nov 30, 2023, at 10:53 PM, Joshua Poore wrote: > > Site updates are Live! > > https://flagon.apache.org/releases/ > > I modified some of the links you added to point at the apache m

Re: Updating flagon site with Distill release

need further guidance on pushing that email. Same process as is documented in UserALE.js release process. Great work, Josh > On Nov 29, 2023, at 11:53 PM, Joshua Poore wrote: > > I got you Jason… looking into it now. > >> On Nov 13, 2023, at 4:22 PM, proton_mail

Re: Updating flagon site with Distill release

I got you Jason… looking into it now. > On Nov 13, 2023, at 4:22 PM, proton_mail_bridge > wrote: > > Thank you to all for participating in the first release of Distill! Distill > 0.1.0 is available for download, but before I can send an official notice of > the release, the flagon site needs

Re: Roll-Call for Apache Flagon

Hi Chris— Sorry for the short response yesterday, just want to clarify things a bit: I just want to make sure the board understands that the VOTE in question wasn’t derelict over lack of PMC/community attention. Rather, the release managers are new to the process and didn’t annotate the VOTE

Re: [VOTE] Release Apache Flagon Distill 0.1.0

(and binding PMC) with a RESULT note to cap this thread. Remember we VOTED for RC3 just now—don’t tally across RCs. (We should close those threads—e.g., withdraw the vote for RC1 and RC2, given that the release managers decided to spin new RC rather than proceed with earlier VOTEs). Great work Joshua

Re: [VOTE] Release Apache Flagon Distill 0.1.0

+1 (binding) Excellent Job! I checked: [ X ] Build and Unit Tests Pass [ X ] Signatures and Hashes Match Keys [ X ] LICENSE, and NOTICE Files in Source and Binary Release Packages [ X ] LICENSE, and NOTICE are consistent with ASF and Incubator Policy [ - ] CHANGELOG included with release

Re: [VOTE] Release Apache Flagon Distill 0.1.0

, Josh > On Oct 16, 2023, at 10:34 PM, Joshua Poore wrote: > > GREAT WORK! > > but… -1 (please don’t kill me) (Binding) > > Remember that initial releases are the hardest! > > I checked: > > [ X ] Build and Unit Tests Pass > [ X ] Signatures and Hashes Match Ke

Re: [VOTE] Release Apache Flagon Distill 0.1.0

GREAT WORK! but… -1 (please don’t kill me) (Binding) Remember that initial releases are the hardest! I checked: [ X ] Build and Unit Tests Pass [ X ] Signatures and Hashes Match Keys (checked SHA 512) [ X ] LICENSE, and NOTICE Files in Source and Binary Release Packages [ X ] LICENSE, and

Re: [VOTE] Release Apache Flagon Distill 0.1.0

://github.com/pyenv/pyenv#homebrew-in-macos pyenv/pyenv: Simple Python version management github.com Big thanks to Jason for introducing me to pyenv! -J > On Oct 9, 2023, at 11:26 PM, Joshua Poore wrote: > > +0 for me. > > VERY close, but needs some minor changes to documentati

Re: [VOTE] Release Apache Flagon Distill 0.1.0

and pyenv). Again, excellent release candidate! I think this is so close—just some docs updates. I will continue reviewing src for basic compliance issues. Thanks again for the great work! Josh > On Oct 7, 2023, at 10:01 PM, Joshua Poore wrote: > > I was referring to Python’s own d

DRAFT Quarterly Report for Review

Hi All, I will update this if our Distill 0.1.0 RC candidate passes—please jump into to that thread and peek at the new Python package. Very exciting to see and see new release managers working this! Please find DRAFT report text for review. The report will be submitted 10/11. Plz post any

Re: [VOTE] Release Apache Flagon Distill 0.1.0

atch. We should improve the documentation on this front. > > Best > > Evan Jones > Website: www.ea-jones.com > > > On Sat, Oct 7, 2023 at 8:52 PM Joshua Poore wrote: > >> Hi folks, >> >> If you’re testing the distill package (and amped like me about

Re: [VOTE] Release Apache Flagon Distill 0.1.0

Hi folks, If you’re testing the distill package (and amped like me about this RC!!!), I found that docs on how to call the package into your python IDE or notebook from TestPy are a bit rough. this call works: pip install -i https://test.pypi.org/pypi/ --extra-index-url

Re: Distill release

Actually, we need to do this a little bit differently. There is a template for a release VOTE that we need to follow. Let me send you some notes offline on what information you’ll need for this before we proceed with the VOTE. > On Aug 31, 2023, at 2:44 PM, Evan Jones wrote: > > Hi > > +1 >

Re: [REVIEW] Flagon AUG 2023 Quarterly Report

Report published! > On Aug 9, 2023, at 12:23 AM, Joshua Poore wrote: > > Plz feel free to comment on this—note the deadline to submit is 09 AUG (I’ll > submit in the evening). > >> On Aug 7, 2023, at 12:10 AM, Joshua Poore wrote: >> >> Hi All, >> &

Re: [REVIEW] Flagon AUG 2023 Quarterly Report

Plz feel free to comment on this—note the deadline to submit is 09 AUG (I’ll submit in the evening). > On Aug 7, 2023, at 12:10 AM, Joshua Poore wrote: > > Hi All, > > Please find a draft report for review below. Don’t hesitate to raise any > concerns or make comments: &

[2.4.0] Flagon Release Dev Thread

the ASF process really kicks in. See below for the GH project. https://github.com/apache/flagon-useralejs/projects/9 Apache Flagon UserALE.js v2.4.0 · apache/flagon-useralejs github.com > On Aug 7, 2023, at 12:15 AM, Joshua Poore wrote: > > Would love to work with you on this and sho

Re: [DISCUSS] Flagon UserALE.js Release

Unless breaking changes. So, >> sounds like this suffices. >> >> Time to dig into our release process and testing. Specifically, wondering >> what all additionally will people potentially do manually - since would >> want to work towards systematizing and au

[REVIEW] Flagon AUG 2023 Quarterly Report

Hi All, Please find a draft report for review below. Don’t hesitate to raise any concerns or make comments: ## Description: The mission of Apache Flagon is the creation and maintenance of software related to thin-client behavioral logging capability useful for business analytics, usage

[DISCUSS] Flagon UserALE.js Release

Hi All, It’s high-time we do a UserALE.js release. We’ve had some great community contributions and we should update packages through Apache and NPM distro for security reasons. Given some of the adds to UserALE.js since last release. Given we have substantive new features, but those

Re: Notifications@ ?

> > Sounds great - thanks for digging into getting this cleaned up! > > On Wed, Jun 14, 2023 at 9:06 PM Joshua Poore wrote: > >> from: >> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA=git+-+.asf.yaml+features >> >> The hierar

Re: Notifications@ ?

that otherwise, fall back to the targets that were configured when the repository was set up finally, fall back to dev@project for issues/PRs and commits@ for commits feeling optimistic this works when new lists are up and running. > On Jun 14, 2023, at 11:58 PM, Joshua Poore wrote: >

Re: Notifications@ ?

going to dev@ (I am seeing mods to the titles consistent with asf.yaml). I’ll run another test when the new lists are active. It could require some more experimentation. Bear with us @dev… We’ll get it. > On Jun 14, 2023, at 11:16 PM, Joshua Poore wrote: > > OK, I have requested the Noti

Re: Notifications@ ?

email signatures in replies]. > > > > > On Tue, Jun 13, 2023, 9:12 PM Joshua Poore <mailto:poor...@apache.org>> wrote: >> Hey Austin, >> >> This is looking an awful like the other thread on dev: >> https://lists.apache.org/thread/5374nqhnd

Re: Nix ?

ed do feel free to reachout to collab, and/or > comment on https://github.com/apache/flagon/issues/34 > > On Tue, Jun 13, 2023, 9:00 PM Joshua Poore wrote: > >> Regretfully, I’m not. wish I could be more helpful. >> >>> On Jun 11, 2023, at 6:33 PM, Austin Bennett wr

Re: Notifications@ ?

Hey Austin, This is looking an awful like the other thread on dev: https://lists.apache.org/thread/5374nqhndp46fmv0hzdjp9b6s6v833bj This all involves add additional email lists and then pipeline Github/Gitbox notifications through to different lists. My original proposal: 1) to open a

Re: [GitHub] [flagon-useralejs] poorejc commented on pull request #358: Updated examples to use addCallbacks

I’m not sure that will work, but I’m definitely sure, it won’t work until we configure ask.yaml correctly :) > On Jun 9, 2023, at 10:52 PM, Austin Bennett wrote: > > TEST: > > Does this comment go to GH as well? Otherwise, I think there is a > usability problem with piping issue/pr comments

Re: [DISCUSS] Changes to Apache Flagon Repo

yone have an interest and bandwidth to address? > > On Fri, Jun 9, 2023 at 6:56 PM Joshua Poore wrote: > >> Recent PR from Austin raised an excellent point about the current >> structure of our Apache/Flagon repo. >> >> Presently, this repo contains: >>

[DISCUSS] Changes to Apache Flagon Repo

Recent PR from Austin raised an excellent point about the current structure of our Apache/Flagon repo. Presently, this repo contains: 1. Website assets 2. Integration examples (e.g., ELK) Keeping this repo together as a jumble of top level “utilities” does prevent us from improving automation

Re: managing GitHub messages on threads

> ... why opt all subscribers of dev list to get that traffic, when there is > another way to get that info for anyone that wants? > > > > On Mon, Jun 5, 2023 at 9:18 PM Joshua Poore <mailto:poor...@apache.org>> wrote: >> Hi Folks, >> >> I wanted to raise

managing GitHub messages on threads

Hi Folks, I wanted to raise that we’ve been (slowly) looking to address a sensible way to manage the “rage” that GitHub adds to our lists. We don’t want an inundation of GitHub comms on the lists to dissuade usage of the lists. Here’s my proposal: 1) to open a ‘maintenance’ list for flagon

Fwd: [ANNOUNCE] Jira Account Cleanup for Non-ASF Users

FYSA Joshua Poore Begin forwarded message: > From: Chris Lambertus > Date: April 26, 2023 at 4:12:39 PM EDT > To: annou...@infra.apache.org > Subject: [ANNOUNCE] Jira Account Cleanup for Non-ASF Users > Reply-To: us...@infra.apache.org > >  > Hi folks, > >

Reminder: Flagon Git Repo Names Have Been Reassigned out of Incubator Namespace

ALCON (esp committers)— Reminder that our transition from incubator to TLP at ASF also means that some of our infrastructure is migrating to a different namespace. Most notably, our .git and GitHub resources are NO LONGER @ incubator-flagon-[product]. We are NOW @ flagon-[product]. On Github,

FLAGON IS A TOP LEVEL PROJECT

All, I’m so excited to tell you that the ASF Board unanimously approved the resolution to establish Apache Flagon as an ASF Top Level Project. HUGE thanks to our community—PMC, committers, contributors, users. Apache projects are built from communities. Thank You! I also want to congratulate

Re: [DISCUSS] Flagon CI

; : "~1.0.20" } } > > Read more here: > > https://docs.npmjs.com/cli/v6/configuring-npm/package-json > <https://docs.npmjs.com/cli/v6/configuring-npm/package-json> > > On Fri, Feb 3, 2023 at 6:23 PM, Joshua Poore <mailto:poor...@apache.org>> wrote: &

Re: [DISCUSS] Flagon CI

added a quick badge to Readme to indicate Node.js support—up on test. Comments? https://github.com/apache/incubator-flagon-useralejs/tree/test > On Feb 3, 2023, at 9:23 PM, Joshua Poore wrote: > > Complete agreement with that! > > With nothing else heard this week, I’ll bump

Re: [DISCUSS] Flagon CI

L 11 Nov 2023 [ 1 ]. After that point ( once EOL > ) software is increasingly dangerous to continue to use, not to mention > harder to support. > > > [1] https://nodejs.org/en/blog/announcements/nodejs16-eol/ > <https://nodejs.org/en/blog/announcements/nodejs16-eol/> &

Re: 2023 Summer of Code

That’s a great idea! > On Feb 2, 2023, at 4:46 PM, Austin Bennett wrote: > > https://summerofcode.withgoogle.com/ > > There are possibilities to take on students via GSOC under the ASF > umbrella. I have mentored for GSOC in the past. Putting on Flagon's > radar, in case interested in

Re: [DISCUSS] Flagon CI

Silly me—I forgot to couch this in the context of UserALE.js! For the avoidance of doubt... > On Jan 30, 2023, at 11:37 PM, Joshua Poore wrote: > > All, > > I’ve been doing some simple dependency management—mostly for security, and to > stay on top of modernization

[DISCUSS] Flagon CI

All, I’ve been doing some simple dependency management—mostly for security, and to stay on top of modernization. We’re about at that time when some of the versions of Node.js that we test against are nearing (or past) the end of life [1]. Consistent with [1], I think we should be testing and

JAN 23 Podling Report

Hello, Please quickly review our JAN ’23 Podling Report… not much to report. Oh wait! We passed our Resolution to graduate as TLP! That’s in there :) https://cwiki.apache.org/confluence/display/INCUBATOR/January2023#flagon

Re: Graduation VOTE has passed at the IPMC

Am so excited that I forgot the RESULT thread link https://lists.apache.org/list.html?gene...@incubator.apache.org > On Dec 8, 2022, at 9:14 PM, Joshua Poore wrote: > > All, > > Can’t tell you how happy I am to inform the Flagon community that our VOTE to > Graduate F

Graduation VOTE has passed at the IPMC

All, Can’t tell you how happy I am to inform the Flagon community that our VOTE to Graduate Flagon from the ASF Incubator as a TOP LEVEL PROJECT has PASSED!!! Next step is that our Resolution is passed to the ASF Board! I think I’ll celebrate by updating our dependencies :) Thanks to

Re: Web Extension updates

, but there is scenario in which we have to choose which build is on master. I think we should go with Chrome. Joshua Poore > On Nov 6, 2022, at 5:35 PM, Austin Bennett wrote: > > Looks like Chrome might be slightly more generous on the deprecation > timeline: https://developer.chr

Re: Web Extension updates

lity, i would expecr changes >> needed to support to be not especially contentious even if involved >> significant modification. >> >> It sounds like this can be done without breaking things for our users, if >> that's the case then not concerned about version n

Re: [RESULT][VOTE] Graduation of Flagon Project

Just adding the complete tally to this thread— RESULT is +7 in favor of Graduation from the Community; +2 Binding IPMC from Mentors The breakdown is as follows: + 1 [7]: Joshua Poore Gedd Johnson Amir Ghaemi Furkan KAMACI (IPMC/binding) Evan Jones Austin Bennett Lewis Mcgibbney (IPMC

Re: [ VOTE ] Graduation of Flagon Project

Emphatic +1 for me. Sincerely, Josh > On Oct 31, 2022, at 5:13 PM, lewis john mcgibbney wrote: > > +1 > > On Mon, Oct 31, 2022 at 09:31 Austin Bennett > wrote: > Hi Flagon Community, > +1 > Given recent discussions around the graduation status of the project, it is

Re: [DISCUSS] Graduate Apache Flagon

Hi Austin, Yeah… see convo on private. Was planning on community VOTE next week. Or you can initiate. Joshua Poore > On Oct 25, 2022, at 3:54 PM, Austin Bennett > wrote: > > Looks like community consensus is for graduation. > > Is next step a formal vote? Or, somethi

[DISCUSS] Graduate Apache Flagon

Hi All, I’m initiating this DISCUSS thread to talk through the communities perspective (at this point in time) on Graduation as a Top Level project. Flagon has tried to Graduate twice before first in 2018, and then in 2020. Each time, we didn’t get any strong blockers, but some tickets that we

[DISCUSS] OCT Podling Report -- ATTN Mentors

Hi All, IPMC confirmed that we need to report this month, too. Boring report… Notwithstanding, please find the latest Flagon podling report: https://cwiki.apache.org/confluence/display/INCUBATOR/October2022#flagon

Fwd: [RESULT] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling

he/incubator-flagon-distill/tree/distill_server_legacy <https://github.com/apache/incubator-flagon-distill/tree/distill_server_legacy> best, Josh > Begin forwarded message: > > From: Joshua Poore > Subject: [RESULT] Accept ICLA and Software Grant from UMD Into the Apache > Fl

Re: [DISCUSS] Flagon SEP Quarterly Report Up for Review

eck the > report. It may be the reason for other mentors as well. > > Kind Regards, > Furkan KAMACI > > On Thu, Sep 15, 2022 at 1:26 AM Furkan KAMACI > wrote: > >> Hi Joshua, >> >> Thanks for preparing the report! I will check it. >> >> Kind

[DISCUSS] Flagon OCT Quarterly Report Up for Review

Hi Folks, It looks like our JUL report wasn’t signed off on (no reason). We were asked to report SEPT, however, I missed that window. I have therefore prepared an OCT report well in advance of deadline. Please find the report here:

Re: [ DISCUSS ] Dependabot PRs?

ms something a GH Action could do [ after tests pass ] -- without > having spent about any time with this thought, it looks like it could parse > updated package-lock to get versions and then replace/update those versions > in package.json, and run tests accordingly. > > > >

Re: Proposal to include Docs Meta Data in based UserALE.js

FYSA— have opened up a dev branch for this issue: https://github.com/apache/incubator-flagon-useralejs/tree/doc-logging-wip > On Aug 29, 2022, at 9:41 PM, Joshua Poore wrote: > > Hi All, > > Great thread and proposal on GitHub from some users. Looking for community >

Proposal to include Docs Meta Data in based UserALE.js

Hi All, Great thread and proposal on GitHub from some users. Looking for community thoughts. Thread: https://github.com/apache/incubator-flagon-useralejs/issues/266 Jist: There is interest in configuring a user-facing config (via options api) to automatically log the .dataset property of

Web Extension updates

All, Looking for comments on this: I think there are only few end users that actually use our Web Extension, however, it’s a pretty valuable tool in user testing uninstrumented applications. Presently, our WebExtension (on Master) is Manifest v2. However, as you may be aware Chrome is

Re: [ DISCUSS ] Dependabot PRs?

Dependabot updates package-file not package.json. When I clear these updates, i like to update package.json and test for collisions. I agree dependabot is just alerting us to updates. Proposal: why don’t we have dependabot merge changes into the test branch. then we can update package.json in

Maintenance PR awaiting review

As per a GREAT discussion on dev—rather than just pushing maintenance commits directly to master, I made a pull request for a number of package updates that fix A LOT of vulnerabilities that have cropped up. PR is here: https://github.com/apache/incubator-flagon-useralejs/pull/279

Re: [DISCUSS] What Reviews Required-or-Needed / When OK to merge?

Great thread! RE: > *I assume we ultimately need a committer to review the work of > anon-committer ahead of merge ( since someone with permissions > eventuallyhas to actually accept/merge/commit the code ). In general, is > onereviewer/committer sufficient?* > IMO, yes, one reviewer who is also

[RESULT] Accept UMD Software Grant into Apache Flagon

of the generous donation through our Notice File! -J > On Jun 4, 2022, at 10:00 PM, Lewis John McGibbney wrote: > > Just VOTE’d. > Excellent community building. > lewismc > > On Sat, Jun 4, 2022 at 17:42 Joshua Poore <mailto:poor...@apache.org>> wrote: > Feel free t

Re: [DISCUSS] Accept UMD Software Grant into Apache Flagon

Feel free to continue discussing. However, I have initiated a VOTE on private@ to accept the CCLA and Software Grant. > On May 31, 2022, at 9:49 PM, Joshua Poore wrote: > > Hi All, > > I’m very excited to say that the University of Maryland has executed an CCLA > w

[DISCUSS] Accept UMD Software Grant into Apache Flagon

Hi All, I’m very excited to say that the University of Maryland has executed an CCLA with Software Grant for the Apache Flagon project! The Software Grant encompasses a refactor of the Apache Flagon Distill product, which has been deprecated for a few years now [1] This Grant includes ~150

[ANNOUNCEMENT] Austin Bennett added as Apache Flagon Committer and PPMC

All-- I am pleased to Announce that Austin Bennet has been added as a Committer and PPMC member following a passing VOTE at the PPMC level. Austin has participated in the Flagon community for a few years, and has been active in discussions, governance VOTEs, and Release VOTEs. Austin is

Flagon Related Publication RE Distill and Analytics

Hi All, For your reading enjoyment: My team at University of Maryland presented a paper on our work on Distill to the 2022 AAAI Spring Symposium on AI Engineering. Our paper is now available as a proceedings here: http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=884337

[RESULT] Release Apache Flagon (Incubating) UserALE.js 2.3.0

me >> - DISCLAIMER exists >> - LICENSE and NOTICE are fine >> - No unexpected binary files >> - Checked PGP signatures >> - Checked checksums >> - Code compiles and tests successfully run >> >> Kind Regards, >> Furkan KAMACI >> >> On Thu,

FYSA Deprecated Flagon Projects

As per actions recommended by IPMC in advance of Graduation [1], I have submitted an INFRA ticket [2] to retire deprecated an unmaintained Flagon products, which are as follows: https://gitbox.apache.org/repos/asf/incubator-flagon-stout.git

Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0

org>). I’d be willing to sponsor a VOTE for you to become an Apache Committer and Flagon PPMC member. This thread isn’t the right place to discuss, though. > On May 10, 2022, at 5:10 PM, Joshua Poore wrote: > > Austin, > > Because we’re still a podling, PPMC (Podling Project

DRAFT MAY22 FLAGON PODLING REPORT UP

So sorry this is late, but ready for MENTOR Sign Off https://cwiki.apache.org/confluence/display/INCUBATOR/May2022#flagon

Fwd: [VOTE] Release Apache Flagon UserALE.js 2.3.0

FYSA: VOTE pushed to IPMC. We need +2 Binding to release. > Begin forwarded message: > > From: Joshua Poore > Subject: [VOTE] Release Apache Flagon UserALE.js 2.3.0 > Date: May 10, 2022 at 5:18:00 PM EDT > To: gene...@incubator.apache.org > > Hello IPMC— > > Pl

Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0

> According to [3] "The only time when a PPMC member’s vote is binding is for > the addition of new PPMC members and committers. Release votes are only > binding for IPMC members." ... so that seems like for a release the only > binding vote cast has been @Furkam. As I see it

Actions Slip

Hi folks, I’m working the report now and will pass the vote thread up to incubator. Apologies for the delays—kids have COVID atm and struggling a bit keeping up.

Re: Podling Flagon Report Reminder - May 2022

Slipped my notice. I can get it in on or after the 9th. Joshua Poore > On May 3, 2022, at 7:15 PM, Furkan KAMACI wrote: > > Hi, > > Is there anybody working on the report? Feel free to ask if you need help. > > Kind Regards, > Furkan KAMACI

Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0

Bump! > On Apr 23, 2022, at 1:32 PM, Joshua Poore wrote: > > Reminder! Please VOTE for this release!! > > Joshua Poore > > >> On Apr 13, 2022, at 5:16 PM, Furkan KAMACI wrote: >> >> Hi, >> >> +1 from me. >> >> I checked:

Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0

Reminder! Please VOTE for this release!! Joshua Poore > On Apr 13, 2022, at 5:16 PM, Furkan KAMACI wrote: > > Hi, > > +1 from me. > > I checked: > > - Incubating in name > - DISCLAIMER exists > - LICENSE and NOTICE are fine > - No unexpected bin

Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0

ASF and Incubator > Policy > [x ] CHANGELOG included with release distribution > [x ] All Source Files Have Correct ASF Headers > [x ] No Binary Files in Source Release Packages > > - Gedd Johnson > > On Sun, Apr 10, 2022 at 12:38 PM Joshua Poore wrote: > >&g

Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0

aders (ran RAT tool: only .gitignore and .babelrc (json) exclude headers) [ x ] No Binary Files in Source Release Packages (except for supporting .png files) > On Apr 10, 2022, at 1:36 PM, Joshua Poore wrote: > > Please VOTE on the Apache Flagon (Incubating) UserALE.js 2.3.0 Releas

[VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0

Please VOTE on the Apache Flagon (Incubating) UserALE.js 2.3.0 Release Candidate # 01. About Flagon: http://flagon.incubator.apache.org/ This Minor release includes: Fixes issue in autostart configurations and start(), stop() export usage Adds additional unit tests for autostart configurations

UserALE.js 2.3.0-RC-01 branch open

Hello- Currently even with test, not merged with Master yet. Would appreciate any additional eyes on. Have modified versioning, docs, changlog, etc. Testing now for licensing, and NPM packaging prior to moving to package dist.dev UserALE.js testing framework:

Re: [DISCUSS] Prepping for New Minor release of UserALE.js (Incubating)

Nothing else heard RE RC label—closing discussion. > On Apr 5, 2022, at 11:42 PM, Joshua Poore wrote: > > Inline responses: > >> On Apr 5, 2022, at 4:11 PM, Gedd Johnson wrote: >> >> Sounds good Josh. I don't have a strong opinion on calling it 2.2.1 or &g

Re: [DISCUSS] Prepping for New Minor release of UserALE.js (Incubating)

g the project on the other side… More on that soon—have to read up on the processes Apache side for accepting gifts and CCLAs into the project. > > Regards, > Gedd > > On Mon, Apr 4, 2022 at 9:12 PM Joshua Poore wrote: > >> Good PR just closed @ source [1]. Huge than

[Mentors] Q1 2022 Flagon Report

All, Please find the Q1 2022 Flagon Report here: https://cwiki.apache.org/confluence/display/INCUBATOR/January2022#flagon Feel free to review and provide comments to me at earliest soonest. NLT 01/07/2022. Mentors, please indicate your sign-off NLT 01/07/2022. In sum, the big news this

OCT 2021 FLAGON PODLING REPORT

Hi All, Slow-ish quarter, but the OCT 2021 FLAGON PODLING Report is prepared and ready for review (and signoff). Please find it here: https://cwiki.apache.org/confluence/display/INCUBATOR/October2021#flagon As a general community update: I am pleased to report that I have been working with a

AUG 2021 FLAGON Report Up

Hello, Been a slog this quarter. Apologies for the delay in the report. Mentors—please review, comment and sign. I’ll be able to make changes needed. https://cwiki.apache.org/confluence/display/INCUBATOR/August2021 Josh

Re: Podling Flagon Report Reminder - August 2021

Hi Furkan, I have time to do it tomorrow. Haven’t forgotten. Joshua Poore > On Aug 7, 2021, at 10:22 AM, Furkan KAMACI wrote: > > Hi, > > Is there anybody working on the report? Feel free to ask if you need help. > > Kind Regards, > Furkan KAMACI > >&g

[RESULT] Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.2.0

es Match Keys >>>> [X] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release >>>> Packages >>>> [X] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and >> Incubator >>>> Policy >>>> [X] CHANGELOG included with release

Re: [VOTE] Release Apache Flagon (Incubating) 2.2.0

Echoing Gedd here—would be great to get +1 binding vote from Mentors prior to moving up to Incubator IPMC. Joshua Poore > On Jun 8, 2021, at 2:48 PM, Gedd Johnson wrote: > > Hi all, > > Just a reminder to VOTE on RC3 mentioned in this thread. We are currently > sitting

Re: [VOTE] Release Apache Flagon (Incubating) 2.2.0

+1 RC3 Looks great! Licenses and headers are resolved. I added CHANGELOG to svn dev repo (top level; Changelog is already included in source files). That doesn’t break the RC candidate, or require re-roll. Woohoo! Great work Gedd!! I checked: [X] Build and Unit Tests Pass [X] Integration

[CANCELLED] Re: [VOTE] Release Apache Flagon (Incubating) 2.2.0

-1 Sorry, it looks like there is still a missing license. Working it now, and will add a new RC tag and branch. Here’s my RAT Run: the .babelrc file is about the only file that doesn’t need a license (its config for build and will parse license). The /example/log-label-example/index.html is

  1   2   3   4   5   6   7   >