[RESULT][VOTE] Graduate Apache Flagon as Top Level Project

[Joshua Poore]

Hello Incubator!

The IPMC VOTE [1] on Graduating Apache Flagon as a Top Level Project is closed, 
following (more than) 72 hours.

The VOTE Passes!

RESULTS:

[ 6 (3 BINDING) ] +1 Apache Flagon is ready to graduate as a TLP
[ 0 ]  0  Let’s DISCUSS some more
[ 0 ] -1 I have some concerns that should be addressed 

Binding Votes:

* Furkan Kamaci
* Dave Fisher
* Madhawa Gunasekera

Non-Binding Votes:

* Joshua Poore
* Austin Bennett
* Goson Zhang

Thanks to all who participated in the IPMC VOTE, the Incubator at large (we 
learned a lot here), our Mentors (!!), and our tight community for getting 
Flagon to this point!

Please find our Community VOTE [2] and RESULT [3] on lists@. 

Respectfully,

Josh Poore (Flagon PPMC)

[1] https://lists.apache.org/thread/9fvnpbpwfrvm23zljjlnfmqvq4n4nss9 
<https://lists.apache.org/thread/9fvnpbpwfrvm23zljjlnfmqvq4n4nss9>
[2] https://lists.apache.org/thread/9fvnpbpwfrvm23zljjlnfmqvq4n4nss9 
<https://lists.apache.org/thread/9fvnpbpwfrvm23zljjlnfmqvq4n4nss9>
[3] https://lists.apache.org/thread/1vk3qkfr5vx6zxyq5gr3kqxrkr2oh206 
<https://lists.apache.org/thread/1vk3qkfr5vx6zxyq5gr3kqxrkr2oh206>

Re: [VOTE] Graduate Apache Flagon as Top Level Project

[Joshua Poore]

Thanks to all who participated in this VOTE. 72 hours has elapsed. The VOTE is 
closed. Please see RESULT thread.

> On Dec 2, 2022, at 11:02 AM, Madhawa Gunasekara  wrote:
> 
> +1 (binding)
> Madhawa
> 
> 
> On Fri, Dec 2, 2022 at 4:51 PM Furkan KAMACI  wrote:
> 
>> Hi,
>> 
>> +1 (binding)!
>> 
>> Kind regards
>> Furkan KAMACI
>> 
>> On Fri, Dec 2, 2022 at 8:13 AM Goson zhang  wrote:
>> 
>>> +1 ( non-binding )
>>> 
>>> Good luck!
>>> 
>>> Dave Fisher  于2022年12月2日周五 11:49写道：
>>> 
>>>> +1(binding)
>>>> 
>>>> Best,
>>>> Dave
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On Dec 1, 2022, at 6:57 PM, Joshua Poore  wrote:
>>>>> 
>>>>> Hello Incubator,
>>>>> 
>>>>> Following a DISCUSSION on general@incubator [0], we are calling a
>> VOTE
>>>> to Graduate Apache Flagon from the Apache Incubator to a Top Level
>>> project.
>>>> Please VOTE accordingly:
>>>>> 
>>>>> [ ] + 1 : Apache Flagon is ready to graduate as a TLP
>>>>> [ ]   0  : Let’s DISCUSS some more
>>>>> [ ] - 1  : I have some concerns that should be addressed (please
>> state)
>>>>> 
>>>>> Thank You in advance for participating in the VOTE. The VOTE will be
>>>> open for at least 72 hours.
>>>>> 
>>>>> Respectfully,
>>>>> 
>>>>> Joshua Poore (Flagon PPMC)
>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>>>>> 
>>>>> Flagon has been incubating since 2016-07-13 (originally ‘SensSoft’
>>> [1]).
>>>> During our incubation, the Flagon project developed steadily,
>> developing
>>>> viable open-source capability and doing so with democratized governance
>>> and
>>>> commitment to productization, maintenance, and experimentation.
>>> Throughout
>>>> our long incubation, our close and consistent community followed the
>>> Apache
>>>> Way.
>>>>> 
>>>>> About Apache Flagon:
>>>>> 
>>>>> Apache Flagon is an open-soure, thin-client behavioral logging
>>>> capability useful for business analytics, usage analytics, usability
>> and
>>>> user testing. It's also for science into how information technology is
>>>> used. Flagon supports a range of streamlined deployment schemas ranging
>>>> from single webpage analysis to enterprise level monitoring, making it
>>> easy
>>>> to collect data without heavy modification of your own code. Using
>>> Elastic
>>>> products, Flagon makes it easy to scale, integrate other services,
>> access
>>>> your data and get the insights you need out of it. In the spirit of
>>>> customization, the Apache Flagon project collects a number of modular
>>>> products and capabilities to help you build the stack that suites your
>>>> needs.
>>>>> 
>>>>> Our community and our mentors believe that Flagon has met the
>>>> Incubator’s maturity model[2]. We believe that we are ready to graduate
>>>> from the Incubator as a self-governing, Top-Level Project.
>>>>> 
>>>>> Specifically,
>>>>> 
>>>>> 1. Our code is well curated, maintained, documented and released
>>> through
>>>> Apache processes and with the Apache (v2) License.
>>>>> 2. Our code is broadly disseminated—through official Apache
>>>> distribution, NPM, GitHub (and soon PyPI).
>>>>> 3. We maintain an Apache-Compliant Website[3] to link users to
>> official
>>>> release mirrors [4]
>>>>> 4. The community changed its name from 'SensSoft' to 'Flagon' to
>> remove
>>>> corporate entanglement with the organization that originally initiated
>>> the
>>>> project, and has completed IP Clearance processes for ‘Flagon’ [5]
>>>>> 5. In total, we have produced 7 Apache releases with 4 different
>>> release
>>>> managers.
>>>>> 6. In the past year, we have onboarded 4 new committers, 1 new PPMC,
>>> and
>>>> accepted a major software grant from the University of Maryland; our
>>>> community is small, but active in VOTEs, Releases

Re: [VOTE] Graduate Apache Flagon as Top Level Project

[Joshua Poore]

Shocking no one, I am a huge +1 (non-binding)

- J

> On Dec 1, 2022, at 9:56 PM, Joshua Poore  wrote:
> 
> Hello Incubator,
> 
> Following a DISCUSSION on general@incubator [0], we are calling a VOTE to 
> Graduate Apache Flagon from the Apache Incubator to a Top Level project. 
> Please VOTE accordingly:
> 
> [ ] + 1 : Apache Flagon is ready to graduate as a TLP
> [ ]   0  : Let’s DISCUSS some more
> [ ] - 1  : I have some concerns that should be addressed (please state)
> 
> Thank You in advance for participating in the VOTE. The VOTE will be open for 
> at least 72 hours.
> 
> Respectfully,
> 
> Joshua Poore (Flagon PPMC)
> 
> 
> 
> Flagon has been incubating since 2016-07-13 (originally ‘SensSoft’ [1]). 
> During our incubation, the Flagon project developed steadily, developing 
> viable open-source capability and doing so with democratized governance and 
> commitment to productization, maintenance, and experimentation. Throughout 
> our long incubation, our close and consistent community followed the Apache 
> Way.
> 
> About Apache Flagon: 
> 
> Apache Flagon is an open-soure, thin-client behavioral logging capability 
> useful for business analytics, usage analytics, usability and user testing. 
> It's also for science into how information technology is used. Flagon 
> supports a range of streamlined deployment schemas ranging from single 
> webpage analysis to enterprise level monitoring, making it easy to collect 
> data without heavy modification of your own code. Using Elastic products, 
> Flagon makes it easy to scale, integrate other services, access your data and 
> get the insights you need out of it. In the spirit of customization, the 
> Apache Flagon project collects a number of modular products and capabilities 
> to help you build the stack that suites your needs.
> 
> Our community and our mentors believe that Flagon has met the Incubator’s 
> maturity model[2]. We believe that we are ready to graduate from the 
> Incubator as a self-governing, Top-Level Project.
> 
> Specifically, 
> 
> 1. Our code is well curated, maintained, documented and released through 
> Apache processes and with the Apache (v2) License. 
> 2. Our code is broadly disseminated—through official Apache distribution, 
> NPM, GitHub (and soon PyPI).
> 3. We maintain an Apache-Compliant Website[3] to link users to official 
> release mirrors [4]
> 4. The community changed its name from 'SensSoft' to 'Flagon' to remove 
> corporate entanglement with the organization that originally initiated the 
> project, and has completed IP Clearance processes for ‘Flagon’ [5]
> 5. In total, we have produced 7 Apache releases with 4 different release 
> managers.
> 6. In the past year, we have onboarded 4 new committers, 1 new PPMC, and 
> accepted a major software grant from the University of Maryland; our 
> community is small, but active in VOTEs, Releases, and DISCUSSions. 
> 7. Governance is conducted and documented through Apache lists 
> 
> Our last Graduation discussion was 10/2020, at which point the Incubator 
> identified issues related to deprecated sub-projects and some committers that 
> were not subscribed to @private lists [6]. Since then we have resolved these 
> issues and continued to develop our products, grow our community, and operate 
> the Apache Way.
> 
> Our community has discussed graduation [7], VOTE’d in favor of it [8,9], and 
> the PPMC has reviewed our Graduation Resolution [10] (below).
> 
> -
> BEGIN DRAFT RESOLUTION
> -
> 
> Establish the Apache Flagon Project 
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of the 
> Foundation and consistent with the Foundation's purpose to establish a 
> Project Management Committee charged with the creation and maintenance of 
> open-source software, for distribution at no charge to the public, related to 
> behavioral logging capability useful for business analytics, usage analytics, 
> usability and user testing. 
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to 
> be known as the "Apache Flagon Project", be and hereby is established 
> pursuant to Bylaws of the Foundation; and be it further 
> 
> RESOLVED, that the Apache Flagon Project be and hereby is responsible for the 
> creation and maintenance of software related to thin-client behavioral 
> logging capability useful for business analytics, usage analytics, usability 
> and user testing, and be it further 
> 
> RESOLVED, that the office of "Vice President, Apache F

[VOTE] Graduate Apache Flagon as Top Level Project

[Joshua Poore]

Hello Incubator,

Following a DISCUSSION on general@incubator [0], we are calling a VOTE to 
Graduate Apache Flagon from the Apache Incubator to a Top Level project. Please 
VOTE accordingly:

[ ] + 1 : Apache Flagon is ready to graduate as a TLP
[ ]   0  : Let’s DISCUSS some more
[ ] - 1  : I have some concerns that should be addressed (please state)

Thank You in advance for participating in the VOTE. The VOTE will be open for 
at least 72 hours.

Respectfully,

Joshua Poore (Flagon PPMC)


 
Flagon has been incubating since 2016-07-13 (originally ‘SensSoft’ [1]). During 
our incubation, the Flagon project developed steadily, developing viable 
open-source capability and doing so with democratized governance and commitment 
to productization, maintenance, and experimentation. Throughout our long 
incubation, our close and consistent community followed the Apache Way.

About Apache Flagon: 

Apache Flagon is an open-soure, thin-client behavioral logging capability 
useful for business analytics, usage analytics, usability and user testing. 
It's also for science into how information technology is used. Flagon supports 
a range of streamlined deployment schemas ranging from single webpage analysis 
to enterprise level monitoring, making it easy to collect data without heavy 
modification of your own code. Using Elastic products, Flagon makes it easy to 
scale, integrate other services, access your data and get the insights you need 
out of it. In the spirit of customization, the Apache Flagon project collects a 
number of modular products and capabilities to help you build the stack that 
suites your needs.

Our community and our mentors believe that Flagon has met the Incubator’s 
maturity model[2]. We believe that we are ready to graduate from the Incubator 
as a self-governing, Top-Level Project.

Specifically, 

1. Our code is well curated, maintained, documented and released through Apache 
processes and with the Apache (v2) License. 
2. Our code is broadly disseminated—through official Apache distribution, NPM, 
GitHub (and soon PyPI).
3. We maintain an Apache-Compliant Website[3] to link users to official release 
mirrors [4]
4. The community changed its name from 'SensSoft' to 'Flagon' to remove 
corporate entanglement with the organization that originally initiated the 
project, and has completed IP Clearance processes for ‘Flagon’ [5]
5. In total, we have produced 7 Apache releases with 4 different release 
managers.
6. In the past year, we have onboarded 4 new committers, 1 new PPMC, and 
accepted a major software grant from the University of Maryland; our community 
is small, but active in VOTEs, Releases, and DISCUSSions. 
7. Governance is conducted and documented through Apache lists 

Our last Graduation discussion was 10/2020, at which point the Incubator 
identified issues related to deprecated sub-projects and some committers that 
were not subscribed to @private lists [6]. Since then we have resolved these 
issues and continued to develop our products, grow our community, and operate 
the Apache Way.

Our community has discussed graduation [7], VOTE’d in favor of it [8,9], and 
the PPMC has reviewed our Graduation Resolution [10] (below).

-
BEGIN DRAFT RESOLUTION
-

Establish the Apache Flagon Project 

WHEREAS, the Board of Directors deems it to be in the best interests of the 
Foundation and consistent with the Foundation's purpose to establish a Project 
Management Committee charged with the creation and maintenance of open-source 
software, for distribution at no charge to the public, related to behavioral 
logging capability useful for business analytics, usage analytics, usability 
and user testing. 

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to 
be known as the "Apache Flagon Project", be and hereby is established pursuant 
to Bylaws of the Foundation; and be it further 

RESOLVED, that the Apache Flagon Project be and hereby is responsible for the 
creation and maintenance of software related to thin-client behavioral logging 
capability useful for business analytics, usage analytics, usability and user 
testing, and be it further 

RESOLVED, that the office of "Vice President, Apache Flagon" be and hereby is 
created, the person holding such office to serve at the direction of the Board 
of Directors as the chair of the Apache Flagon Project, and to have primary 
responsibility for management of the projects within the scope of 
responsibility of the Apache Flagon Project; and be it further 

RESOLVED, that the persons listed immediately below be and hereby are appointed 
to serve as the initial members of the Apache Flagon Project: 

* Joshua Poore  
* Lewis John McGibbney 
* David Meikle 
* Tim Allison 
* Furkan Kamaci 
* Steve York  
* Michelle Beard  
* Ro

[DISCUSS] Graduate Flagon from Apache Incubator as Top Level Project

[Joshua Poore]

Hello Incubator—

72 Hours has (definitely) elapsed on this DISCUSSION thread.

We gave a lot of extra time on this thread following the holiday. I’m with 
Austin, closing this thread and opening a VOTE.

Josh

> On Nov 27, 2022, at 12:11 PM, Austin Bennett  wrote:
> 
> To not leave this discussion completely undiscussed :-)  -->
> 
> My vote/thoughts appeared on dev@flagon, which is ultimately in favor of
> graduation.
> 
> Flagon mentors hadn't raised any other issues, so it seems without [m-]any
> critical/needed comments/suggestion during this discussion, it is otherwise
> getting time to bring this to a VOTE -- perhaps in another day or few [ at
> least sometime after TGiving holiday break for those US based ]?
> 
> 
> On Wed, Nov 23, 2022 at 8:32 PM Joshua Poore  wrote:
> 
>> Hello Incubator,
>> 
>> 
>> Flagon has been incubating since 2016-07-13 (originally ‘SensSoft’ [1]).
>> During our incubation, the Flagon project developed steadily, developing
>> viable open-source capability and doing so with democratized governance and
>> commitment to productization, maintenance, and experimentation. Throughout
>> our long incubation, our close and consistent community followed the Apache
>> Way.
>> 
>> Our community and our mentors believe that Flagon has met the Incubator’s
>> maturity model[2]. We believe that we are ready to graduate from the
>> Incubator as a self-governing, Top-Level Project.
>> 
>> Specifically,
>> 
>> 1. Our code is well curated, maintained, documented and released through
>> Apache processes and with the Apache (v2) License.
>> 2. Our code is broadly disseminated—through official Apache distribution,
>> NPM, GitHub (and soon PyPI).
>> 3. We maintain an Apache-Compliant Website[3] to link users to official
>> release mirrors [4]
>> 4. The community changed its name from 'SensSoft' to 'Flagon' to remove
>> corporate entanglement with the organization that originally initiated the
>> project, and has completed IP Clearance processes for ‘Flagon’ [5]
>> 5. In total, we have produced 7 Apache releases with 4 different release
>> managers.
>> 6. In the past year, we have onboarded 4 new committers, 1 new PPMC, and
>> accepted a major software grant from the University of Maryland; our
>> community is small, but active in VOTEs, Releases, and DISCUSSions.
>> 7. Governance is conducted and documented through Apache lists
>> 
>> Our last Graduation discussion was 10/2020, at which point the Incubator
>> identified issues related to deprecated sub-projects and some committers
>> that were not subscribed to @private lists [6]. Since then we have resolved
>> these issues and continued to develop our products, grow our community, and
>> operate the Apache Way.
>> 
>> Our community has discussed graduation [7], VOTE’d in favor of it [8,9],
>> and the PPMC has reviewed our Graduation Resolution [10] (below).
>> 
>> -
>> BEGIN DRAFT RESOLUTION
>> -
>> 
>> Establish the Apache Flagon Project
>> 
>> WHEREAS, the Board of Directors deems it to be in the best interests of
>> the Foundation and consistent with the Foundation's purpose to establish a
>> Project Management Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the public, related
>> to behavioral logging capability useful for business analytics, usage
>> analytics, usability and user testing.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
>> to be known as the "Apache Flagon Project", be and hereby is established
>> pursuant to Bylaws of the Foundation; and be it further
>> 
>> RESOLVED, that the Apache Flagon Project be and hereby is responsible for
>> the creation and maintenance of software related to thin-client behavioral
>> logging capability useful for business analytics, usage analytics,
>> usability and user testing, and be it further
>> 
>> RESOLVED, that the office of "Vice President, Apache Flagon" be and hereby
>> is created, the person holding such office to serve at the direction of the
>> Board of Directors as the chair of the Apache Flagon Project, and to have
>> primary responsibility for management of the projects within the scope of
>> responsibility of the Apache Flagon Project; and be it further
>> 
>> RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache Flagon Project:
>&g

[DISCUSS] Graduate Flagon from Apache Incubator as Top Level Project

[Joshua Poore]

Hello Incubator,


Flagon has been incubating since 2016-07-13 (originally ‘SensSoft’ [1]). During 
our incubation, the Flagon project developed steadily, developing viable 
open-source capability and doing so with democratized governance and commitment 
to productization, maintenance, and experimentation. Throughout our long 
incubation, our close and consistent community followed the Apache Way.

Our community and our mentors believe that Flagon has met the Incubator’s 
maturity model[2]. We believe that we are ready to graduate from the Incubator 
as a self-governing, Top-Level Project.

Specifically, 

1. Our code is well curated, maintained, documented and released through Apache 
processes and with the Apache (v2) License. 
2. Our code is broadly disseminated—through official Apache distribution, NPM, 
GitHub (and soon PyPI).
3. We maintain an Apache-Compliant Website[3] to link users to official release 
mirrors [4]
4. The community changed its name from 'SensSoft' to 'Flagon' to remove 
corporate entanglement with the organization that originally initiated the 
project, and has completed IP Clearance processes for ‘Flagon’ [5]
5. In total, we have produced 7 Apache releases with 4 different release 
managers.
6. In the past year, we have onboarded 4 new committers, 1 new PPMC, and 
accepted a major software grant from the University of Maryland; our community 
is small, but active in VOTEs, Releases, and DISCUSSions. 
7. Governance is conducted and documented through Apache lists 

Our last Graduation discussion was 10/2020, at which point the Incubator 
identified issues related to deprecated sub-projects and some committers that 
were not subscribed to @private lists [6]. Since then we have resolved these 
issues and continued to develop our products, grow our community, and operate 
the Apache Way.

Our community has discussed graduation [7], VOTE’d in favor of it [8,9], and 
the PPMC has reviewed our Graduation Resolution [10] (below).

-
BEGIN DRAFT RESOLUTION
-

Establish the Apache Flagon Project 

WHEREAS, the Board of Directors deems it to be in the best interests of the 
Foundation and consistent with the Foundation's purpose to establish a Project 
Management Committee charged with the creation and maintenance of open-source 
software, for distribution at no charge to the public, related to behavioral 
logging capability useful for business analytics, usage analytics, usability 
and user testing. 

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to 
be known as the "Apache Flagon Project", be and hereby is established pursuant 
to Bylaws of the Foundation; and be it further 

RESOLVED, that the Apache Flagon Project be and hereby is responsible for the 
creation and maintenance of software related to thin-client behavioral logging 
capability useful for business analytics, usage analytics, usability and user 
testing, and be it further 

RESOLVED, that the office of "Vice President, Apache Flagon" be and hereby is 
created, the person holding such office to serve at the direction of the Board 
of Directors as the chair of the Apache Flagon Project, and to have primary 
responsibility for management of the projects within the scope of 
responsibility of the Apache Flagon Project; and be it further 

RESOLVED, that the persons listed immediately below be and hereby are appointed 
to serve as the initial members of the Apache Flagon Project: 

* Joshua Poore  
* Lewis John McGibbney 
* David Meikle 
* Tim Allison 
* Furkan Kamaci 
* Steve York  
* Michelle Beard  
* Robert Foley 
* Austin Bennett 
* Gedd Johnson 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Joshua Poore be appointed to the 
office of Vice President, Apache Flagon, to serve in accordance with and 
subject to the direction of the Board of Directors and the Bylaws of the 
Foundation until death, resignation, retirement, removal or disqualification, 
or until a successor is appointed; and be it further 

RESOLVED, that the initial Apache Flagon PMC be and hereby is tasked with the 
creation of a set of bylaws intended to encourage open development and 
increased participation in the Apache Flagon Project; and be it further 

RESOLVED, that the Apache Flagon Project be and hereby is tasked with the 
migration and rationalization of the Apache Incubator Flagon podling; and be it 
further 

RESOLVED, that all responsibilities pertaining to the Apache Incubator Flagon 
podling encumbered upon the Apache Incubator Project are hereafter discharged.

--
END DRAFT RESOLUTION
--

We look forward to the Incubator’s feedback and taking the next step with 
Flagon.

This discussion will be open for 72 or more hours.

Respectfully,

Joshua Poore (Flagon PPMC)

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/SensSo

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

[Joshua Poore]

" wrote:
>>>> Note that you're using public and private lists which is a big no-no.
>>>> 
>>>> I'll be honest I don't understand what you're trying to get the IPMC to
>>>> vote on. You may need some help from mentors. I saw IP clearance and
>>> will
>>>> point out that [1] isn't for podlings.  Likewise if this CCLA is new
>>> after
>>>> your proposal then likely [2] needs to be updated instead. After which
>>> your
>>>> mentors should be verifying the distribution rights.
>>>> 
>>>> 
>>>> [1]: https://incubator.apache.org/ip-clearance/index.html
>>>> [2]: https://incubator.apache.org/projects/flagon.html
>>>> 
>>>> On Mon, Aug 29, 2022, 21:06 Joshua Poore  wrote:
>>>> 
>>>>> Hello General!
>>>>> 
>>>>> Refreshing this 72 VOTE:
>>>>> 
>>>>> I am looking for additional review and binding VOTEs from the
>>> Incubator
>>>>> regarding a recent SW grant (via CCLA) from UMD to the Flagon
>>> Podling. The
>>>>> Flagon community has VOTED to accept for reasons outlined below and
>>>>> Secretary has accepted the CCLA. We are seeking concurrence from the
>>>>> incubator.
>>>>> 
>>>>> Details follow:
>>>>> 
>>>>>> On Aug 19, 2022, at 9:32 PM, Joshua Poore 
>>> wrote:
>>>>>> 
>>>>>> Hello Incubator!
>>>>>> 
>>>>>> I am continuing a 72 VOTE from the Flagon Community on Incubator
>>> General
>>>>> regarding the acceptance of an ICLA and Software Grant into the Apache
>>>>> Flagon (Incubating) Podling.
>>>>>> 
>>>>>> The purpose of this VOTE is to establish consensus and transparency
>>> wrt
>>>>> to IP Clearance.
>>>>>> 
>>>>>> We conducted a Community Discussion @ Flagon and a VOTE.
>>>>>> 
>>>>>> VOTE Thread on Flagon Private:
>>>>> https://lists.apache.org/thread/t5gof3sj40xrv2ylrgntx6oz2vdcc37t
>>>>>> 
>>>>>> VOTE Result on Flagon Private:
>>>>> https://lists.apache.org/thread/dvz7rtxl77pfqb3c3tgn36g1wbfgr54h
>>>>>> 
>>>>>> [3] +1 (+2 Binding)
>>>>>> [0] 0
>>>>>> [0] -1
>>>>>> 
>>>>>> Accepted Submission of ICLA to Secretary:
>>>>> https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Respectfully,
>>>>>> 
>>>>>> Josh (Flagon PPMC)
>>>>>> 
>>>>>> 
>>>>>> Details on the Software Grant Follow (copied from original Flagon
>>> VOTE)
>>>>> below:
>>>>>> 
>>>>>> 
>>>>>> The Software Grant encompasses a refactor of the Apache Flagon
>>> Distill
>>>>> product, which has been deprecated for a few years now [1]
>>>>> 
>>>>>> This Grant includes ~150 new commits and thousands of new insertions
>>>>> (and a lot of deletions)  At UMD my team and I re-thought Distill as a
>>>>> Python Package (for distro through PyPI) [2] that allows users to:
>>>>> 
>>>>>> - efficiently segment UserALE.js (or User Behavior Logs) data
>>>>> 
>>>>>> - curate segments - transform segments with logical operations
>>>>> (intersection, union, etc.)
>>>>> 
>>>>>> - filter log data extracted from segments
>>>>> 
>>>>>> - apply analytics (e.g., statistical, graphs) to data extracted from
>>>>> segments
>>>>> 
>>>>>> - support graph-based visualization (funnel, sankey)
>>>>> 
>>>>>> Additionally:
>>>>> 
>>>>>> - code is well documented [3]
>>>>> 
>>>>>> - excellent working examples [4]
>>>>> 
>>>>>> Distill also provides examples for dashboards to visualize segments
>>>>> using both Apache Superset and Plotly/Dash
>>>>> 
>>>>>> The original Distill product was tethered to a front-end (Tap),
>>> relied
>>>>> on rudimenta

Re: [VOTE] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling

[Joshua Poore]

Thanks, John!

This is very helpful links!

Best,

Josh

> On 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
> repo I linked in a bit, but I'm not seeing any major issues with the code.
> 
> - John
> 
> [1]:
> https://github.com/UMD-ARLIS/incubator-flagon-distill/tree/distill_toolkit_refactor
> TLPs: https://lists.apache.org/thread/r7jx0d2fy37kwj792n0qf5rcttyqzmzp ,
> https://lists.apache.org/thread/b2gmkbp879m72gdyztl674tqhtpdl7zn
> 
> [1]:
> https://github.com/UMD-ARLIS/incubator-flagon-distill/tree/distill_toolkit_refactor
> 
> On Wed, Sep 14, 2022 at 5:52 PM Joshua C. Poore  wrote:
> 
>> Hi John,
>> 
>> Thanks for your response.
>> 
>> I had a long thread with Calvin, Justin, and Craig Russell to clarify the
>> process of onboarding new SW grants into existing podlings RE CCLA. The
>> thread is on private@incubator, which I'm unable to grab a permalink for
>> through lists...
>> 
>> Bottom line up front: Suggestion was that formal votes through the
>> incubator were not necessary in this case, but discussion and a vote on
>> general level was encouraged to document consensus.
>> 
>> Trying to adhere to good practice, but at this point a "consensus vote" on
>> general is perfunctory.
>> 
>> Respectfully,
>> 
>> Josh (Flagon PPMC)
>> 
>> On 2022/08/30 11:05:03 "John D. Ament" wrote:
>>> Note that you're using public and private lists which is a big no-no.
>>> 
>>> I'll be honest I don't understand what you're trying to get the IPMC to
>>> vote on. You may need some help from mentors. I saw IP clearance and will
>>> point out that [1] isn't for podlings.  Likewise if this CCLA is new
>> after
>>> your proposal then likely [2] needs to be updated instead. After which
>> your
>>> mentors should be verifying the distribution rights.
>>> 
>>> 
>>> [1]: https://incubator.apache.org/ip-clearance/index.html
>>> [2]: https://incubator.apache.org/projects/flagon.html
>>> 
>>> On Mon, Aug 29, 2022, 21:06 Joshua Poore  wrote:
>>> 
>>>> Hello General!
>>>> 
>>>> Refreshing this 72 VOTE:
>>>> 
>>>> I am looking for additional review and binding VOTEs from the Incubator
>>>> regarding a recent SW grant (via CCLA) from UMD to the Flagon Podling.
>> The
>>>> Flagon community has VOTED to accept for reasons outlined below and
>>>> Secretary has accepted the CCLA. We are seeking concurrence from the
>>>> incubator.
>>>> 
>>>> Details follow:
>>>> 
>>>>> On Aug 19, 2022, at 9:32 PM, Joshua Poore 
>> wrote:
>>>>> 
>>>>> Hello Incubator!
>>>>> 
>>>>> I am continuing a 72 VOTE from the Flagon Community on Incubator
>> General
>>>> regarding the acceptance of an ICLA and Software Grant into the Apache
>>>> Flagon (Incubating) Podling.
>>>>> 
>>>>> The purpose of this VOTE is to establish consensus and transparency
>> wrt
>>>> to IP Clearance.
>>>>> 
>>>>> We conducted a Community Discussion @ Flagon and a VOTE.
>>>>> 
>>&

Re: [MENTORS] Late podling reports and missing signoffs

[Joshua Poore]

Thanks Calvin! I’ll alert mentors to the move!

Joshua Poore


> On Sep 14, 2022, at 8:39 PM, Calvin Kirs  wrote:
> 
> Joshua Poore  于2022年9月15日周四 08:21写道：
>> 
>> Thanks Justin!
>> 
>> I didn’t see a record for Flagon in the Sept report… OK to paste back in on 
>> my end?
> 
> hi, I have copied the report from the OCT report. (I deleted the
> previous record due to no submission due), thank you for your
> submission.
>> 
>> Josh
>> 
>> Joshua Poore
>> 
>> 
>>>> On Sep 14, 2022, at 6:24 PM, Justin Mclean  
>>>> wrote:
>>> 
>>> Hi,
>>> 
>>>> Apologies RE Flagon reporting. Just missed the window for SEPT. I have 
>>>> added a report for OCT and requested Mentor review earlier.
>>> 
>>> You still have a couple of day in which you could submit it.
>>> 
>>> Kind Regards,
>>> Justin
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> -- 
> Best wishes！
> CalvinKirs
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] Late podling reports and missing signoffs

[Joshua Poore]

Thanks Justin!

I didn’t see a record for Flagon in the Sept report… OK to paste back in on my 
end?

Josh

Joshua Poore


> On Sep 14, 2022, at 6:24 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Apologies RE Flagon reporting. Just missed the window for SEPT. I have added 
>> a report for OCT and requested Mentor review earlier.
> 
> You still have a couple of day in which you could submit it.
> 
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling

[Joshua Poore]

Hello General!

Refreshing this 72 VOTE:

I am looking for additional review and binding VOTEs from the Incubator 
regarding a recent SW grant (via CCLA) from UMD to the Flagon Podling. The 
Flagon community has VOTED to accept for reasons outlined below and Secretary 
has accepted the CCLA. We are seeking concurrence from the incubator. 

Details follow: 

> On Aug 19, 2022, at 9:32 PM, Joshua Poore  wrote:
> 
> Hello Incubator!
> 
> I am continuing a 72 VOTE from the Flagon Community on Incubator General 
> regarding the acceptance of an ICLA and Software Grant into the Apache Flagon 
> (Incubating) Podling.
> 
> The purpose of this VOTE is to establish consensus and transparency wrt to IP 
> Clearance. 
> 
> We conducted a Community Discussion @ Flagon and a VOTE.
> 
> VOTE Thread on Flagon Private: 
> https://lists.apache.org/thread/t5gof3sj40xrv2ylrgntx6oz2vdcc37t
> 
> VOTE Result on Flagon Private: 
> https://lists.apache.org/thread/dvz7rtxl77pfqb3c3tgn36g1wbfgr54h
> 
> [3] +1 (+2 Binding)
> [0] 0 
> [0] -1
> 
> Accepted Submission of ICLA to Secretary: 
> https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw
> 
> 
> 
> Respectfully,
> 
> Josh (Flagon PPMC)
> 
> 
> Details on the Software Grant Follow (copied from original Flagon VOTE) below:
> 
> 
> The Software Grant encompasses a refactor of the Apache Flagon Distill 
> product, which has been deprecated for a few years now [1] 

> This Grant includes ~150 new commits and thousands of new insertions (and a 
> lot of deletions)  At UMD my team and I re-thought Distill as a Python 
> Package (for distro through PyPI) [2] that allows users to:

>  - efficiently segment UserALE.js (or User Behavior Logs) data

> - curate segments - transform segments with logical operations (intersection, 
> union, etc.)

> - filter log data extracted from segments

> - apply analytics (e.g., statistical, graphs) to data extracted from segments

> - support graph-based visualization (funnel, sankey)  

> Additionally:

> - code is well documented [3]

> - excellent working examples [4]  

> Distill also provides examples for dashboards to visualize segments using 
> both Apache Superset and Plotly/Dash  

> The original Distill product was tethered to a front-end (Tap), relied on 
> rudimentary (and error-prone) processing of segments within the client. This 
> made Distill difficult to maintain and required users to adopt tap, limiting 
> their analytical use-cases with UserALE.js and Distill.  Overall, I think 
> that Distill provides a far more scaleable product to engage (and expand) our 
> development community. I think this will add real value to Apache Flagon.  


> Overhead/Actions prior to release:

>  - Documentation builds will need be adjusted for a new repo/branch

> - Additional documentation for a few analytical functions (i.e., click-rate)

> - Minor tweaks to simply code in a few functions (i.e., click-rate)

> - Some restructuring of Repo to consolidate and organize examples

> - a few additional README’s should be added (i.e., examples /dir)  

> IP Clearance  The Software Grant is signed by Felicia Metz, esq. who is an 
> Associate Director at the University of Maryland’s, UMD Ventures office, 
> which has authority to release UMD IP. That makes accepting this grant 
> significantly easier from an IP Clearance perspective.  New Committers  The 
> UMD executed CCLA includes 5 new committers and potentially new PPMC members 
> [see 5 for executed Software Grant from UMD]
> 
> [1] https://github.com/apache/incubator-flagon-distill 
> [2] 
> https://github.com/UMD-ARLIS/incubator-flagon-distill/tree/distill_toolkit_refactor
>  
> [3] 
> https://incubator-flagon-distill.readthedocs.io/en/distill_toolkit_refactor 
> [4] 
> https://github.com/UMD-ARLIS/incubator-flagon-distill/blob/distill_toolkit_refactor/examples/Segments_Demo.ipynb
>  
> [5] https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling

[Joshua Poore]

Hello Incubator!

I am continuing a 72 VOTE from the Flagon Community on Incubator General 
regarding the acceptance of an ICLA and Software Grant into the Apache Flagon 
(Incubating) Podling.

The purpose of this VOTE is to establish consensus and transparency wrt to IP 
Clearance. 

We conducted a Community Discussion @ Flagon and a VOTE.

VOTE Thread on Flagon Private: 
https://lists.apache.org/thread/t5gof3sj40xrv2ylrgntx6oz2vdcc37t

VOTE Result on Flagon Private: 
https://lists.apache.org/thread/dvz7rtxl77pfqb3c3tgn36g1wbfgr54h

[3] +1 (+2 Binding)
[0] 0 
[0] -1

Accepted Submission of ICLA to Secretary: 
https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw



Respectfully,

Josh (Flagon PPMC)


Details on the Software Grant Follow (copied from original Flagon VOTE) below:


 The Software Grant encompasses a refactor of the Apache Flagon Distill 
product, which has been deprecated for a few years now [1]  This Grant includes 
~150 new commits and thousands of new insertions (and a lot of deletions)  At 
UMD my team and I re-thought Distill as a Python Package (for distro through 
PyPI) [2] that allows users to:  - efficiently segment UserALE.js (or User 
Behavior Logs) data - curate segments - transform segments with logical 
operations (intersection, union, etc.) - filter log data extracted from 
segments - apply analytics (e.g., statistical, graphs) to data extracted from 
segments - support graph-based visualization (funnel, sankey)  Additionally: - 
code is well documented [3] - excellent working examples [4]  Distill also 
provides examples for dashboards to visualize segments using both Apache 
Superset and Plotly/Dash  The original Distill product was tethered to a 
front-end (Tap), relied on rudimentary (and error-prone) processing of segments 
within the client. This made Distill difficult to maintain and required users 
to adopt tap, limiting their analytical use-cases with UserALE.js and Distill.  
Overall, I think that Distill provides a far more scaleable product to engage 
(and expand) our development community. I think this will add real value to 
Apache Flagon.  Overhead/Actions prior to release:  - Documentation builds will 
need be adjusted for a new repo/branch - Additional documentation for a few 
analytical functions (i.e., click-rate) - Minor tweaks to simply code in a few 
functions (i.e., click-rate) - Some restructuring of Repo to consolidate and 
organize examples - a few additional README’s should be added (i.e., examples 
/dir)  IP Clearance  The Software Grant is signed by Felicia Metz, esq. who is 
an Associate Director at the University of Maryland’s, UMD Ventures office, 
which has authority to release UMD IP. That makes accepting this grant 
significantly easier from an IP Clearance perspective.  New Committers  The UMD 
executed CCLA includes 5 new committers and potentially new PPMC members [see 5 
for executed Software Grant from UMD]

[1] https://github.com/apache/incubator-flagon-distill 
  [2] 
https://github.com/UMD-ARLIS/incubator-flagon-distill/tree/distill_toolkit_refactor
 

  [3] 
https://incubator-flagon-distill.readthedocs.io/en/distill_toolkit_refactor 
/  
[4] 
https://github.com/UMD-ARLIS/incubator-flagon-distill/blob/distill_toolkit_refactor/examples/Segments_Demo.ipynb
 

 
[5] https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw

Re: [ANNOUNCE] Release of Apache Flagon UserALE.js (Incubator) v2.3.0

[Joshua Poore]

The Apache Flagon team is pleased to announce the immediate availability of 
Apache Flagon UserALE.js (Incubating) version 2.3.0

Apache Flagon UserALE.js (Incubating) is a free, open-source application for 
thin-client behavioral logging. Apache UserALE.js is suited for business 
analytics and enterprise application monitoring, but built for precision 
workflow analysis, UI/UX research and user-testing. Apache UserALE.js 
(Incubating) uses the Apache Software License v2.0.

The version 2.3.0 release addresses/adds [issues/functionality]:
• 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

The full CHANGELOG can be found linked on Apache Flagon's Releases page: 
http://flagon.incubator.apache.org/releases/ 


Apache UserALE.js (Incubating) v2.3.0 release artifacts are available through 
the Apache Software Foundation's official download mirrors, which can be 
accessed conveniently through the Apache Flagon website download page: 
http://flagon.incubator.apache.org/releases/ 
. This release is also available 
as an npm package for node.js applications, found on the npm registry: 
https://www.npmjs.com/package/flagon-userale 
.


Thank You,

Joshua C. Poore (on behalf of Apache Flagon PPMC)

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

[Joshua Poore]

Thank you to all who participated in the VOTE to release Apache Flagon 
(Incubating) UserALE.js 2.3.0

The VOTE has elapsed. The complete thread can be found here: 
https://lists.apache.org/thread/99gx99xmc32dsthwdj2ml231n9hdz75q

RESULT:

[ 6 ] +1 (+3 Binding/IPMC)
[ 0 ] 0
[ 0 ] -1

The VOTE passes! We will continue with release procs.

Thank You,

Josh (Flagon PPMC)

> On May 19, 2022, at 9:34 AM, Calvin Kirs  wrote:
> 
> Hi,
> +1 (binding)
> 
> I checked :
> - Incubating in name
> - LICENSE and NOTICE are fine
> - DISCLAIMER exists
> - No unexpected binary files
> - All ASF files have ASF headers
> - Checksums and GPG signatures are valid.
> 
> Furkan KAMACI  于2022年5月19日周四 09:51写道：
>> 
>> Hi,
>> 
>> +1 from me (binding, carrying over my vote).
>> 
>> 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 Thu, May 19, 2022 at 4:06 AM Joshua Poore  wrote:
>> 
>>> IPMC,
>>> 
>>> Please VOTE on our Release Candidate for Apache Flagon (Incubating)
>>> UserALE.js 2.3.0
>>> 
>>>> On May 10, 2022, at 5:18 PM, Joshua Poore  wrote:
>>>> 
>>>> Hello IPMC—
>>>> 
>>>> Please VOTE on the Apache Flagon (Incubating) UserALE.js 2.3.0 Release
>>> Candidate # 01.
>>>> 
>>>> Flagon Community VOTE can be found here:
>>> https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv <
>>> https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv>
>>>> 
>>>> Summary of Community VOTE:
>>>> 
>>>> +1 : 4 (1 IPMC Binding - Furkan Kamaci, 2 PPMC Non-Binding)
>>>> +0: 0
>>>> -1: 0
>>>> 
>>>> About Flagon: http://flagon.incubator.apache.org/ <
>>> 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 <
>>> 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
>>> <
>>> 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/ <
>>> 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/
>>> <
>>> 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 <
>>> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS>
>>>> 
>>>> Link to Successful CI Build:
>>> https://github.com/apache/incubator-flagon-useralejs/runs/5958813955 <
>>> 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
>>> <
>>> 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 

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

[Joshua Poore]

IPMC,

Please VOTE on our Release Candidate for Apache Flagon (Incubating) UserALE.js 
2.3.0

> On May 10, 2022, at 5:18 PM, Joshua Poore  wrote:
> 
> Hello IPMC— 
> 
> Please VOTE on the Apache Flagon (Incubating) UserALE.js 2.3.0 Release 
> Candidate # 01.
> 
> Flagon Community VOTE can be found here: 
> https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv 
> <https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv> 
> 
> Summary of Community VOTE:
> 
> +1 : 4 (1 IPMC Binding - Furkan Kamaci, 2 PPMC Non-Binding)
> +0: 0
> -1: 0
> 
> About Flagon: http://flagon.incubator.apache.org/ 
> <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 
> <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 
> <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/ 
> <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/
>  
> <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 
> <https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS>
> 
> Link to Successful CI Build: 
> https://github.com/apache/incubator-flagon-useralejs/runs/5958813955 
> <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
>  
> <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
> [ x ] New source code (React app, OpenTelemetry Ex) have compatible licenses 
> (ALv2, MIT)
> [ x ] All Source Files Have Correct ASF Headers (ran RAT tool: only json / 
> .png files exclude headers)
> [ x ] No Binary Files in Source Release Packages (except for supporting .png 
> files)
> 
> 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.3.0!


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Flagon UserALE.js 2.3.0

[Joshua Poore]

Hello IPMC— 

Please VOTE on the Apache Flagon (Incubating) UserALE.js 2.3.0 Release 
Candidate # 01.

Flagon Community VOTE can be found here: 
https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv 
 

Summary of Community VOTE:

+1 : 4 (1 IPMC Binding - Furkan Kamaci, 2 PPMC Non-Binding)
+0: 0
-1: 0

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
[ x ] New source code (React app, OpenTelemetry Ex) have compatible licenses 
(ALv2, MIT)
[ x ] All Source Files Have Correct ASF Headers (ran RAT tool: only json / .png 
files exclude headers)
[ x ] No Binary Files in Source Release Packages (except for supporting .png 
files)

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.3.0!

Re: [MENTORS] Old releases in release area

[Joshua Poore]

Flagon’s old releases are removed.

Thnx

> On Apr 27, 2021, at 12:59 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> A few projects need to clean up their release area as they have multiple 
> releases listed in then, only the last release need to be listed as the older 
> releases are archived. [16]
> 
> The projects are:
> Crail [1]
> DataLab [2]
> Doris [3]
> Flagon [4]
> Hivemall [5]
> Livy [6]
> Milagro [7]
> MXNet [8]
> Nemo [9]
> NLPCraft [10]
> NuttX [11]
> Pinot [12]
> Toree [13]
> Tuweni [14]
> YuniKorn [15]
> 
> Thanks,
> Justin
> 
> 1. https://dist.apache.org/repos/dist/release/incubator/crail/
> 2. https://dist.apache.org/repos/dist/release/incubator/datalab/
> 3. https://dist.apache.org/repos/dist/release/incubator/doris/
> 4. https://dist.apache.org/repos/dist/release/incubator/flagon/
> 5. https://dist.apache.org/repos/dist/release/incubator/hivemall/
> 6. https://dist.apache.org/repos/dist/release/incubator/livy/
> 7. https://dist.apache.org/repos/dist/release/incubator/milagro/
> 8. https://dist.apache.org/repos/dist/release/incubator/mxnet/
> 9 https://dist.apache.org/repos/dist/release/incubator/nemo/
> 10. https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/
> 11. https://dist.apache.org/repos/dist/release/incubator/nuttx/
> 12. https://dist.apache.org/repos/dist/release/incubator/pinot/
> 13. https://dist.apache.org/repos/dist/release/incubator/toree/
> 14. https://dist.apache.org/repos/dist/release/incubator/tuweni/
> 15. https://dist.apache.org/repos/dist/release/incubator/yunikorn/
> 16 https://archive.apache.org/dist/incubator/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] Old releases in release area

[Joshua Poore]

Copy. Flagon is on it. Thanks for heads up!

Joshua Poore


> On Apr 27, 2021, at 9:13 AM, Dave Fisher  wrote:
> 
> The clutch analysis for each podling provides a list of each valid release 
> in the distribution area.
> 
> eg. http://incubator.apache.org/clutch/doris
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On Apr 26, 2021, at 10:00 PM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> A few projects need to clean up their release area as they have multiple 
>> releases listed in then, only the last release need to be listed as the 
>> older releases are archived. [16]
>> 
>> The projects are:
>> Crail [1]
>> DataLab [2]
>> Doris [3]
>> Flagon [4]
>> Hivemall [5]
>> Livy [6]
>> Milagro [7]
>> MXNet [8]
>> Nemo [9]
>> NLPCraft [10]
>> NuttX [11]
>> Pinot [12]
>> Toree [13]
>> Tuweni [14]
>> YuniKorn [15]
>> 
>> Thanks,
>> Justin
>> 
>> 1. https://dist.apache.org/repos/dist/release/incubator/crail/
>> 2. https://dist.apache.org/repos/dist/release/incubator/datalab/
>> 3. https://dist.apache.org/repos/dist/release/incubator/doris/
>> 4. https://dist.apache.org/repos/dist/release/incubator/flagon/
>> 5. https://dist.apache.org/repos/dist/release/incubator/hivemall/
>> 6. https://dist.apache.org/repos/dist/release/incubator/livy/
>> 7. https://dist.apache.org/repos/dist/release/incubator/milagro/
>> 8. https://dist.apache.org/repos/dist/release/incubator/mxnet/
>> 9 https://dist.apache.org/repos/dist/release/incubator/nemo/
>> 10. https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/
>> 11. https://dist.apache.org/repos/dist/release/incubator/nuttx/
>> 12. https://dist.apache.org/repos/dist/release/incubator/pinot/
>> 13. https://dist.apache.org/repos/dist/release/incubator/toree/
>> 14. https://dist.apache.org/repos/dist/release/incubator/tuweni/
>> 15. https://dist.apache.org/repos/dist/release/incubator/yunikorn/
>> 16 https://archive.apache.org/dist/incubator/
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hi All,

Time for the VOTE on Releasing Apache Flagon UserALE.js (Incubating) 2.1.1 has 
elapsed.

The VOTE has PASSED.

The RESULT is as follows:

[ 6 ] +1, let's get it released!!!
[ 0 ] +/-0, fine, but consider to fix few issues before…
[ 0 ] -1, nope, because... (and please explain why)

The VOTE passes with +6 in favor of the Release.

+3 (Binding) VOTES from IPMC (Mentors)
—
Lewis Mcgibbney
David Meikle
Furkan Kamaci

We’ll package the release for distro through our Apache mirrors and NPM in 
advance of our official ANNOUNCEMENT.

Thanks all!

Josh

> On Mar 10, 2021, at 9:02 PM, Joshua Poore  wrote:
> 
> Hi general@ 
> 
> Please take a look at our release if you can. 
> 
> Sincerely,
> 
> poorejc
> 
>> On Mar 6, 2021, at 9:49 PM, Joshua Poore  wrote:
>> 
>> Hello general@,
>> 
>> Please VOTE on the Apache Flagon UserALE.js 2.1.1 Release Candidate # 02.
>> 
>> About Flagon: http://flagon.incubator.apache.org/
>> 
>> Link to Community VOTE thread: 
>> https://lists.apache.org/thread.html/r5f246d4f1e7a28a919e55c0c6a24e2d55c2abf80c8b41ea268f943a8%40%3Cdev.flagon.apache.org%3E
>> 
>> RESULT from Community VOTE thread:
>> 
>> [ 6 ] +1, let's get it released!!!
>> [ 0 ] +/-0, fine, but consider to fix few issues before…
>> [ 0 ] -1, nope, because... (and please explain why)
>> 
>> +3 from PPMC and +3 are Binding (IPMC mentors)
>> 
>> The 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)
>> 
>> 
>> Release Candidate Details Follow:
>> 
>> 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+Testing+Framework
>> 
>> 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
> 
> 
> -
> 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.1

[Joshua Poore]

Hi general@ 

Please take a look at our release if you can. 

Sincerely,

poorejc

> On Mar 6, 2021, at 9:49 PM, Joshua Poore  wrote:
> 
> Hello general@,
> 
> Please VOTE on the Apache Flagon UserALE.js 2.1.1 Release Candidate # 02.
> 
> About Flagon: http://flagon.incubator.apache.org/
> 
> Link to Community VOTE thread: 
> https://lists.apache.org/thread.html/r5f246d4f1e7a28a919e55c0c6a24e2d55c2abf80c8b41ea268f943a8%40%3Cdev.flagon.apache.org%3E
> 
> RESULT from Community VOTE thread:
> 
> [ 6 ] +1, let's get it released!!!
> [ 0 ] +/-0, fine, but consider to fix few issues before…
> [ 0 ] -1, nope, because... (and please explain why)
> 
> +3 from PPMC and +3 are Binding (IPMC mentors)
> 
> The 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)
> 
> 
> Release Candidate Details Follow:
> 
> 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+Testing+Framework
> 
> 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


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hello general@,

Please VOTE on the Apache Flagon UserALE.js 2.1.1 Release Candidate # 02.

About Flagon: http://flagon.incubator.apache.org/

Link to Community VOTE thread: 
https://lists.apache.org/thread.html/r5f246d4f1e7a28a919e55c0c6a24e2d55c2abf80c8b41ea268f943a8%40%3Cdev.flagon.apache.org%3E

RESULT from Community VOTE thread:

[ 6 ] +1, let's get it released!!!
[ 0 ] +/-0, fine, but consider to fix few issues before…
[ 0 ] -1, nope, because... (and please explain why)

+3 from PPMC and +3 are Binding (IPMC mentors)

The 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)


Release Candidate Details Follow:

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/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+Testing+Framework

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

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

[Joshua Poore]

Justin,

You’re right. Lapse of judgement under pressure by users—parallel VOTE threads 
is bad process.

Cancelling this VOTE. Carrying votes on the thread back to dev, and will let 
voting continue for 72 hrs (vote is currently passing).

Apologies.

This release is in the spirit of graduation—you’ll see movement on that very 
soon.

Thanks,

Josh

> On Feb 21, 2021, at 3:30 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> For a major or minor release I would. This is a patch release, and would 
>> like start wrangling requisite binding votes to shorten release/voting time.
> 
> I'm sorry but that the process is you need to vote first on your dev list and 
> then here, not following this process take up IPMC when a vote that should be 
> on a dev list doesn’t pass.
> 
> Please cancel this votes and bring it back here once teh vote has passed on 
> the your dev list. If you don’t want the IPMC valuing on your release then 
> graduate :-)
> 
> Kind Regards,
> Justin
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
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.1

[Joshua Poore]

+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


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

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/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: [VOTE] Graduate Apache Flagon (incubating) as a Top Level Project

[Joshua Poore]

Hi All,

> On Oct 8, 2020, at 12:29 PM, Dave Fisher  wrote:
> 
> 
> 
>> On Oct 8, 2020, at 9:20 AM, Lewis John McGibbney  wrote:
>> 
>> Hi Justin,
>> 
>> On 2020/10/08 06:22:37, Justin Mclean  wrote: 
>> 
>>> So assuming 2 of the products are no longer maintained but it looks like 
>>> the other 2 without releases are. Are they going to be maintained and is 
>>> there some intention of making a releases of them in the future?
>>> 
>> 
>> Products which have been released
>> * UserALE.js

UserALE.js has had Apache releases and is actively maintained and developed 
against. Should be a new minor release later this quarter

>> 
>> Products which may be released
>> * UserALE.PyQt5 (I think)

UserALE.pyqt5 will be retired

>> 
>> Product which have not been released and are not maintained
>> * Distill - http://flagon.apache.org/docs/distill/
>> * TAP - http://flagon.apache.org/docs/tap/
>> * STOUT - http://flagon.apache.org/docs/stout/

STOUT and TAP will also be retired

We’re pulling relevant functionality from those to sub-projects into Distill, 
which will be released after a significant refactor. 

> 
> Assuming that the IP is clear and a future release has no known Policy issues 
> then I’m ok.
> 
> If these are truly to be retired then it might be friendly to make the 
> repository read only after adding a DISCLAIMER to the README file. This 
> DISCLAIMER might include that the repository may not have all the expected IP 
> review that an Apache Release has and that it should be used to the user’s 
> own risk.

We have some disclaimers notices in our READMEs, but agree should also go in 
DISCLAIMER file until projects are shelved or re-released. Good action.

Will coordinate with docs/website update

Will also beat bushes to get committers subscribed to the right lists.

> 
> Not blockers to me.
> 
> Regards,
> Dave
> 

Thanks, all!

>> 
>> I hope this clarifies.
>> Thank you
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>> 
>> For additional commands, e-mail: general-h...@incubator.apache.org 
>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> 
> For additional commands, e-mail: general-h...@incubator.apache.org 
> 

Re: [MENTORS] July reports due today Wednesday 1st July

[Joshua Poore]

Flagon’s report is posted for Mentor review on the wiki. Sorry for the delay.

-J

> On Jun 30, 2020, at 8:55 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> Thanks for for the submitted from from several podlings. 
> 
> Reports are due today and we’re still missing a report from the following 
> projects:
> 
> AGE 
> Annotator 
> BlueMarlin 
> Flagon 
> Gobblin 
> Hivemall 
> Liminal 
> Livy 
> Milagro 
> MXNet 
> NuttX 
> Pony Mail 
> Warble 
> Weex 
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] https://www.apache.org/dist/ has been deprecated

[Joshua Poore]

Flagon’s download page links have been updated to point @ 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 
> . Thank you for the notification Justin.
> 
> 
> 
> DolphinScheduler(Incubator) PPMC
> Gang Li 李岗
> 
> 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
> 

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

[Joshua Poore]

The VOTE to Release Apache Flagon UserALE.js (Incubating) ver 2.1.0 has passed, 
and is closed.

RESULT is as follows:

[ 6 ] +1 

Justin Mclean (IPMC)
Dave Meikle (IPMC)
Tim Allison (IPMC)
Furkan Kamaci (IPMC)
Rob Foley (PPMC)
Joshua Poore (PPMC)

[ 0 ]  0 
[ 0 ] -1 

Thank You to all that voted and contributed to the Release.

I will complete the Release checklist and ANNOUNCE.

Thanks,

Josh


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] https://www.apache.org/dist/ has been deprecated

[Joshua Poore]

Copy. Will update links with new release (which seems imminent)

Sent from my iPhone

> On Mar 4, 2020, at 4:14 AM, Justin Mclean  wrote:
> 
> 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
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hi Folks,
 
Continuing this VOTE to release Apache Flagon UserALE.js (Incubating) 2.1.0 RC1 
on general@ for release approval
 
VOTE carried over from dev@ are sufficient for Release:

[ 5 ] +1, let's get it released!!!

Dave Meikle (Binding)
Tim Allison (Binding)
Furkan Kamaci (Binding)
Rob Foley
Joshua Poore

[ 0 ] +/-0, fine, but consider to fix few issues before...
[ 0 ] -1, nope, because... (and please explain why)

VOTE Thread: 
https://lists.apache.org/thread.html/r349e933464eb84ecb7326012b98bc1bec6505fa7da84b58200120c59%40%3Cdev.flagon.apache.org%3E

Two Minor issues were discovered during the VOTE that will be resolved in the 
next release:
1. NOTICE FILE should be copyright 2020 ASF (is currently 2019-2020)
2. ALv2 License Header Missing from webpack.config.js in /examples directory 
(has been fixed at Master for next release)

Download Page: 
http://flagon.incubator.apache.org/releases/ (links have not yet been updated 
pending release)

This release will also be made available through NPM: 
https://www.npmjs.com/package/flagon-userale 

This VOTE will be open on general@ for 72 hours.

Thnx!

Release Details Follow:

About Flagon: 
http://flagon.incubator.apache.org/

 
This Minor release includes :
 
• Module package-bundler deployment support (include UserALE.js via 
'import' & 'require')
• Updated existing example page to include a range of HTML elements
• New example page for including UserALE.js as a module (Webpack 
example)
• Added support for logging from HTML Forms
• Added SessionId persistence via SessionStorage
• Exposes a wide range of functions to support custom logging with 
UserALE.js
• Added support for passing auth-headers via log pipeline to back-end
• Added additional log fields: browser type and version, inner 
width/height (for heatmaps)
 
We solved 31 issues: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345442=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED_8301b4e9c1c91354ea85ab02c89ec979db077d9a_lin
 
 
Git source tag (7746500): 
https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.1.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.1.0-RC-01/
 
 
PGP release keys (signed using F9374FAE3FCADF6E): 
https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS 
 
Link to Successful Jenkins Build: 
https://builds.apache.org/job/useralejs-ci/101/ 
 
Reference to UserALE.js testing framework to assist in verifying this release: 
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.1.0

[ANNOUNCE] Release of Apache Flagon UserALE.js (Incubator) v2.0.2

[Joshua Poore]

The Apache Flagon team is pleased to announce the immediate availability of 
Apache Flagon UserALE.js (Incubating) version 2.0.2
  
Apache Flagon UserALE.js (Incubating) is a free, open-source application for 
thin-client behavioral logging. Apache UserALE.js is suited for business 
analytics and enterprise application monitoring, but built for precision 
workflow analysis, UI/UX research and user-testing. Apache UserALE.js 
(Incubating) uses the Apache Software License v2.0.
 
The version 2.0.2 release addresses/adds [issues/functionality]:
• 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.

The full CHANGELOG can be found linked on Apache Flagon's Releases page: 
http://flagon.incubator.apache.org/releases/
 
Apache UserALE.js (Incubating) v2.0.2 release artifacts are available through 
the Apache Software Foundation's official download mirrors, which can be 
accessed conveniently through the Apache Flagon website download page: 
http://flagon.incubator.apache.org/releases/. This release is also available as 
an npm package for node.js applications, found on the npm registry: 
https://www.npmjs.com/package/flagon-userale.
 
 
Thank You,
 
Joshua C. Poore (on behalf of Apache Flagon PPMC)
 
 
Apache Flagon is an effort undergoing incubation at The Apache Software 
Foundation (ASF),
sponsored by the Apache Incubator project. Incubation is required of all newly 
accepted
projects until a further review indicates that the infrastructure, 
communications, and
decision making process have stabilized in a manner consistent with other 
successful
ASF projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project has 
yet to be
fully endorsed by the ASF.

Note: This announcement is a corrected version of a previous announcement
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Release of Apache Flagon UserALE.js (Incubating) v2.0.2

[Joshua Poore]

The Flagon team is pleased to announce the immediate availability of Apache 
Flagon UserALE.js (Incubating) version 2.0.2.
  
Apache UserALE.js (Incubating) is Apache Flagon's free, open-source application 
for thin-client behavioral logging. UserALE.js is suited for business analytics 
and enterprise application monitoring, but built for precision workflow 
analysis, UI/UX research and user-testing. Apache UserALE.js (Incubating) uses 
the Apache Software License v2.0.
 
The version 2.0.2 release addresses/adds [issues/functionality]:
• 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.
 
The full CHANGELOG can be found on Flagon's JIRA instance [0].
 
Apache UserALE.js (Incubating) v2.0.2 release artifacts are available through 
the Apache Software Foundation's official download mirrors, which can be 
accessed conveniently through the Flagon website download page [1]. This 
release is also available as source code on GitHub [2], and as an npm package 
for node.js applications, found on the npm registry [3].
 
 
Thank You,
 
Joshua C. Poore (on behalf of Apache Flagon PPMC)
  
[0] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621=12345954
[1] 
https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.2-08_21_2019
 
[2] http://flagon.incubator.apache.org/releases/
[3] https://www.npmjs.com/package/flagon-userale
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] was [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.2

[Joshua Poore]

All,

The VOTE to Release Apache Flagon UserALE.js (Incubating) v2.0.2 has concluded. 
Thanks to all who voted.

This VOTE has passed successfully within the Apache Flagon community and the 
Incubator Project community. 

The VOTE tally is as follows:

[+1] 8  
Joshua Poore
Rob Foley (`Confused`)
Laura Mariano
Furkan Kamaci*
Arthi Vezhavendan
Tim Allison*
Dave Meikle*
Justin McLean*

[0] 0

[-1]

*Binding IPMC VOTE

The Apache Flagon community will progress to remaining release processes.


Thanks,

Joshua Poore (FLAGON PPMC)


> On Aug 20, 2019, at 12:40 AM, Dave Fisher  wrote:
> 
> You have enough IPMC votes from your mentors.
> 
> I think you are good.
> 
> Sent from my iPhone
> 
>> On Aug 19, 2019, at 7:36 PM, Joshua Poore  wrote:
>> 
>> Hi Folks—
>> 
>> Just a reminder to VOTE on Apache Flagon UserALE.js (Incubating) v2.0.2. 
>> 
>> We’ve passed the VOTE on dev@, still looking for a few binding VOTE on 
>> general to release this security patch. 
>> 
>> Many thanks!
>> 
>> Josh
>> 
>>> On Aug 17, 2019, at 6:16 PM, Justin Mclean  wrote:
>>> 
>>> Hi,
>>> 
>>> +1(binding)
>>> 
>>> I checked the new binaries and they container the DISCLAIMER and signatures 
>>> and hashes match. It would off been easier to review if this was another RC 
>>> as then an easy comparison could be made with the previous files.
>>> 
>>> Thanks,
>>> Justin
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> -
> 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) v2.0.2

[Joshua Poore]

Ok. Thanks for guidance and clarification. 



> On Aug 21, 2019, at 12:45 AM, Justin Mclean  wrote:
> 
> Hi,
> 
>> I asked you about this after you caught the missing disclaimer, but didn’t 
>> hear back inside of 24 hours so I made a judgement call—I hope I did the 
>> right thing. 
> 
> Well it not the wrong thing, it just something that I don;t think has 
> happened before.
> 
>> My logic in this case was that because our Disclaimer was in src, and there 
>> were no issues with the Disclaimer itself, repackaging the RC with the 
>> Disclaimer in the .bin files would not have required any new commits to 
>> files. +1s from dev@ (especially Binding) would have indicated approval of 
>> the Disclaimer as well. 
> 
> Change the binary changes the signatures and hashes, if teh project was a TLP 
> IMO that would require another vote.
> 
>> We had +3 IPMC VOTES on dev@, however, to date we only have +2 on general@. 
>> Do I need one more on general@?
> 
> You can carry over the IPMC votes.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
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) v2.0.2

[Joshua Poore]

Hi Justin,

Thanks for the attention on this VOTE. 

I asked you about this after you caught the missing disclaimer, but didn’t hear 
back inside of 24 hours so I made a judgement call—I hope I did the right 
thing. Would appreciate any guidance on my logic here.

My logic in this case was that because our Disclaimer was in src, and there 
were no issues with the Disclaimer itself, repackaging the RC with the 
Disclaimer in the .bin files would not have required any new commits to files. 
+1s from dev@ (especially Binding) would have indicated approval of the 
Disclaimer as well. 

Were it the case that I needed to modify file content for compliance, I would 
have had to change the commit stream and push tags forward. In the case, I 
would have certainly kicked back to dev@ to VOTE again.

Also, a little confused about Dave Fisher’s response in our VOTE thread. He 
said, 

"You have enough IPMC votes from your mentors.

I think you are good.”

We had +3 IPMC VOTES on dev@, however, to date we only have +2 on general@. Do 
I need one more on general@?

Josh

> On Aug 21, 2019, at 12:09 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> It's a little unusual as they voted before the binary was changed so this 
> really should have been two seperate vote threads. But I ‘m fine if you count 
> them this time.
> 
> 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) v2.0.2

[Joshua Poore]

Hi Folks—

Just a reminder to VOTE on Apache Flagon UserALE.js (Incubating) v2.0.2. 

We’ve passed the VOTE on dev@, still looking for a few binding VOTE on general 
to release this security patch. 

Many thanks!

Josh

> On Aug 17, 2019, at 6:16 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1(binding)
> 
> I checked the new binaries and they container the DISCLAIMER and signatures 
> and hashes match. It would off been easier to review if this was another RC 
> as then an easy comparison could be made with the previous files.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
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) v2.0.2

[Joshua Poore]

General@

Following Justin’s comment below—Disclaimer missing from .bin release 
packages—I have repackaged release candidate #1 to include Disclaimers and 
pushed to https://dist.apache.org/repos/dist/dev/incubator/flagon/ 
<https://dist.apache.org/repos/dist/dev/incubator/flagon/>.

As this issue was a file omission and did not affect source or build artifacts, 
the commit reference used for voting in dev@ have not changed, nor have git 
tags for the release candidate. .bin packages now include our Disclaimer.

As a matter of good practice I have re-evaluated the repackaged release 
candidate against the following:

[ 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 Unexpected Binary Files in Source Release Packages

Please feel free to evaluate as you VOTE. See the thread below for the interim 
summary of VOTEs on dev@

VOTE details follow:

Please VOTE on the Apache Flagon (Incubating) 2.0.2 Release Candidate # 1

This VOTE has passed successfully within the Apache Flagon community. We are 
now posting the VOTE on general@ as required by Apache Release Management 
policies. 

Interim RESULT on dev@ are as follows:

[+1] 7  
Joshua Poore
Rob Foley (`Confused`)
Laura Mariano
Furkan Kamaci*
Arthi Vezhavendan
Tim Allison*
Dave Meikle*

[0] 0

[-1]

*Binding IPMC/PPMC Mentor VOTE

The VOTE thread on dev@ can be found here: 
https://lists.apache.org/thread.html/1d0efb2a17b1b1a3bb83a6bf882f994000f7d9db316f8b244db54076@%3Cdev.flagon.apache.org%3E
 
<https://lists.apache.org/thread.html/1d0efb2a17b1b1a3bb83a6bf882f994000f7d9db316f8b244db54076@%3Cdev.flagon.apache.org%3E>

VOTE details follow:

About Flagon: http://flagon.incubator.apache.org/ 
<http://flagon.incubator.apache.org/> <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><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>
 
<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 UserALE.js 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/>

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

Thanks,

Josh

> On Aug 14, 2019, at 8:27 AM, Joshua Poore  wrote:
> 
> Hi Justin,
> 
> Please clarify your VOTE. Are we at -1 or 0 from you? If its a 0 - "consider 
> fixing a few issues”. I can easily roll a new release with DISCLAIMERS in bin 
> push as new release package so that this issue can be vetted prior to 
> release, but doesn’t require another VOTE altogeth

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

[Joshua Poore]

Hi Justin,

Please clarify your VOTE. Are we at -1 or 0 from you? If its a 0 - "consider 
fixing a few issues”. I can easily roll a new release with DISCLAIMERS in bin 
push as new release package so that this issue can be vetted prior to release, 
but doesn’t require another VOTE altogether.

Josh

> On Aug 13, 2019, at 11:58 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding) on the source release, but sorry it’s -1 (binding) for the 
> binaries as they are missing the DISCLAIMER file [2]
> 
> You might want to consider using a checklist when checking releases [1]. Also 
> when voting on release it a good idea to list what you checked rather than 
> just saying +1.
> 
> I checked:
> - incubating in name
> - signatures and hashes fine
> - DISCLAIMER in source but not in binary releases
> - LICENSE and NOTICE fine
> - all source files have ASF headers
> - no unexpected binary files in source release
> 
> There also no need to put the KEYS fine inside the release, it's sort of a 
> bit late to find it there after you unzipped it :-)
> 
> Thanks,
> Justin
> 
> 1. 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 2. https://incubator.apache.org/policy/incubation.html#disclaimers
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hi Folks,
 
Please VOTE on the Apache Flagon 2.0.2 Release Candidate # 1

This VOTE has passed successfully within the Apache Flagon community. We are 
now posting the VOTE on general@ as required by Apache Release Management 
policies. 


Interim RESULT on dev@ are as follows:

[+1] 7  
Joshua Poore
Rob Foley (`Confused`)
Laura Mariano
Furkan Kamaci*
Arthi Vezhavendan
Tim Allison*
Dave Meikle*

[0] 0

[-1]

*Binding IPMC/PPMC Mentor VOTE

The VOTE thread on dev@ can be found here: 
https://lists.apache.org/thread.html/1d0efb2a17b1b1a3bb83a6bf882f994000f7d9db316f8b244db54076@%3Cdev.flagon.apache.org%3E
 
<https://lists.apache.org/thread.html/1d0efb2a17b1b1a3bb83a6bf882f994000f7d9db316f8b244db54076@%3Cdev.flagon.apache.org%3E>
 


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 UserALE.js 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: Flagon needs more mentors

[Joshua Poore]

Hey Furkan,

I’m on the PPMC for Flagon. Just want to say  thanks for volunteering! I’ll 
reach out later this evening with more info.

Thanks Again!

Joshua Poore


> On Jul 24, 2019, at 7:23 AM, Furkan KAMACI  wrote:
> 
> Hi Justin,
> 
> I am also volunteering to be a mentor for Apache Flagon too. I've time to
> mentor it and I believe that I can help them through their journey of
> graduating from Apache Incubator.
> 
> Kind Regards,
> Furkan KAMACI
> 
> 
>> On Wed, Jul 24, 2019 at 2:04 PM Tim Allison  wrote:
>> 
>> I recently joined Flagon as a mentor. Please do help!
>> 
>>> On Tue, Jul 23, 2019 at 8:55 PM Justin Mclean  wrote:
>>> 
>>> Hi,
>>> 
>>> Flagon mentors seem to have gone missing, and this is slowing them down
>> on
>>> their path to graduation.
>>> 
>>> Can anyone help out by mentoring the project?
>>> 
>>> Apache Flagon [1] is a generalized user behavioural logging platform for
>>> web
>>> pages and thin-client applications
>>> 
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1. http://flagon.apache.org
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [ANNOUNCE] Apache Training (incubating) - Navigating the ASF Incubator Process 1.0

[Joshua Poore]

+1!

Joshua Poore


> On Jul 13, 2019, at 2:41 AM, Justin Mclean  wrote:
> 
> Hello Community,
> 
> The Apache Training (incubating) team is pleased to announce the source
> release of Navigating the ASF Incubator Process 1.0 (incubating).
> 
> This is a slide deck containing an overview of how to navigate the ASF
> incubating process from start to finish.
> 
> Apache Training aim is to create high-quality training material for various 
> projects in an open source form. Up until now everyone who wants to offer a 
> Training course for one of the Apache projects needs to create her or his 
> own slides/labs and keep them up-to-date. This is a significant investment 
> of time and money. This project aims to spread that burden and help all 
> Apache projects as we can create shared resources and we can also create 
> cross-project training resources.
> 
> The official source release are available from
> https://training.apache.org/downloads.html 
> <https://training.apache.org/downloads.html>.
> 
> If you have any usage questions, or have problems when upgrading, please
> don't hesitate to let us know by sending feedback to d...@training.apache.org 
> <mailto:d...@training.apache.org>
> or opening a GitHub issue at https://github.com/apache/?q=incubator-training 
> <https://github.com/apache/?q=incubator-training>.
> 
> *Disclaimer*
> 
> Apache Training is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Incubator. Incubation is required of all
> newly accepted projects until a further review indicates that the
> infrastructure, communications, and decision making process have stabilized
> in a manner consistent with other successful ASF projects. While incubation
> status is not necessarily a reflection of the completeness or stability of
> the code, it does indicate that the project has yet to be fully endorsed by
> the ASF.
> 
> Thanks,
> Apache Training PPMC


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: New disclaimer text

[Joshua Poore]

Replies inline:

> On Jul 12, 2019, at 3:49 AM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Adding an additional disclaimer that we may have known issues adds 
>> additional barriers to adoption and community growth.
> 
> I think the question to be asked is does that add barries more than having to 
> have 100% compliant releases? I think the answer may depend on the podling. 
> Have does that work out for 50 odd podlings?

I’m looking at this from a corporate investment perspective, having some 
insights into that process: you’re right, each podling has a different market 
with different community dynamics. I’m not going to speculate as to the 
base-rates. What I can say is that the ASF needs to be (and probably is) 
tracking the growth in the tech start-up, small-business market. The Apache 
license is highly desirable by small business and those working under VC, as is 
the `Apache` brand (even US gov’t agencies are looking at this more closely). 
This is going to be a huge potential drivers for growth in projects and 
communities. Looking at things from this perspective, if there is an additional 
disclaimer that make an Apache Incubator project look riskier to adopt than 
some other junk on GitHub with more than 10 stars, then I see an unnecessary 
barrier in exploiting how the growing tech market can accelerate the growth of 
open-source projects. Open-source no longer just about a bunch of folks who 
love keeping software free and open, or folks to love collaborating, its also 
about driving technology markets in strategic ways. I hold all three of these 
interests.

> 
>> Here’s one way for the ASF Incubator: Apache’s key marketing point is the 
>> Apache Way. Break down critical processes, determine key performance 
>> indicators against those processes, and centrally track metrics (license 
>> compliance, community participation, release compliance, notice, keys, 
>> whatever, whatever).
> 
> I really like the idea, would you be willing to work on it further?

I would, and I will, but I can’t do it all on my own. Some of the back-end 
stuff and navigating the INFRA reqs will be beyond my skills. However, I can 
contribute and at least work on marshaling other volunteer resources, managing 
tickets, requirements generation, and drawing in examples from some of the 
existing badges that are so popular in say, the node.js community. My action to 
start a thread in the near-term on this for discussion, I might need your help 
in directing other podlings PPMCs to the thread so that we get the best range 
of requirements and levels of interest from the podlings. I will also add a 
confluence page on this proposal.

> 
> Some things to consider. I don’t know it we have enough volunteer time to 
> implement something along those line or if we could come out with clear 
> metrics to suit all podlings. However in some ways this work has already been 
> done with the maturity model. There are issues this this as well a) not all 
> IPMC members or podlings think it should be used so so it's optional. b) 
> we’ve had podlings fill it in and ask to graduate that were clearly not ready 
> to graduate.

That’s OK. We’ll run it to ground. At minimum, I think the conversation will be 
a forcing function to really ascertain whether the larger podling community 
cares about the disclaimer as much as a few vocal committers.

> 
>> The additional disclaimer communicates that Apache has little trust in its 
>> podlings, at large.
> 
> About 1 in 5 podling releases put up fro IPMC have serious issues and have 
> previously have attracted -1 votes by IPMC members. If we allow those to be 
> released then I think we need to add something to the the disclaimer, we just 
> need to work out a balance.

Communication of distrust isn’t the same thing as how we trust something right 
now. It's clear that if these compliance issues are really risks from a legal 
perspective then you have very good reason to distrust some podlings. How the 
Incubator communicates that distrust and its implications for giving podlings a 
real shot at success is the crux of the issues. My point is that any Incubation 
model requires some element of risk because those risks are precisely the value 
adds to incubator participants. Beyond a balance in accepting risk, we need to 
help find the Incubator better, more efficient ways of managing risks. I 
suppose that’s the tl;dr version of the manifesto I accidentally wrote the 
other night.

> 
>> -1. These are connected issues: Mentors are IMPCs "tip of the spear" for 
>> managing compliance risk and for adding value to podlings. I have so much 
>> respect for Justin and other IPMC regulars who tirelessly volunteer and 
>> monitor general@, dig into minor releases to test builds and check 
>> compliance. It’s heroic, but heroes are a sign of struggling operations in 
>> orgs, and heroes burn out.
> 
> I’ve yet to see any proposal that deals with the issue of how it would get 
> around that only PMC members 

Re: New disclaimer text

[Joshua Poore]

Hi,

I’m also a PPMC member (Apache Flagon). It seems the Incubator is at an 
inflection point—been tracking how different threads on general@ are 
capitulating on issues of identity and process. Gian’s points are SPOT on, but 
so are Justin’s. I have some reconciliatory thoughts and suggestions, which I’m 
embedding in line:

> On Jul 10, 2019, at 5:44 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Speaking as a member of a currently-incubating project (Apache Druid) where
>> we have always strived to do releases with no known licensing issues, the
>> text sounds needlessly scary to downstream consumers.

> And that may be the problem with a one solution fits all process. It has been 
> suggested before we let podlings choose which release process they want.  
> However that may get too complex and make voting on releases inconsistent.

+1 on both points. The value we (podlings) take out of the Incubator is 
mentorship and scaffolding in adopting the Apache Way. In doing so, the “Way”, 
its processes, and the policies that shape those processes are meant to improve 
our offerings (code), our adoptability, and grow a sustainable community. 
Adding an additional disclaimer that we may have known issues adds additional 
barriers to adoption and community growth. An Incubator by definition takes on 
risk—infrastructure, time,  and opportunity, sunk, and operational costs—to 
help nurture its participants. That risk is directly yoked to the participants’ 
value gains from participating. Placing additional barriers to growth and 
adoption to eliminate the ASF’s risk breaks the incubator model altogether. 

> 
>> IMO this disclaims too much, and would chill adoption of incubating
>> software by people that care about having clean licensing. PPMCs should be
>> able to say "we believe this release is clean and have vetted it using a
>> normal Apache vetting process" or maybe even "we have vetted this release
>> and it is clean other than the following list of known issues". If they
>> can't say one of those two statements, then maybe it's not time to do their
>> first release yet.
> 
> The idea is to allow podlings to make releases that may not comply with 
> policy. Have a hard switch from your releases doesn’t comply to everything 
> must comply is too difficult for some podlings.

+1 on both point and counterpoint. This disclaims too much and there needs to 
be compliance to policy. The risk the Incubator needs to take is that 100% 
compliance is an eventual, but measurable goal. Yet, the Incubator needs a 
means to manage risk. A better model than the disclaimer: progressively 
incentivize compliance with metrics. 

Here’s one way for the ASF Incubator: Apache’s key marketing point is the 
Apache Way. Break down critical processes, determine key performance indicators 
against those processes, and centrally track metrics (license compliance, 
community participation, release compliance, notice, keys, whatever, whatever). 
Then build some Apache-branded badges that expose those metrics publicly so 
that all your podlings can stick them on their GitHub READMEs, same way as we 
have for CI, test coverage, etc., etc. Doing something like this, the Incubator 
is using the brand to incentivize organic compliance and manage risk. Implicit 
in this usage of the Apache brand is communication that podling projects are 
not fully endorsed by Apache, but the project being looked after by a trusted 
organization. Podlings have clear metrics that they can communicate and take 
actions to move the needle on. Podlings have a way to discriminate themselves 
from other open-source projects and from other podlings by showing positive 
values on their badges. This whole model provides a discriminator for all 
podlings in that other open-source projects don’t have the infrastructure to 
communicate these metrics; these badges’ existence engenders trust in the ASF & 
Incubator brand(s) and skepticism about non-Apache projects. Podlings who work 
to budge metrics can communicate to consumers and potential community members 
and continually brings them in line with Apache policy—the value they get from 
the incubator is now directly proportional to compliance (Incubator risk 
reduction). The Incubator also gets a better way to track incubation status, 
direct special attention to podlings that are bottoming out (before removal) 
and podlings that are showing progressive improvement. This method (or similar) 
tells the public how much trust Apache has in a particular podling. The 
additional disclaimer communicates that Apache has little trust in its 
podlings, at large.

Maybe this is too much technically (I doubt that), maybe this isn’t the best or 
only way to do this, but the key theme here is: measurable, progressive 
improvement. That should be sufficient to stay in the Incubator and necessary 
to graduate. Importantly, “progressive” means that metrics are updated 
regularly and not just at the time of release... 

> 
>> And yeah, as 

Re: [ANNOUNCEMENT] Release of Apache Flagon UserALE.js v2.0.0

[Joshua Poore]

Thanks, @sebb

Shall I rework and repost?

Joshua Poore


> On Jul 8, 2019, at 5:27 AM, sebb  wrote:
> 
> Apache Flagon is an incubating project.
> 
> As such, announcements should include the standard disclaimer.
> 
> Thanks!
> 
>> On Mon, 8 Jul 2019 at 09:06, Joshua Poore  wrote:
>> 
>> The Apache Flagon team is pleased to announce the immediate availability of 
>> Apache Flagon UserALE.js version 2.0.0!
>> 
>> Apache UserALE.js is Flagon's free, open-source application for thin-client 
>> behavioral logging. It's perfect for business analytics and enterprise 
>> application monitoring, but powerful enough for UI/UX research and 
>> user-testing. UserALE.js uses the Apache Software License v2.0.
>> 
>> UserALE.js is released as source code on GitHub [0], downloads for source on 
>> Apache download mirrors linked to our website [1], as well as an npm package 
>> for node.js applications, found on the npm registry [2].
>> 
>> This version 2.0.0 release adds major functionality to UserALE.js beyond 
>> version 1.0.0:
>> 
>> 1. Interval Logs
>> 2. WebExtensionSupport for Chrome/Firefox
>> 3. API support for filtering, mapping, and custom logs
>> 4. Overhauled Unit Tests
>> 
>> The full Jira release report can be found here [3].
>> 
>> Thank you,
>> 
>> Josh (on behalf of Apache Flagon PPMC)
>> 
>> [0] 
>> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.0-06_26_2019
>> [1] http://flagon.incubator.apache.org/releases/
>> [2] https://www.npmjs.com/package/flagon-userale
>> [3] 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621=12343068
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Late podling reports / mentor sign off due Tuesday July 9th

[Joshua Poore]

Hi Justin,

Flagon updated to a .md format as requested. .md files are being stripped from 
our lists: https://lists.apache.org/list.html?d...@flagon.apache.org 
. We only just 
realized.

I’ve put report in a file list on confluence. Mentor will review and post to 
wiki. Just in case, link is here: 
https://cwiki.apache.org/confluence/display/FLAGON/Podling+Reports 


> On Jul 4, 2019, at 4:06 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> The due date has come and gone and we’re still missing reports from:
> Amaterasu
> DLab
> Flagon
> Livy
> Tuweni
> 
> Good to see that BRPC and Iceberg who failed to report last last month did 
> report this month. DLab has failed to report for the second time.
> 
> If you mentor one of the above project please try to get them to submit a 
> report ASAP or they will need to report next month.
> 
> Mentor signoff due is due by Tuesday July 9th.
> 
> Thanks, 
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

[RESULT] was: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Hi Everyone,

VOTING for Apache Flagon UserALE.js (Incubating) v2.0.0 has closed on both dev@ 
and general@.

This Major release includes a wealth of additional features beyond v1.0.0, 
notably:

1. Interval Logs
2. WebExtensionSupport for Chrome/Firefox
3. API support for filtering, mapping, and custom logs 
4. Overhauled Unit Tests

The VOTE's have been counted and RESULT's are as follows:

[ 7 ] +1, let's get it released!!!
Joshua Poore
Laura Mariano
Rob Foley
Michael Schreiber
Dave Meikle* (Flagon PMC)
Justin Mclean* (IPMC)
Paul King* (IPMC)

[ 0 ] +/-0, fine, but consider to fix few issues before…
[ 0 ] -1, nope, because... (and please explain why)

* Binding VOTE

The VOTE to release Apache Flagon UserALE.js (Incubating) v2.0.0 PASSES!

Thanks to all who VOTED!

The Flagon community will now progress with the remainder of the release 
procedures.


> On Jul 1, 2019, at 7:15 PM, Paul King  wrote:
> 
> Yes, when I say "probably worth correcting" I mean for future builds if
> possible. Good luck with the release.
> 
> Cheers, Paul.
> 
> 
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> On Tue, Jul 2, 2019 at 2:05 AM Joshua Poore 
> wrote:
> 
>> Thanks, Paul.
>> 
>> Yes, some of our webextension files are build from a few other source
>> files. The best way we could manage to get headers in those these build
>> files resulted in some repetition of headers from various arc files. We’ll
>> see if we can’t find a better way, but at present we’re leaning on
>> compliance and functional soundness.
>> 
>> Joshua Poore
>> 
>> 
>>> On Jul 1, 2019, at 10:01 AM, Paul King  wrote:
>>> 
>>> +1 (binding)
>>> 
>>> Checked:
>>> * incubator in name
>>> * LICENSE/NOTICE files
>>> * checksums
>>> * ASF headers in files (though a few js files in UserAleWebExtension have
>>> the header repeated multiple times - not a big deal but probably worth
>>> correcting unless these files are generated that way)
>>> 
>>> Cheers, Paul.
>>> 
>>> 
>>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>> 
>>> Virus-free.
>>> www.avast.com
>>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>> 
>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>> 
>>> On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
>>> wrote:
>>> 
>>>> Hi Folks,
>>>> 
>>>> 72 hours has passed on our VOTE on general@ to Release Apache Flagon
>>>> v2.0.0.
>>>> 
>>>> We are missing one binding VOTE from IPMC to release. Please review and
>>>> VOTE.
>>>> 
>>>> We presently have +4 community votes & +2  binding votes. No one has
>> voted
>>>> +0 or -1.
>>>> 
>>>> Thanks!
>>>> 
>>>> Joshua Poore
>>>> 
>>>> 
>>>>> On Jun 29, 2019, at 8:06 PM, Justin Mclean 
>>>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> +1 (binding)
>>>>> 
>>>>> I checked:
>>>>> - incubating in name
>>>>> - signature and hashes fine
>>>>> - DISCLAIMER exists
>>>>> - LICENSE has minor issue (see below)
>>>>> - NOTICE is fine
>>>>> - all ASF files have correct headers
>>>>> 
>>>>> As noted above the LICENSE file has incorrect copyright line in the
>>>> license appendix.
>>>>> 
>>>>> Thanks,
>>>>> Justin
>>>>> -
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>> 
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>> 
>>>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Thanks, Paul.

Yes, some of our webextension files are build from a few other source files. 
The best way we could manage to get headers in those these build files resulted 
in some repetition of headers from various arc files. We’ll see if we can’t 
find a better way, but at present we’re leaning on compliance and functional 
soundness.

Joshua Poore


> On Jul 1, 2019, at 10:01 AM, Paul King  wrote:
> 
> +1 (binding)
> 
> Checked:
> * incubator in name
> * LICENSE/NOTICE files
> * checksums
> * ASF headers in files (though a few js files in UserAleWebExtension have
> the header repeated multiple times - not a big deal but probably worth
> correcting unless these files are generated that way)
> 
> Cheers, Paul.
> 
> 
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
> wrote:
> 
>> Hi Folks,
>> 
>> 72 hours has passed on our VOTE on general@ to Release Apache Flagon
>> v2.0.0.
>> 
>> We are missing one binding VOTE from IPMC to release. Please review and
>> VOTE.
>> 
>> We presently have +4 community votes & +2  binding votes. No one has voted
>> +0 or -1.
>> 
>> Thanks!
>> 
>> Joshua Poore
>> 
>> 
>>> On Jun 29, 2019, at 8:06 PM, Justin Mclean 
>> wrote:
>>> 
>>> Hi,
>>> 
>>> +1 (binding)
>>> 
>>> I checked:
>>> - incubating in name
>>> - signature and hashes fine
>>> - DISCLAIMER exists
>>> - LICENSE has minor issue (see below)
>>> - NOTICE is fine
>>> - all ASF files have correct headers
>>> 
>>> As noted above the LICENSE file has incorrect copyright line in the
>> license appendix.
>>> 
>>> Thanks,
>>> Justin
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Hi Folks,

72 hours has passed on our VOTE on general@ to Release Apache Flagon v2.0.0.

We are missing one binding VOTE from IPMC to release. Please review and VOTE.

We presently have +4 community votes & +2  binding votes. No one has voted +0 
or -1.

Thanks!

Joshua Poore


> On Jun 29, 2019, at 8:06 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - signature and hashes fine
> - DISCLAIMER exists
> - LICENSE has minor issue (see below)
> - NOTICE is fine
> - all ASF files have correct headers
> 
> As noted above the LICENSE file has incorrect copyright line in the license 
> appendix.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Ok, cool. We’ll get it right on Master.

Joshua Poore


> On Jun 30, 2019, at 1:19 AM, Justin Mclean  wrote:
> 
> HI,
> 
>> Is it just the Copyright symbol that’s incorrect? Or do you see something 
>> else. Just checking so that I know what to fix. Its the only thing I can see 
>> as different from [1]
> 
> Sorry, incorrect to probably not teh right word. I just noticed it was 
> different to the standard one. Probably no need to change it but it also 
> probably best to stick to the original text, I leave it up to you.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Hi Justin,

Thanks for the review!

RE License appendix:

Is it just the Copyright symbol that’s incorrect? Or do you see something else. 
Just checking so that I know what to fix. Its the only thing I can see as 
different from [1]

reads as follwos:

  APPENDIX: How to apply the Apache License to your work.

 To apply the Apache License to your work, attach the following
 boilerplate notice, with the fields enclosed by brackets "[]"
 replaced with your own identifying information. (Don't include
 the brackets!)  The text should be enclosed in the appropriate
 comment syntax for the file format. We also recommend that a
 file or class name and description of purpose be included on the
 same "printed page" as the copyright notice for easier
 identification within third-party archives.

  © Copyright [] [name of copyright owner]

  Licensed under the Apache License, Version 2.0 (the "License");
  you may not use this file except in compliance with the License.
  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.

[1] https://www.apache.org/licenses/LICENSE-2.0 


> On Jun 29, 2019, at 8:06 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - signature and hashes fine
> - DISCLAIMER exists
> - LICENSE has minor issue (see below)
> - NOTICE is fine
> - all ASF files have correct headers
> 
> As noted above the LICENSE file has incorrect copyright line in the license 
> appendix.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Doris 0.10.0-incubating-rc04

[Joshua Poore]

crap. Sorry, posts on wrong thread!

> On Jun 30, 2019, at 12:13 AM, Joshua Poore  wrote:
> 
> Hi Justin,
> 
> Thanks for the review!
> 
> RE License appendix:
> 
> Is it just the Copyright symbol that’s incorrect? Or do you see something 
> else. Just checking so that I know what to fix. Its the only thing I can see 
> as different from [1]
> 
> reads as follwos:
> 
>   APPENDIX: How to apply the Apache License to your work.
> 
>  To apply the Apache License to your work, attach the following
>  boilerplate notice, with the fields enclosed by brackets "[]"
>  replaced with your own identifying information. (Don't include
>  the brackets!)  The text should be enclosed in the appropriate
>  comment syntax for the file format. We also recommend that a
>  file or class name and description of purpose be included on the
>  same "printed page" as the copyright notice for easier
>  identification within third-party archives.
> 
>   © Copyright [] [name of copyright owner]
> 
>   Licensed under the Apache License, Version 2.0 (the "License");
>   you may not use this file except in compliance with the License.
>   You may obtain a copy of the License at
> 
>   http://www.apache.org/licenses/LICENSE-2.0
> 
>   Unless required by applicable law or agreed to in writing, software
>   distributed under the License is distributed on an "AS IS" BASIS,
>   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>   See the License for the specific language governing permissions and
>   limitations under the License.
> 
> [1] https://www.apache.org/licenses/LICENSE-2.0 
> <https://www.apache.org/licenses/LICENSE-2.0>
> 
>> On Jun 29, 2019, at 8:53 PM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> +1 (binding)
>> 
>> I checked:
>> - incubating in name
>> - DISCLAIMER exists
>> - LICENSE has some minor issues (see below)
>> - NOTICE is fine
>> - ASF file have ASF headers
>> - No unexpected binary files
>> - I didn’t compile as I’m on an unsupported platform
>> 
>> LICENSE is missing:
>> - UTF-8 library [1][2]
>> - These files [3][4] copyright Facebook. The headers in this files may not 
>> be correct.
>> - MIT licensed Sizzle from [6]
>> 
>> The licensing information list in headers of [3][4] is confusing e.g Is it 
>> under an APLv2 license, or an AL or GPL license, or a BSD license? You might 
>> also want to read this JIRA [5] to double check that the version of rocksDB 
>> you are using is OK and not Category X.
>> 
>> Thanks,
>> Justin
>> 
>> 1. ./be/src/gutil/utf/LICENSE
>> 2. ./be/src/gutil/utf/rune.c
>> 3. ./be/src/util/coding.cpp
>> 4. ./be/src/util/coding.cpp
>> 5. https://issues.apache.org/jira/browse/LEGAL-303
>> 6. /webroot/static/jquery.js
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Doris 0.10.0-incubating-rc04

[Joshua Poore]

Hi Justin,

Thanks for the review!

RE License appendix:

Is it just the Copyright symbol that’s incorrect? Or do you see something else. 
Just checking so that I know what to fix. Its the only thing I can see as 
different from [1]

reads as follwos:

   APPENDIX: How to apply the Apache License to your work.

  To apply the Apache License to your work, attach the following
  boilerplate notice, with the fields enclosed by brackets "[]"
  replaced with your own identifying information. (Don't include
  the brackets!)  The text should be enclosed in the appropriate
  comment syntax for the file format. We also recommend that a
  file or class name and description of purpose be included on the
  same "printed page" as the copyright notice for easier
  identification within third-party archives.

   © Copyright [] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

[1] https://www.apache.org/licenses/LICENSE-2.0 


> On Jun 29, 2019, at 8:53 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - DISCLAIMER exists
> - LICENSE has some minor issues (see below)
> - NOTICE is fine
> - ASF file have ASF headers
> - No unexpected binary files
> - I didn’t compile as I’m on an unsupported platform
> 
> LICENSE is missing:
> - UTF-8 library [1][2]
> - These files [3][4] copyright Facebook. The headers in this files may not be 
> correct.
> - MIT licensed Sizzle from [6]
> 
> The licensing information list in headers of [3][4] is confusing e.g Is it 
> under an APLv2 license, or an AL or GPL license, or a BSD license? You might 
> also want to read this JIRA [5] to double check that the version of rocksDB 
> you are using is OK and not Category X.
> 
> Thanks,
> Justin
> 
> 1. ./be/src/gutil/utf/LICENSE
> 2. ./be/src/gutil/utf/rune.c
> 3. ./be/src/util/coding.cpp
> 4. ./be/src/util/coding.cpp
> 5. https://issues.apache.org/jira/browse/LEGAL-303
> 6. /webroot/static/jquery.js
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

[VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Hi Folks,

Please VOTE on the Apache Flagon 2.0.0 Release Candidate # 2.

About Flagon: http://flagon.incubator.apache.org/ 
<http://flagon.incubator.apache.org/>

We require +2 binding votes from PMC to proceed with the release.

Our community and mentors have voted on this release with the following results:

[ 5 ] +1, let's get it released!!!
Joshua Poore
Laura Mariano
Rob Foley
Michael Schreiber
Dave Meikle*

[ ] +/-0, fine, but consider to fix few issues before...
[ ] -1, nope, because... (and please explain why)

see Apache Flagon community VOTE thread @lists: 
https://lists.apache.org/thread.html/488a0a3d686fd6b1948527f4e14c07f353365cdd56aa9b62f7327003@%3Cdev.flagon.apache.org%3E
 
<https://lists.apache.org/thread.html/488a0a3d686fd6b1948527f4e14c07f353365cdd56aa9b62f7327003@%3Cdev.flagon.apache.org%3E>

This Major release includes a wealth of additional features beyond v1.0.0, 
notably:

1. Interval Logs
2. WebExtensionSupport for Chrome/Firefox
3. API support for filtering, mapping, and custom logs 
4. Overhauled Unit Tests

We solved 59 issues: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343068=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Ceda9fbce2795c14b56345bf5daee2a8a893d249c%7Clin
 
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343068=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED|eda9fbce2795c14b56345bf5daee2a8a893d249c|lin>
 

Git source tag (909b531): 
https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.0-RC2_06_26_2019
 
<https://github.com/apache/incubator-flagon-useralejs/commit/909b5315888d2bd89fa4570b46d80f77318b58bb>

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.0-RC2/
 
<https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.0.0-RC2/>

PGP release keys (signed using F9374FAE3FCADF6E): 
https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS 
<https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS> (new keys will 
be moved over to /release after ReRelease completes)

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

[RELEASE] WAS: [VOTE] (Re)Release Apache Flagon UserALE.js (Incubating) 1.0.0

[Joshua Poore]

Hi Everyone,

The VOTE to (Re)Release Apache Flagon UserALE.js (Incubating) 1.0.0 has closed. 
 The RESULT is:

[9] +1, let’s get it released!!
Joshua Poore
Rob Foley
Laura Mariano
Michelle Beard (voted in private@)
Michael Schrieber
Arthi Vezhavendan
Dave Meikle*
Justin McLean*
Jan Piotrowski*

[0] +/-0, fine, but consider to fix few issues before...
[0] -1, nope, because... (and please explain why)

Thanks to all for VOTING!

I will work with mentors for the remainder of release procedures.

Thanks,

Josh


> On Jun 27, 2019, at 9:33 AM, Joshua Poore  wrote:
> 
> Thanks, Jan. 
> 
> We’ll make good on comment, and have been watching issues IPMC has been 
> raising with other podlings. We’ve integrated a lot of  into our next release.
> 
> Joshua Poore
> 
> 
>> On Jun 27, 2019, at 6:16 AM, Jan Piotrowski  wrote:
>> 
>> +1
>> 
>> I trust Justin's judgement here, and I'm sure you'll work out any
>> issues with further releases.
>> 
>> -J
>> 
>> Am Do., 27. Juni 2019 um 06:14 Uhr schrieb Joshua Poore
>> :
>>> 
>>> Hi Folks,
>>> 
>>> Another friendly reminder: please VOTE on the ReRelease of Apache Flagon 
>>> UserAle.js (Incubating) 1.0.0.
>>> 
>>> Our ReRelease was mandated by IPMC due to build artifacts that lacked 
>>> “incubating” markings.
>>> 
>>> At this point we have +6 votes from our community and +2 Binding. We need 
>>> one more VOTE from general@ to release and 2 of our mentors are AWOL. We’re 
>>> entering the 10th consecutive day of this VOTE on general@ and that’s a 
>>> very, very long time to wait on a ReRelease.
>>> 
>>> Thanks to Justin for voting.
>>> 
>>> Tomorrow, we’ll be pushing v2.0.0 for a VOTE on general, as its wrapping up 
>>> a VOTE in community. Again we’re down two mentors. Am hoping that we’re 
>>> able to get feedback from IPMC a little more quickly. We have users waiting 
>>> on an NPM packaged version of this release.
>>> 
>>> Thanks,
>>> 
>>> Joshua Poore
>>> 
>>> 
>>>> On Jun 25, 2019, at 11:49 PM, Joshua Poore  wrote:
>>>> 
>>>> Ah, I understand. Copyright attribution is misplaced in License file 
>>>> altogether—appendix gives instruction for how to add a copyright to 
>>>> derivative works. *palm-to-face*. Thanks and sorry for being thick!
>>>> 
>>>> Josh
>>>> 
>>>>> On Jun 25, 2019, at 9:10 PM, Joshua Poore  wrote:
>>>>> 
>>>>> Hi Justin,
>>>>> 
>>>>> Dave Meikle and I worked to make the copyrights correct prior to this 
>>>>> ReRelease.
>>>>> 
>>>>> Our License File reads:
>>>>> 
>>>>> © Copyright 2018 The Apache Software Foundation.
>>>>> 
>>>>> Our Notice Fille reads:
>>>>> 
>>>>> Copyright 2019 The Apache Software Foundation
>>>>> 
>>>>> We thought that was consistent with 
>>>>> https://www.apache.org/legal/src-headers.html 
>>>>> <https://www.apache.org/legal/src-headers.html>, however, both should be 
>>>>> dated ‘2019’ (oversight).
>>>>> 
>>>>> If not, or you see something I missed, please don’t hesitate to point it 
>>>>> out and I’ll make sure we get it right.
>>>>> 
>>>>> Thanks!
>>>>> 
>>>>>>> From: Justin Mclean >>>>>> <mailto:jus...@classsoftware.com>>
>>>>>>> Date: June 25, 2019 at 8:11:25 PM EDT
>>>>>>> To: general@incubator.apache.org <mailto:general@incubator.apache.org>
>>>>>>> Subject: Re: [VOTE] (Re)Release Apache Flagon UserALE.js (Incubating) 
>>>>>>> 1.0.0
>>>>>>> Reply-To: general@incubator.apache.org 
>>>>>>> <mailto:general@incubator.apache.org>
>>>>>>> 
>>>>>>> HI,
>>>>>>> 
>>>>>>>> Copyrights are 2019 in V2.0.0 under vote now in dev@. Moving forward, 
>>>>>>>> we’ll be more careful.
>>>>>>> 
>>>>>>> Which would still be incorrect that line should say:
>>>>>>> Copyright [] [name of copyright owner]
>>>>>>> 
>>>>>>> As it where a 3rd party put their copyright notice in their file 
>>>>>>> headers.
>>>>>>> 
&g

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

[Joshua Poore]

Thanks, Jan. 

We’ll make good on comment, and have been watching issues IPMC has been raising 
with other podlings. We’ve integrated a lot of  into our next release.

Joshua Poore


> On Jun 27, 2019, at 6:16 AM, Jan Piotrowski  wrote:
> 
> +1
> 
> I trust Justin's judgement here, and I'm sure you'll work out any
> issues with further releases.
> 
> -J
> 
> Am Do., 27. Juni 2019 um 06:14 Uhr schrieb Joshua Poore
> :
>> 
>> Hi Folks,
>> 
>> Another friendly reminder: please VOTE on the ReRelease of Apache Flagon 
>> UserAle.js (Incubating) 1.0.0.
>> 
>> Our ReRelease was mandated by IPMC due to build artifacts that lacked 
>> “incubating” markings.
>> 
>> At this point we have +6 votes from our community and +2 Binding. We need 
>> one more VOTE from general@ to release and 2 of our mentors are AWOL. We’re 
>> entering the 10th consecutive day of this VOTE on general@ and that’s a 
>> very, very long time to wait on a ReRelease.
>> 
>> Thanks to Justin for voting.
>> 
>> Tomorrow, we’ll be pushing v2.0.0 for a VOTE on general, as its wrapping up 
>> a VOTE in community. Again we’re down two mentors. Am hoping that we’re able 
>> to get feedback from IPMC a little more quickly. We have users waiting on an 
>> NPM packaged version of this release.
>> 
>> Thanks,
>> 
>> Joshua Poore
>> 
>> 
>>> On Jun 25, 2019, at 11:49 PM, Joshua Poore  wrote:
>>> 
>>> Ah, I understand. Copyright attribution is misplaced in License file 
>>> altogether—appendix gives instruction for how to add a copyright to 
>>> derivative works. *palm-to-face*. Thanks and sorry for being thick!
>>> 
>>> Josh
>>> 
>>>> On Jun 25, 2019, at 9:10 PM, Joshua Poore  wrote:
>>>> 
>>>> Hi Justin,
>>>> 
>>>> Dave Meikle and I worked to make the copyrights correct prior to this 
>>>> ReRelease.
>>>> 
>>>> Our License File reads:
>>>> 
>>>> © Copyright 2018 The Apache Software Foundation.
>>>> 
>>>> Our Notice Fille reads:
>>>> 
>>>> Copyright 2019 The Apache Software Foundation
>>>> 
>>>> We thought that was consistent with 
>>>> https://www.apache.org/legal/src-headers.html 
>>>> <https://www.apache.org/legal/src-headers.html>, however, both should be 
>>>> dated ‘2019’ (oversight).
>>>> 
>>>> If not, or you see something I missed, please don’t hesitate to point it 
>>>> out and I’ll make sure we get it right.
>>>> 
>>>> Thanks!
>>>> 
>>>>>> From: Justin Mclean >>>>> <mailto:jus...@classsoftware.com>>
>>>>>> Date: June 25, 2019 at 8:11:25 PM EDT
>>>>>> To: general@incubator.apache.org <mailto:general@incubator.apache.org>
>>>>>> Subject: Re: [VOTE] (Re)Release Apache Flagon UserALE.js (Incubating) 
>>>>>> 1.0.0
>>>>>> Reply-To: general@incubator.apache.org 
>>>>>> <mailto:general@incubator.apache.org>
>>>>>> 
>>>>>> HI,
>>>>>> 
>>>>>>> Copyrights are 2019 in V2.0.0 under vote now in dev@. Moving forward, 
>>>>>>> we’ll be more careful.
>>>>>> 
>>>>>> Which would still be incorrect that line should say:
>>>>>> Copyright [] [name of copyright owner]
>>>>>> 
>>>>>> As it where a 3rd party put their copyright notice in their file headers.
>>>>>> 
>>>>>> Thanks,
>>>>>> Justin
>>>>>> -
>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>>>>>> <mailto:general-unsubscr...@incubator.apache.org>
>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org 
>>>>>> <mailto:general-h...@incubator.apache.org>
>>>>>> 
>>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hi Folks,

Another friendly reminder: please VOTE on the ReRelease of Apache Flagon 
UserAle.js (Incubating) 1.0.0.

Our ReRelease was mandated by IPMC due to build artifacts that lacked 
“incubating” markings.

At this point we have +6 votes from our community and +2 Binding. We need one 
more VOTE from general@ to release and 2 of our mentors are AWOL. We’re 
entering the 10th consecutive day of this VOTE on general@ and that’s a very, 
very long time to wait on a ReRelease. 

Thanks to Justin for voting.

Tomorrow, we’ll be pushing v2.0.0 for a VOTE on general, as its wrapping up a 
VOTE in community. Again we’re down two mentors. Am hoping that we’re able to 
get feedback from IPMC a little more quickly. We have users waiting on an NPM 
packaged version of this release.

Thanks,

Joshua Poore


> On Jun 25, 2019, at 11:49 PM, Joshua Poore  wrote:
> 
> Ah, I understand. Copyright attribution is misplaced in License file 
> altogether—appendix gives instruction for how to add a copyright to 
> derivative works. *palm-to-face*. Thanks and sorry for being thick!
> 
> Josh  
> 
>> On Jun 25, 2019, at 9:10 PM, Joshua Poore  wrote:
>> 
>> Hi Justin, 
>> 
>> Dave Meikle and I worked to make the copyrights correct prior to this 
>> ReRelease. 
>> 
>> Our License File reads:
>> 
>>  © Copyright 2018 The Apache Software Foundation.
>> 
>> Our Notice Fille reads:
>> 
>> Copyright 2019 The Apache Software Foundation
>> 
>> We thought that was consistent with 
>> https://www.apache.org/legal/src-headers.html 
>> <https://www.apache.org/legal/src-headers.html>, however, both should be 
>> dated ‘2019’ (oversight).
>> 
>> If not, or you see something I missed, please don’t hesitate to point it out 
>> and I’ll make sure we get it right.
>> 
>> Thanks!
>> 
>>>> From: Justin Mclean >>> <mailto:jus...@classsoftware.com>>
>>>> Date: June 25, 2019 at 8:11:25 PM EDT
>>>> To: general@incubator.apache.org <mailto:general@incubator.apache.org>
>>>> Subject: Re: [VOTE] (Re)Release Apache Flagon UserALE.js (Incubating) 1.0.0
>>>> Reply-To: general@incubator.apache.org 
>>>> <mailto:general@incubator.apache.org>
>>>> 
>>>> HI,
>>>> 
>>>>> Copyrights are 2019 in V2.0.0 under vote now in dev@. Moving forward, 
>>>>> we’ll be more careful.
>>>> 
>>>> Which would still be incorrect that line should say:
>>>> Copyright [] [name of copyright owner]
>>>> 
>>>> As it where a 3rd party put their copyright notice in their file headers.
>>>> 
>>>> Thanks,
>>>> Justin
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>>>> <mailto:general-unsubscr...@incubator.apache.org>
>>>> For additional commands, e-mail: general-h...@incubator.apache.org 
>>>> <mailto:general-h...@incubator.apache.org>
>>>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Ah, I understand. Copyright attribution is misplaced in License file 
altogether—appendix gives instruction for how to add a copyright to derivative 
works. *palm-to-face*. Thanks and sorry for being thick!

Josh  

> On Jun 25, 2019, at 9:10 PM, Joshua Poore  wrote:
> 
> Hi Justin, 
> 
> Dave Meikle and I worked to make the copyrights correct prior to this 
> ReRelease. 
> 
> Our License File reads:
> 
>   © Copyright 2018 The Apache Software Foundation.
> 
> Our Notice Fille reads:
> 
> Copyright 2019 The Apache Software Foundation
> 
> We thought that was consistent with 
> https://www.apache.org/legal/src-headers.html 
> <https://www.apache.org/legal/src-headers.html>, however, both should be 
> dated ‘2019’ (oversight).
> 
> If not, or you see something I missed, please don’t hesitate to point it out 
> and I’ll make sure we get it right.
> 
> Thanks!
> 
>>> From: Justin Mclean >> <mailto:jus...@classsoftware.com>>
>>> Date: June 25, 2019 at 8:11:25 PM EDT
>>> To: general@incubator.apache.org <mailto:general@incubator.apache.org>
>>> Subject: Re: [VOTE] (Re)Release Apache Flagon UserALE.js (Incubating) 1.0.0
>>> Reply-To: general@incubator.apache.org <mailto:general@incubator.apache.org>
>>> 
>>> HI,
>>> 
>>>> Copyrights are 2019 in V2.0.0 under vote now in dev@. Moving forward, 
>>>> we’ll be more careful.
>>> 
>>> Which would still be incorrect that line should say:
>>> Copyright [] [name of copyright owner]
>>> 
>>> As it where a 3rd party put their copyright notice in their file headers.
>>> 
>>> Thanks,
>>> Justin
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>>> <mailto:general-unsubscr...@incubator.apache.org>
>>> For additional commands, e-mail: general-h...@incubator.apache.org 
>>> <mailto:general-h...@incubator.apache.org>
>>> 
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hi Justin, 

Dave Meikle and I worked to make the copyrights correct prior to this 
ReRelease. 

Our License File reads:

   © Copyright 2018 The Apache Software Foundation.

Our Notice Fille reads:

Copyright 2019 The Apache Software Foundation

We thought that was consistent with 
https://www.apache.org/legal/src-headers.html 
, however, both should be dated 
‘2019’ (oversight).

If not, or you see something I missed, please don’t hesitate to point it out 
and I’ll make sure we get it right.

Thanks!

>> From: Justin Mclean > >
>> Date: June 25, 2019 at 8:11:25 PM EDT
>> To: general@incubator.apache.org 
>> Subject: Re: [VOTE] (Re)Release Apache Flagon UserALE.js (Incubating) 1.0.0
>> Reply-To: general@incubator.apache.org 
>> 
>> HI,
>> 
>>> Copyrights are 2019 in V2.0.0 under vote now in dev@. Moving forward, we’ll 
>>> be more careful.
>> 
>> Which would still be incorrect that line should say:
>> Copyright [] [name of copyright owner]
>> 
>> As it where a 3rd party put their copyright notice in their file headers.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>> 
>> For additional commands, e-mail: general-h...@incubator.apache.org 
>> 
>> 

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

[Joshua Poore]

Hi General@,

Another friendly reminder to please VOTE on the (Re)Release of Apache Flagon 
UserALE (Incubating) 1.0.0.

We have +6 Community votes, +2 binding IPMC votes. We need one more IPMC VOTE 
to release!!

Thanks!

> On Jun 24, 2019, at 10:33 AM, Joshua Poore  wrote:
> 
> Copy.
> 
> Copyrights are 2019 in V2.0.0 under vote now in dev@. Moving forward, we’ll 
> be more careful.
> 
> Thanks!
> 
> Joshua Poore
> 
> 
>> On Jun 24, 2019, at 9:37 AM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>>> 1. Will certainly fix copyright before pushing to release distro.
>> 
>> Well actually that would change the hashes / invalidate the signatures. It’s 
>> very minor just fix next release.
>> 
>>> So, yes. We’ll be hunting for 2 new mentors.
>> 
>> I suggest you send an email to genaral@incubator asking for some mentors.
>> 
>> Thanks,
>> Justin
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Copy.

Copyrights are 2019 in V2.0.0 under vote now in dev@. Moving forward, we’ll be 
more careful.

Thanks!

Joshua Poore


> On Jun 24, 2019, at 9:37 AM, Justin Mclean  wrote:
> 
> Hi,
> 
>> 1. Will certainly fix copyright before pushing to release distro.
> 
> Well actually that would change the hashes / invalidate the signatures. It’s 
> very minor just fix next release.
> 
>> So, yes. We’ll be hunting for 2 new mentors.
> 
> I suggest you send an email to genaral@incubator asking for some mentors.
> 
> Thanks,
> Justin
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hi Justin,

1. Will certainly fix copyright before pushing to release distro.

2. One committer accidentally voted in private@ (tried to express that in the 
release thread notes in the VOTE) and our newest contributor voted after the 
VOTE went to general (dev@ was cc’d).

3. Mentors: Of our three mentors, one has been uncharacteristically non 
responsive and another hasn’t really contributed since he joined. We’ve been 
discussing this with our the mentor that has really been engaged. So, yes. 
We’ll be hunting for 2 new mentors.

Thanks!

Joshua Poore


> On Jun 23, 2019, at 6:26 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked the source release:
> - signatures and hashes good
> - incubating in name
> - disclaimer exists
> - LICENSE and NOTICE fine
> - all source files have ASF headers
> - no unexpected binary files
> 
> There's one very minor issue in that LICENSE appendix includes " © Copyright 
> 2018 The Apache Software Foundation.” this is incorrect.
> 
> In your vote thread you state:
> "The community VOTE passes unanimously with +6, including 1 PPMC binding 
> VOTE. The VOTE will now move to general@ to see if we receive the remaining 
> +2 binding VOTEs to proceed with reRelease.”
> 
> It actually has 5 PPMC and 1 IPMC votes that I can see.
> 
> Given this is a very easy release to check, why have your mentors not voted 
> on it? Do you need additional mentors?
> 
> Thanks,
> Justin
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Joshua Poore]

Hi General,

Just a friendly reminder to Flagon Mentors and larger IPMC vote on the 
(Re)Release of Apache Flagon UserALE.js (Incubating) 1.0.0; we’re still short 
of +2 binding votes.

Thanks!


> On Jun 20, 2019, at 9:33 PM, Joshua Poore  wrote:
> 
> Hello,
> 
> On Jun 17th we posted an IPMC VOTE on the (Re)Release of Apache Flagon 
> UserALE.js (Incubating) 1.0.0, in accordance with a request by IPMC to 
> correctly annotate the release file names.
> 
> We did not receive any VOTEs from general@ within the 72 hour voting period. 
> Therefore, we are initiating another VOTE on general@, which will last for 72 
> hours.
> 
> Our community has voted in favor of this release by a majority of +7 in 
> favor, 0 in favor of additional development and, 0 against the release. This 
> tally includes +1 Binding Vote from PPMC. 
> 
> WE NEED +2 BINDING VOTES FOR THIS RELEASE VOTE TO PASS. 
> 
> 
> VOTE thread:
> https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
>  
> <https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E>
> 
> VOTE thread II (split accidentally to private):
> https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
>  
> <https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E>
> 
> Please VOTE on Apache FLAGON UserALE.js 1.0.0 Release Candidate #3:
> 
> We solved 50 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin
>  
> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED|d2c9eccb98c0590b13b40b9d863a18bfc463546f|lin>
> 
> Git source tag (d99ad9a2757fb5e412437227c6f9508d06c192e1):
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
>  
> <https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019>
> 
> 
> Source Release Branch:
> https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease 
> <https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease>
> 
> 
> Source Release Candidate Artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/flagon/ 
> <https://dist.apache.org/repos/dist/dev/incubator/flagon/>
> 
> PGP release keys (signed with F9374FAE3FCADF6E):
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS 
> <https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS>
> 
> 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 1.0.0 & 1.0.0r.
> 
> 
> 
>> On Jun 18, 2019, at 7:03 AM, Michael Schreiber 
>>  wrote:
>> 
>> +1
>> 
>> On Mon, Jun 17, 2019 at 9:35 PM Joshua Poore  wrote:
>> 
>>> Hello,
>>> 
>>> I am calling a VOTE to (re)Release Apache Flagon UserALE.js (Incubating)
>>> v1.0.0.
>>> 
>>> There are two reasons for this (re)Release:
>>> 
>>> 1. Original release artifacts were not properly annotated with
>>> (incubating) flag—IPMC asked us to regenerate the release with appropriate
>>> annotation.
>>> 2. Our name was officially changed from Apache SensSoft —> Flagon. This
>>> release bears our new project name.
>>> 
>>> We conducted a VOTE within our own community, resulting in +6 votes in
>>> favor of the (re)Release, including +1 binding vote from PPMC:
>>> 
>>> VOTE thread:
>>> https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
>>> <
>>> https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
>>>> 
>>> VOTE thread II (split accidentally to private):
>>> https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
>>> <
>>> https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
>>>> 
>>> 
>>> Please VOTE on Apache FLAGON UserALE.js 1.0.0 Release Candidate #3:
&

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

[Joshua Poore]

Hello,

On Jun 17th we posted an IPMC VOTE on the (Re)Release of Apache Flagon 
UserALE.js (Incubating) 1.0.0, in accordance with a request by IPMC to 
correctly annotate the release file names.

We did not receive any VOTEs from general@ within the 72 hour voting period. 
Therefore, we are initiating another VOTE on general@, which will last for 72 
hours.

Our community has voted in favor of this release by a majority of +7 in favor, 
0 in favor of additional development and, 0 against the release. This tally 
includes +1 Binding Vote from PPMC. 

WE NEED +2 BINDING VOTES FOR THIS RELEASE VOTE TO PASS. 


VOTE thread:
https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
 
<https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E>

VOTE thread II (split accidentally to private):
https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
 
<https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E>

Please VOTE on Apache FLAGON UserALE.js 1.0.0 Release Candidate #3:

We solved 50 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin
 
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED|d2c9eccb98c0590b13b40b9d863a18bfc463546f|lin>

Git source tag (d99ad9a2757fb5e412437227c6f9508d06c192e1):
https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
 
<https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019>


Source Release Branch:
https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease 
<https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease>


Source Release Candidate Artifacts:
https://dist.apache.org/repos/dist/dev/incubator/flagon/ 
<https://dist.apache.org/repos/dist/dev/incubator/flagon/>

PGP release keys (signed with F9374FAE3FCADF6E):
https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS 
<https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS>

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 1.0.0 & 1.0.0r.



> On Jun 18, 2019, at 7:03 AM, Michael Schreiber 
>  wrote:
> 
> +1
> 
> On Mon, Jun 17, 2019 at 9:35 PM Joshua Poore  wrote:
> 
>> Hello,
>> 
>> I am calling a VOTE to (re)Release Apache Flagon UserALE.js (Incubating)
>> v1.0.0.
>> 
>> There are two reasons for this (re)Release:
>> 
>> 1. Original release artifacts were not properly annotated with
>> (incubating) flag—IPMC asked us to regenerate the release with appropriate
>> annotation.
>> 2. Our name was officially changed from Apache SensSoft —> Flagon. This
>> release bears our new project name.
>> 
>> We conducted a VOTE within our own community, resulting in +6 votes in
>> favor of the (re)Release, including +1 binding vote from PPMC:
>> 
>> VOTE thread:
>> https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
>> <
>> https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
>>> 
>> VOTE thread II (split accidentally to private):
>> https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
>> <
>> https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
>>> 
>> 
>> Please VOTE on Apache FLAGON UserALE.js 1.0.0 Release Candidate #3:
>> 
>> We solved 50 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin
>> <
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin>
>> <
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED|d2c9eccb98c0590b13b40b9d863a18bfc463546f|lin
>> <
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Creat

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

[Joshua Poore]

Hello,

I am calling a VOTE to (re)Release Apache Flagon UserALE.js (Incubating) 
v1.0.0. 

There are two reasons for this (re)Release:

1. Original release artifacts were not properly annotated with (incubating) 
flag—IPMC asked us to regenerate the release with appropriate annotation.
2. Our name was officially changed from Apache SensSoft —> Flagon. This release 
bears our new project name. 

We conducted a VOTE within our own community, resulting in +6 votes in favor of 
the (re)Release, including +1 binding vote from PPMC:

VOTE thread: 
https://lists.apache.org/thread.html/7a3c960ee54692cd6d88fb88b83c787244bb0e1b4a476050093d3b4a@%3Cdev.flagon.apache.org%3E
 

VOTE thread II (split accidentally to private): 
https://lists.apache.org/thread.html/83a96438bd60ea4c0aec2d5f103d68cbb430a44c72ef2d3d0cfe655f@%3Cdev.flagon.apache.org%3E
 


Please VOTE on Apache FLAGON UserALE.js 1.0.0 Release Candidate #3:

We solved 50 issues: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin
 

 
>

Git source tag (d99ad9a2757fb5e412437227c6f9508d06c192e1): 
https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
 

 
>

Source Release Branch: 
https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease 
> 

Source Release Candidate Artifacts: 
https://dist.apache.org/repos/dist/dev/incubator/flagon/ 
>

PGP release keys (signed with F9374FAE3FCADF6E): 
https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS 
> (new keys must 
must be copied over to http://apache.org/dist/incubator/flagon/ 
 
>)

Vote will be open for 72 hours.

Thank you to everyone that is able to VOTE as well as everyone that contributed 
to Apache FLAGON 1.0.0 & 1.0.0r.

[ ] +1, let's get it released!!!
[ ] +/-0, fine, but consider to fix few issues before...
[ ] -1, nope, because... (and please explain why)

[NOTICE] Apache SensSoft INFRA migration to Apache Flagon name nearly complete

[Joshua Poore]

Hello,

Writing to inform general@ that INFRA has migrated Apache SensSoft’s assets [1] 
to reflect our approved name change [2]. A complete list of migrated assets is 
below.

Please update list subscriptions.

The podling committers and mentors will be working to clean up podling.xml 
[3]/.yml [4] files. However, flagon.xml/.yml files have been created, but have 
not yet been pushed to incubator projects website.

The apache wiki page will also need to be modified.


INFRA’s heroic efforts are documented at [5]


Complete list of migrated assets:

Lists:

d...@flagon.incubator.apache.org
comm...@flagon.incubator.apache.org
u...@flagon.incubator.apache.org
priv...@flagon.incubator.apache.org

Repositories:

incubator-flagon.git
incubator-flagon-distill.git
incubator-flagon-stout.git
incubator-flagon-tap.git
incubator-flagon-user-ale.git
incubator-flagon-userale-pyqt5.git
incubator-flagon-useralejs.git

Website:

http://flagon.incubator.apache.org/ 

Confluence:

*pending Key update

JIRA:

https://issues.apache.org/jira/projects/FLAGON/summary

[1]  https://issues.apache.org/jira/browse/INFRA-18100 

[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154 

[3] 
http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/flagon.xml?view=markup
 

[4] 
http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings/flagon.yml?view=markup
 

[5] 
https://issues.apache.org/jira/browse/INFRA-18100?focusedCommentId=16805320=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16805320
 

Fwd: [jira] [Resolved] (PODLINGNAMESEARCH-154) Establish Whether "Apache Flagon" is a Suitable Name

[Joshua Poore]

Hello, 

Apache SensSoft’s PODLINGNAMESEARCH for a new podling name has successfully 
concluded (see below). The name our community most prefers—Apache Flagon—has 
been approved by the VP of Brand. As we understand it, our next steps are to 
work with INFRA to change the name of some of our various assets. However, we 
wanted to reach out to IPMC to alert them of our name change status and confirm 
that there were no additional steps or approvals needed before we begin working 
with INFRA. Please let us know if there are additional steps.

Many Thanks!

Josh

> Begin forwarded message:
> 
> From: "Mark Thomas (JIRA)" 
> Subject: [jira] [Resolved] (PODLINGNAMESEARCH-154) Establish Whether "Apache 
> Flagon" is a Suitable Name
> Date: February 20, 2019 at 11:59:00 AM EST
> To: poor...@me.com
> 
> 
> [ 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
> Mark Thomas resolved PODLINGNAMESEARCH-154.
> ---
>Resolution: Fixed
> 
> Approved.
> 
> Mark
> 
>> Establish Whether "Apache Flagon" is a Suitable Name
>> 
>> 
>>Key: PODLINGNAMESEARCH-154
>>URL: 
>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154
>>Project: Podling Suitable Names Search
>> Issue Type: Suitable Name Search
>>   Reporter: Joshua Poore
>> 
>> Related to "Apache SensSoft" renaming. Investigating the suitability of new 
>> names nominated by our community: 
>> https://lists.apache.org/list.html?d...@senssoft.apache.org. Apache SensSoft 
>> is a generalized behavioral logging package for thin-client applications for 
>> user analytics. 
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)

[NOTICE] Request to Add New Mentors to Apache SensSoft Podling

[Joshua Poore]

Hello!

Mr. Atri Sharma and Mr. Dave Meikle have kindly offered their support as 
mentors of the Apache SensSoft podling. We would like to begin the process of 
onboarding them. 

@Justin—can you advise us as to the steps that the existing mentor (@lewis) or 
committers need take (beyond assigning appropriate permissions on JIRA, etc., 
etc.)? We want to make sure we’re adopting the appropriate steps. Your 
assistance would be very much appreciated.

Best,

Josh
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [NEW MENTORS REQUIRED] Apache SensSoft

[Joshua Poore]

Hi Dave, Atri!

Thanks for reaching out. I work very closely with Lewis—I’ve been with the 
project since day one, and a few years before that :). I’m happy to help answer 
any questions you might have about the polling, where we’re strong, where we’re 
weak, and what we’d like to do with it. Feel free to take the conversation over 
to dev:

dev-subscr...@senssoft.incubator.apache.org

Best,

Josh




> 
>> On Nov 9, 2018, at 1:29 PM, loo...@gmail.com wrote:
>> 
>> Hi Lewis,
>> 
>> I'd be up for helping too.
>> 
>> Cheers,
>> Dave
>> 
>> On Thu, 8 Nov 2018 at 22:06, lewis john mcgibbney 
>> wrote:
>> 
>>> Hi Folks,
>>> We are looking for new motivated mentors for the Apache SensSoft
>>> (Incubating) project [0] look at that kick ass Website :)
>>> In a nutshell SensSoft is a generalized user behavioral logging platform
>>> for web pages and thin-client applications.
>>> The podling was accepted into the Apache Incubator on 2016-07-13 so has
>>> been maturing and has made one release during that timeframe.
>>> We have been struggling somewhat with active mentorship which has
>>> attributed to the podling struggling with the final push through to
>>> graduation.
>>> Interestingly the SensSoft community is also going through the process of a
>>> PODLINGNAMESEARCH meaning that we will no longer be SensSoft but something
>>> else. This is an excellent time for a mentor or two to come aboard and help
>>> us drive onwards to TLP status.
>>> Please let us know at d...@senssoft.apache.org if you are interested,
>>> Lewis
>>> 
>>> [0] http://senssoft.apache.org/
>>> 
>>> --
>>> http://home.apache.org/~lewismc/
>>> http://people.apache.org/keys/committer/lewismc
>>> 
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org