Re: How to review so-called "binary releases"?

[Carlos Santana]

You could split the review in 2 emails

1. Vote as ASF on the release of the source tgz artifact and release
2. Ask for a review on the publishing of a binary artifact based on the source 
tgz from email vote #1 (this is not a ASF Vote, just a request for review a 
binary) this email of course would be after email #1 is vote closed.

- Carlos Santana
IBM STSM
@csantanapr

> On Nov 20, 2018, at 11:03 PM, Julian Hyde  wrote:
> 
> +1 to what Bertrand wrote. Solves the problem very neatly. Thank you, 
> Bertrand.
> 
> It goes a long way towards answering my original question, because “What 
> should voters check for when reviewing binary artifacts?” is now a matter for 
> each PMC, not a matter for the Foundation.
> 
> +1 to Roman’s suggestion to make it part of policy.
> 
> If we follow Bertrand’s semantics then the semantics of a vote are a little 
> more complex than before. The voter is voting on the release (consisting only 
> of source artifacts), an act of the Foundation, and the binary artifacts, an 
> act of the PMC. It would be extremely helpful if there were a template for 
> the text of the vote email that release managers you use, if they so chose. 
> Roman, could you include such a template the the revised release policy?
> 
> Julian
> 
> 
>> On Nov 20, 2018, at 7:05 PM, Roman Shaposhnik  wrote:
>> 
>> On Fri, Nov 16, 2018 at 6:59 AM Jim Jagielski > <mailto:j...@jagunet.com>> wrote:
>>> 
>>> 
>>> 
>>>> On Nov 15, 2018, at 2:41 AM, Bertrand Delacretaz 
>>>>  wrote:
>>>> 
>>>> 
>>>> I see this as a two-level thing:
>>>> 
>>>> a) The source release is an Act of the Foundation, it is what the
>>>> foundation produces
>>>> 
>>>> b) For the binaries, the PMC states that it thinks they are good and
>>>> declares that the published digests and signatures are the correct
>>>> ones. The Foundation does not state anything about them - use at your
>>>> own risk but in practice that risk is very low if the PMC members
>>>> collectively recommend using them.
>>>> 
>>>> That's not very different from what other open source projects do - we
>>>> need a) for our legal shield but b) is exactly like random open source
>>>> projects operate.
>>>> 
>>>> You have to trust an open source project when you use their binaries,
>>>> and you can use digests and signatures to verify that those binaries
>>>> are the same that everyone else uses - I don't think anyone provides
>>>> more guarantees than that, except when you pay for someone to state
>>>> that those binaries are good.
>>>> 
>>>> If people agree with this view we might need to explain this better,
>>>> "unofficial" does not mean much, this two-level view might be more
>>>> useful.
>>> 
>>> Agree 100%. Thx for very clearly and accurately describing all this.
>> 
>> +1 to this as well.
>> 
>> In fact, I love it so much that I'd like to have it published as part of our
>> official guide:
>>  http://www.apache.org/legal/release-policy.html#compiled-packages 
>> <http://www.apache.org/legal/release-policy.html#compiled-packages>
>> 
>> Any objections?
>> 
>> Thanks,
>> Roman.
>> 
>> -
>> 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][LAZY][IP CLEARANCE] OpenWhisk Composer

[Carlos Santana]

+1 

- Carlos Santana
@csantanapr

> On Nov 17, 2018, at 10:38 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi Incubator PMC members,
> 
> The OpenwWhisk podling would like to accept a donation of the Composer
> module, as per https://issues.apache.org/jira/browse/INCUBATOR-222
> 
> See http://incubator.apache.org/ip-clearance/openwhisk-composer.html
> 
> Please vote to approve this contribution.
> 
> This majority vote is open for at least 72 hours and as usual lazy
> consensus applies.
> 
> -Bertrand
> 
> -
> 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: How to review so-called "binary releases"?

[Carlos Santana]

The Jim we are in strongly agreement then :-)

Willem
Yes I think that’s the word “DISCLAIMER”, was the concept and idea I was 
describing. 

I think it depends on the binary (ie npm tgz, jar, docker image, dll, 
executable) and location (website, sftp, maven, npm registry, nuget, etc) on 
where to put this. Up to each community what’s the best was to make user 
downloading aware that this DISCLAIMER exist. 

- Carlos Santana
@csantanapr

> On Nov 7, 2018, at 8:10 PM, Willem Jiang  wrote:
> 
> DISCLAIMER

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

Re: How to review so-called "binary releases"?

[Carlos Santana]

Jim

What do you think now?
Was that a good or bad thing?

TLDR; I’m in favor of convenient binaries is just the how they are handled. 

Sorry for my brevity, what I meant is that binaries should not be beside next 
to the source release seating on the same server and giving the same guarantees 
for both type of artifacts (source vs binary).  

Now in terms of convenience :-)
ASF should not block a project of making binaries available to their community 
for what ever purpose they think appropriate (ie nightly, binary of a RC, 
binary of final RC)

ASF should provide guidance to the projects to make sure they make their 
communities aware that a source artifact is different from a binary artifact. 
A project for example can put warnings and bold text on the location (ie 
directory, readme, inside the binary, download webpage, wiki etc) where the 
community downloads a copy of the binary. 
The warning can say this is not a release of the ASF, is just a convenient 
binary “download on your own risk”, we provide sha256 sum and maybe the binary 
is even signed, but best practice is for you to download the source and be in 
control of building the binary. 



- Carlos Santana
@csantanapr

> On Nov 7, 2018, at 7:04 AM, Jim Jagielski  wrote:
> 
> Just a FYI that in the early days of the ASF (and the httpd project), 
> community binaries were a common offering...
> -
> 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: How to review so-called "binary releases"?

[Carlos Santana]

ASF should only distribute source 

Having binaries/compiled along side of the source is not a good signal and 
confusing. 

- Carlos Santana
@csantanapr

> On Nov 7, 2018, at 4:24 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
>> On Tue, Nov 6, 2018 at 11:07 PM David Nalley  wrote:
>> ... To my mind, allowing projects to distribute 'convenience binaries'
>> from our hardware, in a place we say contains releases, and which is
>> occasionally consumed in such a way as to dwarf what we call official
>> releases[1], makes them actions of the Foundation despite our
>> protestations
> 
> I tend to agree and would feel *much* more comfortable if binaries
> went to a different place like binaries.apache.org where we can have
> all sort of loud disclaimers.
> 
> I don't know how practical that is in terms of our mirroring system,
> and that might make releases a bit more complicated but it would make
> things much clearer IMO.
> 
> -Bertrand
> 
> -
> 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: Inviting new committers to a podling

[Carlos Santana]

Hi Craig

In general I agree with:
- Document more details about the process
- Add standard templates for inviting, accepting and welcoming emails to
nominee

I think the process currently describe it works and I don't see why the
need for the change
https://incubator.apache.org/guides/ppmc.html
Section: Adding new committers
Section: Voting in a new PPMC member

We have followed this process for some recent members we added to OpenWhisk.

For PPMC members:
We held a vote on ppmc private, give the minimum 72 hours for the vote, and
close the vote when there are 3 or more votes.
But we don't require ALL members to vote +1 to move forward, this would be
extremely difficult to get ALL votes.
Then we do the [NOTICE] to IPMC private list as indicated in the process
doc, with a minimum of 72 hours to hear back from IPMC on any objections
this takes care of the PPMC member being added in isolation by the PPMC.
Once more than 72 hours has pass and not negative feedback from IPMC we
send invitation to new member, they accept, mentor requires Apache account.

For Committers members:
We follow similar process as ppmc new member.
We held a vote on ppmc private, give the minimum 72 hours for the vote, and
close the vote when there are 3 or more votes.
But we don't require ALL members to vote +1 to move forward, this would be
extremely difficult to get ALL votes.
Once more than 72 hours has pass and not negative feedback from IPMC we
send invitation to new member, they accept, mentor requires Apache account.

The only difference is we don't send an email [NOTICE] to private IPM for
them to evaluate the nominee and reject in 72 hours.

Would adding the step to send a [NOTICE] to private IPMC for Committers
would address your concerns?

I would be against changing the documented process to be more strict, to
require ALL PPMC members to vote +1, and at least 3 +1 IPMC to vote get
someone added as a Committer or PPMC member.

-- Carlos


On Mon, Apr 30, 2018 at 7:50 PM Craig Russell  wrote:

> I would respectfully suggest that the PPMC guide section that describes
> how to invite new committers and PPMC members is not adequate to the task.
>
> This is what I think is the relevant section of
> https://incubator.apache.org/guides/ppmc.html :
>
> There are no ASF wide rules on how to decide when to make someone a
> committer, podlings need to agree an approach that works for them. Some ASF
> projects have a high bar requiring significant contributions before someone
> is considered, other projects grant it more freely to anyone who shows
> interest in contributing. Some projects use formal [DISCUSS] and [VOTE]
> threads on the private mailing list, others use a more lazy consensus
> approach. For more information see, commit access and the ASF How it Works
> document, which explains meritocracy and roles.
>
> Once the decision has been made the proposer offers committership to the
> nominee. If the nominee accepts the responsibility of being a committer for
> the project, the nominee formally becomes an Apache committer.
>
> The proposer then asks an Incubator PMC member (typically one of the
> mentors) to follow the documented procedures
> http://www.apache.org/dev/pmc.html#newcommitter to complete the process.
> If the nominee is already an Apache committer on another project, the
> Incubator PMC member simply updates the SVN authorization settings to
> include the nominee as a committer on the podling.
>
> I suggest that we look again at this section for these aspects:
>
> 1. We should document how we expect podlings to discuss, vote, and invite
> committers and PPMC members. The paragraph describing how to decide on new
> committers should be non-prescriptive with regard to the criteria, but
> prescribe the process. If a podling doesn't want to follow the process of
> discussing, voting, and inviting, it should explicitly document what it
> wants to do so that its unique process can be incorporated into the
> project's unique Project By-Laws. But most podlings will want to follow the
> processes of most TLPs:
>
> a: discuss in private the desire to invite a new committer/PPMC member
> b: hold a vote in private, with +1, -1, +0 and -0
> c: end the vote when all PPMC members have voted, or at least 72 hours
> have passed; with at least three binding (IPMC members) votes in favor, and
> no -1 votes
>
> 2. We should document the process in the guide and *not* refer to the page
> that describes how PMCs invite new committers. The processes are different
> in the case of podlings and it is simply confusing to mix them. Podlings
> especially could use help with "standard" emails similar to those found
> here: http://community.apache.org/newcommitter.html#new-committer-process
>
> 3. It is not obvious what the policy is for a podling to invite new
> committers and PPMC members. I don't believe it should be the
> responsibility of the podling to decide in isolation the process to invite
> new committers, just 

Re: Updating the Board Report Reminder Template

[Carlos Santana]

Good suggestion John

+1

- Carlos Santana
@csantanapr

> On Apr 20, 2018, at 7:08 PM, John D. Ament <johndam...@apache.org> wrote:
> 
> All,
> 
> I'd like to propose a minor tweak to our email reminder for podling board
> reports.  You can find the current template at [1].
> 
> We've seen an increasing trend of podlings including potential committer
> names in the report.  The podling reports should not include potential
> committers/PPMCs, since those votes could fail.
> 
> Therefore, I'd like to add a blurb "Your report should omit mentions to any
> potential committers, and instead mention that there are potential
> committers being considered."
> 
> Thoughts?
> 
> John
> 
> [1]:
> http://svn.apache.org/repos/asf/incubator/public/trunk/email_reminder_template.txt

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

Re: Altering PMC for graduation

[Carlos Santana]

For Apache OpenWhisk we are in same situation so it would be good to understand 
the guideline on how to handle such situation. 

- Carlos Santana
@csantanapr

> On Mar 23, 2018, at 4:06 PM, Dave Neuman <neu...@apache.org> wrote:
> 
> Hey IPMC,
> I had a question about altering the PMC for graduation.
> We have a few folks who are no longer active participants in our project
> that are still a part of our PMC.  In the process of generating our
> graduation resolution we were wondering if we could take the opportunity to
> have these members just be committers and not PMC members anymore?  If yes,
> what would the process look like, would it be enough to just make the
> roster alterations in Whimsy?  I have already spoken to each of these
> people individually and made sure they were on-board with just being
> committers and not PMC members.
> 
> We are really excited to draft our resolution and I think this is the last
> thing standing in our way!
> 
> 
> Thanks in advance for the help!
> 
> Dave

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

Re: Google Summer of Code 2018 Mentor Registration

[Carlos Santana]

I got ACK from the OpenWhisk PPMC to include OpenWhisk in GSOC 2018

I went ahead and created ideas in JIRA [1]

What are the next steps I need to take to register as a mentor, and any
deadline?


[1] OpenWhisk GSOC ideas:
OpenWhisk GSOC: Core: AutoGen Swagger (Scala)
https://issues.apache.org/jira/browse/COMDEV-276
OpenWhisk GSOC: Performance: Improve Load Balancer (Scala)
https://issues.apache.org/jira/browse/COMDEV-277
OpenWhisk GSOC: New Runtimes: (TypeScript, C#, .Net, Kotlin, Dart, Rust, R,
Ruby)
https://issues.apache.org/jira/browse/COMDEV-278
OpenWhisk GSOC: SDKs via Swagger (Python, Java, Scala, PHP, Go)
https://issues.apache.org/jira/browse/COMDEV-279
OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCode, IntelliJ)
https://issues.apache.org/jira/browse/COMDEV-280
OpenWhisk GSOC: WebSite & Sandbox (HTML/JS/CSS)
https://issues.apache.org/jira/browse/COMDEV-281

-- Carlos Santana
OpenWhisk PPMC


On Thu, Mar 8, 2018 at 9:29 PM Huxing Zhang <hux...@apache.org> wrote:

> Hi Carlos,
>
> Please refer to this thread [1] for more details.
>
>
> https://lists.apache.org/thread.html/4911a8b50e83a7104047dffa1656215ea8f991ede960dfe3dd784d0e@%3Cgeneral.incubator.apache.org%3E
>
>
> On Thu, Mar 8, 2018 at 6:43 PM, Carlos Santana <csantan...@gmail.com>
> wrote:
> > Hi OpenWhisk want to mentor
> >
> > What do we need to submit to be mentors?
> >
> > I’m currently drafting some ideas
> >
> > - Carlos Santana
> > @csantanapr
> >
> >> On Mar 8, 2018, at 5:18 AM, Huxing Zhang <hux...@apache.org> wrote:
> >>
> >> Hi,
> >>
> >>> On Wed, Feb 28, 2018 at 7:43 AM, Stian Soiland-Reyes <st...@apache.org>
> wrote:
> >>> Any podlings participating in GSOC this year?
> >>> (strongly recommended!)
> >>
> >> Dubbo is planning to participate. Mentor registration is on the way
> >> and ideas will come soon.
> >>
> >>>
> >>> See below for mentor registration procedure - mentors need
> >>> acknowledgement from someone else on your private@podling.incubator
> list
> >>> (aka the podling PMC). Note that you do NOT normally need ACK from the
> >>> Incubator PMC. [1]
> >>>
> >>> -
> >>>
> >>> Terminology: Your GSOC "mentors" are probably different from your
> >>> existing Incubator "mentors"!  The GSOC mentor can be any of the
> >>> committers of your podling (that the PPMC deem suitable for mentoring a
> >>> student fresh to your code base).
> >>>
> >>> Later your incubator mentors can assist in how to give the students
> >>> access, e.g. how to process pull requests or ask for ICLAs. Your PPMC
> is
> >>> free to decide when/if to grant a successful GSOC student
> committership.
> >>>
> >>> See my separate email [2] on how to register GSOC ideas in JIRA to
> >>> attract potential students.
> >>>
> >>>
> >>> [1] http://markmail.org/message/kl5akdi2oohp32c6
> >>> [2]
> https://lists.apache.org/thread.html/4e2b5b0ef2e565a08470ecbf9b2a6fc27a25ce28d4708334c9073fb9@%3Cgeneral.incubator.apache.org%3E
> >>>
> >>>
> >>>> On Sat, 24 Feb 2018 22:19:34 +0100, Ulrich Stärk <u...@apache.org>
> wrote:
> >>>> Dear PMCs,
> >>>>
> >>>> I'm happy to announce that the ASF has made it onto the list of
> accepted organizations for
> >>>> Google Summer of Code 2018! [1,2]
> >>>>
> >>>> It is now time for mentors to sign up, so please pass this email on
> to your community and
> >>>> podlings. If you aren’t already subscribed to
> ment...@community.apache.org you should do so now else
> >>>> you might miss important information.
> >>>>
> >>>> Mentor signup requires two steps: mentor signup in Google's system
> [3] and PMC acknowledgement.
> >>>>
> >>>> If you want to mentor a project in this year's SoC you will have to
> >>>>
> >>>> 1. Be an Apache committer.
> >>>> 2. Request an acknowledgement from the PMC for which you want to
> mentor projects. Use the below
> >>>> template and *do not forget to copy ment...@community.apache.org*.
> We will use the email adress you
> >>>> indicate to send the invite to be a mentor for Apache.
> >>>>
> >>>> PMCs, read carefully please.
> >>>>
> >>>> We request that each mentor is acknowledged by a PMC member. This is
> to 

Re: Google Summer of Code 2018 Mentor Registration

[Carlos Santana]

Hi OpenWhisk want to mentor 

What do we need to submit to be mentors?

I’m currently drafting some ideas 

- Carlos Santana
@csantanapr

> On Mar 8, 2018, at 5:18 AM, Huxing Zhang <hux...@apache.org> wrote:
> 
> Hi,
> 
>> On Wed, Feb 28, 2018 at 7:43 AM, Stian Soiland-Reyes <st...@apache.org> 
>> wrote:
>> Any podlings participating in GSOC this year?
>> (strongly recommended!)
> 
> Dubbo is planning to participate. Mentor registration is on the way
> and ideas will come soon.
> 
>> 
>> See below for mentor registration procedure - mentors need
>> acknowledgement from someone else on your private@podling.incubator list
>> (aka the podling PMC). Note that you do NOT normally need ACK from the
>> Incubator PMC. [1]
>> 
>> -
>> 
>> Terminology: Your GSOC "mentors" are probably different from your
>> existing Incubator "mentors"!  The GSOC mentor can be any of the
>> committers of your podling (that the PPMC deem suitable for mentoring a
>> student fresh to your code base).
>> 
>> Later your incubator mentors can assist in how to give the students
>> access, e.g. how to process pull requests or ask for ICLAs. Your PPMC is
>> free to decide when/if to grant a successful GSOC student committership.
>> 
>> See my separate email [2] on how to register GSOC ideas in JIRA to
>> attract potential students.
>> 
>> 
>> [1] http://markmail.org/message/kl5akdi2oohp32c6
>> [2] 
>> https://lists.apache.org/thread.html/4e2b5b0ef2e565a08470ecbf9b2a6fc27a25ce28d4708334c9073fb9@%3Cgeneral.incubator.apache.org%3E
>> 
>> 
>>> On Sat, 24 Feb 2018 22:19:34 +0100, Ulrich Stärk <u...@apache.org> wrote:
>>> Dear PMCs,
>>> 
>>> I'm happy to announce that the ASF has made it onto the list of accepted 
>>> organizations for
>>> Google Summer of Code 2018! [1,2]
>>> 
>>> It is now time for mentors to sign up, so please pass this email on to your 
>>> community and
>>> podlings. If you aren’t already subscribed to ment...@community.apache.org 
>>> you should do so now else
>>> you might miss important information.
>>> 
>>> Mentor signup requires two steps: mentor signup in Google's system [3] and 
>>> PMC acknowledgement.
>>> 
>>> If you want to mentor a project in this year's SoC you will have to
>>> 
>>> 1. Be an Apache committer.
>>> 2. Request an acknowledgement from the PMC for which you want to mentor 
>>> projects. Use the below
>>> template and *do not forget to copy ment...@community.apache.org*. We will 
>>> use the email adress you
>>> indicate to send the invite to be a mentor for Apache.
>>> 
>>> PMCs, read carefully please.
>>> 
>>> We request that each mentor is acknowledged by a PMC member. This is to 
>>> ensure the mentor is in good
>>> standing with the community. When you receive a request for 
>>> acknowledgement, please ACK it and cc
>>> ment...@community.apache.org
>>> 
>>> Lastly, it is not yet too late to record your ideas in Jira (see my 
>>> previous emails for details).
>>> Students will now begin to explore ideas so if you haven’t already done so, 
>>> record your ideas
>>> immediately!
>>> 
>>> Cheers,
>>> 
>>> Uli
>>> 
>>> mentor request email template:
>>> 
>>> to: private@.apache.org
>>> cc: ment...@community.apache.org
>>> subject: GSoC 2018 mentor request for 
>>> 
>>>  PMC,
>>> 
>>> please acknowledge my request to become a mentor for Google Summer of Code 
>>> 2018 projects for Apache
>>> .
>>> 
>>> I would like to receive the mentor invite to 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> [1] https://summerofcode.withgoogle.com/organizations/
>>> [2] https://summerofcode.withgoogle.com/organizations/5718432427802624/
>>> [3] https://summerofcode.withgoogle.com/
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> For additional commands, e-mail: dev-h...@community.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> -- 
> Best Regards！
> Huxing
> 
> -
> 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: Two issues with license and notice auditing

[Carlos Santana]

As always Sebb thank you for your advice and quick response.


On Fri, Mar 2, 2018 at 10:27 AM sebb <seb...@gmail.com> wrote:

> On 2 March 2018 at 11:41, Carlos Santana <csantan...@gmail.com> wrote:
> > Thanks sebb
> >
> > What do we do with “Apache Tentacles cannot support tar.gz”
>
> Never used it, but here are some suggestions:
>
> Provide a patch to the project.
>
> Unpack the archive and check it manually
>
> Unpack the archive and repack as zip, then use tentacles again.
>
> If there is a zip archive as well as a tar.gz, then use Tentacles to
> check the zip, and a diff program to check that the contents of the
> two archives are the same.
> (which they should be, barring any EOL considerations).
>
> > How are others dealing with this? Are you using Tentacles or another tool
> > in your releases?
> >
> > — Carlks
> >
> > On Fri, Mar 2, 2018 at 5:07 AM sebb <seb...@gmail.com> wrote:
> >
> >> On 2 March 2018 at 04:28, Carlos Santana <csantan...@gmail.com> wrote:
> >> > Forwarding to Incubator mailing list to see if they any guidance.
> >> >
> >> > -- Forwarded message -
> >> > From: Ying Chun Guo <guoyi...@cn.ibm.com>
> >> > Date: Thu, Mar 1, 2018 at 10:27 PM
> >> > Subject: Two issues with license and notice auditing
> >> > To: <d...@openwhisk.apache.org>
> >> >
> >> >
> >> > Hi, team
> >> >
> >> > When we are using Apache Creadur to audit licensing and notice files,
> we
> >> > met with two problems. I'm looking for any people who have
> experiences on
> >> > that.
> >> >
> >> > 1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short
> >> format
> >> > of Apache license header, which we plan to use in the small test
> files.
> >>
> >> Please raise a JIRA against RAT so the license can be added to the list.
> >>
> >> Meanwhile, you can add your own licenses:
> >>
> >>
> https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html
> >>
> >> > 2. Apache Tentacles cannot support tar.gz files in the staging repo.
> >> >
> >> > We have solutions to bypass these two questions. For the first issue,
> we
> >> > can put those files with mini headers in the Rat exclusion list.
> >>
> >> Please don't do that; see above.
> >>
> >> > For the
> >> > second issue, we can use bash script to check LICENSE and NOTICE or we
> >> can
> >> > use zip format instead, other than tar.gz. But I would like to check
> if
> >> > there are any other suggestions to these issues. Thanks.
> >> >
> >> > Best regards
> >> > Ying Chun Guo (Daisy)
> >>
>

Re: Two issues with license and notice auditing

[Carlos Santana]

Thanks sebb

What do we do with “Apache Tentacles cannot support tar.gz”

How are others dealing with this? Are you using Tentacles or another tool
in your releases?

— Carlks

On Fri, Mar 2, 2018 at 5:07 AM sebb <seb...@gmail.com> wrote:

> On 2 March 2018 at 04:28, Carlos Santana <csantan...@gmail.com> wrote:
> > Forwarding to Incubator mailing list to see if they any guidance.
> >
> > -- Forwarded message -
> > From: Ying Chun Guo <guoyi...@cn.ibm.com>
> > Date: Thu, Mar 1, 2018 at 10:27 PM
> > Subject: Two issues with license and notice auditing
> > To: <d...@openwhisk.apache.org>
> >
> >
> > Hi, team
> >
> > When we are using Apache Creadur to audit licensing and notice files, we
> > met with two problems. I'm looking for any people who have experiences on
> > that.
> >
> > 1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short
> format
> > of Apache license header, which we plan to use in the small test files.
>
> Please raise a JIRA against RAT so the license can be added to the list.
>
> Meanwhile, you can add your own licenses:
>
> https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html
>
> > 2. Apache Tentacles cannot support tar.gz files in the staging repo.
> >
> > We have solutions to bypass these two questions. For the first issue, we
> > can put those files with mini headers in the Rat exclusion list.
>
> Please don't do that; see above.
>
> > For the
> > second issue, we can use bash script to check LICENSE and NOTICE or we
> can
> > use zip format instead, other than tar.gz. But I would like to check if
> > there are any other suggestions to these issues. Thanks.
> >
> > Best regards
> > Ying Chun Guo (Daisy)
>

Fwd: Two issues with license and notice auditing

[Carlos Santana]

Forwarding to Incubator mailing list to see if they any guidance.

-- Forwarded message -
From: Ying Chun Guo 
Date: Thu, Mar 1, 2018 at 10:27 PM
Subject: Two issues with license and notice auditing
To: 


Hi, team

When we are using Apache Creadur to audit licensing and notice files, we
met with two problems. I'm looking for any people who have experiences on
that.

1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short format
of Apache license header, which we plan to use in the small test files.
2. Apache Tentacles cannot support tar.gz files in the staging repo.

We have solutions to bypass these two questions. For the first issue, we
can put those files with mini headers in the Rat exclusion list. For the
second issue, we can use bash script to check LICENSE and NOTICE or we can
use zip format instead, other than tar.gz. But I would like to check if
there are any other suggestions to these issues. Thanks.

Best regards
Ying Chun Guo (Daisy)

Re: Google Summer of Code 2018 is coming

[Carlos Santana]

This is great will be awesome to add an idea for having a student work on 
Serverless maybe adding support for a new programming language 

- Carlos Santana
@csantanapr

> On Feb 27, 2018, at 6:35 PM, Stian Soiland-Reyes <st...@apache.org> wrote:
> 
> Reminder to podlings of how to register ideas for Google Summer of Code.
> (see below)
> 
> It is still not too late!  This is a great way to learn how to engage
> with new contributors to your project, hopefully picking up new
> committers and fresh code on the way!
> 
> Just decide on someone from your podling committers to be a GSOC mentor
> for the student (Note that this "mentor" probably is different from your
> existing incubator mentors!) - and register some ideas in JIRA using the
> "gsoc2018" label.  If your project is not (yet) using JIRA, you can post
> the ideas under the COMDEV project including your podling name in the
> title.
> 
> See separate email on mentor registration.
> 
>> On Sun, 21 Jan 2018 22:22:33 +0100, Ulrich Stärk <u...@apache.org> wrote:
>> Hello PMCs (incubator Mentors, please forward this email to your podlings),
>> 
>> Google Summer of Code [1] is a program sponsored by Google allowing students 
>> to spend their summer
>> working on open source software. Students will receive stipends for 
>> developing open source software
>> full-time for three months. Projects will provide mentoring and project 
>> ideas, and in return have
>> the chance to get new code developed and - most importantly - to identify 
>> and bring in new committers.
>> 
>> The ASF will apply as a participating organization meaning individual 
>> projects don't have to apply
>> separately.
>> 
>> If you want to participate with your project we ask you to do the following 
>> things as soon as
>> possible but please no later than 2017-01-30:
>> 
>> 1. understand what it means to be a mentor [2].
>> 
>> 2. record your project ideas.
>> 
>> Just create issues in JIRA, label them with gsoc2018, and they will show up 
>> at [3]. Please be as
>> specific as possible when describing your idea. Include the programming 
>> language, the tools and
>> skills required, but try not to scare potential students away. They are 
>> supposed to learn what's
>> required before the program starts.
>> 
>> Use labels, e.g. for the programming language (java, c, c++, erlang, python, 
>> brainfuck, ...) or
>> technology area (cloud, xml, web, foo, bar, ...) and record them at [5].
>> 
>> Please use the COMDEV JIRA project for recording your ideas if your project 
>> doesn't use JIRA (e.g.
>> httpd, ooo). Contact d...@community.apache.org if you need assistance.
>> 
>> [4] contains some additional information (will be updated for 2017 shortly).
>> 
>> 3. subscribe to ment...@community.apache.org; restricted to potential 
>> mentors, meant to be used as a
>> private list - general discussions on the public d...@community.apache.org 
>> list as much as possible
>> please). Use a recognized address when subscribing (@apache.org or one of 
>> your alias addresses on
>> record).
>> 
>> Note that the ASF isn't accepted as a participating organization yet, 
>> nevertheless you *have to*
>> start recording your ideas now or we will not get accepted.
>> 
>> Over the years we were able to complete hundreds of projects successfully. 
>> Some of our prior
>> students are active contributors now! Let's make this year a success again!
>> 
>> Cheers,
>> 
>> Uli
>> 
>> P.S.: Except for the private parts (label spreadsheet mostly), this email is 
>> free to be shared
>> publicly if you want to.
>> 
>> [1] https://summerofcode.withgoogle.com/
>> [2] http://community.apache.org/guide-to-being-a-mentor.html
>> [3] http://s.apache.org/gsoc2018ideas
>> [4] http://community.apache.org/gsoc.html
>> 
> 
> -
> 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: [incubator/openwhisk] openwhisk-incubator-rc1/

[Carlos Santana]

I think is Vincent testing some automation scripts for the upcoming release
process

It was uploaded to dev/ but them cp/move to dist/

You can see here:
https://dist.apache.org/repos/dist/release/incubator/openwhisk/openwhisk-incubator-rc1/

Vincent if your done with you dev/testing please delete the directory from
dist


-- Carlos


On Fri, Feb 9, 2018 at 3:46 PM John D. Ament  wrote:

> Henk,
>
> I believe that these files are on /dist/dev/incubator.  Since that is the
> staging area of releases, and part of our release checks include
> verifications of signatures, shas, etc, you can exclude that area from your
> scans.
>
> John
>
> On Fri, Feb 9, 2018 at 3:23 PM Henk P. Penning  wrote:
>
> > Hi,
> >
> >today two artifacts were released into
> >
> >  dist/incubator/openwhisk/openwhisk-incubator-rc1/
> >
> >... without any checksum or signature files.
> >
> >For details see :
> >
> >  https://checker.apache.org/projs/incubator.html
> >
> >Please fix this soon.
> >
> >Regards,
> >
> >Henk Penning -- apache.org infrastructure ; dist & mirrors
> >
> >    _
> > Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> > Faculty of Science, Utrecht UniversityT +31 30 253 4106
> <+31%2030%20253%204106>
> > <+31%2030%20253%204106> / \_/ \
> > Leuvenlaan 4, 3584CE Utrecht, NL
> > <
> https://maps.google.com/?q=Leuvenlaan+4,+3584CE+Utrecht,+NL=gmail=g
> >
> > F +31 30 253 4553 <+31%2030%20253%204553>
> <+31%2030%20253%204553> \_/ \_/
> > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Updating PPMC rosters via whimsy

[Carlos Santana]

+100 to the following simplification:
For that reason, I'd like to make a simplifying assumption: that all mentors 
are PPMC members, and all PPMC members are committers.

- Carlos Santana
@csantanapr

> On May 26, 2017, at 6:10 PM, Sam Ruby <ru...@intertwingly.net> wrote:
> 
> For that reason, I'd like to make a simplifying assumption: that all mentors 
> are PPMC members, and all PPMC members are committers.

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

Re: Slack

[Carlos Santana]

I use Slack everyday internally for my work. 
I like Slack and the fact that I can use one tool for open source and internal 
company things. 

Apache Cordova (1400 members)and Apache Incubating OpenWhisk (175 members) both 
use Slack there is no limit on number of users and there is an open invite from 
the website from both projects. 

PS: I also use Slack for Ionic open source project with 3000 members also free 
tier. 

- Carlos Santana
@csantanapr

> On Mar 27, 2017, at 3:08 PM, Wade Chandler <wadechand...@apache.org> wrote:
> 
> I have used Gitter; not a good product honestly; not really comparable. IRC
> has limitations in the editing and group experience. The others require
> keeping up infrastructure. Slack just works, and works well for what it
> does. Some of us in the NB community discussed these points while setting
> it up and choosing. Too, they have been letting communities use it for free
> a long time. We use Atlassian products too, but don't get me going on
> hipchat differences; one of which is the sed like comment editing oddness.
> 
> Thanks
> 
> Wade
> 
> On Mar 27, 2017 12:57 PM, "Phillip Rhodes" <motley.crue@gmail.com>
> wrote:
> 
>> I don't understand the desire to use a closed-source, proprietary,
>> locked-down walled-garden application like Slack to begin with.   Why
>> not use one of the several open-source look-a-like versions that are
>> available?  Or use Gitter, which is about to go Open Source[1].
>> 
>> [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
>> software-chat-startup-gitter-will-open-source-the-code/
>> 
>> 
>> Phil
>> This message optimized for indexing by NSA PRISM
>> 
>> 
>> On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <wadechand...@apache.org>
>> wrote:
>>> The 90 member thing is really odd to me. I think you should write Slack
>> help to ask for details about your issue. The agreement does mention
>> invites where people don’t accept, and too many of those, could reduce your
>> ability to add more members, but this has been really rare in my
>> experience, and we have way more for NetBeans, and other than perhaps 10
>> people, our over 300+ members were self invited using
>> https://netbeans.signup.team/ <https://netbeans.signup.team/> Too, before
>> I set all this up, one of the questions I specifically asked Slack was
>> related to limitations, members, etc as it was a worry for us, and they
>> said there is no real limit on the number of members, but did mention the
>> message limits on logging etc, and directed us to setup a log bot while
>> taking our request for some other OSS subscription models.
>>> 
>>> Hope it helps,
>>> 
>>> Wade
>>> 
>>> 
>>> 
>>>> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net>
>> wrote:
>>>> 
>>>> Yes, but they will be member anyway, so it won't change the limit we
>> have today (90), right ?
>>>> 
>>>> Regards
>>>> JB
>>>> 
>>>>> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
>>>>> Hi JB,
>>>>> 
>>>>> A common practice/hack is to create a small web app that allows people
>> to
>>>>> send themselves invitations using the Slack API.
>>>>> For example:
>>>>> http://www.skill-space.com/blog/2015/11/16/create-an-
>> auto-invite-channel-using-slack-heroku1
>>>>> 
>>>>> Cheers,
>>>>> Yaniv
>>>>> 
>>>>> 
>>>>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
>>>>> wrote:
>>>>> 
>>>>>> Hi Wade,
>>>>>> 
>>>>>> You are right: invite people on Slack means adding them as member.
>>>>>> 
>>>>>> However, how can we accept Slack participants without inviting them ?
>> Is it
>>>>>> possible ?
>>>>>> 
>>>>>> Thanks !
>>>>>> Regards
>>>>>> JB
>>>>>> 
>>>>>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
>>>>>>> My understanding is there isn’t a max limit on Slack for users for
>> free,
>>>>>> and I have confirmed this with Slack there is not supposed to be a
>>>>>> limitation on numbers of members. NetBeans for instance has 320
>> members.
>>>>>> Did someone tell you this or did you run into some issue? If so, you
>> might

Re: ASF on Facebook!

[Carlos Santana]

I didn't know, this is very good thanks for sharing Raphael

- Carlos Santana
OpenWhisk
@csantanapr

> On Mar 17, 2017, at 2:43 AM, Raphael Bircher <rbircherapa...@gmail.com> wrote:
> 
> Hi at all
> 
> Some people maybe already notice it. The Apache Software Foundation is now on 
> Facebook. Tha page can be found under 
> https://www.facebook.com/ApacheSoftwareFoundation/ .
> 
> So you are invited to give us a like. If your project has a Facebook page 
> too, please contact me, so the ASF site can like you too.
> 
> The Admins for the FB Page are Rich and I.
> 
> Regards, Raphael
> 
> -- 
> My introduction https://youtu.be/Ln4vly5sxYU
> 
> -
> 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: [jira] [Created] (INCUBATOR-171) Submission: Anonymous-21

[Carlos Santana]

Thank Hedhman for letting me know, I recently join the list sonI was not sure. 

Sounds good with me then. 

- Carlos Santana
@csantanapr

> On Feb 5, 2017, at 9:33 PM, Niclas Hedhman <nic...@hedhman.org> wrote:
> 
> I think it was said to be ok, as the total number of issues in Incubator
> project itself is quite small. The current "flood" related to a new logo is
> not "normal".
> 
> On Sun, Feb 5, 2017 at 10:22 PM, Carlos Santana <csantan...@gmail.com>
> wrote:
> 
>> Is this normal to get all this issues notifications from JIRA to the
>> general@ list instead of a issues@ mailing list?
>> 
>> Makes it hard to keep up with the general@ list.
>> 
>> Just curious to know and providing feedback
>> 
>> - Carlos Santana
>> @csantanapr
>> 
>>> On Feb 5, 2017, at 9:19 AM, Sally Khudairi (JIRA) <j...@apache.org>
>> wrote:
>>> 
>>> Sally Khudairi created INCUBATOR-171:
>>> 
>>> 
>>>Summary: Submission: Anonymous-21
>>>Key: INCUBATOR-171
>>>URL: https://issues.apache.org/jira/browse/INCUBATOR-171
>>>Project: Incubator
>>> Issue Type: Task
>>> Components: LogoSubmission
>>>   Reporter: Sally Khudairi
>>>Attachments: Anonymous-21.png
>>> 
>>> Submission for Anonymous-21
>>> 
>>> 
>>> 
>>> --
>>> This message was sent by Atlassian JIRA
>>> (v6.3.15#6346)
>>> 
>>> -
>>> 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
>> 
>> 
> 
> 
> -- 
> Niclas Hedhman, Software Developer
> http://polygene.apache.org <http://zest.apache.org> - New Energy for Java

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

Re: [jira] [Created] (INCUBATOR-171) Submission: Anonymous-21

[Carlos Santana]

Is this normal to get all this issues notifications from JIRA to the general@ 
list instead of a issues@ mailing list?

Makes it hard to keep up with the general@ list. 

Just curious to know and providing feedback

- Carlos Santana
@csantanapr

> On Feb 5, 2017, at 9:19 AM, Sally Khudairi (JIRA) <j...@apache.org> wrote:
> 
> Sally Khudairi created INCUBATOR-171:
> 
> 
> Summary: Submission: Anonymous-21
> Key: INCUBATOR-171
> URL: https://issues.apache.org/jira/browse/INCUBATOR-171
> Project: Incubator
>  Issue Type: Task
>  Components: LogoSubmission
>Reporter: Sally Khudairi
> Attachments: Anonymous-21.png
> 
> Submission for Anonymous-21
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)
> 
> -
> 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: Write access to January report page

[Carlos Santana]

Thanks Marvin

On Tue, Jan 10, 2017 at 12:14 AM Marvin Humphrey <mar...@rectangular.com>
wrote:

> On Mon, Jan 9, 2017 at 11:34 AM, Carlos Santana <csantan...@gmail.com>
> wrote:
> > Hi my I just created a userid CarlosSantana on the wiki
> > Can I get write access?
>
> Done.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Write access to January report page

[Carlos Santana]

Hi my I just created a userid CarlosSantana on the wiki
Can I get write access?