Re: [VOTE] Release Apache Flagon Distill 0.1.0
Hi, +1 from me too! Kind regards, Furkan Kamaci On Sat, Oct 21, 2023 at 9:30 PM Austin Bennett wrote: > Missed who was PMC/not [ thanks for counting @ > jason_...@protonmail.com.invalid If others not able, I should be able to > find a little time to dig in later this week; roll-call also made it sound > like there were a few others active, so must imagine we can get the > requisite VOTEs. > > > > On Fri, Oct 20, 2023 at 7:49 AM proton_mail_bridge > wrote: > >> Let me add my +1. And while we have 4 yes votes, only 2 are binding. So >> one additional PMC yes vote is still required. >> >> Apache Phone Book <https://people.apache.org/phonebook.html?pmc=flagon> >> people.apache.org <https://people.apache.org/phonebook.html?pmc=flagon> >> [image: favicon.ico] >> <https://people.apache.org/phonebook.html?pmc=flagon> >> <https://people.apache.org/phonebook.html?pmc=flagon> >> >> >> - Jason >> >> On Oct 18, 2023, at 2:55 PM, Austin Bennett wrote: >> >> Great, thanks, congratulations -- I haven't dug in, yet, but sufficient >> votes are in! Naturally, gotta wait the 72 hours, but seems the release >> likely to go out! >> >> On Wed, Oct 18, 2023 at 11:42 AM Amir Ghaemi wrote: >> >> Hi all, >> >> +1 >> Great work! >> >> [✓] Build and Unit Tests Pass (On Windows - Python 3.10) >> [✓] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release >> Packages >> [✓] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and Incubator >> Policy >> [✓] All Source Files Have Correct ASF Headers >> [ ] No Binary Files in Source Release Packages >> [ ] Signatures and Hashes Match Keys >> [ ] CHANGELOG included with release distribution >> >> Best, >> *Amir M. Ghaemi* >> >> >>
Re: Roll-Call for Apache Flagon
Hi, I’m also willing and able. Kind regards, Furkan Kamaci On Sat, Oct 21, 2023 at 8:07 PM Rob Foley wrote: > I am still willing to contribute, though most of my contributions are > more on the legacy side at this point. > > Rob > > On 10/21/2023 12:26 PM, jason_y54 wrote: > > Hey Chris, > > > > I’m also willing and able. > > > > - Jason > > > > On Sat, Oct 21, 2023 at 10:45 AM, Evan Jones <[evan.a.jon...@gmail.com > ](mailto:On Sat, Oct 21, 2023 at 10:45 AM, Evan Jones < wrote: > > > >> Hi Chris, > >> > >> Willing and able. > >> > >> Best > >> > >> Evan Jones > >> Website: www.ea-jones.com > >> > >> On Sat, Oct 21, 2023 at 10:10 AM Christofer Dutz < > christofer.d...@c-ware.de> > >> wrote: > >> > >>> Hi all, > >>> > >>> I was tasked at the last board report to pursue a roll call for Apache > >>> Flagon after we saw that a VOTE thread has currently been open for > over 2 > >>> weeks with only one vote (which was “-0”). > >>> Also seeing that only 2 people have done any commits in the last few > >>> months feels rather strange for a project that has been a TLP for only > 7 > >>> months now. > >>> > >>> Please reply to this thread if you’re still willing and able to > contribute > >>> to this project. > >>> > >>> Thanks, > >>> Chris > >> > >
Re: JAN 23 Podling Report
Hi Joshua, Thanks, already signed :) Kind regards, Furkan Kamaci On Tue, Jan 10, 2023 at 5:41 PM Joshua Poore wrote: > 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: [ VOTE ] Graduation of Flagon Project
Definitely +1! On Tue, Nov 1, 2022 at 7:58 PM Amir Ghaemi wrote: > +1 > > Best Regards, > *Amir M. Ghaemi* > > > On Tue, Nov 1, 2022 at 7:06 AM Gedd Johnson wrote: > > > +1 > > > > Best, > > Gedd Johnson > > > > On Mon, Oct 31, 2022 at 23:22 Joshua Poore wrote: > > > > > 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 time to work through the process. We have had a recent discussion > > >> on-list, and consensus seems to be in favor of graduation. The next > > step > > >> seems to be a recommendation that we make an official VOTE, per: > > >> https://incubator.apache.org/guides/graduation > > >> .html#community_graduation_vote > > >> > > >> *Please VOTE* for the actual record. I will also let the Incubator > know > > >> the vote is occurring [ per the link above ], and imagine that I will > > tally > > >> the votes later on Friday the 4th to allow for >= 72 hours; we'll see > > how > > >> this thread goes. > > >> > > >> Per https://www.apache.org/foundation/voting.html* ideally votes will > > >> be +1, 0, or -1* And, as I understand it, only IPMC votes are binding, > > >> as found in https://incubator.apache.org/guides/participation.html. > > >> > > >> > > >> Please consider this my +1. > > >> > > >> The existing community has demonstrated addressing the requirements as > > >> found in the incubator guidelines for graduation. Graduation is an > > >> important milestone signaling project maturity, and a great step > towards > > >> ongoing growth and evolution. > > >> > > >> Cheers - > > >> Austin > > >> > > >> -- > > > http://home.apache.org/~lewismc/ > > > http://people.apache.org/keys/committer/lewismc > > > > > > > > > > > >
Re: [RESULT] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling
That's great. Thanks Joshua! On Tue, Sep 27, 2022 at 6:02 AM Austin Bennett wrote: > Great, thanks josh! > > On Mon, Sep 26, 2022, 7:23 PM Joshua Poore wrote: > > > Good news! > > > > I think we’re clear on all our actions following the CCLA and SW Grant. > > > > I’ve pushed the SW grant to the Apache Flagon Distill repo ( > > https://github.com/apache/incubator-flagon-distill < > > https://github.com/apache/incubator-flagon-distill>). > > > > I’ve also started on some of our overhead actions (updating copyright, > > headers, etc.) on a dev branch: > > https://github.com/apache/incubator-flagon-distill/tree/license_headers > < > > https://github.com/apache/incubator-flagon-distill/tree/license_headers> > > > > I’ve preserved our legacy code on another branch: > > > https://github.com/apache/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 Flagon Podling > > > Date: September 26, 2022 at 10:18:23 PM EDT > > > To: gene...@incubator.apache.org > > > Reply-To: gene...@incubator.apache.org > > > > > > The VOTE is closed. Thanks to all those who VOTE’d! > > > > > > The RESULTS are as follows: > > > > > > [4] +1 (3 IPMC Binding) > > > [0] 0 > > > [0] -1 > > > > > > The consensus VOTE to accept the SW Grant from UMD for the Distill > > refactor has passed. > > > > > > Some additional clarification following from John’s comments: > > > > > > 1. UMD has granted the copyright to ASF (this is explicitly stated in > > our IP disclosure case through UMD Ventures)--those of us that can commit > > on behalf of UMD are changing the copyright statement to appropriately > > reflect ASF. > > > 2. This is a substantial SW gift, but there remains much overhead > before > > an official ASF release—including ensuring appropriate headers are on > every > > source file. > > > 3. .ipynb are json, however, it’s easy enough to include an ASF header > > in a cell at the top of notebook. Notwithstanding, we’ll ask around and > see > > if there is a (better) best practice. > > > > > > Thanks! > > > > > > Josh (on behalf of Flagon PPMC) > > > > > >> On Sep 17, 2022, at 10:11 AM, John D. Ament > > wrote: > > >> > > >> Here's my +1 on the code > > >> > > >> There's a few notes: > > >> - I would recommend the podling add some kind of reference to this > > clause > > >> in their NOTICE file: Copyright 2022 The Applied Research Laboratory > for > > >> Intelligence and Security (ARLIS) (see [1]) > > >> - There's many files missing any headers. I think it's safe to assume > > they > > >> follow the same license since there is a LICENSE file at the root. I > > >> couldn't find any evidence that the files missing headers were > > copy/pasted > > >> from other repositories. > > >> - For files like the .ipynb files, I don't think there's a way to > > >> explicitly add a license header (since they're JSON files). You may > > want > > >> to consult with legal on how to add license file references for them. > > >> > > >> > > >> [1]: > > >> > > > https://github.com/UMD-ARLIS/incubator-flagon-distill/blob/distill_toolkit_refactor/NOTICE > > >> > > >> > > >> On Fri, Sep 16, 2022 at 11:12 AM John D. Ament > > > >> wrote: > > >> > > >>> Hey Josh, > > >>> > > >>> Thanks for the clarification, I found the thread from Craig. For > > future > > >>> reference, you shouldn't be voting on accepting a CCLA and/or SGA. > > >>> Procedure wise, this doesn't make sense. You're voting on accepting > a > > code > > >>> donation, and it's just that code donations from the foundation's > > >>> standpoint require a SGA. The vote to accept the donation happens on > > the > > >>> podling's private list. I think we're in alignment up to that point > > (other > > >>> than the fact that the vote on the private list looks a bit off). > > >>> > > >>> To be 100% clear on the scope, you're looking for a third vote to > view > > the > > >>> repo at [1] and confirm whether or not the content within is > compliant > > to > > >>> be imported into a repository hosted by the ASF? Where I'm concerned > > with > > >>> the original vote, you're including in scope adding 5 new committers > > (which > > >>> aren't named in the vote thread) to the project. It's not apparent > > that > > >>> both are in scope, the vote to add committers should be separate from > > the > > >>> vote to add code to the repository (usually you would import the code > > >>> first, then vote to add the committers to the project). Do keep in > > mind > > >>> since these are your coworkers you're not building a diverse > community > > of > > >>> committers. > > >>> > > >>> I'm including a few links to show a bit better how TLPs have handled > > this > > >>> before to give a little better picture. I'll take a deeper look in > the >
Re: [DISCUSS] Flagon SEP Quarterly Report Up for Review
Hi, Thanks Joshua! I've signed off the report. Kind Regards, Furkan KAMACI On Thu, Sep 15, 2022 at 5:28 AM Joshua Poore wrote: > No worries, Furkan! You and the other mentors have been fantastic. No > biggie—I think we’re in good faith with the Incubator. > > FYSA—Justin and Calvin said there is still time to submit for SEPT and > moved the report from OCT>SEP > > Find it here: > https://cwiki.apache.org/confluence/display/INCUBATOR/September2022#flagon > < > https://cwiki.apache.org/confluence/display/INCUBATOR/September2022#flagon > > > > Same report. > > Thanks again, Furkan! > > Josh > > > On Sep 14, 2022, at 6:29 PM, Furkan KAMACI > wrote: > > > > Hi, > > > > Btw, I was on summer vacation and did not have a chance to check 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 Regards, > >> Furkan KAMACI > >> > >> On Thu, Sep 15, 2022 at 12:35 AM Joshua Poore > wrote: > >> > >>> 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: > >>> > https://cwiki.apache.org/confluence/display/INCUBATOR/October2022#flagon > >>> > >>> Welcome to receive any comments. > >>> > >>> Best, > >>> > >>> Josh > >> > >> > >
Re: [DISCUSS] Flagon OCT Quarterly Report Up for Review
Hi, Btw, I was on summer vacation and did not have a chance to check 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 Regards, > Furkan KAMACI > > On Thu, Sep 15, 2022 at 12:35 AM Joshua Poore wrote: > >> 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: >> https://cwiki.apache.org/confluence/display/INCUBATOR/October2022#flagon >> >> Welcome to receive any comments. >> >> Best, >> >> Josh > >
Re: [DISCUSS] Flagon OCT Quarterly Report Up for Review
Hi Joshua, Thanks for preparing the report! I will check it. Kind Regards, Furkan KAMACI On Thu, Sep 15, 2022 at 12:35 AM Joshua Poore wrote: > 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: > https://cwiki.apache.org/confluence/display/INCUBATOR/October2022#flagon > > Welcome to receive any comments. > > Best, > > Josh
Re: [ANNOUNCEMENT] Austin Bennett added as Apache Flagon Committer and PPMC
Hi Austin, Welcome on board! Kind Regards, Furkan KAMACI On Fri, May 27, 2022 at 6:04 PM Austin Bennett wrote: > Thanks, all -- glad to be voted in to be even more a part of the community, > and looking forward to seeing the things we will develop! > > > > > On Thu, May 26, 2022 at 7:42 PM Joshua Poore wrote: > > > 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 already a committer with ASF within the Apache Beam community. > > He brings with him a rich set of ideas for our project and deep > experience > > in FOSS development, the Apache Way. We welcome his help in development, > > steerage, and governance! > > > > PPMC is working with mentors to complete onboarding > > > > Welcome to full-tilt Flagon, Austin! And Thank You! > > > > Best, > > > > Josh (PPMC) > > > > > > >
Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0
Hi, We have 3 binding votes (Joshua Poore, Gedd Johnson, Furkan KAMACI) and 1 non-binding vote (Austin Bennett). So, the vote has passed in terms of the ASF rules. Kind Regards, Furkan KAMACI On Sun, May 8, 2022 at 3:21 AM Austin Bennett wrote: > At least 72 hours have passed :-) > > But ... doesn't look like received 3 +1 votes from PPMC; was there enough > for this to pass? I can look up but don't recall off head the incubating > project guidelines. > > > > > On Sat, May 7, 2022 at 3:52 PM Furkan KAMACI > wrote: > > > Hi, > > > > Is this voting closed or not? > > > > Kind Regards, > > Furkan KAMACI > > > > On Tue, May 3, 2022 at 10:04 PM Austin Bennett < > > whatwouldausti...@gmail.com> > > wrote: > > > > > Based on what has been checked, it looks good to me, so +1 ( > non-binding > > > ). > > > > > > A process questions to ensure things get covered, long term: > > > > > > * is there a concrete list for things actually desired to be checked as > > > part of release process ( I see some things, ex: > > > https://github.com/apache/incubator-flagon/tree/master/release and > some > > > info https://flagon.incubator.apache.org/releases/ and > > > > > > > > > https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure > > > but not an actual list of things we want to ensure are covered by a > > machine > > > or human )? > > > > > > Also, I don't recall -- Does the project have a targeted release cycle > ( > > > ex: every month, quarter, etc ), or just cutting releases as desired? > > That > > > might help inform what all checks are worth automating. > > > > > > > > > On Tue, May 3, 2022 at 11:43 AM Joshua Poore > > > wrote: > > > > > > > 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 < > furkankam...@gmail.com> > > > > wrote: > > > > >> > > > > >> Hi, > > > > >> > > > > >> +1 from me. > > > > >> > > > > >> I checked: > > > > >> > > > > >> - Incubating in name > > > > >> - 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 Wed, Apr 13, 2022 at 11:54 PM Joshua Poore < > poor...@apache.org> > > > > wrote: > > > > >>> > > > > >>> REMINDER PPMC, Mentors—please don’t forget to VOTE for this > > release!! > > > > >>> > > > > >>> This release contains some great PR work from our community!!! > > > > >>> > > > > >>>>> On Apr 11, 2022, at 12:05 PM, Gedd Johnson < > uncleg...@apache.org > > > > > > > wrote: > > > > >>>> > > > > >>>> [x] +1, let's get it released!!! > > > > >>>> > > > > >>>> [x ] Build and Unit Tests Pass > > > > >>>> [x ] Integration Tests Pass > > > > >>>> [x ] "Incubating" in References to Project and Distribution File > > > Names > > > > >>>> [x ] Signatures and Hashes 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 distribution > > > > >>>> [x ] All Source Files Have Correct ASF Headers > > > > >>>> [x ] No Binary Files in Source Releas
Re: [VOTE] Release Apache Flagon (Incubating) UserALE.js 2.3.0
Hi, Is this voting closed or not? Kind Regards, Furkan KAMACI On Tue, May 3, 2022 at 10:04 PM Austin Bennett wrote: > Based on what has been checked, it looks good to me, so +1 ( non-binding > ). > > A process questions to ensure things get covered, long term: > > * is there a concrete list for things actually desired to be checked as > part of release process ( I see some things, ex: > https://github.com/apache/incubator-flagon/tree/master/release and some > info https://flagon.incubator.apache.org/releases/ and > > https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure > but not an actual list of things we want to ensure are covered by a machine > or human )? > > Also, I don't recall -- Does the project have a targeted release cycle ( > ex: every month, quarter, etc ), or just cutting releases as desired? That > might help inform what all checks are worth automating. > > > On Tue, May 3, 2022 at 11:43 AM Joshua Poore > wrote: > > > 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: > > >> > > >> - Incubating in name > > >> - 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 Wed, Apr 13, 2022 at 11:54 PM Joshua Poore > > wrote: > > >>> > > >>> REMINDER PPMC, Mentors—please don’t forget to VOTE for this release!! > > >>> > > >>> This release contains some great PR work from our community!!! > > >>> > > >>>>> On Apr 11, 2022, at 12:05 PM, Gedd Johnson > > wrote: > > >>>> > > >>>> [x] +1, let's get it released!!! > > >>>> > > >>>> [x ] Build and Unit Tests Pass > > >>>> [x ] Integration Tests Pass > > >>>> [x ] "Incubating" in References to Project and Distribution File > Names > > >>>> [x ] Signatures and Hashes 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 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: > > >>>> > > >>>>> +1 (PPMC) > > >>>>> > > >>>>> I checked: > > >>>>> > > >>>>> [ x ] Build and Unit Tests Pass > > >>>>> [ x ] Integration Tests Pass (Example Page, Webpack (NPM), React > > (NPM) > > >>>>> [ x ] "Incubating" in References to Project and Distribution File > > Names > > >>>>> [ x ] Signatures and Hashes 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 distribution > > >>>>> [ x ] New source code (React app, OpenTelemetry Ex) has compatible > > >>>>> licenses (ALv2, MIT) > > >>>>> [ x ] All Source Files Have Correct ASF Headers (ran RAT tool: only > > >>>>> .gitignore and .babelrc (json) exclude headers) > > >>>>> [ x ] No Binary Files in Source Release Packages (except for > > supporting > > >>>>> .png files) > > >>>>> > > >>>>>>
Podling Flagon Report Reminder - May 2022
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
Hi, +1 from me. I checked: - Incubating in name - 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 Wed, Apr 13, 2022 at 11:54 PM Joshua Poore wrote: > REMINDER PPMC, Mentors—please don’t forget to VOTE for this release!! > > This release contains some great PR work from our community!!! > > > On Apr 11, 2022, at 12:05 PM, Gedd Johnson wrote: > > > > [x] +1, let's get it released!!! > > > > [x ] Build and Unit Tests Pass > > [x ] Integration Tests Pass > > [x ] "Incubating" in References to Project and Distribution File Names > > [x ] Signatures and Hashes 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 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: > > > >> +1 (PPMC) > >> > >> I checked: > >> > >> [ x ] Build and Unit Tests Pass > >> [ x ] Integration Tests Pass (Example Page, Webpack (NPM), React (NPM) > >> [ x ] "Incubating" in References to Project and Distribution File Names > >> [ x ] Signatures and Hashes 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 distribution > >> [ x ] New source code (React app, OpenTelemetry Ex) has compatible > >> licenses (ALv2, MIT) > >> [ x ] All Source Files Have Correct ASF Headers (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 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 > >>> Adds React App.js example/test utility > >>> Adds additional examples (non-user log examples) > >>> Minor updates to update deprecated downstream dev dependencies > >>> Minor changes to documentation, updated examples > >>> > >>> Resolved issues: > >> https://github.com/apache/incubator-flagon-useralejs/projects/9 > >>> > >>> Git source tag (566b279; > >> > https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.3.0-RC-01 > >> ) > >>> > >>> Staging repo: https://dist.apache.org/repos/dist/dev/incubator/flagon/ > >>> > >>> Source Release Artifacts: > >> > https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.3.0-RC-01/ > >>> > >>> PGP release keys (signed using F9374FAE3FCADF6E): > >> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS > >>> > >>> Link to Successful CI Build: > >> https://github.com/apache/incubator-flagon-useralejs/runs/5958813955 > >>> > >>> Reference to the UserALE.js testing framework to assist in your unit > and > >> integration tests: > >> > https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure > >>> > >>> I checked: > >>> > >>> [ x ] Build and Unit Tests Pass > >>> [ x ] Integration Tests Pass (Example Page, Webpack (NPM), React (NPM) > >>> [ x ] "Incubating" in References to Project and Distribution File Names > >>> [ x ] Signatures and Hashes 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 distribution > >
Re: [Mentors] Q1 2022 Flagon Report
Hi Joshua, Thanks for preparing the report! Kind Regards, Furkan KAMACI On Thu, Jan 6, 2022 at 5:25 AM Joshua Poore wrote: > 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 quarter is that we are currently working on a > CCLA with UMD for a software gift (refactored Distill) into the project, > along with new committers. Expect to see corresponding VOTE threads this > quarter. Some contributions will start filtering into UserALE.js as well. > > Best, > > Josh
Re: Podling Flagon Report Reminder - August 2021
Hi, Is there anybody working on the report? Feel free to ask if you need help. Kind Regards, Furkan KAMACI On Sun, Aug 1, 2021 at 7:24 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, 18 August 2021. > 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, August 04). > > 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/August2021 > > 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: [VOTE] Release Apache Flagon (Incubating) 2.2.0
Hi, +1 from me. I checked: - Incubating in name - 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 Tue, Jun 8, 2021 at 11:17 PM lewis john mcgibbney wrote: > +1 the RC looks good. > Same tests as Josh... same results. > > On Tue, Jun 8, 2021 at 11:47 Gedd Johnson wrote: > > > Hi all, > > > > Just a reminder to VOTE on RC3 mentioned in this thread. We are currently > > sitting at +2 and require at least one more vote to continue in the > > release process. > > > > Thanks! > > Gedd Johnson > > > > On Sat, Jun 5, 2021 at 5:59 PM Gedd Johnson > > wrote: > > > >> +1 > >> > >> Thanks all again for the feedback! > >> > >> [X] Build and Unit Tests Pass > >> [X] Integration Tests Pass > >> [X] "Incubating" in References to Project and Distribution File Names > >> [X] Signatures and Hashes 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 distribution > >> [X] All Source Files Have Correct ASF Headers > >> [X] No Binary Files in Source Release Packages > >> > >> On Thu, Jun 3, 2021 at 8:35 PM Joshua Poore wrote: > >> > >>> +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 Tests Pass > >>> [X] "Incubating" in References to Project and Distribution File Names > >>> [X] Signatures and Hashes 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 distribution > >>> [X] All Source Files Have Correct ASF Headers > >>> [X] No Binary Files in Source Release Packages > >>> > >>> RAT Run Looks Good (.babelrc can’t take headers—will be parsed, > binaries > >>> are images for web extension): > >>> > >>> Files with Apache License headers will be marked AL > >>> Binary files (which do not require any license headers) will be > marked > >>> B > >>> Compressed archives will be marked A > >>> Notices, licenses etc. will be marked N > >>> AL./apache-flagon-useralejs-incubating-2.2.0-src/.asf.yaml > >>> !? ./apache-flagon-useralejs-incubating-2.2.0-src/.babelrc > >>> N ./apache-flagon-useralejs-incubating-2.2.0-src/DISCLAIMER > >>> N ./apache-flagon-useralejs-incubating-2.2.0-src/KEYS > >>> N ./apache-flagon-useralejs-incubating-2.2.0-src/LICENSE > >>> N ./apache-flagon-useralejs-incubating-2.2.0-src/NOTICE > >>> AL > >>> ./apache-flagon-useralejs-incubating-2.2.0-src/doap-userale.js.rdf > >>> AL./apache-flagon-useralejs-incubating-2.2.0-src/rollup.config.js > >>> AL > >>> ./apache-flagon-useralejs-incubating-2.2.0-src/build/userale-2.2.0.js > >>> AL > >>> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/userale-2.2.0.min.js > >>> AL > >>> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/background.js > >>> AL > >>> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/content.js > >>> AL > >>> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/options.js > >>> AL > >>> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/optionsPage.html > >>> B > >>> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/icons/border-48.png > >>> AL > ./apache-flagon-useralejs-incubating-2.2.0-src/example/index.html > >>> AL./
Re: [VOTE] Release Apache Flagon (Incubating) 2.2.0
Hi Gedd, Thanks for spinning the release candidate. However, I see that people are still voting on the RC#2 mail thread. Could you mention you have closed the vote for RC#2 with a brief explanation of the reason at that mail thread? Kind Regards, Furkan KAMACI On Sun, May 30, 2021 at 10:25 PM Gedd Johnson wrote: > Hi Folks, > Please VOTE on the Apache Flagon 2.2.0 Release Candidate #3. > > About Flagon: http://flagon.incubator.apache.org/ > > This Minor release includes: > > 1. Adding a page load log feature > 2. Refactoring the build pipeline using Rollup > 3. Adding a journey testing suite > 4. Fixing a bug with sendOnClose > > We solved 21 issues: > https://github.com/apache/incubator-flagon-useralejs/projects/7 > > Git source tag (2b996df): > https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.2.0-RC3 > > Staging repo: https://dist.apache.org/repos/dist/dev/incubator/flagon/ > > Source Release Artifacts: > > https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.2.0-RC3/ > > PGP release keys (signed using A88C905BD4516D4C): > https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS > > Link to successful Github CI Build: > https://github.com/apache/incubator-flagon-useralejs/actions > > Reference the useralejs testing framework to assist in your unit and > integration tests: > > https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Testing+Framework > > Vote will be open for 72 hours. Please VOTE as follows: > > [ ] +1, let's get it released!!! > [ ] +/-0, fine, but consider to fix few issues before... > [ ] -1, nope, because... (and please explain why) > > Along with your VOTE, please indicate testing and checks you've made > against build artifacts, src, and documentation: > > [ ] Build and Unit Tests Pass > [ ] Integration Tests Pass > [ ] "Incubating" in References to Project and Distribution File Names > [ ] Signatures and Hashes Match Keys > [ ] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release > Packages > [ ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and Incubator > Policy > [ ] CHANGELOG included with release distribution > [ ] All Source Files Have Correct ASF Headers > [ ] No Binary Files in Source Release Packages > > Thank you to everyone that is able to VOTE as well as everyone that > contributed to Apache Flagon 2.2.0 >
Re: [VOTE] Release Apache Flagon (Incubating) 2.2.0
Hi, -0 from me. I checked: - Incubating in name - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary files - Checked PGP signatures - Checked checksums - Code compiles and tests successfully run Since we are a community that is nearing graduation, we should solve the ASF headers problem. Some files do not have it (i.e. rollup.config). By the way, thanks for the effort you have made! Kind Regards, Furkan KAMACI On Tue, May 25, 2021 at 4:09 AM Joshua Poore wrote: > Hi All, > > Please remember to VOTE on this Release! > > Josh > > > On May 24, 2021, at 7:58 AM, Gedd Johnson > wrote: > > > > Morning all, > > > > Adding my vote: > > > > +1 > > > > [X] Build and Unit Tests Pass > > [X] Integration Tests Pass > > [X] "Incubating" in References to Project and Distribution File Names > > [X] Signatures and Hashes 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 distribution > > [X] All Source Files Have Correct ASF Headers > > [X] No Binary Files in Source Release Packages > > > > On Sat, May 22, 2021 at 1:19 PM Joshua Poore wrote: > > > >> Great work Gedd! And, AMAZING job on your very first Apache release > >> candidate! > >> > >> +1 > >> > >> I’ll note that there are a few src files that don’t have ALv2 headers on > >> them (didn’t catch these before RC packaged). These are configuration > files > >> that are part of the testing (cypress journey test) framework, or > examples, > >> and not actually part of the build pipeline, or src artifacts, or > exports > >> (i.e., this is not what would be consumed by other projects as source > >> (through script or npm module)). I’m OK with getting license headers on > >> those files in the next minor release (added to Master branch ASAP). > (see > >> RAT run below) > >> > >> > >> I checked: > >> > >> [ X ] Build and Unit Tests Pass > >> [ X ] Integration Tests Pass > >> [ X ] "Incubating" in References to Project and Distribution File Names > >> [ X ] Signatures and Hashes 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 distribution (I added in release > >> files (was included in src distro)) > >> [ X ] All Source Files Have Correct ASF Headers (see below)... > >> [ X ] No Binary Files in Source Release Packages > >> > >> RAT RUN: > >> > >> * > >> > >> * > >> Files with Apache License headers will be marked AL > >> Binary files (which do not require any license headers) will be marked > B > >> Compressed archives will be marked A > >> Notices, licenses etc. will be marked N > >> B ./apache-flagon-useralejs-incubating-2.2.0-src/.DS_Store > >> AL./apache-flagon-useralejs-incubating-2.2.0-src/.asf.yaml > >> !? ./apache-flagon-useralejs-incubating-2.2.0-src/.babelrc > >> N ./apache-flagon-useralejs-incubating-2.2.0-src/DISCLAIMER > >> N ./apache-flagon-useralejs-incubating-2.2.0-src/KEYS > >> N ./apache-flagon-useralejs-incubating-2.2.0-src/LICENSE > >> N ./apache-flagon-useralejs-incubating-2.2.0-src/NOTICE > >> AL > ./apache-flagon-useralejs-incubating-2.2.0-src/doap-userale.js.rdf > >> AL./apache-flagon-useralejs-incubating-2.2.0-src/rollup.config.js > >> AL > >> ./apache-flagon-useralejs-incubating-2.2.0-src/build/userale-2.2.0.js > >> AL > >> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/userale-2.2.0.min.js > >> AL > >> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/background.js > >> AL > >> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/content.js > >> AL > >> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/options.js > >> AL > >> > ./apache-flagon-useralejs-incubating-2.2.0-src/build/UserALEWebExtension/optionsPage.html > >> B > >> > ./apache-flagon-useralejs-incubating-2.2
Re: [DISCUSS] Establish Apache Flagon TLP and Graduate from Incubator
Hi Joshua, Thanks for the detailed report! This version is much better. Kind Regards, Furkan KAMACI On Mon, Apr 12, 2021 at 4:17 PM Joshua Poore wrote: > Following Furkan’s suggestions, I’ve added some flavor to the report in > #contributor and #project fields. Adding metrics now. Given time is short, > just giving everyone a heads up that mods have/are being made: > https://cwiki.apache.org/confluence/display/INCUBATOR/April2021#flagon < > https://cwiki.apache.org/confluence/display/INCUBATOR/April2021#flagon> > > Thanks, > > Josh > > > On Apr 11, 2021, at 1:44 PM, Joshua Poore > wrote: > > > > Great feedback, Furkan. I’ll add more depth to the report. > > > > Joshua Poore > > > > > >> On Apr 11, 2021, at 9:31 AM, Furkan KAMACI > wrote: > >> > >> Hi Joshua, > >> > >> It's great you've pinged for the graduation discussion. > >> > >> By the way, thanks for filling the report. I've signed it. However, > >> elaborating how has the community/project developed since the last > report > >> part could be nice. You can add some metrics there. Also, it may be > >> worth mentioning that the last elected person was Committer and PPMC. > >> > >> Kind Regards, > >> Furkan KAMACI > >> > >>> On Sun, Apr 11, 2021 at 4:25 AM Joshua Poore > wrote: > >>> > >>> Hi Dave, > >>> > >>> The report is up on on the Wiki. Thanks for the patience. > >>> > >>> Josh > >>> > >>>>> On Apr 8, 2021, at 11:13 AM, Dave Fisher wrote: > >>>> > >>>> Hey Joshua, > >>>> > >>>> Good to see this. It would be great for Flagon to submit their Podling > >>> report today at > >>> https://cwiki.apache.org/confluence/display/INCUBATOR/April2021#flagon > >>>> > >>>> Regards, > >>>> Dave > >>>> > >>>> On 2021/04/08 02:58:39, Joshua Poore wrote: > >>>>> It would be great to have some discussion about Graduating. Any > >>> thoughts about TLP vs. joining another project. Beyond answer that > question > >>> (given new projects like Superset), we’ve been ready to graduate for a > >>> while IMHO, despite having a small community. We should move on this in > >>> CY2021 Q2. > >>>>> > >>>>> If nothing else heard in one more week, I think we should pick up the > >>> vote we started on the IPMC mailing list in CY2020 Q4. We addressed all > >>> those actions (less more active community discussion on graduating :) > ). > >>>>> > >>>>> Josh > >>>>> > >>>>>> On Mar 11, 2021, at 9:50 PM, Joshua Poore > wrote: > >>>>>> > >>>>>> Hi All, > >>>>>> > >>>>>> I’m not sure if you’re aware but UserALE.js is lighting up a bit. > >>> We’ve gotten some really incredible PRs recently and we’re getting some > >>> attention from new and existing users—I hear more contributions on the > way. > >>>>>> > >>>>>> IMHO this is a good time to Graduate. The project is healthy and > >>> modernized and I suspect we’ll see some real organic growth in the > >>> committer base very soon. > >>>>>> > >>>>>> @Mentors any thoughts? When last we discussed graduating it was > clear > >>> that we should be our own TLP. I can get behind that. However, there > are > >>> new projects like Apache Superset that might be interesting targets to > >>> explore graduating into. Any advice on that front, given what we’re > seeing? > >>> Anyone else in the community have thoughts at this point? Last note > from > >>> IPMC made it clear that they would certainly like to see us graduate :) > >>>>>> > >>>>>> poorejc > >>>>>> > >>>>>>> On Feb 20, 2021, at 9:25 PM, Joshua Poore >>> <mailto:poor...@apache.org>> wrote: > >>>>>>> > >>>>>>> Hi All, > >>>>>>> > >>>>>>> If you all recall back in 2018 we actually started voting to > graduate > >>> from the Incubator. There was a shake up in our team due to a bunch of > >>> people leaving certain orgs all at the same time and we kind of left > this
Re: [DISCUSS] Q2 2021 Flagon Podling Report
Hi Joshua, Thanks for filling it. I've signed it off and wrote my comments to the other email thread. Kind Regards, Furkan KAMACI On Sun, Apr 11, 2021 at 4:30 AM Joshua Poore wrote: > Hi All, > > Just a few days until the report needs to be signed. Please feel free to > review and comment here if there are any obvious issues. > > Report can be found here: > https://cwiki.apache.org/confluence/display/INCUBATOR/April2021#flagon < > https://cwiki.apache.org/confluence/display/INCUBATOR/April2021#flagon> > > MENTORS—please check this one out. If all goes well, I think this report > may be our last podling report. Will need your signature ASAP. > > Josh
Re: [DISCUSS] Establish Apache Flagon TLP and Graduate from Incubator
Hi Joshua, It's great you've pinged for the graduation discussion. By the way, thanks for filling the report. I've signed it. However, elaborating how has the community/project developed since the last report part could be nice. You can add some metrics there. Also, it may be worth mentioning that the last elected person was Committer and PPMC. Kind Regards, Furkan KAMACI On Sun, Apr 11, 2021 at 4:25 AM Joshua Poore wrote: > Hi Dave, > > The report is up on on the Wiki. Thanks for the patience. > > Josh > > > On Apr 8, 2021, at 11:13 AM, Dave Fisher wrote: > > > > Hey Joshua, > > > > Good to see this. It would be great for Flagon to submit their Podling > report today at > https://cwiki.apache.org/confluence/display/INCUBATOR/April2021#flagon > > > > Regards, > > Dave > > > > On 2021/04/08 02:58:39, Joshua Poore wrote: > >> It would be great to have some discussion about Graduating. Any > thoughts about TLP vs. joining another project. Beyond answer that question > (given new projects like Superset), we’ve been ready to graduate for a > while IMHO, despite having a small community. We should move on this in > CY2021 Q2. > >> > >> If nothing else heard in one more week, I think we should pick up the > vote we started on the IPMC mailing list in CY2020 Q4. We addressed all > those actions (less more active community discussion on graduating :) ). > >> > >> Josh > >> > >>> On Mar 11, 2021, at 9:50 PM, Joshua Poore wrote: > >>> > >>> Hi All, > >>> > >>> I’m not sure if you’re aware but UserALE.js is lighting up a bit. > We’ve gotten some really incredible PRs recently and we’re getting some > attention from new and existing users—I hear more contributions on the way. > >>> > >>> IMHO this is a good time to Graduate. The project is healthy and > modernized and I suspect we’ll see some real organic growth in the > committer base very soon. > >>> > >>> @Mentors any thoughts? When last we discussed graduating it was clear > that we should be our own TLP. I can get behind that. However, there are > new projects like Apache Superset that might be interesting targets to > explore graduating into. Any advice on that front, given what we’re seeing? > Anyone else in the community have thoughts at this point? Last note from > IPMC made it clear that they would certainly like to see us graduate :) > >>> > >>> poorejc > >>> > >>>> On Feb 20, 2021, at 9:25 PM, Joshua Poore <mailto:poor...@apache.org>> wrote: > >>>> > >>>> Hi All, > >>>> > >>>> If you all recall back in 2018 we actually started voting to graduate > from the Incubator. There was a shake up in our team due to a bunch of > people leaving certain orgs all at the same time and we kind of left this > alone for a while. > >>>> > >>>> @lewis raised this issue last quarter. We had a few actions from the > Incubator (summarized here > https://cwiki.apache.org/confluence/display/FLAGON/Incubator+Graduation < > https://cwiki.apache.org/confluence/display/FLAGON/Incubator+Graduation>). > Most of those are covered now. > >>>> > >>>> Some of those actions are covered in the latest release candidate I > just pushed to vote (Flagon UserALE.js 2.1.1), which put our release > processes and artifacts in compliance with ASF policy on 3rd party distros > (like NPM). > >>>> > >>>> Let’s pick up the discussion on Graduation: > >>>> > >>>> My feeling after a big job change recently (i’m not at a university), > I think it will be much easier for me to foster community growth and > participation in the project. I’m ready for this and would like to see this > done. We’re a little project, but we have a pretty stable user base, which > I work with regularly. Likely, I’ll be doing more funded work in this area. > So, I’m all for it (+1). > >>>> > >>>> Who’s with me? Ready to be official ASF members? > >>>> > >>>> Josh > >>>> > >>>>> Begin forwarded message: > >>>>> > >>>>> From: lewis john mcgibbney lewi...@apache.org>> > >>>>> Subject: Proposed Resolution: Establish Apache Flagon TLP > >>>>> Date: September 20, 2020 at 3:11:14 PM EDT > >>>>> To: gene...@incubator.apache.org gene...@incubator.apache.org> > >>>>> Cc: dev@flagon.apache.org <mailto:dev@flagon.apache.org> >
Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.1
Hi, +1 Kind Regards, Furkan KAMACI On Sun, Feb 21, 2021 at 8:57 PM Rob Foley wrote: > +1 > > On Sun, Feb 21, 2021 at 12:38 PM Joshua Poore wrote: > > > +1 (non-binding, Flagon PPMC) > > > > > On Feb 21, 2021, at 12:34 PM, Laura Mariano > > > wrote: > > > > > > +1 > > > > > > On Sat, Feb 20, 2021 at 9:06 PM Joshua Poore > wrote: > > > > > >> Hi Folks, > > >> > > >> Please VOTE on the Apache Flagon UserALE.js 2.1.1 Release Candidate # > > 02. > > >> > > >> About Flagon: http://flagon.incubator.apache.org/ > > >> > > >> This Patch release includes: > > >> > > >> > > >> Fixes bug in SessionID creation at initial PageLoad > > >> Update to Node.js/NPM Engine support (tested 12.x, 13.x, 14.x, 15.x) > > >> Minor updates to resolve extant vulnerabilities in dependency tree > > >> Minor updates to update deprecated downstream dev dependencies > > >> Minor updates to build pipelines to accommodate dependency updates > > >> Minor changes to documentation > > >> Minor QOL upgrades to UserALE.js repository (CI, Dependabot) > > >> Ensured release artifacts and processes consistent with Apache > Incubator > > >> NPM release policies (following successful vote, this will be pushed > to > > >> flagon-userale npm project). > > >> > > >> Resolved issues: > > >> https://github.com/apache/incubator-flagon-useralejs/projects/3 > > >> > > >> Git source tag (7768e76 < > > >> > > > https://github.com/apache/incubator-flagon-useralejs/commit/7768e767a8215cdd9fbe5c8ab98a8caa89da0b32 > > >): > > >> > > > https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.1.1-RC2 > > >> > > >> Staging repo: > https://dist.apache.org/repos/dist/dev/incubator/flagon/ > > >> > > >> Source Release Artifacts: > > >> > > > https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.1-RC2/ > > >> > > >> PGP release keys (signed using F9374FAE3FCADF6E): > > >> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS > > >> > > >> Link to Successful CI Build: > > >> > > > https://github.com/apache/incubator-flagon-useralejs/actions/runs/585237168 > > >> > > >> Reference to the UserALE.js testing framework to assist in your unit > and > > >> integration tests: > > >> > > > https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure > > >> > > >> I checked: > > >> > > >> [ x ] Build and Unit Tests Pass > > >> [ x ] Integration Tests Pass > > >> [ x ] "Incubating" in References to Project and Distribution File > Names > > >> [ x ] Signatures and Hashes 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 distribution > > >> [ x ] All Source Files Have Correct ASF Headers (ran RAT tool: only > > >> .gitignore and .babelrc (json) exclude headers) > > >> [ x ] No Binary Files in Source Release Packages > > >> > > >> Vote will be open for 72 hours. Please VOTE as follows: > > >> > > >> [ ] +1, let's get it released!!! > > >> [ ] +/-0, fine, but consider to fix few issues before... > > >> [ ] -1, nope, because... (and please explain why) > > >> > > >> Along with your VOTE, please indicate testing and checks you've made > > >> against build artifacts, src, and documentation: > > >> > > >> [ ] Build and Unit Tests Pass > > >> [ ] Integration Tests Pass > > >> [ ] "Incubating" in References to Project and Distribution File Names > > >> [ ] Signatures and Hashes Match Keys > > >> [ ] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release > > >> Packages > > >> [ ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and > > Incubator > > >> Policy > > >> [ ] CHANGELOG included with release distribution > > >> [ ] All Source Files Have Correct ASF Headers > > >> [ ] No Binary Files in Source Release Packages > > >> > > >> Thank you to everyone that is able to VOTE as well as everyone that > > >> contributed to Apache Flagon UserALE.js 2.1.1 > > > > >
Re: [ACTION] Graduate Flagon from the Incubator
Hi Lewis, I am +1 for graduation resolution! I'll check the required steps for it. Kind Regards, Furkan KAMACI On Sun, Sep 20, 2020 at 9:50 PM lewis john mcgibbney wrote: > Hi dev@, > I just realized that we actually VOTE'd in favor of graduating the project > from the Incubator. This happened in May 2018 when the project was under > former name SensSoft!!! > > > https://lists.apache.org/thread.html/8fc3d752a4000b461fd7e8afd45b916025cc2b16bae52d65ca5a3083%40%3Cdev.senssoft.apache.org%3E > > I'm going to go ahead and draft a Graduation Resolution which I will post > here and we can move forward with the graduation. > > Lewis > > -- > http://home.apache.org/~lewismc/ > http://people.apache.org/keys/committer/lewismc >
Re: Podling Flagon Report Reminder - July 2020
Hi All, Is there anybody working on the report? Let me know if you need help. Kind Regards, Furkan KAMACI On Thu, Jun 25, 2020 at 6:37 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 July 2020. > 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, July 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/July2020 > > 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 >
Apache Flagon Logo
Hi All, I was checking Flagon for the things need to be done by mentors. I see that no logo has uploaded to ASF: https://whimsy.apache.org/pods.cgi/project/flagon You can verify it from here: https://www.apache.org/logos/?#flagon Did anybody has taken an action for that? Kind Regards, Furkan KAMACI
Re: [DISCUSS] APR 2020 Podling Report Draft
Hi, Thanks for preparing the report Joshua! Kind Regards, Furkan KAMACI On Tue, Mar 31, 2020 at 9:59 PM David Meikle wrote: > Thanks Joshua, looks good to me. > > If there are no comments here, I'll move it over tonight. > > Hope you and your loved ones are safe and well! > > Cheers, > Dave > > On Sun, 29 Mar 2020 at 00:24, Joshua Poore wrote: > > > Hi All, > > > > Please review the following report. It needs to be posted on the > Incubator > > wiki NLT 01 APR 2020. > > > > Mentors need to sign off by 01 APR 2020. > > > > Feel free to comment or suggest revisions. > > > > For a formatted version, see the draft report here: > > https://cwiki.apache.org/confluence/display/FLAGON/APR+2020 < > > https://cwiki.apache.org/confluence/display/FLAGON/APR+2020> > > > > Flagon > > > > 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: > > > > • Grow the Flagon Committer/Contributor/Community Base > > • Refine release processes for core analytic product (Distill) > > • 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? > > > > • continued improving release processes and code base > > • continued to generate a wide user base > > • discussing collaborations for R applications > > • new potential committers are identified and will be introduced > > soon > > 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 > > • Analytical products are being refactored to grow user base > > • 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 > > • Community building > > • Nearing graduation X > > • Other: > > Date of last release: > > > > 2020-03-17 (ANNOUNCEMENT IMMINENT) > > > > 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? > > > > Are things falling through the cracks? If so, please list any open issues > > that need to be addressed. > > > > • Our mentors have been very supportive and responsive. > > Is the PPMC managing the podling's brand / trademarks? > > > > Are 3rd parties respecting and correctly using the podlings name and > > brand? If not what actions has the PPMC taken to correct this? Has the > VP, > > Brand approved the project name? > > > > • 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: > > • (flagon) Furkan Kamaci > > Comments: >
Re: [MENTORS] https://www.apache.org/dist/ has been deprecated
Hi, Thanks Joshua! Kind Regards, Furkan KAMACI 29 Mar 2020 Paz, saat 06:37 tarihinde Joshua Poore şunu yazdı: > Flagon’s download page links have been updated to point @ > downloads.apache.org <http://downloads.apache.org/>. > > Thanks, > > Josh > > > On Mar 11, 2020, at 11:23 PM, lgcareer2...@outlook.com wrote: > > > > I have changed DolphinScheduler to point at downloads.apache.org < > http://downloads.apache.org/>. Thank you for the notification Justin. > > > > > > > > DolphinScheduler(Incubator) PPMC > > Gang Li 李岗 > > > > lgcareer2...@outlook.com<mailto:lgcareer2...@outlook.com> > > > > From: Justin Mclean > > Date: 2020-03-04 17:14 > > To: general > > Subject: [MENTORS] https://www.apache.org/dist/ has been deprecated > > Hi, > > > > The new URL to use is https://downloads.apache.org. Currently there is > a redirect in place that should work but it would be be good to double > check that all is working > > > > The following podling may need to update their download pages: > > Crail > > Daffodil > > DolphinScheduler > > Flagon > > Gobblin > > Hudi > > IoTDB > > Livy > > Milagro > > Pinot > > PonyMail > > ShardingSphere > > Toree > > Training > > Tuweni > > Weex > > > > And there may be others I’ve not identified. If you are a mentor of one > of these projects please reach out and organise for this to be done. > > > > Thanks, > > Justin > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > >
Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0
Hi, +1 from me. I checked: - Incubating in name - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary files - Checked PGP signatures - Checked Checksums PS: Should it be Copyright 2019-2020 The Apache Software Foundation at NOTICE file? Kind Regards, Furkan KAMACI On Mon, Feb 24, 2020 at 4:39 PM Tim Allison wrote: > +1 > Late as well...sorry! > > > > On Sat, Feb 22, 2020 at 8:19 PM Joshua Poore > wrote: > > > Hi All, > > > > REMINDER: Please VOTE on the Apache Flagon 2.1.0 Release. > > > > Thanks, > > > > Josh > > > > > On Feb 14, 2020, at 10:33 AM, Rob Foley wrote: > > > > > > A bit late, but +1: > > > > > > [x] Build and Unit Tests Pass > > > [x] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release > > > Packages > > > [x] Signatures and Hashes Match Keys > > > [x] CHANGELOG included with release distribution > > > > > > On Mon, Feb 10, 2020 at 9:14 PM Joshua Poore > > wrote: > > > > > >> pushed updated webpack.config.js that includes ALv2 header > > >> > > >>> On Feb 10, 2020, at 7:34 PM, Joshua Poore > > >> wrote: > > >>> > > >>> Disregard. You’re right. webpack config is .js. Missed that. > > >>> > > >>> You see any issues with our disclaimer given that the webpack config > > >> doesn’t have a header? > > >>> > > >>> Joshua Poore > > >>> > > >>> > > >>>> On Feb 10, 2020, at 7:32 PM, Joshua Poore > > >> wrote: > > >>>> > > >>>> Hi Dave, > > >>>> > > >>>> Thanks for identifying! I thought comments aren’t supported in JSON. > > >> There are custom libs for doing that, but I doubt node and web pack > can > > >> call them. > > >>>> > > >>>> If you can point me to an example, I’ll get it in there. > > >>>> > > >>>> Joshua Poore > > >>>> > > >>>> > > >>>>>>> On Feb 10, 2020, at 5:03 PM, David Meikle > wrote: > > >>>>>>> On Fri, 7 Feb 2020 at 23:12, Joshua Poore > > >> wrote: > > >>>>>>> Hi Folks, > > >>>>>>> Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01 > > >>>>>>> Source Release Artifacts: > > >>>>>>> > > >> > > > https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/ > > >>>>>>> < > > >>>>>>> > > >> > > > https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/ > > >>>>>>> Vote will be open for 72 hours. Please VOTE as follows: > > >>>>>>> [ ] +1, let's get it released!!! > > >>>>>>> [ ] +/-0, fine, but consider to fix few issues before... > > >>>>>>> [ ] -1, nope, because... (and please explain why) > > >>>>> +1 (binding) : Performed the check list provided on the source > > release > > >>>>> package. > > >>>>> There are some files, like the webpack.config.js, flagged by Apache > > RAT > > >>>>> that we could put an AL header on. Not a deal breaker, but worth > > >>>>> considering. > > >>>>> Cheers, > > >>>>> Dave > > >>> > > >> > > >> > > > > >
Re: ATTN: MENTORS Re: Podling Flagon Report Reminder - January 2020
Hi, Thanks Joshua! Kind Regards, Furkan KAMACI 3 Oca 2020 Cum, saat 06:44 tarihinde Joshua C. Poore şunu yazdı: > 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 > >>>>>>>> >
Re: ATTN: MENTORS Re: Podling Flagon Report Reminder - January 2020
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 > >>>>>> > >> >
Re: ATTN: MENTORS Re: Podling Flagon Report Reminder - January 2020
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 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 > >>>> >
Re: Podling Flagon Report Reminder - January 2020
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: Podling Flagon Report Reminder - January 2020
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
Hi Joshua, Great sketches! From a user perspective, I liked the #1 just because of it seems cool. Kind Regards, Furkan KAMACI On Sun, Sep 29, 2019 at 9:40 PM Austin Bennett wrote: > Sensible response and believe am in agreement -- and, related, I don't have > any better ideas for logos at the moment. > > On Sat, Sep 28, 2019 at 10:16 PM Joshua C. Poore > wrote: > > > 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 > > >> > > >> > > >> > > >> > > >
Re: Hacktoberfest 2019
Hi Joshua, There are local events whole around the world for Hacktoberfest. I'll also encourage such people near me for Flagon! Kind Regards, Furkan KAMACI On Sun, Sep 29, 2019 at 6:19 AM Joshua C. Poore wrote: > 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 > > >
Hacktoberfest 2019
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: [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.2
Hi,
+1!
Kind Regards,
Furkan KAMACI
9 Ağu 2019 Cum, saat 05:14 tarihinde Laura Mariano <
laura.j.mari...@gmail.com> şunu yazdı:
> +1
>
>
> On Thu, Aug 8, 2019 at 9:58 PM Confused wrote:
>
> > +1
> >
> > On Thu, Aug 8, 2019 at 9:16 PM Joshua Poore wrote:
> >
> > > +1
> > >
> > > I tested the h*** out of this. Don’t forget to VOTE y’all!
> > >
> > > > On Aug 6, 2019, at 10:16 PM, Joshua Poore
> wrote:
> > > >
> > > >
> > > > Hi Folks,
> > > >
> > > > Please VOTE on the Apache Flagon 2.0.2 Release Candidate # 1
> > > >
> > > > Context: v2.0.1 release had a major, uncaught flaw in the
> package.json
> > > file. Once the VOTE passed to release 2.0.1, this was published to the
> > npm
> > > registry resulting in an unusable npm package. This was immediately
> > > unpublished. However, npm prohibits republishing over the same package
> > > version number. As such, we are treating v2.0.1 as a failed release.
> > v2.0.2
> > > resolves the package.json issue, and adds the final npm dev dependency
> > > update to resolve all install audit warnings rel to Prototype
> Pollution,
> > > and package deprecation notices. See changelog for full details.
> > > Additionally, see the newly added UserALE.js testing framework (on
> > > confluence, link below) for instructions for how to build, perform unit
> > and
> > > integration tests, and test the npm distribution as though it was
> > installed
> > > directly from the npm registry.
> > > >
> > > > VOTE details follow:
> > > >
> > > > About Flagon: http://flagon.incubator.apache.org/ <
> > > http://flagon.incubator.apache.org/>
> > > >
> > > > This Patch release includes :
> > > >
> > > > • Updates to package.json and package-lock.json to resolve
> > > downstream Prototype Pollution vulnerabilities in dev dependencies
> > > > • Updates to package.json and package-lock.json to modernize
> > > deprecated npm modules
> > > > • Minor updates to README documentation for UserALE.js' Example
> > > Test Utilities.
> > > >
> > > > We solved 11 issues:
> > > https://issues.apache.org/jira/projects/FLAGON/versions/12345954 <
> > > https://issues.apache.org/jira/projects/FLAGON/versions/12345954>
> > > >
> > > > Git source tag (43de2fc1e1c5d5e1a83119a91947f7bbe6d313f3):
> > >
> >
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.2-RC1-08_06_2019
> > > <
> > >
> >
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.2-RC1-08_06_2019
> > > >
> > > >
> > > > Staging repo:
> https://dist.apache.org/repos/dist/dev/incubator/flagon/
> > <
> > > https://dist.apache.org/repos/dist/dev/incubator/flagon/>
> > > >
> > > > Source Release Artifacts:
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.0.2-RC1/
> > > <
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.0.2-RC1/
> > > >
> > > >
> > > > PGP release keys (signed using F937rFAE3FCADF6E):
> > > https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS <
> > > https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS>
> > > >
> > > > Reference the {product} testing framework to assist in your unit and
> > > integration tests:
> > >
> >
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Testing+Framework
> > > <
> > >
> >
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Testing+Framework
> > >
> > >
> > > >
> > > > Link to Successful Jenkins Build(s):
> > > https://builds.apache.org/job/useralejs-ci/91/ <
> > > https://builds.apache.org/job/useralejs-ci/91/>,
> > > https://builds.apache.org/job/useralejs-ci/92/ <
> > > https://builds.apache.org/job/useralejs-ci/92/>
> > > >
> > > > Vote will be open for 72 hours. Please VOTE as follows:
> > > >
> > > > [ ] +1, let's get it released!!!
> > > > [ ] +/-0, fine, but consider to fix few issues before...
> > > > [ ] -1, nope, because... (and please explain why)
> > > > Thank you to everyone that is able to VOTE as well as everyone that
> > > contributed to Apache Flagon 2.0.0
> > >
> > >
> >
>
Re: [VOTE] Release Apache Flagon (Incubating) 2.0.1
Hi, +1 from me. I checked: - Incubating in name - Disclaimer exists - LICENSE is fine - NOTICE is fine - No unexpected binary files - Code compiles and tests successfully run On the other hand, I've tried to run example but could not see the event logs at terminal. Accessing to a file is blocked by browsers and could not load userale js. This issue maybe related with this ( https://issues.apache.org/jira/browse/FLAGON-169) but I couldn't find any information at here ( https://github.com/apache/incubator-flagon-useralejs/tree/2.0.1-RC1-07_30_2019/example) It can be included both how to fetch userale js from local file and serve it via nodejs server to access it. Kind Regards, Furkan KAMACI On Thu, Aug 1, 2019 at 11:01 PM Dave Meikle wrote: > Hello, > > On Wed, 31 Jul 2019 at 03:46, Joshua Poore wrote: > > > Please VOTE on the Apache Flagon (Incubating) v2.0.1 Release Candidate # > 1. > > > > Vote will be open for 72 hours. Please VOTE as follows: > > > > [ ] +1, let's get it released!!! > > [ ] +/-0, fine, but consider to fix few issues before... > > [ ] -1, nope, because... (and please explain why) > > > > +1 - signatures, hashes, NOTICE and LICENSE, incubating in name, builds on > Ubuntu 19.04 with Node 12.7.0 > > Cheers, > Dave >
