Re: ASF hosted binaries collecting user data without an explicit opt-in

[Greg Stein]

On Tue, Jun 13, 2017 at 1:00 AM, Roman Shaposhnik 
wrote:
>...

> There's also this:
> https://issues.apache.org/jira/browse/IGNITE-775?
> focusedCommentId=14513325&page=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-14513325
>
> which I find very intriguing.
>
> But I've got to say -- we need INFRA (Greg?) to tell us what they are
> and what they are NOT
> willing to do to enable something like that.
>

If the query is pushed out to the DNS substrate of the Internet, then Infra
really doesn't have much to support :-) ... we'll happily add DNS records
for such.


> If the default is not much -- I think we have no choice but to say
> that since ASF can't
> provide the infrastructure to reliable and securely collect user data
> project that publish
> convenience binaries off of Apache Infra shouldn't do that.
>

The basic policy of Infra is that we'll offer what we can within the budget
given to us by the Board. When an individual project requests resources,
then (again) we'll do what we can for them. You'll see this in daily
make-work, but also in the provision of "project VMs" where we provision a
VM/resources dedicated to a specific project.

However, we have run into an occurrence where a project's VM ran well past
any/all resources that we could provide within the Infrastructure budget
provided by the Board. As a result, we had to shut it down, or the project
needed to request specific budget from the Board to keep that system
running.

So. We can and will do all that we can. If the request is still pretty
nebulous/unclear, then bring it to users@infra for some early discussion.
Once it gets concrete, then file a ticket. We'll go from there.

Cheers,
Greg Stein
Infrastructure Administrator, ASF

[RESULT] [VOTE] - Approve the release of Apache Joshua incubating 6.1

[Tommaso Teofili]

Hi all,

the vote passed with binding +1s from

Lewis John McGibbney
Justin Mclean
John D. Ament

Thanks a lot for your support.
Regards,
Tommaso

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Tommaso Teofili]

result thread is out, will move on with the remaining steps.

Regards,
Tommaso

Il giorno mar 13 giu 2017 alle ore 03:08 lewis john mcgibbney <
lewi...@apache.org> ha scritto:

> PING @Tommaso, can you please close this thread out and we can move on with
> the release?
> Thank you
>
> On Sat, Jun 10, 2017 at 12:56 PM, lewis john mcgibbney  >
> wrote:
>
> > Thank you Justin and John,
> > @tommaso, please progress with the RESULT thread and we can continue with
> > the release process.
> > Lewis
> >
> > On Sat, Jun 10, 2017 at 11:59 AM,  > incubator.apache.org> wrote:
> >
> >>
> >> From: Justin Mclean 
> >> To: general@incubator.apache.org
> >> Cc:
> >> Bcc:
> >> Date: Sat, 10 Jun 2017 12:19:46 +1000
> >> Subject: Re: [VOTE] - Approve the release of Apache Joshua incubating
> 6.1
> >> (rc4)
> >> Hi,
> >>
> >> > @justin, if you are interested in continuing to help Joshua incubating
> >> with
> >> > the release process then pleae stick with us until we iron this one
> out.
> >>
> >> I’ve already voted +1 on the release.
> >>
> >> That GitHub issue looks resolved to me i.e. the copyright owner gave you
> >> permission to use the code under an Apache license.
> >>
> >>
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

[ANNOUNCE] Release Apache Traffic Control 1.8.1 (Incubating)

[Dan Kirkwood]

The Apache Traffic Control team would like to announce the release of
Apache Traffic Control 1.8.1 (incubating).

More details regarding Apache Traffic Control can be found at:
http://trafficcontrol.incubator.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/1.8.1-incubating/

The release notes can be found here:
http://trafficcontrol.incubator.apache.org/downloads/index.html

Thanks!
The Apache Traffic Control Team


Apache Traffic Control 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.

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

[RESULT] [VOTE] Release Apache Traffic Control 1.8.1-incubating

[Dan Kirkwood]

The vote passes with three +1 and no -1 votes.

Thanks!

The Apache Traffic Control (Incubating) team

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

[ANNOUNCE] Apache Fluo 1.1.0-incubating released

[Mike Walch]

The Apache Fluo (incubating) team is happy to announce the release of Fluo
1.1.0-incubating:

https://fluo.apache.org/release/fluo-1.1.0-incubating/

This release improves the scalability of Fluo and a provides a new API for
configuring observers.

Apache Fluo adds distributed transactions to Apache Accumulo, and provides
an observer/notification framework to allow users to incrementally update
large data sets stored in Accumulo.

Thanks,
The Apache Fluo team

=

*Disclaimer*

Apache Fluo is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. 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.

Re: [DRAFT] What the new Status Pages potentially look like

[Dave Fisher]

Hi John -

These are excellent questions. I see each of these as being tuples of various 
kinds.

For example :sga: could have multiple grants each of which has a date and a 
file name to refer to in the foundation records.

The path to the source repository is missing completely.

Some of these items could be transitory. For example distributionRights may be 
confirmed but then something is added which negates those rights until the 
issue is cleared up.

I wonder if it makes sense to provide links to email threads and/or Wiki pages 
with the details?

Regards,
Dave

> On Jun 13, 2017, at 8:22 AM, Jim Apple  wrote:
> 
> What format of data is expected in the fields? Impala's new status
> page SVN config file
> 
> is:
> 
> ---
> :issueTracker: jira
> :wiki: IMPALA
> :jira: IMPALA
> :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> :asfCopyright:
> :distributionRights:
> :ipClearance:
> :sga:
> :website: http://impala.incubator.apache.org
> :graduationDate:
> :resolution:
> 
> I do not know how to fill out asfCopyright, distributionRights,
> ipClearance, or sga. Note that I believe I understand what these
> things ARE, I just don't know how to word them -- "asfCopyright: OK"?
> 
> I also don't know which one(s) correspond to the bold red "No Release
> Yet" on . FWIW, Impala
> has had a couple of ASF releases.
> 
> On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament  wrote:
>> All,
>> 
>> We're piloting a new format for the podling status pages.  Specifically,
>> the current status page leaves a lot to be desired - it's basically crafted
>> html, there's no structure and its hard to find missing items.  The end
>> goal is to have a web form editable in Whimsy, but until we get more input
>> on what the content looks like I don't want to make changes like that.  I'm
>> asking at this point for podlings to take a look at the status output,
>> potentially update their own content, and see if they like the output.
>> 
>> If you navigate to https://whimsy.apache.org/roster/ppmc/ (authentication
>> is via your ASF committer username/password) and find your podling, you'll
>> see your current roster as well as your current status information.
>> 
>> The status pages can be found in SVN at this directory
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>> 
>> Some more information can be found at
>> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
>> 
>> If you're not sure what to fill out, feel free to reach out.
>> 
>> John



signature.asc
Description: Message signed with OpenPGP

Re: [DRAFT] What the new Status Pages potentially look like

[John D. Ament]

Good points Dave.  To be honest, since this is a prototype I don't have
answers any more than "If you think it should do that, we can make it do
that"

What I did have in mind:

---
:issueTracker: jira|github|bugzilla
:wiki: if using confluence, their space key
:jira: if using jira, their issue key (though I suppose this can be
multiple)
:proposal: link to the proposal page.
:asfCopyright: the date that we confirmed ASF copyright headers on the
source code (e.g. the first time a source release passed without any issues)
:distributionRights: the date that we confirmed the resulting binary
satisfied our release policies (e.g. the first time a release included a
binary without any issues)
:ipClearance: a link to the IP Clearance page for this podling.  I guess
this can be multiple?
:sga: date in which a SGA was received
:website: http://impala.incubator.apache.org
:graduationDate: to be filled in when the podling graduates
:resolution: tlp|subproject , if subproject the TLP should be in here
somehwere.  We may want to track as "sponsor."

I can draft this up on a wiki page to gain more input.  What do you think
about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
work through it?  I had a few more questions in line.

On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher  wrote:

> Hi John -
>
> These are excellent questions. I see each of these as being tuples of
> various kinds.
>
> For example :sga: could have multiple grants each of which has a date and
> a file name to refer to in the foundation records.
>
>
We don't usually expose the file name to people outside members, so I'm not
sure this would be useful.  Multiple dates are also not common.


> The path to the source repository is missing completely.
>

Which source repository?  The podlings?  I have a prototype for gitbox
podlings and think I can make it work for ASF git as well.  For SVN, we can
assume default or have a list of values.


>
> Some of these items could be transitory. For example distributionRights
> may be confirmed but then something is added which negates those rights
> until the issue is cleared up.
>
>
+1


> I wonder if it makes sense to provide links to email threads and/or Wiki
> pages with the details?
>
> Regards,
> Dave
>
> > On Jun 13, 2017, at 8:22 AM, Jim Apple  wrote:
> >
> > What format of data is expected in the fields? Impala's new status
> > page SVN config file
> > <
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
> >
> > is:
> >
> > ---
> > :issueTracker: jira
> > :wiki: IMPALA
> > :jira: IMPALA
> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> > :asfCopyright:
> > :distributionRights:
> > :ipClearance:
> > :sga:
> > :website: http://impala.incubator.apache.org
> > :graduationDate:
> > :resolution:
> >
> > I do not know how to fill out asfCopyright, distributionRights,
> > ipClearance, or sga. Note that I believe I understand what these
> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
> >
> > I also don't know which one(s) correspond to the bold red "No Release
> > Yet" on . FWIW, Impala
> > has had a couple of ASF releases.
> >
> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament 
> wrote:
> >> All,
> >>
> >> We're piloting a new format for the podling status pages.  Specifically,
> >> the current status page leaves a lot to be desired - it's basically
> crafted
> >> html, there's no structure and its hard to find missing items.  The end
> >> goal is to have a web form editable in Whimsy, but until we get more
> input
> >> on what the content looks like I don't want to make changes like that.
> I'm
> >> asking at this point for podlings to take a look at the status output,
> >> potentially update their own content, and see if they like the output.
> >>
> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
> (authentication
> >> is via your ASF committer username/password) and find your podling,
> you'll
> >> see your current roster as well as your current status information.
> >>
> >> The status pages can be found in SVN at this directory
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> >>
> >> Some more information can be found at
> >>
> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
> >>
> >> If you're not sure what to fill out, feel free to reach out.
> >>
> >> John
>
>

Re: [DRAFT] What the new Status Pages potentially look like

[Jim Apple]

I'm confused. The message to podlings@ said "If you're not sure what
to fill out, feel free to reach out."

It sounds like there is no set way yet to fill it out.

What can I do to get the bolded, red, inaccurate scare messages off of
our whimsy page?

On Tue, Jun 13, 2017 at 5:30 PM, John D. Ament  wrote:
> Good points Dave.  To be honest, since this is a prototype I don't have
> answers any more than "If you think it should do that, we can make it do
> that"
>
> What I did have in mind:
>
> ---
> :issueTracker: jira|github|bugzilla
> :wiki: if using confluence, their space key
> :jira: if using jira, their issue key (though I suppose this can be
> multiple)
> :proposal: link to the proposal page.
> :asfCopyright: the date that we confirmed ASF copyright headers on the
> source code (e.g. the first time a source release passed without any issues)
> :distributionRights: the date that we confirmed the resulting binary
> satisfied our release policies (e.g. the first time a release included a
> binary without any issues)
> :ipClearance: a link to the IP Clearance page for this podling.  I guess
> this can be multiple?
> :sga: date in which a SGA was received
> :website: http://impala.incubator.apache.org
> :graduationDate: to be filled in when the podling graduates
> :resolution: tlp|subproject , if subproject the TLP should be in here
> somehwere.  We may want to track as "sponsor."
>
> I can draft this up on a wiki page to gain more input.  What do you think
> about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
> work through it?  I had a few more questions in line.
>
> On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher  wrote:
>
>> Hi John -
>>
>> These are excellent questions. I see each of these as being tuples of
>> various kinds.
>>
>> For example :sga: could have multiple grants each of which has a date and
>> a file name to refer to in the foundation records.
>>
>>
> We don't usually expose the file name to people outside members, so I'm not
> sure this would be useful.  Multiple dates are also not common.
>
>
>> The path to the source repository is missing completely.
>>
>
> Which source repository?  The podlings?  I have a prototype for gitbox
> podlings and think I can make it work for ASF git as well.  For SVN, we can
> assume default or have a list of values.
>
>
>>
>> Some of these items could be transitory. For example distributionRights
>> may be confirmed but then something is added which negates those rights
>> until the issue is cleared up.
>>
>>
> +1
>
>
>> I wonder if it makes sense to provide links to email threads and/or Wiki
>> pages with the details?
>>
>> Regards,
>> Dave
>>
>> > On Jun 13, 2017, at 8:22 AM, Jim Apple  wrote:
>> >
>> > What format of data is expected in the fields? Impala's new status
>> > page SVN config file
>> > <
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
>> >
>> > is:
>> >
>> > ---
>> > :issueTracker: jira
>> > :wiki: IMPALA
>> > :jira: IMPALA
>> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
>> > :asfCopyright:
>> > :distributionRights:
>> > :ipClearance:
>> > :sga:
>> > :website: http://impala.incubator.apache.org
>> > :graduationDate:
>> > :resolution:
>> >
>> > I do not know how to fill out asfCopyright, distributionRights,
>> > ipClearance, or sga. Note that I believe I understand what these
>> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
>> >
>> > I also don't know which one(s) correspond to the bold red "No Release
>> > Yet" on . FWIW, Impala
>> > has had a couple of ASF releases.
>> >
>> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament 
>> wrote:
>> >> All,
>> >>
>> >> We're piloting a new format for the podling status pages.  Specifically,
>> >> the current status page leaves a lot to be desired - it's basically
>> crafted
>> >> html, there's no structure and its hard to find missing items.  The end
>> >> goal is to have a web form editable in Whimsy, but until we get more
>> input
>> >> on what the content looks like I don't want to make changes like that.
>> I'm
>> >> asking at this point for podlings to take a look at the status output,
>> >> potentially update their own content, and see if they like the output.
>> >>
>> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
>> (authentication
>> >> is via your ASF committer username/password) and find your podling,
>> you'll
>> >> see your current roster as well as your current status information.
>> >>
>> >> The status pages can be found in SVN at this directory
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>> >>
>> >> Some more information can be found at
>> >>
>> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
>> >>
>> >> If you're not sure what to fill out, feel free to reach out.
>> >>
>> >> John
>>
>>

-

Re: [DRAFT] What the new Status Pages potentially look like

[John D. Ament]

Jim,

For your specific cases, if all you want is to remove red text:

- for :sga: enter the date in -MM-DD format of when the ASF Secretary
acknowledged your SGA.  Based on the records I have its 2016-03-15
- For the :asfCopyright: and :distributionRights: attributes, I would use
2017-01-20 as that's the day of the results of 2.8 which was the first
release to have no issues during review.

But please do continue to provide input, want to make sure we're building
something useful, not a pain.

HTH,

John

On Tue, Jun 13, 2017 at 8:52 PM Jim Apple  wrote:

> I'm confused. The message to podlings@ said "If you're not sure what
> to fill out, feel free to reach out."
>
> It sounds like there is no set way yet to fill it out.
>
> What can I do to get the bolded, red, inaccurate scare messages off of
> our whimsy page?
>
> On Tue, Jun 13, 2017 at 5:30 PM, John D. Ament 
> wrote:
> > Good points Dave.  To be honest, since this is a prototype I don't have
> > answers any more than "If you think it should do that, we can make it do
> > that"
> >
> > What I did have in mind:
> >
> > ---
> > :issueTracker: jira|github|bugzilla
> > :wiki: if using confluence, their space key
> > :jira: if using jira, their issue key (though I suppose this can be
> > multiple)
> > :proposal: link to the proposal page.
> > :asfCopyright: the date that we confirmed ASF copyright headers on the
> > source code (e.g. the first time a source release passed without any
> issues)
> > :distributionRights: the date that we confirmed the resulting binary
> > satisfied our release policies (e.g. the first time a release included a
> > binary without any issues)
> > :ipClearance: a link to the IP Clearance page for this podling.  I guess
> > this can be multiple?
> > :sga: date in which a SGA was received
> > :website: http://impala.incubator.apache.org
> > :graduationDate: to be filled in when the podling graduates
> > :resolution: tlp|subproject , if subproject the TLP should be in here
> > somehwere.  We may want to track as "sponsor."
> >
> > I can draft this up on a wiki page to gain more input.  What do you think
> > about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
> > work through it?  I had a few more questions in line.
> >
> > On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher 
> wrote:
> >
> >> Hi John -
> >>
> >> These are excellent questions. I see each of these as being tuples of
> >> various kinds.
> >>
> >> For example :sga: could have multiple grants each of which has a date
> and
> >> a file name to refer to in the foundation records.
> >>
> >>
> > We don't usually expose the file name to people outside members, so I'm
> not
> > sure this would be useful.  Multiple dates are also not common.
> >
> >
> >> The path to the source repository is missing completely.
> >>
> >
> > Which source repository?  The podlings?  I have a prototype for gitbox
> > podlings and think I can make it work for ASF git as well.  For SVN, we
> can
> > assume default or have a list of values.
> >
> >
> >>
> >> Some of these items could be transitory. For example distributionRights
> >> may be confirmed but then something is added which negates those rights
> >> until the issue is cleared up.
> >>
> >>
> > +1
> >
> >
> >> I wonder if it makes sense to provide links to email threads and/or Wiki
> >> pages with the details?
> >>
> >> Regards,
> >> Dave
> >>
> >> > On Jun 13, 2017, at 8:22 AM, Jim Apple  wrote:
> >> >
> >> > What format of data is expected in the fields? Impala's new status
> >> > page SVN config file
> >> > <
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
> >> >
> >> > is:
> >> >
> >> > ---
> >> > :issueTracker: jira
> >> > :wiki: IMPALA
> >> > :jira: IMPALA
> >> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> >> > :asfCopyright:
> >> > :distributionRights:
> >> > :ipClearance:
> >> > :sga:
> >> > :website: http://impala.incubator.apache.org
> >> > :graduationDate:
> >> > :resolution:
> >> >
> >> > I do not know how to fill out asfCopyright, distributionRights,
> >> > ipClearance, or sga. Note that I believe I understand what these
> >> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
> >> >
> >> > I also don't know which one(s) correspond to the bold red "No Release
> >> > Yet" on . FWIW, Impala
> >> > has had a couple of ASF releases.
> >> >
> >> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament  >
> >> wrote:
> >> >> All,
> >> >>
> >> >> We're piloting a new format for the podling status pages.
> Specifically,
> >> >> the current status page leaves a lot to be desired - it's basically
> >> crafted
> >> >> html, there's no structure and its hard to find missing items.  The
> end
> >> >> goal is to have a web form editable in Whimsy, but until we get more
> >> input
> >> >> on what the content looks like I don't want to make changes like
> that.
> >> I'm
> >> >> asking at this point for podling

[VOTE]: Release Apache RocketMQ 4.1.0(incubating)(RC1)

[dongeforever]

Hello Incubator PMC,


The Apache RocketMQ community has voted and approved the proposal to release 
Apache RocketMQ 4.1.0 (incubating). We now kindly request the IPMC review and 
vote on this incubator release.


Apache RocketMQ is a distributed messaging and streaming platform with low 
latency, high performance and reliability, trillion-level capacity and flexible 
scalability.




[VOTE] Thread:
https://lists.apache.org/thread.html/c81e7329d1e47425a50a11e863257a2798bf17c52e9573e0020c42d0@%3Cdev.rocketmq.apache.org%3E


[RESULT][VOTE] Thread:
https://lists.apache.org/thread.html/626e93ad0ed4c1df6a5ee5b7466b1ab4f4b10f3e6ec72cac11157368@%3Cdev.rocketmq.apache.org%3E


The artifacts:
https://dist.apache.org/repos/dist/dev/incubator/rocketmq/4.1.0-incubating-rc1/


The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1005


Git tag for the release:
https://github.com/apache/incubator-rocketmq/tree/rocketmq-all-4.1.0-incubating


Hash for the release tag:
308598865addb9a857d432c9607478642541093c


Release Notes:
https://rocketmq.apache.org/release-notes-4.1.0-incubating/


The artifacts have been signed with Key : 133C87CA, which can be found in the 
keys file: 
https://dist.apache.org/repos/dist/dev/incubator/rocketmq/KEYS






The vote will be open for at least 72 hours or until necessary number of votes 
are reached.


Please vote accordingly:


[ ] +1 approve 
[ ] +0 no opinion 
[ ] -1 disapprove with the reason


Thanks,
The Apache RocketMQ Team

Re: [VOTE]: Release Apache RocketMQ 4.1.0(incubating)(RC1)

[Justin Mclean]

Hi,

+1 binding

Carried over from dev list. All my usual checks done.

Thanks,
Justin

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