Re: KEYS and keys

[sebb]

On 4 September 2013 02:31, Tim Williams  wrote:
> I notice that Chris just pointed[1] spark to the nifty keys
> listing[1].  Our docs still imply manual maintenance of the typical
> KEYS file[2].  Honestly, I didn't even know the ldap-driven one was
> around.  I assume its fair for projects to just point to the
> p.a.o/keys/groups/${project}.asc file nowadays vs. copying that over
> periodically to KEYS?

The KEYS file has historically been manually maintained.
As new keys are used for signing releases, they are added to the file.
However entries should not be deleted if they have ever been used to
sign a release, otherwise it may not be possible to check the sigs of
archived artifacts.

LDAP does not have all historic keys, or even all historic RMs.

So replacing the KEYS file with a copy from LDAP may lose keys needed
for validating archived files.

Directing users to the p.a.o/keys/groups/${project}.asc files should
work for current releases.
But even that has an problem - if the RM leaves a project whilst the
release is still current, the project.asc file will no longer contain
the RM's key

The problem is even worse for older releases.
People may create new keys and drop old ones which have been used for signing.
People leave a project or the ASF and the LDAP entry is changed.

I don't think the LDAP keys are really suitable for use as a KEYS file
at present.

> Thanks,
> --tim
>
>
> [1] - http://people.apache.org/keys/group/spark.asc
> [2] - 
> http://incubator.apache.org/guides/releasemanagement.html#distribution-signing
>
> -
> 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: binary release artifacts

[sebb]

On 15 September 2013 14:16, Tim Williams  wrote:
> On Sun, Sep 15, 2013 at 5:19 AM, ant elder  wrote:
>> Tim, one of the things we're trying to teach podlings is how to handle
>> disputes and resolve problems in a happy respectful manner. You've out
>> of the blue come on to their dev list without introducing yourself
>> demanding that something that happened nearly two years ago be undone.
>
> My mail on their list wasn't intended to be 'demanding' or rude - my
> apologies if it came across that way.  I honestly went in thinking it
> was a mistake - a simple misunderstanding.
>
>> Its a testament to Chukwa that they've engaged in discussing the
>> matter with you promptly and politely, never the less in under 48
>> hours of starting the discussion you've escalated this to general@
>> with a fairly negative email.
>
> I agree, Eric was prompt and polite.  I "escalated" this for two reasons:
>
> 1) It became apparent that it wasn't a misunderstanding - it's a
> question of policy and it doesn't seem fair to hash that out on their
> dev list.  It wasn't so much "escalation" as taking policy discussions
> to the right audience - if there were a mentor@ list, I would have
> aimed there.
>
> 2) This PMC has a release artifact published that was never voted
> upon.  That was news to me and, I felt, worthy of sunlight -
> especially after the [prompt/polite] defensive reaction received.
>
> Sorry for the negativity, it was borne of frustration.  It's
> frustrating to ask podlings to work hard dotting I's and crossing T's
> only to look around and see other podling's  lackadaisical approach.
>
>> Lets take your LICENSE/NOTICE file issue, you initially said the
>> binary artifact didn't have any, it was then pointed out that in fact
>> it did have them just not where you were looking, you then asserted
>> that is not acceptable and they must only be right at the top
>> directory, it was then pointed out other types of binary distributions
>> like jars also don't have them at the top either, but you have ignored
>> that and instead come here to general@.
>
> I guess I viewed that as a frustrating rationalization.  Their distro
> is a standard tarball - where those files are well expected to be in
> the standard place by both policy and social norm - not some other
> artifact type where an difference is obvious.  Anyway, moving it here
> was less about that and more about the fact that they released an
> artifact without voting.
>
> Though, since you bring it up I'd appreciate that if there's going to
> be no accountability for podlings to locate those source files in the
> right place[1], then yeah, I think we should change the policy to
> state that anywhere in the artifact is acceptable.

I think the only proper places are at the top level for tarballs with
the option of the META-INF directory for jars.

> --tim
>
> [1] - http://apache.org/legal/src-headers.html#notice
>
>> I have no doubt that Chukwa will be happy to help resolve this in
>> whatever way is necessary to satisfy all the ASF policy's, but we
>> don't need a big general@ flame thread to do that.
>>
>>...ant
>>
>> On Sun, Sep 15, 2013 at 3:46 AM, Tim Williams  wrote:
>>> Moving this[1] to general@
>>>
>>> On Sat, Sep 14, 2013 at 2:55 AM, ant elder  wrote:
 On Saturday, September 14, 2013, Tim Williams  wrote:
> Hi Eric,
> I've included references inline for your convenience.  I'll once again
> [strongly] suggest you guys remove that artifact.
>
> Thanks,
> --tim
>
> On Fri, Sep 13, 2013 at 6:53 PM, Eric Yang  wrote:
>> Hi Tim,
>>
>> There is LICENSE.txt and NOTICES.txt in both source and binary package.
  In
>> the binary package, the files are located in $PREFIX/share/doc/chukwa to
>> match what standard Linux file system layout.  We voted for source
 release
>> and there is no Apache restriction that a source release, can not
 procedure
>> a binary package.
>
> "Votes on whether a package is ready to be released use majority
> approval -- i.e., at least three PMC members must vote affirmatively
> for release, and there must be more positive than negative votes."
>
> Each vote is on signed, hashed artifacts, so yes, if you say it's a
> "source vote" then no binary should accompany it.
>
> http://www.apache.org/dev/release.html#approving-a-release
>
>> There is also no restriction that binary release must
>> have LICENSE.txt and NOTICES.txt in the top level directory.
>
> How do you reach that understanding from the sentence below?
>
> "Every Apache distribution should include a NOTICE file in the top
> directory, along with the standard LICENSE file."
>

 Plenty of other release artifacts from other projects have these files
 somewhere other than the top directory, eg most jar releases have them in
 the meta-inf directory.

 There is also ambiguity around convenience binary rel

Re: [DISCUSS] Release of Apache Allura (incubating) v1.0.0

[sebb]

On 16 September 2013 14:17, Dave Brondsema  wrote:
> IPMC members, hello again.  We are still waiting for your votes to be
> cast for Allura's first release: see vote thread Aug portion [1] and
> Sept portion [2]
>
> If there is anything the Allura PPMC can provide or do, to help, please
> let us know.  I think we're just waiting on you all, though.

I see there is a KEYS file is stored at

http://www.apache.org/dist/incubator/allura/KEYS

which is the usual location; however it helps to include it in vote e-mails.

> I hope some of the energy seen recently in discussing the Monitoring
> proposal and welcoming Storm can also be applied to help us through our
> incubation.
>
> Thanks,
> Dave
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-general/201308.mbox/%3CCAGN0FaTfgodR_vkuKTvO6EySfRKuZQJmOm%3Dm4K0mGQhnefD2ng%40mail.gmail.com%3E
> [2]
> http://mail-archives.apache.org/mod_mbox/incubator-general/201309.mbox/%3C5227383D.3070401%40brondsema.net%3E
>
> On 09/11/2013 03:14 AM, Ross Gardler wrote:
>> On 10 September 2013 10:31, Dave Brondsema  wrote:
>>
>>> On 9/9/13 12:22 PM, Marvin Humphrey wrote:
 On Mon, Sep 9, 2013 at 6:47 AM, Rich Bowen  wrote:
> Hmm. Did we do something wrong with our call for vote?
>>>
>>
>> ...
>>
>>
> Can anyone suggest any reason why we've gotten ZERO response to this
>>> message
> or to Dave's followup?

 Allura has four Mentors.  You've voted, but where are the others?

>>>
>>> I wonder this as well :(
>>>
>>>
>> This one has been relocating his family from the UK to the US and is a long
>> way behind on non-work related activities.
>>
>> The good news is that I'm now in a permanent home for the next 10 months
>> and my furniture is clearing customs as we speak. My family and I will have
>> chairs to sit on soon :-D
>>
>> Apologies for not being present for your first release vote.
>>
>> Ross
>>
>
>
> --
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
><><
>

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

Re: [DISCUSS] Release of Apache Allura (incubating) v1.0.0

[sebb]

Sorry, again forgot:

It's useful to have a link to the RAT report (or equivalent) showing
that files have the appropriate license headers.

On 16 September 2013 23:33, sebb  wrote:
> Forgot to say:
>
> AFAIK, Git tags are not immutable, so the vote e-mail should contain
> the hash for the tag.
>
> On 16 September 2013 23:30, sebb  wrote:
>> On 16 September 2013 14:17, Dave Brondsema  wrote:
>>> IPMC members, hello again.  We are still waiting for your votes to be
>>> cast for Allura's first release: see vote thread Aug portion [1] and
>>> Sept portion [2]
>>>
>>> If there is anything the Allura PPMC can provide or do, to help, please
>>> let us know.  I think we're just waiting on you all, though.
>>
>> I see there is a KEYS file is stored at
>>
>> http://www.apache.org/dist/incubator/allura/KEYS
>>
>> which is the usual location; however it helps to include it in vote e-mails.
>>
>>> I hope some of the energy seen recently in discussing the Monitoring
>>> proposal and welcoming Storm can also be applied to help us through our
>>> incubation.
>>>
>>> Thanks,
>>> Dave
>>>
>>> [1]
>>> http://mail-archives.apache.org/mod_mbox/incubator-general/201308.mbox/%3CCAGN0FaTfgodR_vkuKTvO6EySfRKuZQJmOm%3Dm4K0mGQhnefD2ng%40mail.gmail.com%3E
>>> [2]
>>> http://mail-archives.apache.org/mod_mbox/incubator-general/201309.mbox/%3C5227383D.3070401%40brondsema.net%3E
>>>
>>> On 09/11/2013 03:14 AM, Ross Gardler wrote:
>>>> On 10 September 2013 10:31, Dave Brondsema  wrote:
>>>>
>>>>> On 9/9/13 12:22 PM, Marvin Humphrey wrote:
>>>>>> On Mon, Sep 9, 2013 at 6:47 AM, Rich Bowen  wrote:
>>>>>>> Hmm. Did we do something wrong with our call for vote?
>>>>>
>>>>
>>>> ...
>>>>
>>>>
>>>>>>> Can anyone suggest any reason why we've gotten ZERO response to this
>>>>> message
>>>>>>> or to Dave's followup?
>>>>>>
>>>>>> Allura has four Mentors.  You've voted, but where are the others?
>>>>>>
>>>>>
>>>>> I wonder this as well :(
>>>>>
>>>>>
>>>> This one has been relocating his family from the UK to the US and is a long
>>>> way behind on non-work related activities.
>>>>
>>>> The good news is that I'm now in a permanent home for the next 10 months
>>>> and my furniture is clearing customs as we speak. My family and I will have
>>>> chairs to sit on soon :-D
>>>>
>>>> Apologies for not being present for your first release vote.
>>>>
>>>> Ross
>>>>
>>>
>>>
>>> --
>>> Dave Brondsema : d...@brondsema.net
>>> http://www.brondsema.net : personal
>>> http://www.splike.com : programming
>>><><
>>>

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

Re: [VOTE] Release of Apache Allura (incubating) v1.0.0

[sebb]

On 28 August 2013 23:04, Cory Johns  wrote:
> Hello,
>
> This is a call for a vote on Apache Allura 1.0.0 incubating. This is our
> first release.
>
> A vote was held on developer mailing list and it passed with 9 +1's, and 0
> -1's or +0's (vote thread [1], discussion thread [2] which some of the
> votes were cast on, due to some confusion, and result thread [3]), and now
> requires  a vote on general@incubator.apache.org.
>
> Source tar ball and signature are available at:
> https://dist.apache.org/repos/dist/dev/incubator/allura/

The NOTICE file has leading spaces on every line; these should be
removed for a future release.

The parent directory in the archive is called "allura"; generally
projects include the version information, e.g.
"allura-1.0.0-incubating".
That makes it easier to distinguish unpacked archives. Not a release blocker.

There are several 3rd party source items mentioned in the top level NOTICE fie.
However I could not find any corresponding LICENSE files.
Every file needs to be covered by a LICENSE file; not all licenses
require a mention in the NOTICE file, so there is a mismatch here.

I now see that there are multiple copies of the NOTICE and LICENSE
files with differing content.
This is very confusing for the end user (and the reviewer!)

There should be a single NOTICE and LICENSE file in the parent
directory (allura/) which covers all the contents (and nothing else).

I think that is a release blocker.

In fact it looks like the file allura/Allura/LICENSE is intended to be
the file for the entire source release.
It should be in the parent directory.

Also, it looks to me as though some of the NOTICE content is not
necessary; it's vital that only required content is included.
See for example:
http://www.apache.org/dev/licensing-howto.html#mod-notice

I suspect most if not all of the attrributions in the NOTICE file are
not required, and therefore must be removed.

There seem to be some files without the appropriate license header, for example:

allura/AlluraTest/jslint/Makefile
allura/Allura/allura/controllers/controller.template
allura/Allura/allura/public/nf/css/blueprint/src/forms.css
allura/Allura/allura/public/nf/css/blueprint/src/grid.css
allura/Allura/allura/public/nf/css/blueprint/src/ie.css
allura/Allura/allura/public/nf/css/blueprint/src/print.css
allura/Allura/allura/public/nf/css/blueprint/src/reset.css
allura/Allura/allura/public/nf/css/blueprint/src/typography.css

There are other source files without any apparent license header.

> Checksums:
> MD5: 31b9ed4af10b28f4219c00af8592d61c  allura-incubating-1.0.0.tar.gz
> SHA1: 0ca70edeaa497261d7f6cfbedde6cab7a20ec072
> allura-incubating-1.0.0.tar.gz
> SHA512: 
> 38a921da57c3e53085869aa4ea9690e11247161d6351e8235907d28f1497a597f8df7fb41326cfa1c96700a8ed7cf8b79d60520784ee465358d3047680e5
> allura-incubating-1.0.0.tar.gz
>
> The release has been signed with keys (9BB3CE70 and 449C78B1):
> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x56F0526F9BB3CE70
> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xDB6E071B449C78B1
>
> Source corresponding to this release can be found at
> https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/tags/asf_release_1.0.0
>
> Vote will be open for at least 1 week (4/Sep/2013 12PM IST) to allow for it
> being our first release.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks & Regards
> Cory Johns

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

Re: [DISCUSS] Release of Apache Allura (incubating) v1.0.0

[sebb]

Forgot to say:

AFAIK, Git tags are not immutable, so the vote e-mail should contain
the hash for the tag.

On 16 September 2013 23:30, sebb  wrote:
> On 16 September 2013 14:17, Dave Brondsema  wrote:
>> IPMC members, hello again.  We are still waiting for your votes to be
>> cast for Allura's first release: see vote thread Aug portion [1] and
>> Sept portion [2]
>>
>> If there is anything the Allura PPMC can provide or do, to help, please
>> let us know.  I think we're just waiting on you all, though.
>
> I see there is a KEYS file is stored at
>
> http://www.apache.org/dist/incubator/allura/KEYS
>
> which is the usual location; however it helps to include it in vote e-mails.
>
>> I hope some of the energy seen recently in discussing the Monitoring
>> proposal and welcoming Storm can also be applied to help us through our
>> incubation.
>>
>> Thanks,
>> Dave
>>
>> [1]
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201308.mbox/%3CCAGN0FaTfgodR_vkuKTvO6EySfRKuZQJmOm%3Dm4K0mGQhnefD2ng%40mail.gmail.com%3E
>> [2]
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201309.mbox/%3C5227383D.3070401%40brondsema.net%3E
>>
>> On 09/11/2013 03:14 AM, Ross Gardler wrote:
>>> On 10 September 2013 10:31, Dave Brondsema  wrote:
>>>
>>>> On 9/9/13 12:22 PM, Marvin Humphrey wrote:
>>>>> On Mon, Sep 9, 2013 at 6:47 AM, Rich Bowen  wrote:
>>>>>> Hmm. Did we do something wrong with our call for vote?
>>>>
>>>
>>> ...
>>>
>>>
>>>>>> Can anyone suggest any reason why we've gotten ZERO response to this
>>>> message
>>>>>> or to Dave's followup?
>>>>>
>>>>> Allura has four Mentors.  You've voted, but where are the others?
>>>>>
>>>>
>>>> I wonder this as well :(
>>>>
>>>>
>>> This one has been relocating his family from the UK to the US and is a long
>>> way behind on non-work related activities.
>>>
>>> The good news is that I'm now in a permanent home for the next 10 months
>>> and my furniture is clearing customs as we speak. My family and I will have
>>> chairs to sit on soon :-D
>>>
>>> Apologies for not being present for your first release vote.
>>>
>>> Ross
>>>
>>
>>
>> --
>> Dave Brondsema : d...@brondsema.net
>> http://www.brondsema.net : personal
>> http://www.splike.com : programming
>><><
>>

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

Re: [VOTE] Release Apache Spark 0.8.0-incubating (RC6)

[sebb]

On 20 September 2013 21:56, Patrick Wendell  wrote:
> Please vote on releasing the following candidate as Apache Spark
> (incubating) version 0.8.0. This will be the first incubator release for
> Spark in Apache.
>
> The tag to be voted on is v0.8.0-incubating (commit 3b85a85):
> https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=3b85a8558da2c87873c85f227a189e45bf16b65d
>
> The release files, including signatures, digests, etc can be found at:
> http://people.apache.org/~pwendell/spark-0.8.0-incubating-rc6/files/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/pwendell.asc

The KEYS file should normally be under

http://www.apache.org/dist/incubator/spark/

as this is where the release artifacts will be found if the vote succeeds.

Also that location is automatically archived,

It's important that the KEYS file contains all keys used to sign any
releases, so keys should only be added to it, never removed (except
possibly if the key has been compromised).

So please add your key to the KEYS file at that location (creating it
if necessary).

> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-059/
>
> The documentation corresponding to this release can be found at:
> http://people.apache.org/~pwendell/spark-0.8.0-incubating-rc6/docs/
>
> A vote on this release has passed within the Spark PPMC [1] including
> +1 votes from our IPMC mentors (Chris Mattman and Henry Saputra).
>
> Please vote on releasing this package as Apache Spark 0.8.0-incubating!
>
> The vote is open until Monday, September 23rd at 21:00 UTC and passes if
> a majority of at least 3 +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Spark 0.8.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Spark, please see
> http://spark.incubator.apache.org/
>
>
> [1] 
> http://mail-archives.apache.org/mod_mbox/incubator-spark-dev/201309.mbox/%3CCABPQxsvS14wfiABj32b_%2BgtLafmDog%3DcbWjn7v4FoqG5g-a7mQ%40mail.gmail.com%3E
>
> - Patrick
>
> -
> 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: binary release artifacts

[sebb]

On 24 September 2013 10:05, ant elder  wrote:
> I closed LEGAL-178 with the resolution "Not A Problem", which is quite
> different to a resolution of "Fixed" or "Resolved" or "Answered".
>
> From my investigation, things like the text of the AL and various posts in
> the mailing lists over the years answered the question to my satisfaction.
> I doubt everyone agrees yet but the answers for me are:
> - there is no need to vote on the convenience binary artifacts

They still have to have NOTICE and LICENSE files, the contents of
which must agree with the bits actually included.
And Incubator releases must have the DISCLAIMER.

> - in fact voting on them is a bit pointless as you can't easily verify the
> contents anyway, and the ASF only does source releases.

It's still possible to vote on the NOTICE/LICENSE files.

Also, if the binary clearly contains a prohibited dependency it should
be possible for reviewers to comment on this.

> - its ok to have unvoted on convenience binaries in the ASF distribution
> areas

I don't think that's true if my assumptions regarding N&L files above
are correct.

> - there is no requirement to have LICENSE/NOTICE files in the root
> directory of a convenience binary

But they should be there (or in META-INF).

> However i think it would take a fair bit of work to build enough consensus
> around any documentation update. So just closing LEGAL-178 as Not A Problem
> seemed much easier now that it seems like no one is insisting any historic
> artifacts be removed.
>
> Happy to continue discussing this as it does seem an interesting topic, but
> if we do could it be in a new thread not so tied to Chukwa.
>
>...ant
>
>
> On Mon, Sep 23, 2013 at 11:42 PM, Luciano Resende wrote:
>
>> On Mon, Sep 23, 2013 at 2:23 PM, Marvin Humphrey > >wrote:
>>
>> > On Mon, Sep 23, 2013 at 1:45 PM, Luciano Resende 
>> > wrote:
>> >
>> > > Thanks for the summary Marvin,  how about we take the chance to update
>> > our
>> > > policy/documentation to clarify the social norm regarding placement of
>> > > LICENSE/NOTICE in the top level of a distribution but also clarify
>> that,
>> > > any artifact being release by an Apache Project should be reviewed and
>> > > voted, as there were some suggestions on this thread that this was not
>> > the
>> > > case. If we can't clarify that on ASF level, at least we can clarify
>> that
>> > > on the IPMC level.
>> >
>> > I understand the motivation, but I'm actually in favor of keeping the
>> > status
>> > quo.
>> >
>> > As Joe Schaefer pointed out, the VOTE only applies to the canonical
>> source
>> > release.  Binary artifacts cannot be official releases of the ASF, and
>> the
>> > IPMC cannot override that policy.
>> >
>> >
>> Is there any written policy that states that ? I have never heard that the
>> ASF can't have binary artifacts as official releases ?
>>
>> Also, from Joe's message, I think he was mentioning what is done in the
>> context of HTTPD, not necessarily stating a policy or the social norm here
>> at Apache.
>>
>>
>> > Additionally, we still have a lot of work to do to squash licensing
>> > documentation bugs in our canonical source releases.  When we can't even
>> > get
>> > our official releases right, I don't think it makes sense to dilute our
>> > already thin quality control resources.
>> >
>> > Marvin Humphrey
>> >
>> >
>> The issue I see, particularly when evaluating maven based java source
>> releases (no binaries at all), is that the a lot of the dependencies for a
>> project might be transient making much harder and much more work to
>> evaluate a source only release. While reviewing a binary release, you have
>> listed all the binary dependencies and all it's associated license, making
>> the review process much simpler, allowing the reviewer to concentrate on
>> making sure the dependencies are allowed, no specific jars got unaccounted
>> on the license/notice, etc...
>>
>>
>> [1]
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201309.mbox/%3CBF8E0313-15C2-4375-8470-FE0A1DA917C5%40yahoo.com%3E
>>
>>
>>
>> --
>> Luciano Resende
>> http://people.apache.org/~lresende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>>

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

Re: KEYS files within source archives

[sebb]

On 23 September 2013 21:57, Marvin Humphrey  wrote:
>> On Wed, Sep 18, 2013 at 8:25 PM, Dave Brondsema  wrote:
>>
>>> Do you have a KEYS file posted somewhere besides within the release?
>
> Thanks for a good spot and thoughtful observation, Dave.  This is worth
> discussing.
>
> MHO: supplying a KEYS file within the source archive is worthless at best.

+1

> On Wed, Sep 18, 2013 at 9:50 PM, Ted Dunning  wrote:
>> It is in version control as per custom.  Drill uses git so it might not be
>> quite as obvious if you are used to SVN.
>>
>> See, for instance,
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-drill.git;a=blob;f=KEYS;h=205469b84b8bda60fcb87486182d4fb7caf0485d;hb=HEAD
>
> There may be precedent but it seems to me that including a KEYS file within
> a source archive shouldn't be considered a best practice.  (For the record,
> so long as the KEYS file is available from somewhere else safe, I don't think
> the issue blocks Drill's release candidate.)

The canonical place for KEYS files is the distribution area.
This is automatically archived, so the KEYS file is available for use
with archives as well.

> Now that changes to our distribution area are captured via version control
> (dist.apache.org), is there any reason to maintain KEYS in the master branch
> any more?

+1

> There was talk a while back of transitioning to an LDAP-centric key scheme,
> but there are flaws with that approach: former RMs who leave the community
> suddenly causing the key needed for an old release to become unavailable, etc.

Indeed.

> Marvin Humphrey
>
> -
> 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 of Apache MRQL 0.9.0 incubating

[sebb]

On 24 September 2013 13:44, Leonidas Fegaras  wrote:
> Hello,
> This is a call for a vote on Apache MRQL 0.9.0 incubating. MRQL is a
> query processing and optimization system for large-scale, distributed
> data analysis, built on top of Apache Hadoop, Hama, and Spark.
> This is our first release. A vote was held on the MRQL developer
> mailing list and it passed with three +1 votes (plus one late vote),
> and zero -1 or 0 votes (see the vote thread [1] and result thread [2]),
> and now requires a vote on general@incubator.apache.org. The vote will
> be open for 72 hours (it will close on Friday 27/Sep/2013 at 1pm GMT)
> and passes if a majority of at least three +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache MRQL 0.9.0-incubating
> [ ] -1 Do not release this package because...
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachemrql-055/
> You are voting only for the source distribution.
> The source tar ball is available at:
> https://repository.apache.org/content/repositories/orgapachemrql-055/org/apache/mrql/mrql-src-dist/0.9.0-incubating/
> The release candidate consists of the following source distribution
> archives:
> - mrql-src-dist-0.9.0-incubating.[zip|tar.gz]
>   SHA1 of TGZ: 4b5c6c2df32881b77633303435cb0c99856105cd
>   SHA1 of ZIP: edae1009a5ef7a7613f4da4d2d46e1c9339cb70f
> You can compile the sources using 'mvn package'.
>
> In addition, the following supplementary binary distributions are provided
> for user convenience at:
> https://repository.apache.org/content/repositories/orgapachemrql-055/org/apache/mrql/mrql-bin-dist/0.9.0-incubating/
> The binary distribution archives are:
> - mrql-bin-dist-0.9.0-incubating.[zip|tar.gz]
>   SHA1 of TGZ: 27a1c569a0da333a22da260b07356673b81f539c
>   SHA1 of ZIP: 6afdeb2640e6b3a31a97e44a0b5e585e6ade62ac
>
> The release candidate has been signed through the key 798764F1 in:
> http://www.apache.org/dist/incubator/mrql/KEYS
> http://keyserver.kjsl.org:11371/pks/lookup?op=get&search=0xB7737C07798764F1
>
> The release candidate is based on the sources tagged with
> MRQL-0.9.0-incubating-RC1:
> https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=tag;h=a7f69742a21393f98d951a8bc5822ae218ffda60

That does not seem to be the correct tag, because the pom versions
include -SNAPSHOT in them.

> RAT output:
> http://people.apache.org/~fegaras/dist/MRQL-0.9.0-incubating-RC1/rat.txt
> Suitable name search:
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-32

The vote e-mail includes the hashes for tags and archives which is
excellent, as it ties the vote to the items being voted on.
So it's unfortunate that the tag does not agree with the source archive.

Sigs and hashes seem OK to me.

The  and  entries in the POMs should all start
Apache MRQL so it is clear that they are part of the Apache MRQL
product.
This is necessary for clear branding. Also the  affects the
generated NOTICE files under META-INF.
These are currently invalid.

It's a bit confusing to have artifact id of "gen" when all the other
ids include MRQL or mrql.

> Note: The NOTICE includes the 3rd party copyright notices for JLine
> and CUP because the JLine and the CUP runtime libraries are bundled in
> the jar files in the MRQL binary distribution (files lib/*.jar).
> This was required because the MRQL jar files must contain all the
> dependencies in order to run on Hadoop and Hama.

It's OK to bundle 3rd party jars (assuming that the license allows us
to do so, so no GPL for example).
However, the NOTICE and LICENSE files must only refer to the enclosing entity.
Since the source archive does not contain CUP and JLine its N&L files
must not include references to them.
Likewise the top level N&L files in the Git repo should only refer to
files actually contained in the repo.

Also, the NOTICE file looks wrong even for the binary jar; at *most*
two or 3 lines are needed for each external inclusion.
See http://www.apache.org/dev/licensing-howto.html#mod-notice
The licences must either be appended to the LICENSE file or you can
store them in separate files which are linked from the main LICENSE
file.

Some of the POMs in the Nexus staging repo appear to have lost their AL headers.

> To learn more about Apache MRQL, please visit:
> http://wiki.apache.org/mrql/
> Thanks,
> Leonidas Fegaras
>
> [1] http://markmail.org/message/nhyjdxlmas5vlg5x
> [2] http://markmail.org/message/5zsmncpimbdgfyn7
>
>
> -
> 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 of Apache MRQL 0.9.0 incubating

[sebb]

On 26 September 2013 18:44, Leonidas Fegaras  wrote:
> Hi Sebastian,
> Thank you for checking our release.
> I think you clicked on the wrong tree link at our GIT repo.
> The source tree is:
> https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=tree;h=385ba2829bdf184886ac82b5db793f1264bbcf3c;hb=385ba2829bdf184886ac82b5db793f1264bbcf3c
> which corresponds exactly to the tag MRQL-0.9.0-incubating-RC1 as it is
> shown on our call for votes.

The URL I clicked on was as follows which was in the first message of
this vote e-mail thread:


The release candidate is based on the sources tagged with
MRQL-0.9.0-incubating-RC1:
https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=tag;h=a7f69742a21393f98d951a8bc5822ae218ffda60


I then clicked on "tree" and then "pom.xml / raw"

I agree that the URL you have just provided has a pom that looks OK.
But that URL was not in the original vote e-mail..

> These pom.xml files clearly have 0.9.0-incubating. So the link on our call
> was correct but you clicked on the wrong git tree on the GIT page (you got
> the latest tree).

No, see above - the original e-mail link was wrong.

> Also I am not sure about inserting 3rd party licenses on LICENSE. Spark did
> that but I think it was wrong. From what i've read, LICENSE should have only
> the Apache 2.0 license.

No, the LICENSE file should have ALL the relevant licenses, either
included or linked therefrom.

> Please look at LEGAL-177, where we discussed what to put in the MRQL NOTICE
> file.

I already commented on that very issue.

> Please let us know if you consider the rest of the problems you mentioned
> blocking for this release as is.

Yes, I do consider that the N&L issues are blocking.

The N&L files must relate to the included bits and nothing more.
The NOTICE file must include required notices and nothing more.

Does the MRQL source contain any 3rd party code?
If so, what, and where are the files?

It looks as though some of the MRQL jar files contain JLine and CUP runtime.
That seems wrong; Maven jar dependencies should be resolved using the
dependency mechanism. Also, if the jars can be used together, there
will be multiple copies of the classes, which is not good.

Also, combining the 3rd party libraries with the MRQL code means that
users cannot obtain just the binaries for MRQL itself; they will be
forced to build it themselves.

If there is a need to provide a bundled binary containing 3rd party
jars, that is normally done in the zip/tar.gz archives containing the
various components as individual jars.

> Thanks
> Leonidas Fegaras
>
>
> On Sep 26, 2013, at 11:45 AM, sebb wrote:
>
> On 24 September 2013 13:44, Leonidas Fegaras  wrote:
>
> Hello,
>
> This is a call for a vote on Apache MRQL 0.9.0 incubating. MRQL is a
>
> query processing and optimization system for large-scale, distributed
>
> data analysis, built on top of Apache Hadoop, Hama, and Spark.
>
> This is our first release. A vote was held on the MRQL developer
>
> mailing list and it passed with three +1 votes (plus one late vote),
>
> and zero -1 or 0 votes (see the vote thread [1] and result thread [2]),
>
> and now requires a vote on general@incubator.apache.org. The vote will
>
> be open for 72 hours (it will close on Friday 27/Sep/2013 at 1pm GMT)
>
> and passes if a majority of at least three +1 IPMC votes are cast.
>
>
> [ ] +1 Release this package as Apache MRQL 0.9.0-incubating
>
> [ ] -1 Do not release this package because...
>
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachemrql-055/
>
> You are voting only for the source distribution.
>
> The source tar ball is available at:
>
> https://repository.apache.org/content/repositories/orgapachemrql-055/org/apache/mrql/mrql-src-dist/0.9.0-incubating/
>
> The release candidate consists of the following source distribution
>
> archives:
>
> - mrql-src-dist-0.9.0-incubating.[zip|tar.gz]
>
>  SHA1 of TGZ: 4b5c6c2df32881b77633303435cb0c99856105cd
>
>  SHA1 of ZIP: edae1009a5ef7a7613f4da4d2d46e1c9339cb70f
>
> You can compile the sources using 'mvn package'.
>
>
> In addition, the following supplementary binary distributions are provided
>
> for user convenience at:
>
> https://repository.apache.org/content/repositories/orgapachemrql-055/org/apache/mrql/mrql-bin-dist/0.9.0-incubating/
>
> The binary distribution archives are:
>
> - mrql-bin-dist-0.9.0-incubating.[zip|tar.gz]
>
>  SHA1 of TGZ: 27a1c569a0da333a22da260b07356673b81f539c
>
>  SHA1 of ZIP: 6afdeb2640e6b3a31a97e44a0b5e585e6ade62ac
>
>
> The release candidate has been signed through the key 798764F1 in:
>
> http://www.apache.org/dist/

Re: [VOTE] Apache Kalumet 0.6-incubating release (3rd try)

[sebb]

On 1 October 2013 08:00, Jean-Baptiste Onofré  wrote:
> Hi all,
>
> Apache Kalumet 0.6-incubating release has been voted by the Kalumet podling
> PMC.
>
> I forward the release to the Incubator for "final" vote. Please find the
> RELEASE NOTES and staging repository in the original message.
>
> Thanks,
> Regards
> JB
>
>  Original Message 
> Subject: [VOTE] Apache Kalumet 0.6-incubating release (3rd try)
> Date: Thu, 05 Sep 2013 13:30:42 +0200
> From: Jean-Baptiste Onofré 
> Reply-To: kalumet-...@incubator.apache.org
> To: kalumet-...@incubator.apache.org
>
> Hi all,
>
> The first release of Kalumet (0.6-incubating) is available.
> Please take a look on the artifacts (especially the distribution
> archives), review the documentation and make a try.
>
> Release Notes:
> http://svn.apache.org/repos/asf/incubator/kalumet/tags/kalumet-0.6-incubating/RELEASE-NOTES
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekalumet-013/

Where is the KEYS file?
The URL should be included in all votes so reviewers can check the sigs.

The vote e-mail should also include the SCM co-ordinates (SVN
URL+revision or GIT URL+hash). This is so the source archive contents
can be checked against it.

Also, the Nexus URLs are temporary (and not unique), so the hashes of
the source archives should be included in the vote e-mail. Otherwise
there is not way to tie the vote e-mail to the artifacts that are
being voted on.

> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
> -
> 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 Marmotta 3.1.0-incubating

[sebb]

On 30 September 2013 11:17, Sebastian Schaffert  wrote:
> Dear all,
>
> After several months of work since the last incubating release
> (3.0.0-incubating) in April, we are now ready to release version
> 3.1.0-incubating. We fixed all the remaining issues that have been
> discussed in April (see thread [1]) plus many more technical issues. We
> have already held a vote that was open for more than 72 hours on the Apache
> Marmotta developer mailinglist [2]. The vote concluded [3] with 7 positive
> votes, of which 2 have been binding from IPMC members (Andy and Nandana)
> and the remaining 5 from the Apache Marmotta developers.
>
> I'd therefore like to ask the general incubator to check our release
> candidate. The release notes are available at the Jira Issue Tracker [4].
> The vote form is included at the bottom of this mail.
>
> Greetings,
>
> Sebastian
>
>
> [1] http://apache.markmail.org/message/5tieelmeevi2j6xb
> [2] http://apache.markmail.org/message/lk3hc3jutoaxp6dr
> [3] http://apache.markmail.org/message/fvytzho2pnhasw2c
> [4]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321&version=12324026
>
> ===
> A candidate for the Marmotta 3.1.0-incubating release is available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.1.0-incubating/
>
> The release candidate is based on the sources tagged with 3.1.0-incubating
> in:
>
> https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git

What is the hash of the tag please? Tags are not immutable, so should
be included in the vote e-mail for the record.

> The release candidate consists of the following source distribution
> archives:
> - apache-marmotta-3.1.0-
> incubating-src.[zip|tar.gz]
>   SHA1 of ZIP: 763c39dc9d7eb1c7d8fad83742b08f44b6fa5527
>   SHA1 of TGZ: 0f7f3395f22aeeaa4a402f1b08048c84899d9729
>
> In addition, the following supplementary binary distributions are provided:
> - apache-marmotta-3.1.0-incubating-installer.[zip|tar.gz]
>   SHA1 of ZIP: d7417a711a7f80eb29eb93ec75744a314fcf2edd
>   SHA1 of TGZ: 4606fe743f607215dd4f3f39d8506852f529b617
> - apache-marmotta-3.1.0-incubating-ldpath.[zip|tar.gz]
>   SHA1 of ZIP: 4f4db937e0064a4393039b6fb8277be166a971ab
>   SHA1 of TGZ: 5d63f972df2306afec96aa1a8931c4d0dabb2f75
> - apache-marmotta-3.1.0-incubating-webapp.[zip|tar.gz]
>   SHA1 of ZIP: e8e168a29e398cda9220a793958b825a906a3142
>   SHA1 of TGZ: 80d022d316e727b5f011069eec6dc9793b174838
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachemarmotta-092/
>
> Please vote on releasing this package as Apache Marmotta 3.1.0-incubating.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Marmotta PMC votes are cast.
>
> [ ] +1 Release this package as Apache Marmotta 3.1.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> ===
>
> Release Notes - Marmotta - Version 3.1-incubating
>
> ** Sub-task
> * [MARMOTTA-216] - Implement JOIN improvements
> * [MARMOTTA-217] - Implement FILTER improvements
> * [MARMOTTA-218] - Integrate in marmotta-sparql
>
>
> ** Bug
> * [MARMOTTA-28] - Implement tests for core that take into account
> triple store changes
> * [MARMOTTA-63] - Triplestore: garbage collector for nodes currently
> not working properly
> * [MARMOTTA-66] - Rework sesame-commons ResourceUtils
> * [MARMOTTA-143] - unable to import big files
> * [MARMOTTA-150] - BNodes are a dead end in the Linked Data Explorer
> * [MARMOTTA-154] - Youtube video provider doesn't fetch the keywords
> * [MARMOTTA-155] - 3-char lang-tags are not accepted
> * [MARMOTTA-156] - Add Logback configuration to all tests to
> enable/disable debug logging
> * [MARMOTTA-170] - file-store (meta) for ldcache-backend-file contains
> wrong comments
> * [MARMOTTA-171] - remove legacy subdirs from src/main/webapp in
> marmotta-webapp
> * [MARMOTTA-186] - LDPath parser fails on local names that contain '.'
> * [MARMOTTA-187] - ldpath extension for CM does not recognize local
> names with '.' or '-'
> * [MARMOTTA-191] - SPARQL graph results fails under some circunstances
> * [MARMOTTA-197] - ldpath is loosing brackets on re-serialisation
> * [MARMOTTA-204] - Update to Sesame 2.7.1
> * [MARMOTTA-205] - Turtle-Exports do not contain any language tags
> * [MARMOTTA-206] - Strictly follow the standard formatting on the NOTICE
> * [MARMOTTA-208] - Meta Put Webservice Deleting Tuples Incorrectly
> * [MARMOTTA-213] - Address the issues on our NOTICE files
> * [MARMOTTA-214] - Memento timestamp does not use the right template
> * [MARMOTTA-221] - ldpath is loosing quotes for StringConstants on
> re-serialisation
> * [MARMOTTA-225] - Serializing ldpath field mappings with U

Re: [VOTE] Apache Kalumet 0.6-incubating release (3rd try)

[sebb]

On 1 October 2013 18:07, Jean-Baptiste Onofré  wrote:
> Hi Seb,
>
> Thanks for the update:
>
> 1/ KEYS file is here:
>
> http://svn.apache.org/repos/asf/incubator/kalumet/tags/kalumet-0.6-incubating/KEYS
>
> 2/ SVN URLs:
>
> SCM Codebase:
> http://svn.apache.org/repos/asf/incubator/kalumet/branches/0.6.x/

OK, but not relevant to the release vote.

> Release Tag:
> http://svn.apache.org/repos/asf/incubator/kalumet/tags/kalumet-0.6-incubating/

SVN tags are not immutable. What is the revision number of the tag?

>
> 3/ The source archives signature files are on the staging repository
> (including md5 and sha1 hash):

Yes, I know that.

But when the staging repo is published (assuming that the vote
passes), all the URLs listed below will become invalid. It won't be
possible to tie the vote to the archives.

The vote e-mail needs the actual hashes (either MD5 and/or SHA1) of
the source archives.

For example:

apache-kalumet-0.6-incubating-src.zip
MD5: 5664ebc70172b3b66f17d3a3db48594d

> Thanks again Seb for the reminder,
>
> Regards
> JB
>
>
> On 10/01/2013 06:55 PM, sebb wrote:
>>
>> On 1 October 2013 08:00, Jean-Baptiste Onofré  wrote:
>>>
>>> Hi all,
>>>
>>> Apache Kalumet 0.6-incubating release has been voted by the Kalumet
>>> podling
>>> PMC.
>>>
>>> I forward the release to the Incubator for "final" vote. Please find the
>>> RELEASE NOTES and staging repository in the original message.
>>>
>>> Thanks,
>>> Regards
>>> JB
>>>
>>>  Original Message 
>>> Subject: [VOTE] Apache Kalumet 0.6-incubating release (3rd try)
>>> Date: Thu, 05 Sep 2013 13:30:42 +0200
>>> From: Jean-Baptiste Onofré 
>>> Reply-To: kalumet-...@incubator.apache.org
>>> To: kalumet-...@incubator.apache.org
>>>
>>> Hi all,
>>>
>>> The first release of Kalumet (0.6-incubating) is available.
>>> Please take a look on the artifacts (especially the distribution
>>> archives), review the documentation and make a try.
>>>
>>> Release Notes:
>>>
>>> http://svn.apache.org/repos/asf/incubator/kalumet/tags/kalumet-0.6-incubating/RELEASE-NOTES
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachekalumet-013/
>>
>>
>> Where is the KEYS file?
>> The URL should be included in all votes so reviewers can check the sigs.
>>
>> The vote e-mail should also include the SCM co-ordinates (SVN
>> URL+revision or GIT URL+hash). This is so the source archive contents
>> can be checked against it.
>>
>> Also, the Nexus URLs are temporary (and not unique), so the hashes of
>> the source archives should be included in the vote e-mail. Otherwise
>> there is not way to tie the vote e-mail to the artifacts that are
>> being voted on.
>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Do not approve the release (please provide specific comments)
>>>
>>> This vote will be open for 72 hours.
>>>
>>> Thanks,
>>> Regards
>>> JB
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>>
>>> -
>>> 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
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> 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: Apache project bylaws

[sebb]

On 2 October 2013 21:34, Alex Karasulu  wrote:
> On Wed, Oct 2, 2013 at 11:58 PM, Marvin Humphrey 
> wrote:
>
>> On Wed, Oct 2, 2013 at 11:35 AM, Alex Harui  wrote:
>> > I would like to propose a rewrite of [1] by borrowing heavily from [2]
>> but
>> > making sure to emphasize that projects are allowed to have different
>> rules
>> > for all of them (or is the code-commit veto required for all projects).
>> > Any objections to me trying to do that?
>>
>> Rather than a "rewrite", I suggest proposing small, incremental, reversible
>> changes.  Governance is easy to mess up.
>>
>> It would be so nice if we could write unit tests for governance docs to
>> make
>> sure that as they evolve they still solve all the old problems they were
>> intended to address.
>>
>>
> That's a really interesting perspective: governance rules as code, that can
> be unit tested. Heh I like that.

And how does one test that code is working correctly?
One of the most important tests is to check it against the functional
specification.

In the case of governance docs, I think the functional spec. is a list
of what the rules are intended to achieve.
This information should be part of the document.
Knowing what the rules are intended to achieve can help resolve
ambiguities in the rules.

> --
> Regards,
> -- Alex

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

Re: [VOTE] Release Apache Tajo-0.2-incubating RC1

[sebb]

On 27 October 2013 07:40, Hyunsik Choi  wrote:
> Hi folks
>
> This is the first release candidate for Apache Tajo-0.2-incubating,
> and it is also the first official release for Tajo.
>
> The PPMC vote [1][2] was passed with 5 binding +1s and no -1.
>
> Release git tag is at:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git;a=shortlog;h=refs/tags/release-0.2.0-rc1

The NOTICE file is wrong.

===
Apache Tajo
Copyright 2013 The Apache Software Foundation

This product includes software developed by The Apache Software
Foundation (http://www.apache.org/).

This product includes/uses Jetty (http://jetty.mortbay.org/),
Copyright (c) Mort Bay Consulting Pty. Ltd. (Australia)




The middle paragraph must read

=
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
=

Note that it is developed AT not BY.

The third paragraph is also wrong.
Additional notices are ONLY for included bits, so "/uses" must be removed.
Also, the NOTICE file must be appropriate to the container, which is
either SCM (i.e. Git) or the source archive or the binary archive.
Since the source archive and SCM should rarely contain binary code, it
generally has different contents from a binary archive that may
contain permitted 3rd party libraries
Furthermore, only *required* notices should be included [1]

AFAICT there is only a source archive provided, so there is no need to
consider binary dependencies.

It looks like the only possible candidate for the NOTICE file is the
JQuery and JSPlumb javascript source, and as those are both available
under the MIT license, according to [1] it's not needed.

However of course the LICENSE file must contain the appropriate
license text for each (or pointers to them in additional files). The
LICENSE entry should make clear that we are using the MIT license, as
the other choice (GPL2) is not be allowed in ASF releases.


[1] http://www.apache.org/dev/licensing-howto.html#mod-notice


> Release notes is at:
> http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc1/RELEASE_NOTES.html
>
> Release artifacts, signatures, md5, and sha512 are at:
> http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc1/
>
> and the KEYS file containing the PGP keys used to sign the release can
> currently be found at:
> http://people.apache.org/keys/group/tajo.asc
>
> The RAT report is at:
> http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc1/rat.txt
>
> Please vote
> [ ] +1 release this package as apache-tajo-0.2-incubating
> [ ] -1 do not release this package because ...
>
> Thanks,
> Hyunsik Choi
>
> [1] http://markmail.org/message/unaim5aalwjuajr3
> [2] http://markmail.org/message/ywxozclddlp4avov
>
> -
> 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: [PROPOSAL] Weave for Apache Incubator

[sebb]

In which case, maybe consider the related words:

Apache Warp
Apache Weft

Just a thought.

On 29 October 2013 22:14, Upayavira  wrote:
> And Apache Wave too (which is what I first saw before I read the title
> more carefully).
>
> Upayavira
>
> On Tue, Oct 29, 2013, at 09:12 PM, Matt Benson wrote:
>> Hi,
>>   I am concerned about potential confusion with Apache Commons Weaver
>>   [1].
>>
>> Matt
>>
>> [1] https://commons.apache.org/proper/commons-weaver/
>>
>>
>> On Tue, Oct 29, 2013 at 2:53 PM, Andreas Neumann  wrote:
>>
>> > I would like to propose Weave, an abstraction over Apache Hadoop® YARN to
>> > reduce the complexity of developing distributed applications, as an
>> > Apache Incubator
>> > podling.
>> >
>> > The proposal is included in plain text. I would also like to put this on
>> > the wiki, but I appear to lack privileges to create pages. What do I need
>> > to do to get permission?
>> >
>> > -Andreas.
>> >
>> > Abstract
>> > 
>> >
>> > Weave is an abstraction over Apache Hadoop® YARN that reduces the
>> > complexity of developing distributed applications, allowing developers to
>> > focus more on their business logic.
>> >
>> > Proposal
>> > 
>> >
>> > Weave is a set of libraries that reduces the complexity of developing
>> > distributed applications. It exposes the distributed capabilities of Apache
>> > Hadoop® YARN via a simple and intuitive programming model similar to Java
>> > threads. Weave also has built-in capabilities required by many distributed
>> > applications, such as real-time application logs and metrics collection,
>> > application lifecycle management, and network service discovery.
>> >
>> > Background
>> > ==
>> >
>> > Hadoop YARN is a generic cluster resource manager that supports any type of
>> > distributed application. However, YARN’s interfaces are too low level for
>> > rapid application development. It requires a great deal of boilerplate code
>> > even for a simple application, creating a high ramp up cost that can turn
>> > developers away.
>> >
>> > Weave is designed to improve this situation with a programming model that
>> > makes running distributed applications as easy as running Java threads.
>> > With the abstraction provided by Weave, applications can be executed in
>> > process threads during development and unit testing and then be deployed to
>> > a YARN cluster without any modifications.
>> >
>> > Weave also has built-in support for real-time application logs and metrics
>> > collection, delegation token renewal, application lifecycle management, and
>> > network service discovery. This greatly reduces the pain that developers
>> > face when developing, debugging, deploying and monitoring distributed
>> > applications.
>> >
>> > Weave is not a replacement for YARN, it’s a framework that operates on top
>> > of YARN.
>> >
>> > Rationale
>> > =
>> >
>> > Developers who write YARN applications typically find themselves
>> > implementing the same (or similar) boilerplate code over and over again for
>> > every application. It makes sense to distill this common code into a
>> > reusable set of libraries that is perpetually maintained and improved by a
>> > diverse community of developers.
>> >
>> > Weave’s simple thread-like programming model will enable many Java
>> > programmers to develop distributed applications. We believe that this
>> > simplicity will attract developers who would otherwise be discouraged by
>> > complexity, and many new use cases will emerge for the usage of YARN.
>> >
>> > Incubating Weave as an Apache project makes sense because Weave is a
>> > framework built on top of YARN, and Weave uses Apache Zookeeper, HDFS,
>> > Kafka, and other Apache software (see the External Dependencies section).
>> >
>> > Current Status
>> > ==
>> >
>> > Weave was initially developed at Continuuity. The Weave codebase is
>> > currently hosted in a public repository at github.com, which will seed the
>> > Apache git repository.
>> >
>> > Meritocracy
>> > ---
>> > Our intent with this incubator proposal is to start building a diverse
>> > developer community around Weave following the Apache meritocracy model.
>> > Since Weave was initially developed in early 2013, we have had fast
>> > adoption and contributions within Continuuity. We are looking forward to
>> > new contributors. We wish to build a community based on Apache's
>> > meritocracy principles, working with those who contribute significantly to
>> > the project and welcoming them to be committers both during the incubation
>> > process and beyond.
>> >
>> > Community
>> > -
>> > Weave is currently being used internally at Continuuity and is at the core
>> > of our products. We hope to extend our contributor base significantly and
>> > we will invite all who are interested in simplifying the development of
>> > distributed applications to participate.
>> >
>> > Core Developers
>> > ---
>> > Weave is currently being develo

Re: [VOTE] Release Apache Tajo-0.2-incubating RC2

[sebb]

On 31 October 2013 11:54, Hyunsik Choi  wrote:
> Hi folks
>
> This is the third candidate for Apache Tajo-0.2-incubating,
> and it is also the first official release for Tajo.
>
> The PPMC vote [1][2] was passed with 4 binding +1s and no -1.
>
> Release git tag is at:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git;a=shortlog;h=refs/tags/release-0.2.0-rc2

Unfortunately the NOTICE file still looks wrong to me.

Since the protobuf-java-format library uses a BSD license, it suffices
to have the Copyright attribution in the LICENSE file.
The NOTICE file should not therefore mention it, see

http://www.apache.org/dev/licensing-howto.html#mod-notice

> Release notes is at:
> http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc2/RELEASE_NOTES.html
>
> Release artifacts, signatures, md5, and sha1 are at:
> http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc2/
>
> and the KEYS file containing the PGP keys used to sign the release can
> currently be found at:
> http://people.apache.org/keys/group/tajo.asc
>
> The RAT report is at:
> http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc2/rat.txt
>
> Please vote
> [ ] +1 release this package as apache-tajo-0.2-incubating
> [ ] -1 do not release this package because ...
>
> Thanks,
> Hyunsik Choi
>
> [1] http://markmail.org/message/2ggtg55trtn6jab2
> [2] http://markmail.org/message/xp64nr5ajnp5nvoa
>
> -
> 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: Wiki access

[sebb]

What is your Wiki login name?

On 6 November 2013 00:55, P. Taylor Goetz  wrote:
> I'm requesting access to the incubator wiki in order to update the storm 
> podling monthly board report.
>
> Thanks in advance.
>
> P. Taylor Goetz
> Software Architect
>
> Health Market Science
> The Science of Better Results
> 2700 Horizon Drive •King of Prussia, PA •   19406
> P: 610.994.5237 •   M: 610.212.1185 •healthmarketscience.com

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

Re: Majority vs Lazy Majority

[sebb]

On 9 November 2013 07:06, Alex Harui  wrote:
> Hi,
>
> Someday I will get back to improving the Voting and Glossary pages, but
> meanwhile, the Apache Flex PMC is still trying to construct a set of
> bylaws and we are currently discussing whether there is a difference
> between "Majority Approval" which is in the Glossary and "Lazy Majority"
> which isn't, but is used in a lot of other project bylaws but seems to
> have the same meaning.

Is there such a concept as "Lazy Majority" ?

The Glossary only has "Lazy Consensus/Lazy Approval" [1]

The Voting page [2] does not mention Lazy Majority either.

If project bylaws mention "Lazy Majority" then presumably they must
define the concept locally.
[Though what that definition might be, I have no idea]
If the bylaws don't clearly define the concept, then the PMC needs to
determine how to fix the bylaws.

But please let's not add "Lazy Majority" to the foundation pages just
because it happens to be used elsewhere (possibly ambiguously).

[1] http://www.apache.org/foundation/glossary.html#LazyConsensus
[2] http://www.apache.org/foundation/voting.html

> To me, if "Lazy" means that silence give assent, I don't see how you can
> the count votes of those who assent.

Exactly; I agree that Lazy Majority does not make sense as a concept.

> Thoughts?
> -Alex
>
>
> -
> 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: Cultivating Outstanding IP Stewards

[sebb]

On 10 November 2013 08:00, Alex Harui  wrote:
> IMO, there are two problems:
>
> 1) We're trying to train folks to manage IP for their community but they
> have to seek approval from folks are aren't as vested in their community.
> My analogy is telling a new city council member: "Welcome to the city
> council.  For the next year all of your decisions will require
> ratification by 3 state senators".
>
> 2) Release voting takes a long time.  It would seem like tools should be
> able to reduce the time on several of the steps, except for this one from
> [1] "compile it as provided, and test the resulting executable on their
> own platform".
>
> Sometimes I think about trying to get on the IPMC and helping some podling
> get a release out but:
> A) Really, I just want to help check the legal aspects of a podling's
> release and don't have bandwidth to want to take on the other roles
> implied by being on the IPMC.
> B) I don't want to take the time to figure out how to build and test a
> release that I have no vested interest in.
>
> Now, incubating releases are not official releases, right?

Huh?

AIUI, they *are* official releases, but with certain caveats (the DISCLAIMER).

The source is published from the mirrors in the same way as for TLP releases.

That is why it is vital to get the NOTICE and LICENSE files right.

>  So why have
> such time- consuming requirements to get approval from the IPMC?  Let's
> assume that the podling folks tested the building and operation of the
> source package.  Could we build an ant script that any IPMC member or any
> PMC member from any TLP (to expand the pool of potential helpers to folks
> who supposedly know how) can run just to check:
>
> 1) source package has the name "incubating"
> 2) source package is signed
> 3) unzip source package
> 4) grab a tag from SVN/Git
> 5) Diff
> 6) Run Rat (without any fileset exclusions)
>
> Then some podling writes to general@ and says: "can we get legal approval
> to release? Please run the release checker ant script with the following
> inputs   "
>
> Then it could run while I read through all of the other ASF emails and
> eventually I get a report that contains mainly a list of non-Apache files
> in the RAT report that I review and comment on if needed.  To me, if
> you're reviewing a RAT report, you are a building inspector who has looked
> around inside.
>
> Can we make it that "simple"?
>
> For sure, if any podling member is qualified for IPMC before graduation
> they should be nominated and added, and I suppose we could also approve
> them to cast binding votes as a release checker which may be a lower bar
> and maybe less of a time commitment, but I think if it is possible to have
> a larger group of folks approve incubating releases mainly be reviewing
> RAT reports that might make it easier for a podling to get a release out
> the door and still assist in the training of the podling's future PMC
> members.
>
>
> [1] http://www.apache.org/dev/release.html#approving-a-release
>
> My two cents (probably more),
> -Alex
>
> On 11/9/13 9:38 PM, "Marvin Humphrey"  wrote:
>
>>On Sat, Nov 9, 2013 at 4:11 AM, Dave Brondsema  wrote:
>>> On 11/09/2013 02:23 AM, Jake Farrell wrote:
>>
 If mentors are not performing their duties to vote on a given releases
for
 a podling, then it is up to the IPMC as a whole to help that podling by
 doing the do diligence and casting a vote. We all asked to be apart of
the
 IPMC or where honored by a nomination and accepted the role. It is up
to us
 to show these podlings what the Apache was really means. These projects
 have all come to the ASF and we (the IPMC) have openly voted them into
 incubation, its up to us to help them succeed.
>>>
>>> While this is true in theory it's hard in practice to wrangle those
>>> votes together.
>>
>>That's not the only problem.  While IPMC volunteers who perform
>>"freelance"
>>release reviews keep the Incubator from grinding to a halt, our reliance
>>on
>>them undermines the Incubator's effectiveness as an IP clearinghouse.  I
>>wish
>>that we would redirect those volunteer energies elsewhere.
>>
>>IPMC members who vote +1 on an initial incubating release are endorsing
>>the
>>the code import and IP clearance process[1], as well as any work done
>>in-house
>>since incubation started.  Votes on subsequent incubating releases are
>>less
>>weighty because they chiefly endorse work done in-house since the last
>>release.
>>
>>Non-Mentors who swoop in at the last minute to vote +1 on a codebase
>>they've
>>never looked at produced by a community they've never interacted with are
>>not
>>in a position to make such endorsements, particularly for the first
>>incubating
>>release.
>>
>>They are like building inspectors who never go inside.
>>
 Merit stands above all else, and the contributors that you have
pointed out
 are all exceptional individuals that have advanced their projects and
 continued to do so after grad

Re: Majority vs Lazy Majority

[sebb]

On 9 November 2013 12:17, Justin Mclean  wrote:
> Hi,
>
>> Is there such a concept as "Lazy Majority" ?
> Yes many Apache projects define it (eg Ant, Kafka, Hadoop, Pig, Hive and 
> others ) as does Apache HTTP. [1]
> "Lazy majority decides each issue in the release plan."

The phrase is used, but it is not defined anywhere that I could find,
so it is either a typo for something else or it is meaningless.

In both cases the document needs to be tidied up and clarified.

> Different projects however  use different terms, as far as I can see  "Lazy 
> Majority" is used more than " "Majority Approval" but both have the same 
> rules, ie 3 +1s and more +1's than -1's.
>
> My guess is that "Lazy Majority" is used because Majority implies more than 
> 50% of possible voters need to vote.

My guess is that it is a misprint for Lazy Consensus.

> Thanks,
> Justin
>
> 1. http://httpd.apache.org/dev/guidelines.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: Majority vs Lazy Majority

[sebb]

On 19 November 2013 08:29, Bertrand Delacretaz  wrote:
> On Fri, Nov 15, 2013 at 4:03 PM, sebb  wrote:
>> On 9 November 2013 12:17, Justin Mclean  wrote:
> ...
>>> My guess is that "Lazy Majority" is used because Majority implies more than 
>>> 50% of possible voters need to vote.
>>
>> My guess is that it is a misprint for Lazy Consensus
>
> I'd say so - "lazy majority" is mentioned at
> http://ant.apache.org/bylaws.html but I didn't know there was such a
> concept in our projects.

The Ant bylaws do at least define what the terms mean [1], but
unfortunately it seems they have chosen different names from the ones
in the ASF Glossary [2]

For example:

Ant has
Consensus: For this to pass, all voters with binding votes must vote
and there can be no binding vetoes (-1). Consensus votes are rarely
required due to the impracticality of getting all eligible voters to
cast a vote.

ASF has:
'Consensus approval' refers to a vote (sense 1) which has completed
with at least three binding +1 votes and no vetos. Compare Majority
Approval.

Ant:
Lazy Consensus: Lazy consensus requires 3 binding +1 votes and no
binding vetoes.

ASF:
Lazy consensus(Also called 'lazy approval'.):  A decision-making
policy which assumes general consent if no responses are posted within
a defined period.

This is a bit of a mess.

[1] http://ant.apache.org/bylaws.html#Approvals
[2] http://www.apache.org/foundation/glossary.html


> I'd rather keep it simple and avoid mentioning it in the incubator docs.
>
> -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: [VOTE] helix-0.7.0-incubating

[sebb]

On 19 November 2013 07:48, Zhen Zhang  wrote:
> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.7.0-incubating. This is the first release candidate of our fourth
> release at Apache.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault tolerant and scalable
> distributed systems.
>
> Release notes:
> http://helix.incubator.apache.org/site-releases/0.7.0-incubating-site/releasenotes/release-0.7.0-incubating.html
>
> Our vote thread on helix-dev:
> http://markmail.org/message/jevvd7e3v6e75vgg
>
> The following IPMC members have voted +1
> Patrick Hunt
> Olivier Lamy
>
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-139
>
> Distribution:
> *binaries:
> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/binaries/
> *sources:
> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/src/
>
> The 0.7.0-incubating release tag
> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=575a02b463c3482cefd164578214da7d478da27f

The tag has DISCLAIMER and LICENSE files, but the NOTICE file is missing.
This is required for all releases.

> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>
> Please vote on the release. The vote will be open for 72 hours.
>
> [+1]
> [0]
> [-1]
>
> Thanks,
> The Apache Helix Team

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

Re: [VOTE] helix-0.6.2-incubating

[sebb]

On 19 November 2013 02:50, Kanak Biscuitwala  wrote:
> Hi,
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.6.2-incubating. This is the first release candidate of our third
> release at Apache.
>
> Apache Helix is a generic cluster management framework that makes it easy
> to build partitioned and replicated, fault tolerant and scalable
> distributed systems.
>
> Release notes:
> http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html
>
> Our vote thread on helix-dev:
> http://markmail.org/message/f2odmc7ga2i5qqmh
>
> The following IPMC members have voted +1
> Patrick Hunt
> Olivier Lamy
>
> Release artifacts:
> https://repository.apache.org/content/repositories/orgapachehelix-138
>
> Distribution:
> * binaries:
> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/
> * sources:
> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/src/
>
> The 0.6.2-incubating release tag
> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=74efd57c9f7bcb54cb6007dd34646722d6133340

The NOTICE file is missing from the top-level of the tag. It should be
present alongside the LICENSE file.

> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>
> Please vote on the release. The vote will be open for 72 hours.
>
> [+1]
> [0]
> [-1]
>
> Thanks,
> The Apache Helix Team
> -
> 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] helix-0.7.0-incubating

[sebb]

I see that 0.7.0 has been released.

However there was no [VOTE][RESULT] mail as far as I can tell.

On 23 November 2013 14:36, sebb  wrote:
> On 19 November 2013 07:48, Zhen Zhang  wrote:
>> Hi,
>>
>> This is to call for a vote on releasing the following candidate as Apache
>> Helix 0.7.0-incubating. This is the first release candidate of our fourth
>> release at Apache.
>>
>> Apache Helix is a generic cluster management framework that makes it easy
>> to build partitioned and replicated, fault tolerant and scalable
>> distributed systems.
>>
>> Release notes:
>> http://helix.incubator.apache.org/site-releases/0.7.0-incubating-site/releasenotes/release-0.7.0-incubating.html
>>
>> Our vote thread on helix-dev:
>> http://markmail.org/message/jevvd7e3v6e75vgg
>>
>> The following IPMC members have voted +1
>> Patrick Hunt
>> Olivier Lamy
>>
>> Release artifacts:
>> https://repository.apache.org/content/repositories/orgapachehelix-139
>>
>> Distribution:
>> *binaries:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/binaries/
>> *sources:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/src/
>>
>> The 0.7.0-incubating release tag
>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=575a02b463c3482cefd164578214da7d478da27f
>
> The tag has DISCLAIMER and LICENSE files, but the NOTICE file is missing.
> This is required for all releases.
>
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>>
>> Please vote on the release. The vote will be open for 72 hours.
>>
>> [+1]
>> [0]
>> [-1]
>>
>> Thanks,
>> The Apache Helix Team

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

Re: [VOTE] Release HDT version 0.0.1.incubating (RC1)

[sebb]

On 20 November 2013 13:45, Rahul Sharma  wrote:
> Hi,
>
> I would like to call for a vote for Apache Hadoop Development Tools
> (incubating), version 0.0.1.incubating. The vote has happened of the dev
> mailing list and the community has approved the second release
> candidate(RC1) for Apache Hadoop Development Tools (incubating), version
> 0.0.1.incubating.The release has Zookeper and HDFS features from the
> *hadoop-eclipse-merge* codebase. The issues raised for RC0 have been
> addressed in this release.
>
> 1 IPMC votes have already been cast:
>   Roman Shaposhnik (mentor)
>
> Please vote on releasing this package as Apache Hadoop Development Tools
> 0.0.1.incubating.
>
> [ ] +1 Release this package as Apache HDT 0.0.1.incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> PPMC Vote thread :
> http://apache.markmail.org/message/bbdedy4bprhwngew
>
> Vote Result :
> http://apache.markmail.org/message/nq4pylp73n5n6wyn
>
> Source and binary files:
> http://people.apache.org/~rsharma/hdt-0.0.1.incubating-rc1/
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-hdt.git;a=commit;h=0627220f5181bfe698fdc71209ca66864068b352

The NOTICE file says:

"This product includes/uses Eclipse Icons"

The NOTICE file must only reference included bits; the /uses should be deleted.
And if the icons are not actually included the entire paragraph should
be dropped (however it looks as though they are included)


> KEYS file:
> https://dist.apache.org/repos/dist/dev/incubator/hdt/KEYS
>
> Some guideline to verify release can be found at :
> http://apache.markmail.org/message/qj3srhvozapbwmq6
>
> regards,
> Rahul

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

Re: [VOTE] Release Apache Knox-0.3.1-incubating RC3

[sebb]

On 20 November 2013 16:09, larry mccay  wrote:
> Hello All,
>
> This is a call for a vote on Apache Knox Gateway 0.3.1 incubating.
>
> A vote was held on developer mailing list and it passed with 3 +1's, and 0
> -1's or +0's and now
> requires a vote on general@incubator.apache.org.
>
> The [VOTE] thread can be found at:
> http://mail-archives.apache.org/mod_mbox/incubator-knox-dev/201311.mbox/%3CCACRbFyjgLrCSahhtWWHK-%3DaeQFM4Oegbe3fQjs-RV2-TAnhdxA%40mail.gmail.com%3E
>
> The release candidate is a zip archive of the sources in:
> https://git-wip-us.apache.org/repos/asf/incubator-knox.git
> Branch v0.3.1 (git checkout -b v0.3.1)
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=tag;h=5a907022dbc2b0a8534de47fe7b8c871c4f075f9

The NOTICE file is wrong; the first 6 lines should be removed (i.e.
lines with == and following blank line)

Also, the text should be:

"This product includes software developed at"
not
"This product includes software developed by"

> Source archive zip file and signature are available from:
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip.asc
>
> Checksums of the source archive:
>   SHA1:   04bb11360f57c0431c30cfb181e3199868fe6053
>
> The KEYS file can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/KEYS

The KEYS file should really be at the top level of the release area, i.e.

https://dist.apache.org/repos/dist/release/incubator/knox/KEYS

> The release changes file can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/CHANGES
>
> The release has been signed with key (587C089B):
>   http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x82F9C371587C089B
>
> Vote will be open for 72 hours.
>
> thanks,
>
> --larry
>
> Larry McCay

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

Re: [VOTE] helix-0.6.2-incubating

[sebb]

On 23 November 2013 19:57, Kanak Biscuitwala  wrote:
> sebb, I fixed the tag to include NOTICE here: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=d12177168347c9253f3b37946c06a7175f8a1997
>
> The parent directory doesn't actually contain any artifacts that we package 
> as binaries.

Not really relevant.
The NOTICE file must relate to the contents of the collection it
relates to: e.g. the tag or the source archive or the binary archive
etc.
Likewise the LICENSE file.

> Do we need to go through the entire release process again?

Does the release have the correct NOTICE and LICENSE files?

>
>> From: kana...@hotmail.com
>> To: general@incubator.apache.org
>> Subject: [VOTE] helix-0.6.2-incubating
>> Date: Mon, 18 Nov 2013 18:50:31 -0800
>>
>> Hi,
>>
>> This is to call for a vote on releasing the following candidate as Apache
>> Helix 0.6.2-incubating. This is the first release candidate of our third
>> release at Apache.
>>
>> Apache Helix is a generic cluster management framework that makes it easy
>> to build partitioned and replicated, fault tolerant and scalable
>> distributed systems.
>>
>> Release notes:
>> http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html
>>
>> Our vote thread on helix-dev:
>> http://markmail.org/message/f2odmc7ga2i5qqmh
>>
>> The following IPMC members have voted +1
>> Patrick Hunt
>> Olivier Lamy
>>
>> Release artifacts:
>> https://repository.apache.org/content/repositories/orgapachehelix-138
>>
>> Distribution:
>> * binaries:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/
>> * sources:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/src/
>>
>> The 0.6.2-incubating release tag
>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=74efd57c9f7bcb54cb6007dd34646722d6133340
>>
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>>
>> Please vote on the release. The vote will be open for 72 hours.
>>
>> [+1]
>> [0]
>> [-1]
>>
>> Thanks,
>> The Apache Helix Team
> -
> 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] helix-0.7.0-incubating

[sebb]

On 23 November 2013 20:00, Kanak Biscuitwala  wrote:
> sebb, I fixed the tag to include NOTICE here: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=37c20e79d0e132710f0fa0e5e8dbdb95b2e639ff
>
> The parent project doesn't produce any binary artifacts that we release. Do 
> we need to go through the entire release process again?

Again, does the release include the correct NOTICE and LICENSE files?

> 
>> Date: Mon, 18 Nov 2013 23:48:56 -0800
>> Subject: [VOTE] helix-0.7.0-incubating
>> From: zzh...@apache.org
>> To: general@incubator.apache.org
>>
>> Hi,
>>
>> This is to call for a vote on releasing the following candidate as Apache
>> Helix 0.7.0-incubating. This is the first release candidate of our fourth
>> release at Apache.
>>
>> Apache Helix is a generic cluster management framework that makes it easy
>> to build partitioned and replicated, fault tolerant and scalable
>> distributed systems.
>>
>> Release notes:
>> http://helix.incubator.apache.org/site-releases/0.7.0-incubating-site/releasenotes/release-0.7.0-incubating.html
>>
>> Our vote thread on helix-dev:
>> http://markmail.org/message/jevvd7e3v6e75vgg
>>
>> The following IPMC members have voted +1
>> Patrick Hunt
>> Olivier Lamy
>>
>> Release artifacts:
>> https://repository.apache.org/content/repositories/orgapachehelix-139
>>
>> Distribution:
>> *binaries:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/binaries/
>> *sources:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/src/
>>
>> The 0.7.0-incubating release tag
>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=575a02b463c3482cefd164578214da7d478da27f
>>
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>>
>> Please vote on the release. The vote will be open for 72 hours.
>>
>> [+1]
>> [0]
>> [-1]
>>
>> Thanks,
>> The Apache Helix Team
> -
> 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: [RESULT][VOTE] helix-0.7.0-incubating

[sebb]

On 23 November 2013 20:01, Kanak Biscuitwala  wrote:
> Hi:
>
> Closing the vote since it has passed 72 hours.
>
> Here is the result:
>
> +1: 3 (binding)
> Patrick Hunt
> Olivier Lamy
> Mahadev Konar
>
> -1: 0
>
> The vote has passed (pending a response to the email below), thanks a lot to 
> everyone for voting, thanks to the
> mentors for all the support!

Question for the mentors: how come the files were released without the
vote tally?

> Cheers,
> The Helix Team
>
> 
>> From: kana...@hotmail.com
>> To: general@incubator.apache.org
>> Subject: RE: [VOTE] helix-0.7.0-incubating
>> Date: Sat, 23 Nov 2013 12:00:09 -0800
>>
>> sebb, I fixed the tag to include NOTICE here: 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=37c20e79d0e132710f0fa0e5e8dbdb95b2e639ff
>>
>> The parent project doesn't produce any binary artifacts that we release. Do 
>> we need to go through the entire release process again?
>>
>> 
>>> Date: Mon, 18 Nov 2013 23:48:56 -0800
>>> Subject: [VOTE] helix-0.7.0-incubating
>>> From: zzh...@apache.org
>>> To: general@incubator.apache.org
>>>
>>> Hi,
>>>
>>> This is to call for a vote on releasing the following candidate as Apache
>>> Helix 0.7.0-incubating. This is the first release candidate of our fourth
>>> release at Apache.
>>>
>>> Apache Helix is a generic cluster management framework that makes it easy
>>> to build partitioned and replicated, fault tolerant and scalable
>>> distributed systems.
>>>
>>> Release notes:
>>> http://helix.incubator.apache.org/site-releases/0.7.0-incubating-site/releasenotes/release-0.7.0-incubating.html
>>>
>>> Our vote thread on helix-dev:
>>> http://markmail.org/message/jevvd7e3v6e75vgg
>>>
>>> The following IPMC members have voted +1
>>> Patrick Hunt
>>> Olivier Lamy
>>>
>>> Release artifacts:
>>> https://repository.apache.org/content/repositories/orgapachehelix-139
>>>
>>> Distribution:
>>> *binaries:
>>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/binaries/
>>> *sources:
>>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/src/
>>>
>>> The 0.7.0-incubating release tag
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=575a02b463c3482cefd164578214da7d478da27f
>>>
>>> KEYS file available here:
>>> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>>>
>>> Please vote on the release. The vote will be open for 72 hours.
>>>
>>> [+1]
>>> [0]
>>> [-1]
>>>
>>> Thanks,
>>> The Apache Helix Team
>> -
>> 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] helix-0.6.2-incubating

[sebb]

On 23 November 2013 22:07, Kanak Biscuitwala  wrote:
> No, the current release doesn't have a NOTICE file at the top level.

Are you sure about that?

I checked the file helix-0.6.2-incubating-src.zip and it seems to have
NOTICE and LICENSE files in the correct place.

Are you referring to something else?

> The subcomponents we intended for release (i.e. helix-core, helix-agent, 
> helix-examples, and helix-admin-webapp) all have LICENSE, DISCLAIMER, and 
> NOTICE files. If we need a NOTICE file in the top level, then we'll have to 
> re-run the release tools.
>
> If we re-run the release tools, is it required to start a new vote 
> internally, as well as a new vote on this list?
>
> Also, what do we do with the artifacts that have already been released?
>
> Thanks,
> Kanak
>
> 
>> Date: Sat, 23 Nov 2013 21:28:25 +
>> Subject: Re: [VOTE] helix-0.6.2-incubating
>> From: seb...@gmail.com
>> To: general@incubator.apache.org
>>
>> On 23 November 2013 19:57, Kanak Biscuitwala  wrote:
>>> sebb, I fixed the tag to include NOTICE here: 
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=d12177168347c9253f3b37946c06a7175f8a1997
>>>
>>> The parent directory doesn't actually contain any artifacts that we package 
>>> as binaries.
>>
>> Not really relevant.
>> The NOTICE file must relate to the contents of the collection it
>> relates to: e.g. the tag or the source archive or the binary archive
>> etc.
>> Likewise the LICENSE file.
>>
>>> Do we need to go through the entire release process again?
>>
>> Does the release have the correct NOTICE and LICENSE files?
>>
>>>
>>>> From: kana...@hotmail.com
>>>> To: general@incubator.apache.org
>>>> Subject: [VOTE] helix-0.6.2-incubating
>>>> Date: Mon, 18 Nov 2013 18:50:31 -0800
>>>>
>>>> Hi,
>>>>
>>>> This is to call for a vote on releasing the following candidate as Apache
>>>> Helix 0.6.2-incubating. This is the first release candidate of our third
>>>> release at Apache.
>>>>
>>>> Apache Helix is a generic cluster management framework that makes it easy
>>>> to build partitioned and replicated, fault tolerant and scalable
>>>> distributed systems.
>>>>
>>>> Release notes:
>>>> http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html
>>>>
>>>> Our vote thread on helix-dev:
>>>> http://markmail.org/message/f2odmc7ga2i5qqmh
>>>>
>>>> The following IPMC members have voted +1
>>>> Patrick Hunt
>>>> Olivier Lamy
>>>>
>>>> Release artifacts:
>>>> https://repository.apache.org/content/repositories/orgapachehelix-138
>>>>
>>>> Distribution:
>>>> * binaries:
>>>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/
>>>> * sources:
>>>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/src/
>>>>
>>>> The 0.6.2-incubating release tag
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=74efd57c9f7bcb54cb6007dd34646722d6133340
>>>>
>>>> KEYS file available here:
>>>> https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS
>>>>
>>>> Please vote on the release. The vote will be open for 72 hours.
>>>>
>>>> [+1]
>>>> [0]
>>>> [-1]
>>>>
>>>> Thanks,
>>>> The Apache Helix Team
>>> -
>>> 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] helix-0.6.2-incubating

[sebb]

On 23 November 2013 23:47, Kanak Biscuitwala  wrote:
> Oh, interesting. I believe it generates this automatically with the 
> license-maven-plugin in the build/package stage. In that case, is this an 
> acceptable solution, or is an explicit NOTICE file still required?

Every ASF distribution must have LICENSE and NOTICE files (and
DISCLAIMER for podlings)
This includes releases and SCM.

The NOTICE file must not contain any unnecessary content - in
particular it must only contain references to bits that are actually
included in the distribution. I'm not sure whether the plugin handles
this properly yet (early versions were not good in this regard).

> Olivier, can you provide some context?
>
> 
>> Date: Sat, 23 Nov 2013 23:01:14 +
>> Subject: Re: [VOTE] helix-0.6.2-incubating
>> From: seb...@gmail.com
>> To: general@incubator.apache.org
>>
>> On 23 November 2013 22:07, Kanak Biscuitwala  wrote:
>>> No, the current release doesn't have a NOTICE file at the top level.
>>
>> Are you sure about that?
>>
>> I checked the file helix-0.6.2-incubating-src.zip and it seems to have
>> NOTICE and LICENSE files in the correct place.
>>
>> Are you referring to something else?
>>
>>> The subcomponents we intended for release (i.e. helix-core, helix-agent, 
>>> helix-examples, and helix-admin-webapp) all have LICENSE, DISCLAIMER, and 
>>> NOTICE files. If we need a NOTICE file in the top level, then we'll have to 
>>> re-run the release tools.
>>>
>>> If we re-run the release tools, is it required to start a new vote 
>>> internally, as well as a new vote on this list?
>>>
>>> Also, what do we do with the artifacts that have already been released?
>>>
>>> Thanks,
>>> Kanak
>>>
>>> ----
>>>> Date: Sat, 23 Nov 2013 21:28:25 +
>>>> Subject: Re: [VOTE] helix-0.6.2-incubating
>>>> From: seb...@gmail.com
>>>> To: general@incubator.apache.org
>>>>
>>>> On 23 November 2013 19:57, Kanak Biscuitwala  wrote:
>>>>> sebb, I fixed the tag to include NOTICE here: 
>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=d12177168347c9253f3b37946c06a7175f8a1997
>>>>>
>>>>> The parent directory doesn't actually contain any artifacts that we 
>>>>> package as binaries.
>>>>
>>>> Not really relevant.
>>>> The NOTICE file must relate to the contents of the collection it
>>>> relates to: e.g. the tag or the source archive or the binary archive
>>>> etc.
>>>> Likewise the LICENSE file.
>>>>
>>>>> Do we need to go through the entire release process again?
>>>>
>>>> Does the release have the correct NOTICE and LICENSE files?
>>>>
>>>>>
>>>>>> From: kana...@hotmail.com
>>>>>> To: general@incubator.apache.org
>>>>>> Subject: [VOTE] helix-0.6.2-incubating
>>>>>> Date: Mon, 18 Nov 2013 18:50:31 -0800
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> This is to call for a vote on releasing the following candidate as Apache
>>>>>> Helix 0.6.2-incubating. This is the first release candidate of our third
>>>>>> release at Apache.
>>>>>>
>>>>>> Apache Helix is a generic cluster management framework that makes it easy
>>>>>> to build partitioned and replicated, fault tolerant and scalable
>>>>>> distributed systems.
>>>>>>
>>>>>> Release notes:
>>>>>> http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html
>>>>>>
>>>>>> Our vote thread on helix-dev:
>>>>>> http://markmail.org/message/f2odmc7ga2i5qqmh
>>>>>>
>>>>>> The following IPMC members have voted +1
>>>>>> Patrick Hunt
>>>>>> Olivier Lamy
>>>>>>
>>>>>> Release artifacts:
>>>>>> https://repository.apache.org/content/repositories/orgapachehelix-138
>>>>>>
>>>>>> Distribution:
>>>>>> * binaries:
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/
>>>>>> * sources:
>>>>>> https://dist.a

Re: [VOTE] Release Apache Tez-0.2.0-incubating RC0

[sebb]

On 26 November 2013 00:33, Hitesh Shah  wrote:
> Hello folks,
>
> I have created a tez-0.2.0-incubating release candidate (rc0). This is the 
> first release for Tez. Therefore, please do not be gentle.
>
> GIT source tag: 
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.2.0-rc0

Minor nit: the NOTICE.txt file wraps in the wrong place.

>>>
This product includes software developed at The Apache Software
Foundation (http://www.apache.org/).
<<<

should be

>>>
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
<<<

Should be fixed for any future release (or if this one has to be redone)

> Staging site: 
> http://people.apache.org/~hitesh/tez-release-rc/tez-0.2.0-incubating-rc0/

[Not mandatory, but] if you stage at the following URL:

https://dist.apache.org/repos/dist/dev/incubator/tez/

it's then easy to rename the files to the release directory strucure here:

https://dist.apache.org/repos/dist/release/incubator/tez/

> Nexus Staging URL: 
> https://repository.apache.org/content/repositories/orgapachetez-002/
>
> PGP release keys: 
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
> KEYS file also available at 
> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>
> One can look into the issues fixed in this release at: 
> https://issues.apache.org/jira/browse/TEZ/fixforversion/12324349
>
> Vote will be open for 72 hours.

Minor nit: that should be "for at least 72 hours"; the 72 hours is a
*minimum* to ensure that people have time to review and vote.

> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> thanks
> -- Hitesh
> -
> 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 Tez-0.2.0-incubating RC0

[sebb]

On 26 November 2013 22:21, Hitesh Shah  wrote:
> Thanks for the review, Sebb,
>
> Have already updated NOTICE.txt in the master branch for future releases and 
> made a note of the other points in our how to release guide.
>
> Do you recommended starting a new VOTE thread for the re-wording with respect 
> to the 72 hrs period or can I just continue with this one? I had assumed I 
> would be keeping the vote open until enough IPMC votes were received. At this 
> point, I believe we have only one IPMC vote ( from Oliver Lamy).

I wrote:

Should be fixed for any future release (or if this one has to
be redone)

The wording is correct; it is only the word-wrapping that is wrong
I don't think that's enough on its own to warrant a respin of the release.

> thanks
> -- Hitesh
>
> On Nov 26, 2013, at 8:37 AM, sebb wrote:
>
>> On 26 November 2013 00:33, Hitesh Shah  wrote:
>>> Hello folks,
>>>
>>> I have created a tez-0.2.0-incubating release candidate (rc0). This is the 
>>> first release for Tez. Therefore, please do not be gentle.
>>>
>>> GIT source tag: 
>>> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.2.0-rc0
>>
>> Minor nit: the NOTICE.txt file wraps in the wrong place.
>>
>>>>>
>> This product includes software developed at The Apache Software
>> Foundation (http://www.apache.org/).
>> <<<
>>
>> should be
>>
>>>>>
>> This product includes software developed at
>> The Apache Software Foundation (http://www.apache.org/).
>> <<<
>>
>> Should be fixed for any future release (or if this one has to be redone)
>>
>>> Staging site: 
>>> http://people.apache.org/~hitesh/tez-release-rc/tez-0.2.0-incubating-rc0/
>>
>> [Not mandatory, but] if you stage at the following URL:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/tez/
>>
>> it's then easy to rename the files to the release directory strucure here:
>>
>> https://dist.apache.org/repos/dist/release/incubator/tez/
>>
>>> Nexus Staging URL: 
>>> https://repository.apache.org/content/repositories/orgapachetez-002/
>>>
>>> PGP release keys: 
>>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
>>> KEYS file also available at 
>>> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>>>
>>> One can look into the issues fixed in this release at: 
>>> https://issues.apache.org/jira/browse/TEZ/fixforversion/12324349
>>>
>>> Vote will be open for 72 hours.
>>
>> Minor nit: that should be "for at least 72 hours"; the 72 hours is a
>> *minimum* to ensure that people have time to review and vote.
>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> thanks
>>> -- Hitesh
>>> -
>>> 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: Release Verification Checklist

[sebb]

On 27 November 2013 20:45, Marvin Humphrey  wrote:
> Greets,
>
> In response to Bertrand's proposal at , I've created
> a draft release verification checklist:
>
> http://wiki.apache.org/incubator/ReleaseChecklist
>
> It should be emphasized that completing a checklist like this at release
> points is only one aspect of exercising proper IP stewardship over a codebase.
> The checklist says nothing about code provenance, and while it may catch
> licensing documentation bugs, it does little to guard against the possibility
> of actual licensing violations: bogus header swaps, "borrowed" code pasted
> into files with different licensing, and so on.  We don't generally encounter
> such problems at Apache, but we need to stay vigilant.
>
> Design notes:
>
> *   Brevity is important for ease of use.  We don't want to explain what makes
> for a valid LICENSE and NOTICE in a checklist.
> *   +0 and -0 votes are rare, so they are omitted from the template.
> *   All checklist items are optional.  Of course if you leave everything
> unchecked, your indifference is going to be entered into the record.
> *   The dictate that all checklist items are optional is explicitly included
> in the template despite wasting precious space, because otherwise PPMC
> confusion will cause needless stress and wasted time.
> *   Podlings may wish to augment this template with project-specific
> modifications, e.g. "Extended tests pass", "RAT report clean".
> *   The `Apache ID` field is intended to allow whoever enters these checklists
> into the record to copy-and-paste verbatim without having to look up
> credentials.  Hopefully people will actually fill it in regularly.
> *   There is no field identifying the release candidate because that
> information will be carried by email subject, filepath in version control,
> etc.
> *   The checklist text is designed for quick copy/paste into an email.  It
> must take up as little vertical space as possible so that it is easy to
> select with a mouse/trackpad gesture.
> *   The textual layout is intended to stack cleanly and to look good when
> rendered using either fixed-width or variable-width fonts.
>
> Thoughts?

The N&L files also apply to the SCM tree; further the N&L files may be
different for the binary archive (if provided)

> Marvin Humphrey
>
> -
> 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: technical question with maven artifacts and incubating suffix

[sebb]

SNAPSHOT releases are temporary, so I suggest you just delete any that
have been uploaded to to ASF snapshot repo.

Alternatively, change the version to 3.2.1-SNAPSHOT

On 28 November 2013 16:07, Sergio Fernández
 wrote:
> Hi,
>
> in Marmotta we're having now the hangover of the graduation, and I'm facing
> with a technical issue. Sorry if someone considers this a bit of topic of
> general@incubator, but I ask it here instead on dev@maven because the
> implications it may have for all the other podlings.
>
> The case is last week we jumped from:
>
> 3.2.0-incubating-SNAPSHOT
>
> to:
>
> 3.2.0-SNAPSHOT
>
> And I'm now facing some problems updating some app build using Marmotta. My
> guess is that Maven considers this for comparing both versions:
>
> 3.2.0-SNAPSHOT < 3.2.0-incubating-SNAPSHOT
>
> Could someone corroborate my suspicions? I've tried to find such detail in
> the documentation, but nothing.
>
> Thanks in advance.
>
> Cheers,
>
> --
> Sergio Fernández
> Senior Researcher
> Knowledge and Media Technologies
> Salzburg Research Forschungsgesellschaft mbH
> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
> T: +43 662 2288 318 | M: +43 660 2747 925
> sergio.fernan...@salzburgresearch.at
> http://www.salzburgresearch.at
>
> -
> 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: Release Verification Checklist

[sebb]

On 29 November 2013 21:00, Marvin Humphrey  wrote:
> On Wed, Nov 27, 2013 at 5:13 PM, sebb  wrote:
>
>> The N&L files also apply to the SCM tree;
>
> Yes, true.  Here's a message from Doug Cutting to legal-discuss@apache
> on the subject: http://s.apache.org/9r7>.
>
> In my view, it's appropriate for someone reviewing a release to comment on
> whether the SCM tree has proper LICENSE and NOTICE files.  However, I don't
> think that should be a checklist item because the checklist should be specific
> to the release artifacts.

Not sure I understand why the checklist needs to be specific.

> Now, there's another checklist item to which the same critique applies:
>
> [ ] I follow this project's commits list.
>
> I would rather delete this item and be consistent than expand the checklist
> with more such items.
>
>> further the N&L files may be different for the binary archive (if provided)
>
> We should allow podlings which choose to perform quality control on
> convenience binaries to customize their own checklists with additional items
> as they see fit.  However, since 1) only the source archive is officially a
> release by the ASF, and 2) not all podlings make convenience binaries
> available, the default checklist should concern itself with the source archive
> alone.

But if a project does release binaries, these must have valid N&L files.

> Nevertheless, convenience binaries have their own set of common problems
> (including incorrect N&L) which I anticipate we will want to address through
> documentation suggesting a specific block of additional checklist items.

It does not necessarily need to be a separate check item.
Just a reminder that the N&L files are specific to the distributed
items (SCM or release artifact).

> Marvin Humphrey
>
> -
> 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: [PROPOSAL] Log4cxx incubation

[sebb]

I'm not sure why the Incubator needs to be involved at all here.

On 30 November 2013 19:30, Christian Grobmeier  wrote:
> zero feedback? :-)
>
>
> On 28 Nov 2013, at 10:50, Christian Grobmeier wrote:
>
>> Dear Incubator people,
>>
>> I just added a new proposal for the incubation of log4cxx:
>> https://wiki.apache.org/incubator/Log4cxxProposal
>>
>> This project was inactive for a good while at logging.apache.org. When we
>> discussed the attic,
>> a lot of people showed their interest and willingness to work on it.
>>
>> Due to the size of the new team I think it is to start a new incubation.
>>
>> Of course I am willing to step up as Champion and Mentor. Others here who
>> have an interest in logging
>> in C are invited to step up as a mentor too.
>>
>> The goal is to reboot this project and move it back to logging.a.o as soon
>> as the team is ready.
>>
>> As resources are already there, I would like to simply reuse them and just
>> move the svn repos to the incubator tree.
>>
>> Please let me know about your thoughts.
>>
>> Thanks,
>> Christian
>>
>> ---
>> http://www.grobmeier.de
>> @grobmeier
>> GPG: 0xA5CC90DB
>
>
>
> ---
> http://www.grobmeier.de
> @grobmeier
> GPG: 0xA5CC90DB
>
> -
> 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: Release Verification Checklist

[sebb]

On 1 December 2013 19:09, Marvin Humphrey  wrote:
> On Fri, Nov 29, 2013 at 1:33 PM, sebb  wrote:
>> Not sure I understand why the checklist needs to be specific.
>
> The checklist should include only items which might block the release of the
> artifacts under review.  Expanding it to include unrelated concerns imposes an
> unnecessary cost each time someone goes through the checklist.
>
> Let's not make the release process any harder than it needs to be.

Which is easier?
- have one checklist with some items that don't apply to all release votes
- have separate checklists for releases with and without binary artifacts

>> It does not necessarily need to be a separate check item.
>> Just a reminder that the N&L files are specific to the distributed
>> items (SCM or release artifact).
>
> I'm apprehensive that a single checklist which tries to be all things to all
> projects will ultimately prove unworkable.  The design pressure is building
> and eventually, customization will be the only answer.

AFAICT there are only two different kinds of release votes:
- SCM and source
- SCM, source and convenience binaries

> Nevertheless, I've added a second draft to
> http://wiki.apache.org/incubator/ReleaseChecklist which attempts to address
> your concerns.  Here are some of the changes:
>
> *   Pluralize a few items to allow for the possibility that the release
> candidate VOTE encompasses multiple archives -- accommodating both
> projects which release multiple source archives simultaneously and
> projects which make convenience binaries available.
> *   Require that LICENCE and NOTICE be "correct for each distribution".  To my
> mind this is superfluous because it was implied by "correct", but it's
> certainly something that projects get wrong a lot.

The issue is that the N&L files may need to be diffferent for the
binary artifacts.
This is often overlooked.

> *   Simplify the testing checklist item to `[ ] All tests pass.`  This is
> weaker, in that it does not require building and testing of the *source*
> archive, but it is more compatible with more configurations.  The
> checklist item shouldn't require that all tests pass for *all* archives,
> because that doesn't work with platform-specific binaries; this language
> was the best general compromise I could come up with.
> *   Change the "license headers" item to specify "source files", in order to
> resolve an incidental ambiguity with regards to whether "files" meant
> archive files or source files.
>
> Can you live with this second draft?

I don't understand what this means:

ASF copyright correct in each top-level NOTICE.

Why is it necessary in addition to the following?

Top-level LICENSE and NOTICE correct for each distribution.


I think there needs to be a separate list of explanations that detail
the checks.

> Marvin Humphrey
>
> -
> 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: Release Verification Checklist

[sebb]

On 2 December 2013 13:52, Bertrand Delacretaz  wrote:
> Hi,
>
> On Wed, Nov 27, 2013 at 9:45 PM, Marvin Humphrey  
> wrote:
>> ...In response to Bertrand's proposal at , I've 
>> created
>> a draft release verification checklist:
>>
>> http://wiki.apache.org/incubator/ReleaseChecklist ...
>
> Thanks for this!
>
> I have just added an alternate proposal there, which avoids repeating
> the checklist items to make it easier to "review the review".
>
> I think managing and keeping such release manifests in svn, at least
> for incubating projects, would make the release process much clearer
> and easier to understand.

But it is much harder to update an SVN document compared with replying
to an e-mail.

If the proposal is adopted, then I think the comments should be signed
with ASF ids rather than initials (which may be ambiguous)

> -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: [VOTE] Release Apache Knox-0.3.1-incubating RC3

[sebb]

On 20 November 2013 16:09, larry mccay  wrote:
> Hello All,
>
> This is a call for a vote on Apache Knox Gateway 0.3.1 incubating.
>
> A vote was held on developer mailing list and it passed with 3 +1's, and 0
> -1's or +0's and now
> requires a vote on general@incubator.apache.org.
>
> The [VOTE] thread can be found at:
> http://mail-archives.apache.org/mod_mbox/incubator-knox-dev/201311.mbox/%3CCACRbFyjgLrCSahhtWWHK-%3DaeQFM4Oegbe3fQjs-RV2-TAnhdxA%40mail.gmail.com%3E
>
> The release candidate is a zip archive of the sources in:
> https://git-wip-us.apache.org/repos/asf/incubator-knox.git
> Branch v0.3.1 (git checkout -b v0.3.1)
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=tag;h=5a907022dbc2b0a8534de47fe7b8c871c4f075f9

The NOTICE file is wrong:

https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=blob_plain;f=NOTICE;hb=61e85e0b89b415361159bb973d050bdd8ab92acb

The lines enclosed in == need to be removed.

"This product includes software developed by"
should be
"This product includes software developed at"

There is another NOTICE and LICENSE file at
gatway-release/home
These are completely different from the ones at the top-level, and
mention a lot of 3rd party products.

Does the source archive really contain all the 3rd party products as source?
If so, then this needs to be in the NOTICE and LICENSE files at the
top-level of SCM and the source archive.
If not, the references need to be removed.

The N&L files must only relate to bits which are actually included in
the distribution (SCM/source archive/binary archive).

> Source archive zip file and signature are available from:
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip.asc

The source archive contains two copies of the binary archive
hadoop-examples.jar.
External binary dependencies should not be bundled in the source (nor
in the SCM).

> Checksums of the source archive:
>   SHA1:   04bb11360f57c0431c30cfb181e3199868fe6053
>
> The KEYS file can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/KEYS
>
> The release changes file can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/CHANGES
>
> The release has been signed with key (587C089B):
>   http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x82F9C371587C089B
>
> Vote will be open for 72 hours.

(a minimum of)

>
> thanks,
>
> --larry
>
> Larry McCay

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

Re: [VOTE] Release Apache Knox-0.3.1-incubating RC3

[sebb]

On 2 December 2013 20:17, Larry McCay  wrote:
> Thank you  again, Sebb.
> I am noting your new findings here and will fix them asap for the next
> release.
>
> I assume that your lack of an actual vote indicates that these fixes can be
> made in the next release and that you are not indicating that this RC
> should be abandoned. Please let me know if this is an inappropriate
> assumption.

Sorry, I should have said - I think the problems are blockers.
It's vital that the NOTICE and LICENSE files are correct for ASF releases.

So if I were the RM, I would want to redo the release.

>
> On Mon, Dec 2, 2013 at 2:30 PM, sebb  wrote:
>
>> On 20 November 2013 16:09, larry mccay  wrote:
>> > Hello All,
>> >
>> > This is a call for a vote on Apache Knox Gateway 0.3.1 incubating.
>> >
>> > A vote was held on developer mailing list and it passed with 3 +1's, and
>> 0
>> > -1's or +0's and now
>> > requires a vote on general@incubator.apache.org.
>> >
>> > The [VOTE] thread can be found at:
>> >
>> http://mail-archives.apache.org/mod_mbox/incubator-knox-dev/201311.mbox/%3CCACRbFyjgLrCSahhtWWHK-%3DaeQFM4Oegbe3fQjs-RV2-TAnhdxA%40mail.gmail.com%3E
>> >
>> > The release candidate is a zip archive of the sources in:
>> > https://git-wip-us.apache.org/repos/asf/incubator-knox.git
>> > Branch v0.3.1 (git checkout -b v0.3.1)
>> >
>> > Tag:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=tag;h=5a907022dbc2b0a8534de47fe7b8c871c4f075f9
>>
>> The NOTICE file is wrong:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=blob_plain;f=NOTICE;hb=61e85e0b89b415361159bb973d050bdd8ab92acb
>>
>> The lines enclosed in == need to be removed.
>>
>> "This product includes software developed by"
>> should be
>> "This product includes software developed at"
>>
>> There is another NOTICE and LICENSE file at
>> gatway-release/home
>> These are completely different from the ones at the top-level, and
>> mention a lot of 3rd party products.
>>
>> Does the source archive really contain all the 3rd party products as
>> source?
>> If so, then this needs to be in the NOTICE and LICENSE files at the
>> top-level of SCM and the source archive.
>> If not, the references need to be removed.
>>
>> The N&L files must only relate to bits which are actually included in
>> the distribution (SCM/source archive/binary archive).
>>
>> > Source archive zip file and signature are available from:
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip.asc
>>
>> The source archive contains two copies of the binary archive
>> hadoop-examples.jar.
>> External binary dependencies should not be bundled in the source (nor
>> in the SCM).
>>
>> > Checksums of the source archive:
>> >   SHA1:   04bb11360f57c0431c30cfb181e3199868fe6053
>> >
>> > The KEYS file can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/KEYS
>> >
>> > The release changes file can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/CHANGES
>> >
>> > The release has been signed with key (587C089B):
>> >
>> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x82F9C371587C089B
>> >
>> > Vote will be open for 72 hours.
>>
>> (a minimum of)
>>
>> >
>> > thanks,
>> >
>> > --larry
>> >
>> > Larry McCay
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

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

Re: [VOTE] Release Apache Knox-0.3.1-incubating RC3

[sebb]

On 2 December 2013 20:44, Kevin Minder  wrote:
> Sebb,
>
> Thanks for your careful review.  I'd like your continued insight into two
> specific issues that you have raised.
>
> WRT the NOTICE files in root vs gatway-release/home, this is actually an
> issue that I struggled with when laying things out initially.  We certainly
> don't include the source for 3rd party products anywhere.  This covers why
> they are not mentioned in NOTICE at the top level of the source
> repo/archive.  The NOTICE file in gatway-release/home ends up in the root
> of our binary distributions.  This binary distribution does contain the
> JARs for those 3rd party products.  Therefore I thought I was following the
> rules by having these two NOTICE files be different and represent the
> actual content of the respective archives.

I see.
In which case it would be better if the files were called something
like NOTICE.binary or NOTICE_binary and copied to the appropriate file
names as part of the assembly descriptor. That would avoid any
possible confusion for end-users.


The binary NOTICE still has "developed by" when it should be "developed at".

It's important that the NOTICE file only contains required attributions.
See http://www.apache.org/dev/licensing-howto.html#mod-notice

It seems to me that some (most?) of the references are *not* required.
For example the ANTLR license should be covered by the inclusion of
the text in the LICENSE file. It does not also need to be in NOTICE.
Similarly for ASM, Bouncy Castle etc.

See the following page for more info on what licenses are permitted in
binary distributions:
http://www.apache.org/legal/resolved.html

> For hadoop-examples.jar I understand your reaction.  I would like to try
> and justify the inclusion for this specific use case however.  This JAR is
> included for "ease of use", especially for first time users.  Basically to
> use Knox with Hadoop you need to have an existing Hadoop "application".
> Our user's guide walks through an example of uploading and running this
> sample Hadoop application. (It is not used at compile time at all).  If we
> don't check this into SCM and build it as part of Knox, that would create a
> tight coupling between Knox and a specific Hadoop version only used to
> create this post-install sample JAR file.  I think about this similar to
> including a sample JPEG in a image processor distribution.  There you
> wouldn't expect the JPEG to be build from source.

That's not a good analogy as jpegs are rarely built from source.

There has to be a better way to handle the Hadoop jar.

> All that being said, we
> certainly shouldn't have two copies, although fixing that will be an
> interesting maven challenge.

Assembly descriptors allow files to be copied to a different place in
the archive.
This is trivial, so there is definitely no need for *two* copies.

AFAIK Maven also allows jars to be included from the local repo, so it
should be possible to remove the copies from the source entirely.

> Thanks again for your continued feedback!
>
> Kevin.
>
>
> On Mon, Dec 2, 2013 at 3:24 PM, sebb  wrote:
>
>> On 2 December 2013 20:17, Larry McCay  wrote:
>> > Thank you  again, Sebb.
>> > I am noting your new findings here and will fix them asap for the next
>> > release.
>> >
>> > I assume that your lack of an actual vote indicates that these fixes can
>> be
>> > made in the next release and that you are not indicating that this RC
>> > should be abandoned. Please let me know if this is an inappropriate
>> > assumption.
>>
>> Sorry, I should have said - I think the problems are blockers.
>> It's vital that the NOTICE and LICENSE files are correct for ASF releases.
>>
>> So if I were the RM, I would want to redo the release.
>>
>> >
>> > On Mon, Dec 2, 2013 at 2:30 PM, sebb  wrote:
>> >
>> >> On 20 November 2013 16:09, larry mccay  wrote:
>> >> > Hello All,
>> >> >
>> >> > This is a call for a vote on Apache Knox Gateway 0.3.1 incubating.
>> >> >
>> >> > A vote was held on developer mailing list and it passed with 3 +1's,
>> and
>> >> 0
>> >> > -1's or +0's and now
>> >> > requires a vote on general@incubator.apache.org.
>> >> >
>> >> > The [VOTE] thread can be found at:
>> >> >
>> >>
>> http://mail-archives.apache.org/mod_mbox/incubator-knox-dev/201311.mbox/%3CCACRbFyjgLrCSahhtWWHK-%3DaeQFM4Oegbe3fQjs-RV2-TAnhdxA%40mail.gmail.com%3E
>> >> >
>> >> > The release candidate is a zip archive 

Re: [VOTE] Release HDT version 0.0.1.incubating (RC2)

[sebb]

On 29 November 2013 10:21, Rahul Sharma  wrote:
> Hi,
>
> I would like to call for a vote for Apache Hadoop Development Tools
> (incubating), version 0.0.1.incubating. The vote has happened of the dev
> mailing list and the community has approved the third release
> candidate(RC2) for Apache Hadoop Development Tools (incubating), version
> 0.0.1.incubating.The release has Zookeper and HDFS features from the
> *hadoop-eclipse-merge* codebase.The issues raised for RC0 and RC1 have been
> addressed in this release.
>
> 1 IPMC votes have already been cast:
>   Roman Shaposhnik (mentor)
>
> Please vote on releasing this package as Apache Hadoop Development Tools
> 0.0.1.incubating.
>
> [ ] +1 Release this package as Apache HDT 0.0.1.incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> PPMC Vote thread :
> http://apache.markmail.org/message/sqerudh5emqzqfrg
>
> Vote Result :
> http://apache.markmail.org/message/rvskqqernk4fmumt
>
> Source and binary files:
> http://people.apache.org/~rsharma/hdt-0.0.1.incubating-rc2/
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-hdt.git;a=commit;h=02f75eda16a8b91f0b35abad9487a9c83fd4c8d6

NOTICE says:

This product includes Eclipse Icons from
http://tech.joelbecker.net/articles/resources/5-eclipseicons - Eclipse
Public License v 1.0

However the LICENSE file does not include the EPL.

I think this is a blocker; any 3rd party inclusions must be
accompanied by their license, either in the LICENSE file or as a
separate file referenced from the LICENSE file. [The end user must be
able to find the licenses easily, not go searching through directory
trees].

Without knowing the text of the EPL, it's not possible to determine
whether there also needs to be a mention in the NOTICE file (the
LICENSE may be sufficient) It's vital that the NOTICE file only has
required elements in it; unnecessary content must be removed [1]

The binary archive contains some 3rd party libraries; these need to be
mentioned in the embedded LICENSE and perhaps the NOTICE file.

I noticed SLF4J - are there any others?

This is another blocker, IMO.

Note that the NOTICE & LICENSE files must relate to the distribution
to which they belong; generally this means that the ones in the source
archive match the ones at the top-level of SCM (i.e. git here); the
binary archive may require additional entries in LICENSE and possibly
NOTICE.

Also the word "Devlopment" appears in at least one NOTICE file as part
of the product name. Is that really the correct product name?

[1] http://www.apache.org/dev/licensing-howto.html#mod-notice

> PGP keys used to sign the release:
> https://dist.apache.org/repos/dist/dev/incubator/hdt/KEYS
>
> Some guideline to verify release can be found at :
> http://apache.markmail.org/message/qj3srhvozapbwmq6
>
> regards,
> Rahul

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

Re: [VOTE] Release Apache Knox-0.3.1-incubating RC3

[sebb]

Duplicated message.

I already responded to the other copy in the thread

On 2 December 2013 20:11, Kevin Minder  wrote:
> Sebb,
>
> Thanks for your careful review.  I'd like your continued insight into two
> specific issues that you have raised.
>
> WRT the NOTICE files in root vs gatway-release/home, this is actually an
> issue that I struggled with when laying things out initially.  We certainly
> don't include the source for 3rd party products anywhere.  This covers why
> they are not mentioned in NOTICE at the top level of the source
> repo/archive.  The NOTICE file in gatway-release/home ends up in the root of
> our binary distributions.  This binary distribution does contain the JARs
> for those 3rd party products.  Therefore I thought I was following the rules
> by having these two NOTICE files be different and represent the actual
> content of the respective archives.
>
> For hadoop-examples.jar I understand your reaction.  I would like to try and
> justify the inclusion for this specific use case however.  This JAR is
> included for "ease of use", especially for first time users.  Basically to
> use Knox with Hadoop you need to have an existing Hadoop "application".
> Our user's guide walks through an example of uploading and running this
> sample Hadoop application. (It is not used at compile time at all).  If we
> don't check this into SCM and build it as part of Knox, that would create a
> tight coupling between Knox and a specific Hadoop version only used to
> create this post-install sample JAR file.  I think about this similar to
> including a sample JPEG in a image processor distribution.  There you
> wouldn't expect the JPEG to be build from source.  All that being said, we
> certainly shouldn't have two copies, although fixing that will be an
> interesting maven challenge.
>
>
> Thanks again for your continued feedback!
>
> Kevin.
>
> On 12/2/13 2:30 PM, sebb wrote:
>>
>> On 20 November 2013 16:09, larry mccay  wrote:
>>>
>>> Hello All,
>>>
>>> This is a call for a vote on Apache Knox Gateway 0.3.1 incubating.
>>>
>>> A vote was held on developer mailing list and it passed with 3 +1's, and
>>> 0
>>> -1's or +0's and now
>>> requires a vote on general@incubator.apache.org.
>>>
>>> The [VOTE] thread can be found at:
>>>
>>> http://mail-archives.apache.org/mod_mbox/incubator-knox-dev/201311.mbox/%3CCACRbFyjgLrCSahhtWWHK-%3DaeQFM4Oegbe3fQjs-RV2-TAnhdxA%40mail.gmail.com%3E
>>>
>>> The release candidate is a zip archive of the sources in:
>>> https://git-wip-us.apache.org/repos/asf/incubator-knox.git
>>> Branch v0.3.1 (git checkout -b v0.3.1)
>>>
>>> Tag:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=tag;h=5a907022dbc2b0a8534de47fe7b8c871c4f075f9
>>
>> The NOTICE file is wrong:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=blob_plain;f=NOTICE;hb=61e85e0b89b415361159bb973d050bdd8ab92acb
>>
>> The lines enclosed in == need to be removed.
>>
>> "This product includes software developed by"
>> should be
>> "This product includes software developed at"
>>
>> There is another NOTICE and LICENSE file at
>> gatway-release/home
>> These are completely different from the ones at the top-level, and
>> mention a lot of 3rd party products.
>>
>> Does the source archive really contain all the 3rd party products as
>> source?
>> If so, then this needs to be in the NOTICE and LICENSE files at the
>> top-level of SCM and the source archive.
>> If not, the references need to be removed.
>>
>> The N&L files must only relate to bits which are actually included in
>> the distribution (SCM/source archive/binary archive).
>>
>>> Source archive zip file and signature are available from:
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip.asc
>>
>> The source archive contains two copies of the binary archive
>> hadoop-examples.jar.
>> External binary dependencies should not be bundled in the source (nor
>> in the SCM).
>>
>>> Checksums of the source archive:
>>>SHA1:   04bb11360f57c0431c30cfb181e3199868fe6053
>>>
>>> The KEYS file can be found at:
>>>
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/

Re: [VOTE] Release HDT version 0.0.1.incubating (RC2)

[sebb]

On 4 December 2013 03:29, Rahul Sharma  wrote:
> Thanks Sebb for explaining out in detail, since this is our first release I
> think we would require some guidance. We would fix the LICENSE and the
> NOTICE but there a few questions, in the same regard.
>
> This an eclipse plugin so we are using other Eclipse libs like EMF[1].
> These are based on EPL. The libs are not shipped because the eclipse
> runtime environment  takes care of them. Do they need a mention in the
> LICENSE/NOTICE ?

As I already wrote, only bits that are *included* in a distribution
need to be mentioned in the relevant N&L.

> Also the project is build using Tycho[2],  does it require to mention the
> same in LICENSE/NOTICE ?

See above.

You can / should mention these external requirements somewhere, e.g.
in a README or BUILDING file.

Note that there are some restrictions on 3rd party dependencies --
whether included or not.
See http://www.apache.org/legal/resolved.html

But the N&L files are only about *included* bits.

[Your mentors should really have been able to guide you on this, but I
see that only one bothered to vote on the podling list.]

> regards,
> Rahul
>
> [1]http://en.wikipedia.org/wiki/Eclipse_Modeling_Framework
> [2]http://www.sonatype.org/tycho/license
>
>
>
> On Tue, Dec 3, 2013 at 10:49 PM, sebb  wrote:
>
>> On 29 November 2013 10:21, Rahul Sharma  wrote:
>> > Hi,
>> >
>> > I would like to call for a vote for Apache Hadoop Development Tools
>> > (incubating), version 0.0.1.incubating. The vote has happened of the dev
>> > mailing list and the community has approved the third release
>> > candidate(RC2) for Apache Hadoop Development Tools (incubating), version
>> > 0.0.1.incubating.The release has Zookeper and HDFS features from the
>> > *hadoop-eclipse-merge* codebase.The issues raised for RC0 and RC1 have
>> been
>> > addressed in this release.
>> >
>> > 1 IPMC votes have already been cast:
>> >   Roman Shaposhnik (mentor)
>> >
>> > Please vote on releasing this package as Apache Hadoop Development Tools
>> > 0.0.1.incubating.
>> >
>> > [ ] +1 Release this package as Apache HDT 0.0.1.incubating
>> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
>> > [ ] -1 Do not release this package because...
>> >
>> > PPMC Vote thread :
>> > http://apache.markmail.org/message/sqerudh5emqzqfrg
>> >
>> > Vote Result :
>> > http://apache.markmail.org/message/rvskqqernk4fmumt
>> >
>> > Source and binary files:
>> > http://people.apache.org/~rsharma/hdt-0.0.1.incubating-rc2/
>> >
>> > The tag to be voted upon:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-hdt.git;a=commit;h=02f75eda16a8b91f0b35abad9487a9c83fd4c8d6
>>
>> NOTICE says:
>>
>> This product includes Eclipse Icons from
>> http://tech.joelbecker.net/articles/resources/5-eclipseicons - Eclipse
>> Public License v 1.0
>>
>> However the LICENSE file does not include the EPL.
>>
>> I think this is a blocker; any 3rd party inclusions must be
>> accompanied by their license, either in the LICENSE file or as a
>> separate file referenced from the LICENSE file. [The end user must be
>> able to find the licenses easily, not go searching through directory
>> trees].
>>
>> Without knowing the text of the EPL, it's not possible to determine
>> whether there also needs to be a mention in the NOTICE file (the
>> LICENSE may be sufficient) It's vital that the NOTICE file only has
>> required elements in it; unnecessary content must be removed [1]
>>
>> The binary archive contains some 3rd party libraries; these need to be
>> mentioned in the embedded LICENSE and perhaps the NOTICE file.
>>
>> I noticed SLF4J - are there any others?
>>
>> This is another blocker, IMO.
>>
>> Note that the NOTICE & LICENSE files must relate to the distribution
>> to which they belong; generally this means that the ones in the source
>> archive match the ones at the top-level of SCM (i.e. git here); the
>> binary archive may require additional entries in LICENSE and possibly
>> NOTICE.
>>
>> Also the word "Devlopment" appears in at least one NOTICE file as part
>> of the product name. Is that really the correct product name?
>>
>> [1] http://www.apache.org/dev/licensing-howto.html#mod-notice
>>
>> > PGP keys used to sign the release:
>> > https://dist.apache.org/repos/dist/dev/incubator/hdt/KEYS
>> >
>> > Some guideline to verify release can be found at :
>> > http://apache.markmail.org/message/qj3srhvozapbwmq6
>> >
>> > regards,
>> > Rahul
>>
>> -
>> 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: Release Verification Checklist

[sebb]

On 5 December 2013 10:37, Bertrand Delacretaz  wrote:
> Hi,
>
> On Tue, Dec 3, 2013 at 11:39 PM, Marvin Humphrey  
> wrote:
>> On Mon, Dec 2, 2013 at 5:52 AM, Bertrand Delacretaz
>>  wrote:
>> ...3.6 Release consists of source code only, no binaries
>>
>> Technically we allow some "binary" formats like .jpg, .png, etc. in releases
>> without the corresponding composite files from which they were exported
>> (assuming such composite files exist)...
>
> Agreed, I have added a TODO at
> https://wiki.apache.org/incubator/ReleaseChecklist - the manifest
> should point to a page at http://incubator.apache.org that explains
> such things in a bit more detail. Good opportunity to clarify that ;-)
>
>> ...Also, I wonder whether "no binaries"
>> may provoke newbies to ask "What?!  No binaries?!"...
>
> Which is good IMO, once we have a clear explanation.
>
> ...
>> 4.1 Based on its dev list activity, the project looks healthy
>>
>> 4.2 Based on its private list activity, the project looks healthy
>>
>> First, I think these two items should be struck because they belong in a
>> graduation checklist, not a release checklist...
>
> Agreed, I have removed them. Totally agree to keep the checklist as
> small as possible.
>
> I made some other minor changes as well, see wiki history if needed.
>
>>... Second, I'm amused that the "commits list" item was quietly dropped, but 
>>new
>> checklist items have been inserted regarding the dev and private lists...
>
> Pure oversight on my part, sorry...but what would we do if no reviewer
> follows the commit lists? I don't think that's a reason to kill a
> release.

Oversight of the commit list is vital; that is how we ensure that SCM
only contains material that is permitted.

The source release is then checked against SCM to ensure we are only
published vetted material.

If there is no review of the commit list, then the whole system breaks down.

> -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: Release Verification Checklist

[sebb]

Just discovered another important aspect of a release that is often overlooked.

The current source release artifacts must be released via the ASF
mirroring system.
Download pages must not point directly to the ASF servers; they must
use the mirror CGI scripts
Also old releases must not be left on the mirroring system; any
download links must use the ASF archive server.
The download pages must also include links to sigs and hashes and the
KEYS file, all of which must be on the ASF servers (not via mirrors).

There were at least two recent graduations that do (did) not follow these rules.
One provided links to the SVN dist/release area, the other links
directly to www.apache.org/dist


On 13 December 2013 17:48, ant elder  wrote:
> The N word wasn't particularly helpful or constructive, sorry. I do think
> the policy page should be kept simple and generic though, so isn't the
> place to be describing this experiment.
>
>...ant
>
>
> On Fri, Dec 13, 2013 at 3:39 PM, ant elder  wrote:
>
>> Well sorry but IMHO thats nonsense. The Maven decision was an isolated
>> incident and didn't change the way all future Incubator policy should
>> get decided. Insisting that this experiment is done via a change to
>> the main policy just makes it contentious when it doesn't need to be.
>> All the complexity in the language and approach, the three votes etc
>> is exactly why people get the idea that the ASF is a ridiculous place
>> with overbearing rules and process. Its just an experiment, use lazy
>> majority consensus and go try it with a podling.
>>
>>...ant
>>
>> On Fri, Dec 13, 2013 at 3:27 PM, Marvin Humphrey 
>> wrote:
>> > On Fri, Dec 13, 2013 at 12:18 AM, ant elder  wrote:
>> >> I'm also opposed to updating the policy document, so will be voting
>> against
>> >> this just for that.  Its just an experiment so you don't need to be
>> making a
>> >> permanent change to the policy page to try it, especially as its such a
>> >> clunky convoluted change.
>> >
>> > An explicit policy change is required because otherwise there would be
>> > ambiguity as to whether a release which passes under the modified regime
>> is an
>> > act of the Foundation and confers indemnity on the Release Manager.
>> >
>> > The language of the proposed change to the Policy page has been carefully
>> > composed.  It is highly isolated from the rest of our policy and has no
>> force
>> > except on the the experiment.
>> >
>> > This proposal is structured as an incremental, reversible change.  It is
>> > incremental because podlings must be opted in by vote of the IPMC to
>> > participate.  It is reversible because once the experiment has run its
>> course
>> > the relevant section of the policy page can be removed with zero impact
>> > through lazy consensus.
>> >
>> >> (And responding to another related comment in the thread - since when
>> have
>> >> policy updates not required consensus?)
>> >
>> > The 2008 proposal to allow distribution through Maven was enacted after a
>> > contentious majority-rule vote passed 15 to 12.
>> >
>> > Marvin Humphrey
>> >
>> > -
>> > 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 Spark 0.8.0-incubating (rc4)

[sebb]

On 14 December 2013 03:13, Patrick Wendell  wrote:
> Please vote on releasing the following candidate as Apache Spark
> (incubating) version 0.8.1.
>
> The tag to be voted on is v0.8.1-incubating (commit b87d31d):
> https://git-wip-us.apache.org/repos/asf/incubator-spark/repo?p=incubator-spark.git;a=commit;h=b87d31dd8eb4b4e47c0138e9242d0dd6922c8c4e

> The release files, including signatures, digests, etc can be found at:
> http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/

The source archive agrees with the tag, which is good.

However they both contain binaries, which is not good.
Third party jars should *not* be included in SCM nor in source releases.

> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/pwendell.asc

Where is the KEYS file?

> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-040/
>
> The documentation corresponding to this release can be found at:
> http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4-docs/

Not a blocker for the release artifacts themselves, but should be
fixed before any release announcement:

The download page

http://spark.incubator.apache.org/downloads.html

includes a link to the directory containing the sigs and hashes, but
does not link to the KEYS file.
Also it is normal to provide some instructions as to how to do the verification.

The website still invites users to sign up for the Spark 2013
conference which is over.

> For information about the contents of this release see:
> https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=blob;f=CHANGES.txt;h=ce0aeab524505b63c7999e0371157ac2def6fe1c;hb=branch-0.8
>
> A vote on this release has passed within the Spark PPMC [1].
>
> Please vote on releasing this package as Apache Spark 0.8.1-incubating!
>
> The vote is open until Tuesday, December 17th at 03:30 UTC and

s/until/until at least/

> passes if a majority of at least 3 +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Spark 0.8.1-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Spark, please see
> http://spark.incubator.apache.org/
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-spark-dev/201312.mbox/%3CCABPQxsuEYMn_JE0qEOcrt4J5-N1PJWgGcN7m0qzNefW7fsz2PA%40mail.gmail.com%3E
>
> (Note that at present the concluding message isn't shown due to lag in the
> mail archives.)

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

Re: [PROPOSAL] DataFu for Incubation

[sebb]

On 18 December 2013 22:49, Matthew Hayes  wrote:
> Hi all,
>
> I would like to share our draft ASF incubation proposal for DataFu, a library 
> that makes it easier to solve data problems in Hadoop and high level 
> languages based on it.

I am the only person to think that the last part of the name has
unfortunate connotations?
c.f. SNAFU which has the same last two characters.

> The proposal can be found here:
>
> https://wiki.apache.org/incubator/DataFuProposal
>
> The source code is available on GitHub:
>
> https://github.com/linkedin/datafu.
>
> The text of the proposal is copied below.  Feedback is appreciated!
>
> Thanks,
> Matt
>
> == Abstract ==
>
> Data``Fu makes it easier to solve data problems using Hadoop and higher level 
> languages based on it.
>
> == Proposal ==
>
> Data``Fu provides a collection of Hadoop Map``Reduce jobs and functions in 
> higher level languages based on it to perform data analysis.  It provides 
> functions for common statistics tasks (e.g. quantiles, sampling), Page``Rank, 
> stream sessionization, and set and bag operations.  Data``Fu also provides 
> Hadoop jobs for incremental data processing in Map``Reduce.
>
> == Background ==
>
> Data``Fu began two years ago as set of UDFs developed internally at 
> Linked``In, coming from our desire to solve common problems with reusable 
> components.  Recognizing that the community could benefit from such a 
> library, we added documentation, an extensive suite of unit tests, and open 
> sourced the code.  Since then there have been steady contributions to 
> Data``Fu as we encountered common problems not yet solved by it.  Others 
> outside Linked``In have contributed as well.  More recently we recognized the 
> challenges with efficient incremental processing of data in Hadoop and have 
> contributed a set of Hadoop Map``Reduce jobs as a solution.
>
> Data``Fu began as a project at Linked``In, but it has shown itself to be 
> useful to other organizations and developers as well as they have faced 
> similar problems.  We would like to share Data``Fu with the ASF and begin 
> developing a community of developers and users within Apache.
>
> == Rationale ==
>
> There is a strong need for well tested libraries that help developers solve 
> common data problems in Hadoop and higher level languages such as Pig, Hive, 
> Crunch, Scalding, etc.
>
> == Current Status ==
>
> === Meritocracy ===
>
> Our intent with this incubator proposal is to start building a diverse 
> developer community around Data``Fu following the Apache meritocracy model.  
> Since Data``Fu was initially open sourced in 2011, it has received 
> contributions from both within and outside Linked``In.  We plan to continue 
> support for new contributors and work with those who contribute significantly 
> to the project to make them committers.
>
> === Community ===
>
> Data``Fu has been building a community of developers for two years.  It began 
> with contributors from Linked``In and has received contributions from 
> developers at Cloudera since very early on.  It has been included included in 
> Cloudera’s Hadoop Distribution and Apache Bigtop.  We hope to extend our 
> contributor base significantly and invite all those who are interested in 
> solving large-scale data processing problems to participate.
>
> === Core Developers ===
>
> Data``Fu has a strong base of developers at Linked``In.  Matthew Hayes 
> initiated the project in 2011, and aside from continued contributions to 
> Data``Fu has also contributed the sub-project Hourglass for incremental 
> Map``Reduce processing.  Separate from Data``Fu he has also open sourced the 
> White Elephant project.  Sam Shah contributed a significant portion of the 
> original code and continues to contribute to the project.  William Vaughan 
> has been contributing regularly to Data``Fu for the past two years.  Evion 
> Kim has been contributing to Data``Fu for the past year.  Xiangrui Meng 
> recently contributed implementations of scalable sampling algorithms based on 
> research from a paper he published.  Chris Lloyd has provided some important 
> bug fixes and unit tests.  Mitul Tiwari has also contributed to Data``Fu.  
> Mathieu Bastian has been developing Map``Reduce jobs that we hope to include 
> in Data``Fu.  In addition he also leads the open source Gephi project.
>
> === Alignment ===
>
> The ASF is the natural choice to host the Data``Fu project as its goal of 
> encouraging community-driven open-source projects fits with our vision for 
> Data``Fu.  Additionally, other projects Data``Fu integrates with, such as 
> Apache Pig and Apache Hadoop, and in the future Apache Hive and Apache 
> Crunch, are hosted by the ASF and we will benefit and provide benefit by 
> close proximity to them.
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> The core developers have been contributing to Data``Fu for the past two 
> years.  There is very little risk of Data``Fu being abandoned given its 
> widesprea

Re: [PROPOSAL] DataFu for Incubation

[sebb]

OK, but the first association that came to my mind was SNAFU - perhaps
because it shares the last 3 letters with DataFu.

I just thought you ought to be aware that the name could have negative
connotations for some people.

On 19 December 2013 00:16, Matthew Hayes  wrote:
> When we came up with the name a couple years ago, it was inspired by "kung 
> fu", in a playful way as Roman mentioned.  Sort of like saying your Java Fu 
> or Python Fu is excellent.
>
> -Matt
> ____
> From: sebb [seb...@gmail.com]
> Sent: Wednesday, December 18, 2013 3:57 PM
> To: general@incubator.apache.org
> Subject: Re: [PROPOSAL] DataFu for Incubation
>
> On 18 December 2013 22:49, Matthew Hayes  wrote:
>> Hi all,
>>
>> I would like to share our draft ASF incubation proposal for DataFu, a 
>> library that makes it easier to solve data problems in Hadoop and high level 
>> languages based on it.
>
> I am the only person to think that the last part of the name has
> unfortunate connotations?
> c.f. SNAFU which has the same last two characters.
>
>> The proposal can be found here:
>>
>> https://wiki.apache.org/incubator/DataFuProposal
>>
>> The source code is available on GitHub:
>>
>> https://github.com/linkedin/datafu.
>>
>> The text of the proposal is copied below.  Feedback is appreciated!
>>
>> Thanks,
>> Matt
>>
>> == Abstract ==
>>
>> Data``Fu makes it easier to solve data problems using Hadoop and higher 
>> level languages based on it.
>>
>> == Proposal ==
>>
>> Data``Fu provides a collection of Hadoop Map``Reduce jobs and functions in 
>> higher level languages based on it to perform data analysis.  It provides 
>> functions for common statistics tasks (e.g. quantiles, sampling), 
>> Page``Rank, stream sessionization, and set and bag operations.  Data``Fu 
>> also provides Hadoop jobs for incremental data processing in Map``Reduce.
>>
>> == Background ==
>>
>> Data``Fu began two years ago as set of UDFs developed internally at 
>> Linked``In, coming from our desire to solve common problems with reusable 
>> components.  Recognizing that the community could benefit from such a 
>> library, we added documentation, an extensive suite of unit tests, and open 
>> sourced the code.  Since then there have been steady contributions to 
>> Data``Fu as we encountered common problems not yet solved by it.  Others 
>> outside Linked``In have contributed as well.  More recently we recognized 
>> the challenges with efficient incremental processing of data in Hadoop and 
>> have contributed a set of Hadoop Map``Reduce jobs as a solution.
>>
>> Data``Fu began as a project at Linked``In, but it has shown itself to be 
>> useful to other organizations and developers as well as they have faced 
>> similar problems.  We would like to share Data``Fu with the ASF and begin 
>> developing a community of developers and users within Apache.
>>
>> == Rationale ==
>>
>> There is a strong need for well tested libraries that help developers solve 
>> common data problems in Hadoop and higher level languages such as Pig, Hive, 
>> Crunch, Scalding, etc.
>>
>> == Current Status ==
>>
>> === Meritocracy ===
>>
>> Our intent with this incubator proposal is to start building a diverse 
>> developer community around Data``Fu following the Apache meritocracy model.  
>> Since Data``Fu was initially open sourced in 2011, it has received 
>> contributions from both within and outside Linked``In.  We plan to continue 
>> support for new contributors and work with those who contribute 
>> significantly to the project to make them committers.
>>
>> === Community ===
>>
>> Data``Fu has been building a community of developers for two years.  It 
>> began with contributors from Linked``In and has received contributions from 
>> developers at Cloudera since very early on.  It has been included included 
>> in Cloudera’s Hadoop Distribution and Apache Bigtop.  We hope to extend our 
>> contributor base significantly and invite all those who are interested in 
>> solving large-scale data processing problems to participate.
>>
>> === Core Developers ===
>>
>> Data``Fu has a strong base of developers at Linked``In.  Matthew Hayes 
>> initiated the project in 2011, and aside from continued contributions to 
>> Data``Fu has also contributed the sub-project Hourglass for incremental 
>> Map``Reduce processing.  Separate from Data``Fu he has also open sourced the 
>> White Elephant project.  Sam Sha

Re: Question about jar files in svn.

[sebb]

On 19 December 2013 18:26, Henry Saputra  wrote:
> But at the end, when a podling prepare a release there should not
> include jar files as part of the source release artifacts to be VOTED
> on, is this correct?

I think that depends on what the jar files are.
For example. Apache Commons Compress includes some jar files in SVN
and the source release as part of the test data.

But I would not expect to find "external" jar files in the source release.

> - Henry
>
> On Thu, Dec 19, 2013 at 9:21 AM, Marvin Humphrey  
> wrote:
>> On Wed, Dec 18, 2013 at 7:45 PM, Greg Trasuk  wrote:
>>> We’re having a discussion over in d...@river.apache.org that was triggered 
>>> by
>>> the recent discussion here about the Spark podling release.
>>
>> The River discussions seem to be playing out productively.  Here are links 
>> for
>> other people who may be interested:
>>
>> https://issues.apache.org/jira/browse/RIVER-432
>> http://markmail.org/thread/abppti56ipnhnnfy
>>
>>> To be more specific, there doesn’t seem to be any doubt that jars shouldn’t
>>> be included in source release packages, but would it be fair to say that
>>> they should also not be in the svn?
>>
>> My understanding is that it is fine to store jars in version control outside
>> of the main source tree, analogous to providing a separate "-deps" download.
>> Between that and technical solutions which download deps on the fly such as
>> Ivy and Maven, I think that renders the question about whether binaries can
>> reside in the main source tree within version control moot.
>>
>> But there's no strictly enforced policy AFAIK because we discourage people
>> from considering our source control repositories distribution points.  (Note
>> to podlings: this is why we make links to source control only available
>> through the developer portions of our websites, etc.)  That way we don't have
>> to be rigid about enforcing the policies which apply to releases at every
>> single commit point, even as we make best efforts to keep our trees clean.
>>
>> FWIW, the same principles which give us a measure of flexibility about 
>> LICENSE
>> and NOTICE in version control could arguably apply to jar files as well.
>> Here's Board member Doug Cutting back in September on legal-discuss@apache:
>>
>> http://s.apache.org/GNP
>>
>> I think perhaps you're looking for clear lines where things are
>> actually a bit fuzzy.  Certainly releases are official distributions
>> and need LICENSE and NOTICE files.  That line is clear.  On the other
>> hand, we try to discourage folks from thinking that source control is
>> a distribution.  Rather we wish it to be considered our shared
>> workspace, containing works in progress, not yet always ready for
>> distribution to folks outside the foundation.  But, since we work in
>> public, folks from outside the foundation can see our shared workspace
>> and might occasionally mistake it for an official distribution.  We'd
>> like them to still see a LICENSE and NOTICE file.  So it's not a
>> hard-and-fast requirement that every tree that can possibly be checked
>> out have a LICENSE and NOTICE file at its root, but it's a good
>> practice for those trees that are likely to be checked out have them,
>> so that folks who might consume them are well informed.
>>
>> Again, policy flexibility with respect to version control becomes academic if
>> you can restructure the build.  Nevertheless, I hope that this additional
>> background is helpful for River's ongoing discussions.
>>
>> Cheers,
>>
>> Marvin Humphrey
>>
>> -
>> 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: Question about jar files in svn.

[sebb]

On 19 December 2013 18:57, Alex Harui  wrote:
> My understanding of the link I posted way back is that the source package
> cannot contain compiled output that will be executed by the customer.
> IMO, whether it is "external" or not doesn't matter.  The JAR used by the
> Compress tests is hopefully just data, not some part of its functionality.

Yes, the jars are test data.

> On 12/19/13 10:40 AM, "Henry Saputra"  wrote:
>
>>Ah I see.
>>
>>So the point of concern is the "external" jars, but jars that are
>>generated by the project itself (for example for tests) should be
>>fine?

Again, that's ambiguous.

I would not expect to find jars of the project source in source releases.

Note that the Compress test jars were manually created on various
different systems.

>>
>>- Henry
>>
>>On Thu, Dec 19, 2013 at 10:34 AM, sebb  wrote:
>>> On 19 December 2013 18:26, Henry Saputra 
>>>wrote:
>>>> But at the end, when a podling prepare a release there should not
>>>> include jar files as part of the source release artifacts to be VOTED
>>>> on, is this correct?
>>>
>>> I think that depends on what the jar files are.
>>> For example. Apache Commons Compress includes some jar files in SVN
>>> and the source release as part of the test data.
>>>
>>> But I would not expect to find "external" jar files in the source
>>>release.
>>>
>>>> - Henry
>>>>
>>>> On Thu, Dec 19, 2013 at 9:21 AM, Marvin Humphrey
>>>> wrote:
>>>>> On Wed, Dec 18, 2013 at 7:45 PM, Greg Trasuk 
>>>>>wrote:
>>>>>> We¹re having a discussion over in d...@river.apache.org that was
>>>>>>triggered by
>>>>>> the recent discussion here about the Spark podling release.
>>>>>
>>>>> The River discussions seem to be playing out productively.  Here are
>>>>>links for
>>>>> other people who may be interested:
>>>>>
>>>>> https://issues.apache.org/jira/browse/RIVER-432
>>>>> http://markmail.org/thread/abppti56ipnhnnfy
>>>>>
>>>>>> To be more specific, there doesn¹t seem to be any doubt that jars
>>>>>>shouldn¹t
>>>>>> be included in source release packages, but would it be fair to say
>>>>>>that
>>>>>> they should also not be in the svn?
>>>>>
>>>>> My understanding is that it is fine to store jars in version control
>>>>>outside
>>>>> of the main source tree, analogous to providing a separate "-deps"
>>>>>download.
>>>>> Between that and technical solutions which download deps on the fly
>>>>>such as
>>>>> Ivy and Maven, I think that renders the question about whether
>>>>>binaries can
>>>>> reside in the main source tree within version control moot.
>>>>>
>>>>> But there's no strictly enforced policy AFAIK because we discourage
>>>>>people
>>>>> from considering our source control repositories distribution points.
>>>>> (Note
>>>>> to podlings: this is why we make links to source control only
>>>>>available
>>>>> through the developer portions of our websites, etc.)  That way we
>>>>>don't have
>>>>> to be rigid about enforcing the policies which apply to releases at
>>>>>every
>>>>> single commit point, even as we make best efforts to keep our trees
>>>>>clean.
>>>>>
>>>>> FWIW, the same principles which give us a measure of flexibility
>>>>>about LICENSE
>>>>> and NOTICE in version control could arguably apply to jar files as
>>>>>well.
>>>>> Here's Board member Doug Cutting back in September on
>>>>>legal-discuss@apache:
>>>>>
>>>>> http://s.apache.org/GNP
>>>>>
>>>>> I think perhaps you're looking for clear lines where things are
>>>>> actually a bit fuzzy.  Certainly releases are official
>>>>>distributions
>>>>> and need LICENSE and NOTICE files.  That line is clear.  On the
>>>>>other
>>>>> hand, we try to discourage folks from thinking that source
>>>>>control is
>>>>> a distribution.  Rather we wish it

Re: Question about jar files in svn.

[sebb]

On 23 December 2013 05:50, David Crossley  wrote:
> Marvin Humphrey wrote:
>> Greg Trasuk wrote:
>> >
>> > Thanks everyone for the input.  To summarize, it appears that the consensus
>> > argument is:
>> >
>> > - Jar files are not prohibited by policy in project repositories (svn),
>> >   although they may not make a lot of sense.
>> > - Source distributions must not distribute executable code in binary form.
>> >   i.e. Don’t ship dependency jars in the source archive.  However it may be
>> >   acceptable to include things like jar files that are processed during
>> >   testing (sample archives, for instance).
>> > - The project repositories are not generally considered “distributions”, 
>> > but
>> >   we need to be a little careful to avoid users’ confusion on this point.
>
> Regarding that last part, i reckon that is about: only referring
> the development community to the development resources and not
> instructing users to do that.

However, many projects refer to SCM repos on "public" pages, some even
on the download page.
Also, projects that use Maven will have the SCM URLs in the POM.
Maven generated sites will have the Source Repo as part of the
standard documentation.
Such projects should ensure that the SCM has appropriate N&L files at
the top level.

Note also that Roy [1] at least considers that SCM should be classed
as a distribution.

See also [2] and [3]

[1] 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200907.mbox/%3C7A0220B7-5DF1-4F4C-8C27-6CA8A175CFCD%40gbiv.com%3E
[2] 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200907.mbox/%3C1706952606.1247865134823.JavaMail.jira%40brutus%3E
[3] 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200907.mbox/%3C1809771433.1247865614827.JavaMail.jira%40brutus%3E

> -David
>
> -
> 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: LICENSE and NOTICE Role Models

[sebb]

On 23 December 2013 15:28, Kevin Minder  wrote:
> I was thinking that the real problem is that each new project is forced to
> rediscover the right thing to do each time.  From my POV there really aren't
> that many licenses out there.  If there were just a wiki that said...
> 1) If you include source with X license, then Y must go in LICENSE and Z in
> NOTICE.
> 2) If you use a binary with X license, then Y must go in LICENSE and Z in
> NOTICE.
> As new or "one off" license are discovered the legal or whomever actually
> knows the rules adds to the wiki.
>

As far as LICENSE is concerned, the rule is simple, the full license
text must be provided with the bundle that includes the bits.
This can either be in the LICENSE file itself, or (generally better)
the file name should be noted in LICENSE.
Since 3rd party licenses may vary between versions, the LICENSE file
should state the product name *and version* for example:

"MegaCorp Foobar version 3.2.1 is included under license XYZ, see file
res/licenses/XYZ.txt"

A separate issue is whether the inclusion is allowed - but if it is,
the above applies.

For the NOTICE file the rule is also simple - it is for *required" notices only.
However, the problem here is that it is not always obvious what is required.
For some licenses, it is sufficient to have the license text.

I don't think a Wiki page is suitable as the formal documentation for
this however.
It needs to be part of the foundation website.

> On 12/22/13 10:08 PM, Marvin Humphrey wrote:
>>
>> On Wed, Dec 11, 2013 at 2:24 AM, Stephen Connolly
>>  wrote:
>>
>>> It would be great if we could get a resolution on some of the JIRA's in
>>> legal, e.g.
>>>
>>> https://issues.apache.org/jira/browse/LEGAL-26
>>> https://issues.apache.org/jira/browse/LEGAL-27
>>> https://issues.apache.org/jira/browse/LEGAL-31
>>> https://issues.apache.org/jira/browse/LEGAL-136
>>
>> +1
>>
>> The continuing lack of clear resolution also impacts the Incubator.
>> Podlings
>> challenge us with "You say do X, but Apache Foo does Y -- where is it
>> documented that we have to do X?"  Then we go down the path of hunting up
>> Board member quotes and past threads on legal-discuss.
>>
>> It would make things easier on all Apache TLPs and Incubator podlings if
>> we
>> could get the following elements in sync:
>>
>> *   Apache Legal policy documentation.
>> *   http://www.apache.org/dev/licensing-howto.html
>> *   Maven's processes.
>> *   The actual LICENSE/NOTICE practices for the ASF's top ten or so most
>>  popular products.
>>
>>> The most critical one to the Maven PMC is LEGAL-26:
>>
>> Perhaps, though the way that Maven would implement LEGAL-26
>> (LICENSE/NOTICE in
>> svn) is impacted by LEGAL-27 (LICENSE/NOTICE must reference *only* bundled
>> dependencies).
>>
>> I'm not on the Legal Affairs committee, but I did write most of the
>> Licensing
>> How-To.  Come January, I'd like to do what I can to move the process
>> forward.
>> A lot of valuable developer time has been wasted over the years rehashing
>> these issues over and over again, and it's not like most developers relish
>> this stuff.  Clear policy documentation would be a valuable contribution
>> to
>> all of the Foundation's projects.
>>
>> Marvin Humphrey
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader of
> this message is not the intended recipient, you are hereby notified that any
> printing, copying, dissemination, distribution, disclosure or forwarding of
> this communication is strictly prohibited. If you have received this
> communication in error, please contact the sender immediately and delete it
> from your system. 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: Release Retention Policy

[sebb]

On 24 December 2013 00:03, John D. Ament  wrote:
> Hi all,
>
> Recently, DeltaSpike got a ticket to clean up the old dist area in SVN
> from when it was a podling.  Since we have everything tagged in git,
> it's not a big deal to recreate the release in case something goes
> wrong, but looking at it we only have 1 release (0.3-incubating) in
> there.
>
> I'm curious though about the retention policy.  If I delete this
> directory, do I need to the release somewhere else?  Or is it, delete
> it and it's gone, you'll need to rely on git tags.

See:
http://www.apache.org/dev/release.html#archived

Everything on the ASF dist/ tree is archived.

> John
>
> -
> 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: Log4cxx project bootstrapped

[sebb]

On 2 January 2014 10:28, Christian Grobmeier  wrote:
> Hello,
>
> just a short message to let you know i moved the log4cxx tree to the
> incubation tree and committed this auth:

This has caused a problem for the projects.apache.org site.
Please update the location of the DOAP.

> Index: asf-authorization-template
> ===
> --- asf-authorization-template  (Revision 892487)
> +++ asf-authorization-template  (Arbeitskopie)
> @@ -241,6 +241,7 @@
>  libcloud-pmc={reuse:pit-authorization:libcloud-pmc}
>  logging-pmc={reuse:pit-authorization:logging-pmc}
>  logging={ldap:cn=logging,ou=groups,dc=apache,dc=org}
> +log4cxx=grobmeier,sdeboy,fseydoux,chand,nickwilliams,tschoening,rhys,joseph,alexz
>  lucene={ldap:cn=lucene,ou=groups,dc=apache,dc=org}
>  lucene-pmc={reuse:pit-authorization:lucene-pmc}
>  lucene-c=ehatcher,rooneg,pquerna
> @@ -865,6 +866,9 @@
>  [/incubator/lcf]
>  @lucene-connectors = rw
>
> +[/incubator/log4cxx]
> +@log4cxx = rw
> +
>
> With that, the podling is ready to go
>
> Cheers,
> Christian
>
>
> ---
> http://www.grobmeier.de
> The Zen Programmer: http://bit.ly/12lC6DL
> @grobmeier
> GPG: 0xA5CC90DB
>
> -
> 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: wiki edit perms for SteveLoughran

[sebb]

Done

On 3 January 2014 11:54, Steve Loughran  wrote:
> Hi,,
>
> I want to start a proposal for incubating my Hoya work. Can I have edit
> permissions for SteveLoughran?
>
> TIA,
>
> steve

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

Re: Wiki write access for CharlesSimpson

[sebb]

Done

On 7 January 2014 15:15, Charles Simpson  wrote:
> Could I have wiki write access for CharlesSimpson to contribute to the Hoya
> incubator proposal?
>
> Thanks,
>
> Charles

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

Re: Wiki write permissions for LarryMcCay

[sebb]

Done

On 8 January 2014 18:42, larry mccay  wrote:
> Could I please have wiki write access for LarryMcCay to contribute to the
> Hoya
> incubator proposal?
>
> Thanks!

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

Re: January 2014 Incubator report timeline

[sebb]

Yes, I replied directly to them to reduce noise on the main list.
(unlike this message!)

I figured that Wiki admins would (should?) be following the Wiki
commit messages so would see the update to the Contributors page.

On 10 January 2014 03:47, Marvin Humphrey  wrote:
> On Thu, Jan 9, 2014 at 4:27 PM, lars hofhansl  wrote:
>
>> my username is LarsHofhansl
>
> It looks like sebb has whitelisted both you and Andrew.  Thanks, sebb!
>
> Marvin Humphrey
>
> -
> 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: Hoya Proposal

[sebb]

Jenny ?

On 13 January 2014 22:21, Ted Dunning  wrote:
> Too many people will read that as Jena, the city in Thuringia.
>
> https://en.wikipedia.org/wiki/Jena
>
> -1
>
>
>
>
> On Mon, Jan 13, 2014 at 1:57 PM, Andy Seaborne  wrote:
>
>> On 13/01/14 20:25, Bertrand Delacretaz wrote:
>>
>>> On Mon, Jan 13, 2014 at 5:36 PM, Bertrand Delacretaz
>>>  wrote:
>>>
 On Mon, Jan 13, 2014 at 3:33 PM, Steve Loughran 
 wrote:

> ...What do people think about a project name "Hyena"? It's close
> enough, lives
> in the savannah...
>

 I think it's too close to http://jena.apache.org/

>>>
>>> to be clear, this is a strong -1 from me, having confusing project
>>> names inside Apache is not ok. Hyena and Jena sound exactly the same
>>> in several languages, unfortunately.
>>>
>>
>> The "j-e-n" in "Jena" is like "Jen-kins" or "Gen-er-al".
>>
>> It is derived from "Jennifer"
>>
>> http://en.wikipedia.org/wiki/Jennifer_%28given_name%29
>>
>> which is often, but not here, with "nn":
>>
>> http://en.wikipedia.org/wiki/Jenna
>>
>> Andy
>>
>>
>>> -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

Voting status page - what does "Resolved" mean?

[sebb]

The voting status page shows recently closed votes.

All of these have status "Resolved"

What does this status actually mean?

Does it mean that the vote thread has been closed?
If so, then the column in the table seems redundant as it will never
show anything else.

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

Re: lost dist changes

[sebb]

It would help to know what was the latest commit in the backup.

Can then in theory check the commit e-mails to see what occurred
since, and recover any missing files from archive.a.o (presumably)

On 26 January 2014 23:17, Joseph Schaefer  wrote:
> Unfortunately we had to restore dist.apache.org
> from offsite backups and a few commits to the incubator
> tree were lost as a result.  Projects are encouraged
> to check out their dist trees and ensure that the
> latest content is available via dist.apache.org and
> releases at www.apache.org/dist/incubator
>
> Thanks.
>
> -
> 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] Graduation of Apache Spark from the Incubator

[sebb]

On 1 February 2014 02:04, Matei Zaharia  wrote:
> Hi folks,
>
> The Apache Spark community has VOTEd to graduate from the Apache incubator 
> (vote thread: http://s.apache.org/kq, discussion thread: 
> http://s.apache.org/aEQ).
>
> I'm now calling an official IPMC VOTE to make this happen as well. Here's the 
> community tally:
>
> +1
> Matei Zaharia
> Reynold Xin
> Tathagata Das
> Sean McNamara
> Patrick Wendell
> Mark Hamstra
> Chris Mattmann *
> Tom Graves
> Henry Saputra *
> Andy Konwinski
> Josh Rosen
> Mosharaf Chowdhury
> Mridul Muralidharan
> Nick Pentreath
> Andrew Xia
> Haoyuan Li
> Sandy Ryza
> Sebastian Schelter *
> Kostas Sakellis
> Christopher Nguyen
> Aaron Davidson
> Shivaram Venkataraman
> Kay Ousterhout
> Evan Sparks
> Xuefeng Wu
> Konstantin Boudnik
> Rahul Chugh
> Prashant Sharma
> Stephen Haberman
> Prabeesh K.
> Saisai Shao
> Junfeng Feng
> Jason Dai
> Stevo Slavic
> Heiko Braun
> Xia Zhu
> Manoj Awasthi
>
> +0
> (none)
>
> -1
> (none)
>
> * indicates IPMC member
>
> We've made three releases in the incubator, added new committers and IPMC 
> members, checked off the various requirements to migrate the development 
> process to the ASF, and more generally worked to build this community in the 
> Apache way.
>
> Please VOTE to graduate Apache Spark from the incubator. I'll leave the VOTE 
> open for 96 hours, until February 4th, 2014. The graduation resolution is 
> pasted below.
>
> Thanks!
>
> Matei and the Apache Spark community
>
>  snip
>
> 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 fast and flexible large-scale data analysis
> on clusters.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Spark Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
>
> RESOLVED, that the Apache Spark Project be and hereby is
> responsible for the creation and maintenance of software
> related to efficient cluster management, resource isolation
> and sharing across distributed applications; and be it further
> RESOLVED, that the office of "Vice President, Apache Spark" 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 Spark Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Spark 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 Spark Project:
>
> * Mosharaf Chowdhury 
> * Jason Dai 
> * Tathagata Das 
> * Ankur Dave 
> * Aaron Davidson 
> * Thomas Dudziak 
> * Robert Evans 
> * Thomas Graves 
> * Andy Konwinski 
> * Stephen Haberman 
> * Mark Hamstra 
> * Shane Huang 
> * Ryan LeCompte 
> * Haoyuan Li 
> * Sean McNamara 
> * Mridul Muralidharam 
> * Kay Ousterhout 
> * Nick Pentreath 
> * Imran Rashid 
> * Charles Reiss 
> * Josh Rosen 
> * Prashant Sharma 
> * Ram Sriharsha 
> * Shivaram Venkataraman 
> * Patrick Wendell 
> * Andrew Xia 
> * Reynold Xin 
> * Matei Zaharia 

-1

There is a mix of ASF e-mails and non-ASF e-mails above.
All the committers proposed for the initial PMC must (I assume)
already have ASF logins, so please can the ASF mails be used
consistently throughout?
External e-mails are liable to change over time, so are not a good identifier.


> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be
> appointed to the office of Vice President, Apache Spark, 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 Apache Spark Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Spark podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Spark podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
> 
>
>
> -
> 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] Graduation of Apache Spark from the Incubator

[sebb]

On 4 February 2014 20:26, Matei Zaharia  wrote:
> Hi Craig,
>
> Thanks for the list, I'm following up with these folks to get them accounts. 
> I think some people filed an ICLA but never received an account and were thus 
> never added to the repo. A couple of questions:
>
> - What do you mean by "does not appear to be a committer" -- that they 
> weren't added to the repo? All of these individuals have contributed code, 
> but it was merged by someone else.
>
> - Andrew Xia is listed as having an ICLA on file here: 
> http://people.apache.org/committer-index.html

All ICLAs are recorded.

The ones currently without availids (ASF login name) are listed here:

https://people.apache.org/committer-index.html#unlistedclas

> Matei
>
>
>
> On Feb 4, 2014, at 8:12 AM, Craig L Russell  wrote:
>
>> -1 for this resolution as written.
>>
>> Some of the proposed PMC members have filed ICLAs but are not committers; 
>> some have not even filed ICLAs; some appear to have been part of the 
>> original proposal but have not contributed to the project during incubation.
>>
>> Regards,
>>
>> Craig
>>
>> On Jan 31, 2014, at 6:04 PM, Matei Zaharia wrote:
>>
>>> RESOLVED, that the persons listed immediately below be and
>>> hereby are appointed to serve as the initial members of the
>>> Apache Spark Project:
>>>
>>> * Mosharaf Chowdhury 
>>> * Jason Dai 
>>> * Tathagata Das 
>>
>> This person does not appear to be a committer.
>>
>>> * Ankur Dave 
>>
>> This person does not appear to be a committer.
>>
>>> * Aaron Davidson 
>>
>> This person does not appear to be a committer.
>>
>>> * Thomas Dudziak 
>>> * Robert Evans 
>>> * Thomas Graves 
>>> * Andy Konwinski 
>>> * Stephen Haberman 
>>> * Mark Hamstra 
>>> * Shane Huang 
>>> * Ryan LeCompte 
>>> * Haoyuan Li 
>>> * Sean McNamara 
>>> * Mridul Muralidharam 
>>
>> This person does not appear to be a committer.
>>
>>> * Kay Ousterhout 
>>
>> There is no ICLA on file for this person.
>>
>>> * Nick Pentreath 
>>> * Imran Rashid 
>>
>> This person does not appear to be a committer.
>>
>>> * Charles Reiss 
>>> * Josh Rosen 
>>> * Prashant Sharma 
>>> * Ram Sriharsha 
>>
>> There is no ICLA on file for this person.
>>
>>> * Shivaram Venkataraman 
>>> * Patrick Wendell 
>>> * Andrew Xia 
>>
>> There is no ICLA on file for this person.
>>
>>> * Reynold Xin 
>>> * Matei Zaharia 
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:craig.russ...@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>> -
>> 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] Graduation of Apache Knox from the Incubator

[sebb]

The knox incubation status page website link generates a 404.

On 7 February 2014 04:49, Chris Mattmann  wrote:
> Hi Everyone,
>
> The Apache Knox Incubating podling has VOTEd to graduate from the
> Incubator.
> The community VOTE has passed below with the provided tallies. The
> graduation
> resolution draft is pasted below. We welcome your VOTE'ing on Knox's
> graduation
> from the Incubator.
>
> I will leave this VOTE open for at least 72 hours.
>
> [ ] +1 Recommend graduation of Apache Knox from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't recommend graduation of Apache Knox from the Incubator
> because..
>
> Thanks for your VOTE!
>
> Cheers,
> Chris
>
>
>
> -Original Message-
> From: Chris Mattmann 
> Reply-To: "d...@knox.incubator.apache.org" 
> Date: Thursday, February 6, 2014 8:38 PM
> To: "d...@knox.incubator.apache.org" 
> Subject: [RESULT] [VOTE] Graduation of Apache Knox from the Incubator
>
>>Hi Guys,
>>
>>
>>Sorry it took forever for me to close this VOTE! :)
>>
>>Here are the tallies:
>>
>>+1
>>
>>Chris Mattmann*
>>Alan Gates*
>>Larry McCay
>>Dilli Arumugam
>>Kevin Minder
>>
>>* - indicates IPMC
>>
>>This VOTE has passed. I'll now take it to general@incubator.apache.org.
>>
>>Thanks for VOTE'ing!
>>
>>Cheers,
>>Chris
>>
>>-Original Message-
>>From: Chris Mattmann 
>>Reply-To: "d...@knox.incubator.apache.org" 
>>Date: Thursday, December 19, 2013 2:41 PM
>>To: "d...@knox.incubator.apache.org" 
>>Subject: [VOTE] Graduation of Apache Knox from the Incubator
>>
>>>Hi Folks,
>>>
>>>
>>>Time to VOTE on the following resolution to graduate
>>>Apache Knox from the Apache Incubator. Here's a draft
>>>resolution to VOTE on (with Kevin listed as PMC chair).
>>>
>>>I'll leave the VOTE open for the next week. If all goes
>>>well here, I'll take it to general@incubator.a.o and if
>>>all goes well there, we'll take it to the Apache board
>>>for consideration in their January 2014 board meeting.
>>>
>>>Thanks!
>>>
>>>[ ] +1 Graduate Apache Knox from the Incubator
>>>[ ] +0 Don't care.
>>>[ ] -1 Don't graduate Apache Knox from the Incubator because..
>>>
>>>Thanks and here's my enthusiastic +1!
>>>
>>>Cheers,
>>>Chris
>>>
>>>--draft resolution
>>>
>>>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 secure access for Apache Hadoop clusters.
>>>
>>>  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>  Committee (PMC), to be known as the "Apache Knox Project" be
>>>  and hereby is established pursuant to Bylaws of the Foundation;
>>>  and be it further
>>>
>>>  RESOLVED, that the Apache Knox Project be and hereby is
>>>  responsible for the creation and maintenance of software
>>>  related to secure access for Apache Hadoop clusters; and be it further
>>>
>>>  RESOLVED, that the office of "Vice President, Apache Knox", 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 Knox Project, and to have primary responsibility for
>>>management of the projects within the scope of responsibility
>>>  of the Apache Knox 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 Knox Project:
>>>
>>>* Christopher Douglas 
>>>* Chris Mattmann 
>>>* Devaraj Das 
>>>* Dilli Dorai 
>>>* Alan Gates 
>>>* John Speidelkminder 
>>>* Kevin Minder 
>>>* Larry McCay 
>>>* Mahadev Konar 
>>>* Owen O'Malley 
>>>* Sumit Mohanty 
>>>* Tom Beerbower 
>>>* Thomas White 
>>>* Venkatesh Seetharam 
>>>
>>>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kevin Minder be
>>> appointed to the office of Vice President, Apache Knox,
>>>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 Apache Knox Project be and hereby is
>>> tasked with the migration and rationalization of the Apache
>>> Incubator Knox podling; and be it further
>>>
>>> RESOLVED, that all responsibilities pertaining to the Apache
>>> Incubator Knox podling encumbered upon the Apache
>>>Incubator Project are hereafter discharged.
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
> -
> 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.

Re: Tool to generate disclaimer, NOTICE, etc. files

[sebb]

On 8 February 2014 16:49, Alan Cabrera  wrote:
> Do you think it would be helpful if we had a tool that generated these files? 
>  It could work like a command line wizard that prompts the person for 
> licensing information and then generates a valid disclaimer, notice, etc. 
> files.

AIUI the disclaimer file is the same for every project - only the
project name changes.
Seems unnecessary to automate this, though it should be trivial to implement.

The NOTICE file is much harder to automate, as it depends on knowing
what is actually going to be shipped and reading and interpreting all
the relevant licenses.
However it might be possible to create a sort of expert system that
asked the right questions and guided the user to create the NOTICE
file.

> If this is a good idea, what files should we generate?  Currently, all I can 
> think of is disclaimer and notice.
>
> Maybe it could add the info into the project's DOAP file.  If we worked out 
> the kinks then we could create sbt/gradle/mvn plugins to read the DOAP file 
> and insert these files into the correct places in the distributions.  Apache 
> RAT could also use this info as well.

The DOAP could certainly be used to create the DISCLAIMER.

It seems wrong to include any dependency information in the DOAP.

Dependencies must be present somewhere in the build scripts, however
even in Maven (which has very structured info) it's not at all easy to
determine which dependencies are actually included in the release
artifacts (and remember that source and binary artifacts may need
different NOTICE files)

Note also that some source files may require attribution in the NOTICE file.
These won't be documented in any build system; the info has to be
added to the NOTICE file manually when the code is added to SCM.

> WDYT?

Non-trivial; maintaining the meta-data needed to accurately generate
the NOTICE file is likely to require more effort than writing the
NOTICE file itself.

>
> Regards,
> Alan
>
>
> -
> 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: [DISCUSS] [VOTE] Graduation of Apache Knox from the Incubator

[sebb]

On 9 February 2014 03:26, Chris Mattmann  wrote:
> Any idea why Sebb?
>
> This page exists:
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/kno
> x.xml

This includes:

http://incubator.apache.org/knox/";>http://incubator.apache.org/knox/

which does not exist

>
> And has been updated.
>
> As has:
>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
>
>
> Cheers,
> Chris
>
>
>
> -Original Message-
> From: sebb 
> Reply-To: "general@incubator.apache.org" 
> Date: Saturday, February 8, 2014 7:24 PM
> To: "general@incubator.apache.org" 
> Subject: Re: [VOTE] Graduation of Apache Knox from the Incubator
>
>>The knox incubation status page website link generates a 404.
>>
>>On 7 February 2014 04:49, Chris Mattmann  wrote:
>>> Hi Everyone,
>>>
>>> The Apache Knox Incubating podling has VOTEd to graduate from the
>>> Incubator.
>>> The community VOTE has passed below with the provided tallies. The
>>> graduation
>>> resolution draft is pasted below. We welcome your VOTE'ing on Knox's
>>> graduation
>>> from the Incubator.
>>>
>>> I will leave this VOTE open for at least 72 hours.
>>>
>>> [ ] +1 Recommend graduation of Apache Knox from the Incubator.
>>> [ ] +0 Don't care.
>>> [ ] -1 Don't recommend graduation of Apache Knox from the Incubator
>>> because..
>>>
>>> Thanks for your VOTE!
>>>
>>> Cheers,
>>> Chris
>>>
>>>
>>>
>>> -Original Message-
>>> From: Chris Mattmann 
>>> Reply-To: "d...@knox.incubator.apache.org"
>>>
>>> Date: Thursday, February 6, 2014 8:38 PM
>>> To: "d...@knox.incubator.apache.org" 
>>> Subject: [RESULT] [VOTE] Graduation of Apache Knox from the Incubator
>>>
>>>>Hi Guys,
>>>>
>>>>
>>>>Sorry it took forever for me to close this VOTE! :)
>>>>
>>>>Here are the tallies:
>>>>
>>>>+1
>>>>
>>>>Chris Mattmann*
>>>>Alan Gates*
>>>>Larry McCay
>>>>Dilli Arumugam
>>>>Kevin Minder
>>>>
>>>>* - indicates IPMC
>>>>
>>>>This VOTE has passed. I'll now take it to general@incubator.apache.org.
>>>>
>>>>Thanks for VOTE'ing!
>>>>
>>>>Cheers,
>>>>Chris
>>>>
>>>>-Original Message-
>>>>From: Chris Mattmann 
>>>>Reply-To: "d...@knox.incubator.apache.org"
>>>>
>>>>Date: Thursday, December 19, 2013 2:41 PM
>>>>To: "d...@knox.incubator.apache.org" 
>>>>Subject: [VOTE] Graduation of Apache Knox from the Incubator
>>>>
>>>>>Hi Folks,
>>>>>
>>>>>
>>>>>Time to VOTE on the following resolution to graduate
>>>>>Apache Knox from the Apache Incubator. Here's a draft
>>>>>resolution to VOTE on (with Kevin listed as PMC chair).
>>>>>
>>>>>I'll leave the VOTE open for the next week. If all goes
>>>>>well here, I'll take it to general@incubator.a.o and if
>>>>>all goes well there, we'll take it to the Apache board
>>>>>for consideration in their January 2014 board meeting.
>>>>>
>>>>>Thanks!
>>>>>
>>>>>[ ] +1 Graduate Apache Knox from the Incubator
>>>>>[ ] +0 Don't care.
>>>>>[ ] -1 Don't graduate Apache Knox from the Incubator because..
>>>>>
>>>>>Thanks and here's my enthusiastic +1!
>>>>>
>>>>>Cheers,
>>>>>Chris
>>>>>
>>>>>--draft resolution
>>>>>
>>>>>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 secure access for Apache Hadoop clusters.
>>>>>
>>>>>  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>>>  Committee (PMC), to be known as the "Apache Knox 

Re: Tool to generate disclaimer, NOTICE, etc. files

[sebb]

On 9 February 2014 06:47, Ted Dunning  wrote:
> On Sat, Feb 8, 2014 at 7:42 PM, sebb  wrote:
>
>> > WDYT?
>>
>> Non-trivial; maintaining the meta-data needed to accurately generate
>> the NOTICE file is likely to require more effort than writing the
>> NOTICE file itself.
>>
>
>
> Actually, this sounds like a case where the effort for any individual
> project outweighs the benefit of saving the time, but the total effort
> across many projects would make the effort somewhat worth while.  In
> particular, something that enhances the communication between projects and
> between the author of the dependency and the users of that dependency would
> be very helpful.

AFAICT, the only way to amortise the effort between projects is to
have a shared register of NOTICE requirements for each dependency.
(basically each unique license text).

However, that is not sufficient - the NOTICE file must only include
attributions for bits that are actually included in the artifact to
which the NOTICE (and LICENSE) applies. That is something that is
unique to each project, and may change between releases.

Also as already mentioned, source attributions may sometimes be necessary.

> As such, this sounds like a great thing to add to maven.  If it provided me
> with a way to look at all my dependencies and examine my notices file for
> missing acknowledgments, that would be helpful.  Moreover, if there were a
> way for the community of users to upload sample acknowledgements and for
> the owners of such packages to reject or accept these acknowledgments, this
> would crowdsource the effort of approval.

This is an ASF-specific requirement.
I really don't see how crowd-sourcing this to people outside the ASF
is going to help reduce effort.
Also, only the ASF has a vested interest in getting this right.

> My guess is that since getting NOTIFICATIONS right is a largely one shot
> deal, it wouldn't be enough appeal to encourage somebody to actually
> implement the system, but it would certainly make one's life easier in
> small installments.

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

Re: [VOTE] Graduation of Apache Spark from the Incubator

[sebb]

I think it would be better to start a new thread with the updated text.

Also, the two scope descriptions are slightly different:

"related to fast and flexible large-scale data analysis
on clusters."

v.

"related to efficient cluster management, resource isolation
and sharing across distributed applications"

I don't know whether that is important or not.


On 8 February 2014 22:46, Matei Zaharia  wrote:
> Thanks everyone for the votes. Since we now have accounts for everyone, I've 
> updated the committer list below to include ASF IDs. Thanks to INFRA, we also 
> now have both pull request postings and comments on them forwarded to the our 
> mailing list.
>
>  snip
>
> 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 fast and flexible large-scale data analysis
> on clusters.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Spark Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
>
> RESOLVED, that the Apache Spark Project be and hereby is
> responsible for the creation and maintenance of software
> related to efficient cluster management, resource isolation
> and sharing across distributed applications; and be it further
> RESOLVED, that the office of "Vice President, Apache Spark" 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 Spark Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Spark 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 Spark Project:
>
> * Mosharaf Chowdhury 
> * Jason Dai 
> * Tathagata Das 
> * Ankur Dave 
> * Aaron Davidson 
> * Thomas Dudziak 
> * Robert Evans 
> * Thomas Graves 
> * Andy Konwinski 
> * Stephen Haberman 
> * Mark Hamstra 
> * Shane Huang 
> * Ryan LeCompte 
> * Haoyuan Li 
> * Sean McNamara 
> * Mridul Muralidharam 
> * Kay Ousterhout 
> * Nick Pentreath 
> * Imran Rashid 
> * Charles Reiss 
> * Josh Rosen 
> * Prashant Sharma 
> * Ram Sriharsha 
> * Shivaram Venkataraman 
> * Patrick Wendell 
> * Andrew Xia 
> * Reynold Xin 
> * Matei Zaharia 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be
> appointed to the office of Vice President, Apache Spark, 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 Apache Spark Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Spark podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Spark podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
> 
>
>
>
>
>
>
> On Feb 8, 2014, at 9:02 AM, David Nalley  wrote:
>
>> Ted and Henry: Thanks for the thoughtful replies and indulging my concerns.
>>
>> +1 (binding)
>>
>> --David
>>
>> On Fri, Feb 7, 2014 at 12:33 AM, Henry Saputra  
>> wrote:
>>> HI David Nalley,
>>>
>>> Thank you for your comment and concern, really appreciate it.
>>>
>>> As Patrick had mentioned in his reply, this is not a persistent problem.
>>> The reminder I sent was about particular topic which could be
>>> interpreted as design or roadmap topic rather than review for a patch.
>>> Rather than reminding an individual or two involved in the discussion,
>>> I decided to send email to dev@ list to show by example  the open and
>>> transparent discussions the ASF way.
>>>
>>> Hope this gives some more clarification about the state of the podling
>>> embracing the ASF way.
>>>
>>> - Henry
>>>
>>> On Thu, Feb 6, 2014 at 9:19 PM, Patrick Wendell  wrote:
 Hey All - chiming in as an active Spark committer.

> The part that disturbs me is that after the vote passed in the
> community, and came to the IPMC a mentor is still having to remind
> folks that things like strategy and roadmap discussions need to happen
> on the mailing list. That's a pretty foundational concept in my mind
> for an Apache project.

 Henry gave a reminder on the mailing list not because it's a
 persistent problem but because it never explicitly came up prior to
 this. We use github for review comments and in one case this week
 there was a brief discussion that could be interpreted as roadmap - so
 Henry just gave a reminder not to do that. I can't imagine why any
 project would *want* to use gith

Re: [VOTE] Graduation of Apache Spark from the Incubator

[sebb]

On 9 February 2014 17:11, Mattmann, Chris A (3980)
 wrote:
> Thanks Matei and sebb.
>
> Starting a new thread and collecting the VOTEs all over again would be
> time consuming.

So?

Better to than being confusing, as the current thread has become.

Also it may not be clear whether new votes are intended for the update
resolution or the old one.

Do the original votes even count for the amended resolution?

> In the [RESULT] [VOTE] thread, we'll have the updated
> resolution
> text, and it will be present in the board report shortly thereafter. If
> discussion
> needs to continue at that point we can start a [DISCUSS] [RESULT] [VOTE]
> thread.
>
> Thanks for the catch on the different scope descriptions. I think it
> should be
> the first one (the 2nd looks to be an omission from a cut/paste from the
> Mesos
> graduation resolution).
>
> Cheers,
> Chris
>
>
>
> -Original Message-
> From: sebb 
> Reply-To: "general@incubator.apache.org" 
> Date: Sunday, February 9, 2014 7:10 AM
> To: "general@incubator.apache.org" 
> Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator
>
>>I think it would be better to start a new thread with the updated text.
>>
>>Also, the two scope descriptions are slightly different:
>>
>>"related to fast and flexible large-scale data analysis
>>on clusters."
>>
>>v.
>>
>>"related to efficient cluster management, resource isolation
>>and sharing across distributed applications"
>>
>>I don't know whether that is important or not.
>>
>>
>>On 8 February 2014 22:46, Matei Zaharia  wrote:
>>> Thanks everyone for the votes. Since we now have accounts for everyone,
>>>I've updated the committer list below to include ASF IDs. Thanks to
>>>INFRA, we also now have both pull request postings and comments on them
>>>forwarded to the our mailing list.
>>>
>>>  snip
>>>
>>> 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 fast and flexible large-scale data analysis
>>> on clusters.
>>>
>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>> Committee (PMC), to be known as the "Apache Spark Project", be
>>> and hereby is established pursuant to Bylaws of the Foundation;
>>> and be it further
>>>
>>> RESOLVED, that the Apache Spark Project be and hereby is
>>> responsible for the creation and maintenance of software
>>> related to efficient cluster management, resource isolation
>>> and sharing across distributed applications; and be it further
>>> RESOLVED, that the office of "Vice President, Apache Spark" 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 Spark Project, and to have primary responsibility for
>>> management of the projects within the scope of responsibility
>>> of the Apache Spark 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 Spark Project:
>>>
>>> * Mosharaf Chowdhury 
>>> * Jason Dai 
>>> * Tathagata Das 
>>> * Ankur Dave 
>>> * Aaron Davidson 
>>> * Thomas Dudziak 
>>> * Robert Evans 
>>> * Thomas Graves 
>>> * Andy Konwinski 
>>> * Stephen Haberman 
>>> * Mark Hamstra 
>>> * Shane Huang 
>>> * Ryan LeCompte 
>>> * Haoyuan Li 
>>> * Sean McNamara 
>>> * Mridul Muralidharam 
>>> * Kay Ousterhout 
>>> * Nick Pentreath 
>>> * Imran Rashid 
>>> * Charles Reiss 
>>> * Josh Rosen 
>>> * Prashant Sharma 
>>> * Ram Sriharsha 
>>> * Shivaram Venkataraman 
>>> * Patrick Wendell 
>>> * Andrew Xia 
>>> * Reynold Xin 
>>> * Matei Zaharia 
>>>
>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be
>>> appointed to the office of Vice President, Apache Spark, to
>>> serve in accordance with and subject to the direction of the
>>> Board of Directors and the Bylaws of the Foundation until
>>> death, resignation, retire

Re: [VOTE] Release of Apache Allura 1.1.0 incubating

[sebb]

NOTICE file still refers to 2013.

On 13 February 2014 01:06, Dave Brondsema  wrote:
> Hi everyone,
>
> This is a call for a vote on Apache Allura 1.1.0 incubating. This will be our
> second release in the incubator.  Allura is forge software for the development
> of software projects, including source control systems, issue tracking,
> discussion, wiki, and other software project management tools.
>
> A vote was held on developer mailing list and it passed with 7 +1's, and no
> -1's or +0's.  1 vote was from an IPMC member (me).
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F15D4C.7060906%40brondsema.net%3E
>
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52FBA8A9.502%40brondsema.net%3E
>
> Source tarball, signature and checksums are available at:
>   https://dist.apache.org/repos/dist/dev/incubator/allura/
>
> Checksums:
>   MD5:ea72b33323dc8c85ad26d08de4bbc534
>   SHA1:   170729db7c7b26fc3244293bc0a37989121d3973
>   SHA512:
> 24b65e731d2ec5df33ab4959b0edd72ec5fee58ae5ce704b10ef45ecc07259357a645d4989935423a6be7d4f1add8b2512578b9b2133ac5059f6d3c6d7235934
>
> The KEYS file can be found at:
>   http://www.apache.org/dist/incubator/allura/KEYS
>
> The release has been signed with key (9BB3CE70):
>   http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x56F0526F9BB3CE70
>
> Source corresponding to this release can be found at:
>   Commit: a2bc6726d63298638bacf4d02e697e92aaee0bf4
>   Tag:asf_release_1.1.0
>   Browse:
> https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/tags/asf_release_1.1.0
>
> The RAT report is available at:
>   https://sourceforge.net/p/allura/pastebin/52f15c143e5e833783530b74
>
> Vote will be open for at least 72 hours:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> Thanks!
>
> --
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>   <><
>
> -
> 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 Storm 0.9.1-incubating

[sebb]

On 13 February 2014 07:00, P. Taylor Goetz  wrote:
> This is a call for a vote to release Apache Storm (incubating) version
> 0.9.1. This will be the first release of Apache Storm.
>
> A vote was held on the developer mailing list, and passed with 9 +1 votes (6
> binding, 3 non-binding), no 0 votes, and no -1 votes.
>
> Release Vote:
> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c44c5baad-0fd8-454c-84d7-c8da92442...@gmail.com%3e
>
> Release Vote Result:
> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c3a207f1c-3b07-4029-93d4-87abeb412...@gmail.com%3e
>
>
> The tag to be voted upon is v0.9.1-incubating:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=ffc7a81bfba60c735dd6801af4f5e8db3812658c;hb=ffc7a81bfba60c735dd6801af4f5e8db3812658c

NOTICE file still refers to 2013.

The NOTICE file also references software from

Nathan Marz and Yahoo!

However there are no corresponding licenses in the LICENSE file.

Does the source *contain* software from either of the above?
If so, where are the license files?
If not, why are the attributions present in the NOTICE file?

Remember that N&L file entries are only for bits that are actually
included in the distributiion.

> The specific source archive being voted upon can be found here:
>
> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3/apache-storm-0.9.1-incubating-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3
>
> The release artifacts are signed with the key available here:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>
> The staging repository for this release can be found here:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1002/
>
> The generated reports and documentation for this release can be found here:
>
> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-report-rc3
>
> Please vote on releasing this package as Apache Storm 0.9.1-incubating.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 0.9.1-incubating
> [ ]  0 No opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Apache Storm Team

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

Re: [VOTE] Release Apache Storm 0.9.1-incubating

[sebb]

If the code has not changed substantially in 2014 then the date can
stay as 2013.

As to the attribution, that depends on the _exact text_ of the license
provided with the files.
The license(s) should also be included in the LICENSE file.

Note that attributions in the NOTICE file must be passed to downstream
consumers so it is important not to include anything that is not
required.


On 14 February 2014 17:31, Suresh Srinivas  wrote:
> +1 (binding) from me.
>
> Sebb, can you please answer the question related to the NOTICE file. I
> think while it may not be necessary to call out individual or companies
> contributing large portions of the code, it should not block this release
> and can be addressed later.
>
>
> On Thu, Feb 13, 2014 at 7:49 AM, P. Taylor Goetz  wrote:
>
>> Thanks for the input!
>>
>> The majority of the codebase was originally developed by Nathan Marz, and
>> it includes significant contributions from Yahoo!.
>>
>> The project was originally licensed under the Eclipse Public License, but
>> has not transitioned to the Apache v2 license.
>>
>> If putting those attributions in the NOTICE file is not the correct thing
>> to do, please let me know the right way to handle it.
>>
>> It was still 2013 when I last updated the NOTICE file. I'm not sure if
>> that is a blocker for release or not.
>>
>> - Taylor
>>
>> On Feb 13, 2014, at 5:59 AM, sebb  wrote:
>>
>> On 13 February 2014 07:00, P. Taylor Goetz  wrote:
>>
>> This is a call for a vote to release Apache Storm (incubating) version
>> 0.9.1. This will be the first release of Apache Storm.
>>
>> A vote was held on the developer mailing list, and passed with 9 +1 votes
>> (6
>> binding, 3 non-binding), no 0 votes, and no -1 votes.
>>
>> Release Vote:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c44c5baad-0fd8-454c-84d7-c8da92442...@gmail.com%3e
>>
>> Release Vote Result:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c3a207f1c-3b07-4029-93d4-87abeb412...@gmail.com%3e
>>
>>
>> The tag to be voted upon is v0.9.1-incubating:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=ffc7a81bfba60c735dd6801af4f5e8db3812658c;hb=ffc7a81bfba60c735dd6801af4f5e8db3812658c
>>
>>
>> NOTICE file still refers to 2013.
>>
>> The NOTICE file also references software from
>>
>> Nathan Marz and Yahoo!
>>
>> However there are no corresponding licenses in the LICENSE file.
>>
>> Does the source *contain* software from either of the above?
>> If so, where are the license files?
>> If not, why are the attributions present in the NOTICE file?
>>
>> Remember that N&L file entries are only for bits that are actually
>> included in the distributiion.
>>
>> The specific source archive being voted upon can be found here:
>>
>>
>> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3/apache-storm-0.9.1-incubating-src.tar.gz
>>
>> Other release files, signatures and digests can be found here:
>>
>> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3
>>
>> The release artifacts are signed with the key available here:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>
>> The staging repository for this release can be found here:
>>
>> https://repository.apache.org/content/repositories/orgapachestorm-1002/
>>
>> The generated reports and documentation for this release can be found here:
>>
>> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-report-rc3
>>
>> Please vote on releasing this package as Apache Storm 0.9.1-incubating.
>>
>> This vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache Storm 0.9.1-incubating
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>> Apache Storm Team
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>>
>
>
> --
> http://hortonworks.com/download/
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

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

Re: [VOTE] Release Apache Storm 0.9.1-incubating

[sebb]

On 15 February 2014 16:44, P. Taylor Goetz  wrote:
> Hi sebb,
>
> What specifically needs to be done to correct the NOTICE file?
>
> Should the references to Nathan Marz and Yahoo! be removed?

As I already wrote, this depends on the exact license(s) of the
file(s) involved.

> Thanks,
>
> Taylor
>
>> On Feb 14, 2014, at 12:44 PM, sebb  wrote:
>>
>> If the code has not changed substantially in 2014 then the date can
>> stay as 2013.
>>
>> As to the attribution, that depends on the _exact text_ of the license
>> provided with the files.
>> The license(s) should also be included in the LICENSE file.
>>
>> Note that attributions in the NOTICE file must be passed to downstream
>> consumers so it is important not to include anything that is not
>> required.
>>
>>
>>> On 14 February 2014 17:31, Suresh Srinivas  wrote:
>>> +1 (binding) from me.
>>>
>>> Sebb, can you please answer the question related to the NOTICE file. I
>>> think while it may not be necessary to call out individual or companies
>>> contributing large portions of the code, it should not block this release
>>> and can be addressed later.
>>>
>>>
>>>> On Thu, Feb 13, 2014 at 7:49 AM, P. Taylor Goetz  wrote:
>>>>
>>>> Thanks for the input!
>>>>
>>>> The majority of the codebase was originally developed by Nathan Marz, and
>>>> it includes significant contributions from Yahoo!.
>>>>
>>>> The project was originally licensed under the Eclipse Public License, but
>>>> has not transitioned to the Apache v2 license.
>>>>
>>>> If putting those attributions in the NOTICE file is not the correct thing
>>>> to do, please let me know the right way to handle it.
>>>>
>>>> It was still 2013 when I last updated the NOTICE file. I'm not sure if
>>>> that is a blocker for release or not.
>>>>
>>>> - Taylor
>>>>
>>>> On Feb 13, 2014, at 5:59 AM, sebb  wrote:
>>>>
>>>> On 13 February 2014 07:00, P. Taylor Goetz  wrote:
>>>>
>>>> This is a call for a vote to release Apache Storm (incubating) version
>>>> 0.9.1. This will be the first release of Apache Storm.
>>>>
>>>> A vote was held on the developer mailing list, and passed with 9 +1 votes
>>>> (6
>>>> binding, 3 non-binding), no 0 votes, and no -1 votes.
>>>>
>>>> Release Vote:
>>>>
>>>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c44c5baad-0fd8-454c-84d7-c8da92442...@gmail.com%3e
>>>>
>>>> Release Vote Result:
>>>>
>>>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c3a207f1c-3b07-4029-93d4-87abeb412...@gmail.com%3e
>>>>
>>>>
>>>> The tag to be voted upon is v0.9.1-incubating:
>>>>
>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=ffc7a81bfba60c735dd6801af4f5e8db3812658c;hb=ffc7a81bfba60c735dd6801af4f5e8db3812658c
>>>>
>>>>
>>>> NOTICE file still refers to 2013.
>>>>
>>>> The NOTICE file also references software from
>>>>
>>>> Nathan Marz and Yahoo!
>>>>
>>>> However there are no corresponding licenses in the LICENSE file.
>>>>
>>>> Does the source *contain* software from either of the above?
>>>> If so, where are the license files?
>>>> If not, why are the attributions present in the NOTICE file?
>>>>
>>>> Remember that N&L file entries are only for bits that are actually
>>>> included in the distributiion.
>>>>
>>>> The specific source archive being voted upon can be found here:
>>>>
>>>>
>>>> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3/apache-storm-0.9.1-incubating-src.tar.gz
>>>>
>>>> Other release files, signatures and digests can be found here:
>>>>
>>>> http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3
>>>>
>>>> The release artifacts are signed with the key available here:
>>>>
>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>>>
>>>> The staging repository for this release can be found here:
>>>>

Re: [VOTE] Release Celix version 1.0.0.incubating

[sebb]

On 16 February 2014 08:24, Alexander Broekhuis  wrote:
> This is the release vote for Apache Celix, version 1.0.0.incubating
>
> This release has already been approved by:
>
> +1 Marcel Offermans (marrs) (binding)
> +1 Karl Pauls (pauls) (binding)
> +1 Gerrit Binnenmars (non-binding)
> +1 Pepijn Noltes (pnoltes) (non-binding)
>
> See http://incubator.markmail.org/thread/zkkpgitohcziwhtk for their votes.
>
> As can be seen we do not have enough binding votes, so it would really be
> appreciated if some people can find some time to review this release.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12323511&styleName=Html&projectId=12311213&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7Cca8cb9dc9141fab1c4e55ded0645d766d85f7ae2%7Clin
>
> Source files:
> https://dist.apache.org/repos/dist/dev/incubator/celix/celix-1.0.0.incubating/
>
> The tag to be voted upon:
> http://svn.apache.org/repos/asf/incubator/celix/tags/celix-1.0.0.incubating/

The NOTICE file 2nd line says:

Copyright [2012] The Apache Software Foundation

This is wrong on two counts: the [ ] are not required, and the year(s)
should include more than just 2012 unless there has been no
substantive change since then.

> Celix's keys can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/celix/KEYS

These should really be in the release directory, i.e

https://dist.apache.org/repos/dist/release/incubator/celix/

That will ensure the file is available to downloaders from the ASF
mirror source.

Which reminds me: the KEYS file needs to be linked from the download
page for use with the PGP sig.

There is a further issue with the download page.
It currently contains links for SVN. I think those don't belong on a
public download page.
SVN links should be restricted to pages intended for developers, not
the general public.


> Information for voting on a release can be found at
> http://www.apache.org/dev/release.html#approving-a-release
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Disapprove the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis

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

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[sebb]

On 22 February 2014 01:12, James Taylor  wrote:
> Hello everyone,
>
> This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is a
> SQL query engine for Apache HBase, a NoSQL data store.  It is accessed as a
> JDBC driver and enables querying and managing HBase tables using SQL. This
> will be our first release in the incubator.
>
> The RC is available for download at
> http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC2/ and is
> signed with my code signing key 5F5F3233.

What is the URL for the source code tag? And the revision/hash?

It is vital for reviewers to be able to check that the source files
agree with the source code, as that it is when code is added to the
source code repo that the IP checks etc. are done.

Also for the historical record (should there ever be a complaint about
the content) having the URLs in the mail archives could be vital
evidence that the PMC has done due diligence on the release contents.

I've had a quick look at the (sole) archive, and it contains both
source and compiled jars.
Although it is OK to release convenience binaries, there must be a
source only release, as that is the ASF mission - to release open
source.

http://www.apache.org/dev/release.html#what-must-every-release-contain

> A vote was held on developer mailing list [1] and it passed with 4 +1's,
> and no
> -1's or +0's (2 votes were from IPMC members).
>
> Vote will be open for at least 72 hours:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> James
>
> [1] Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201402.mbox/%3CCAAF1JdjsiHGFYQjkMVSWJmGaRJQd0fJJRVAB7J70-i2tLR2UkA%40mail.gmail.com%3E

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

Re: [VOTE] Graduation of Apache Tajo from the Incubator

[sebb]

The Incubation status page has one incomplete section:

"Verify distribution rights"

Seems to me it is fundamental to ensure that this has been done before
considering graduation.


On 22 February 2014 03:44, Mattmann, Chris A (3980)
 wrote:
> Hi Everyone,
>
> After a successful community VOTE [1] in which 4 IPMC members
> already VOTEd positively for graduation, I'm now calling an IPMC
> VOTE to graduate Tajo from the Incubator. Apache Tajo has
> seen successful Incubator releases, has added new contributors,
> has discussed their project on list and consistent with the
> Apache ways. There is a great momentum in the community and
> I am wholeheartedly recommending its graduation from the
> Incubator.
>
> Please VOTE below on the graduation of Apache Tajo from the
> Incubator. The graduation resolution is pasted below.
> I'll leave the VOTE open for at least 72 hours:
>
> [ ] +1 Graduate Apache Tajo from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Tajo from the Incubator because
>
> Here is my enthusiastic +1 for Tajo's graduation!
>
> Cheers,
> Chris
>
> [1] http://s.apache.org/sM
>
> ---resolution
>
> 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 low latency
>   queries, and extract, transform and load
> (ETL) operations for the Hadoop ecosystem.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>   (PMC), to be known as the "Apache Tajo Project" be and hereby is
>   established pursuant to Bylaws of the Foundation; and be it further
>
>   RESOLVED, that the Apache Tajo Project be and hereby is responsible
>   for the creation and maintenance of software
> related to low latency queries, and extract, transform and load
> (ETL) operations for the Hadoop ecosystem; and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Tajo", 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 Tajo Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
>   of the Apache Tajo 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 Tajo
>   Project:
>
> Alex Karasulu 
> Eli Reisman 
> Henry Saputra 
> Hyunsik Choi 
> Jakob Glen Homan 
> Chris Mattmann 
> Owen O'Malley 
> JaeHwa Jung 
> Jinho Kim 
> Jihoon Son 
> Keuntae Park 
> Roshan Sumbaly 
> Sangwook Kim 
> Yi Liu 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hyunsik Choi be appointed
> to the office of Vice President, Apache Tajo, 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 Apache Tajo Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Tajo
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Tajo podling encumbered upon the Apache Incubator Project are
> hereafter discharged.
>
>
>
>
>
>
> -
> 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] Graduation of Apache Tajo from the Incubator

[sebb]

BTW, the copy to the dev@tajo list bounced, as I'm not subscribed.

On 22 February 2014 10:24, sebb  wrote:
> The Incubation status page has one incomplete section:
>
> "Verify distribution rights"
>
> Seems to me it is fundamental to ensure that this has been done before
> considering graduation.
>
>
> On 22 February 2014 03:44, Mattmann, Chris A (3980)
>  wrote:
>> Hi Everyone,
>>
>> After a successful community VOTE [1] in which 4 IPMC members
>> already VOTEd positively for graduation, I'm now calling an IPMC
>> VOTE to graduate Tajo from the Incubator. Apache Tajo has
>> seen successful Incubator releases, has added new contributors,
>> has discussed their project on list and consistent with the
>> Apache ways. There is a great momentum in the community and
>> I am wholeheartedly recommending its graduation from the
>> Incubator.
>>
>> Please VOTE below on the graduation of Apache Tajo from the
>> Incubator. The graduation resolution is pasted below.
>> I'll leave the VOTE open for at least 72 hours:
>>
>> [ ] +1 Graduate Apache Tajo from the Incubator.
>> [ ] +0 Don't care.
>> [ ] -1 Don't graduate Apache Tajo from the Incubator because
>>
>> Here is my enthusiastic +1 for Tajo's graduation!
>>
>> Cheers,
>> Chris
>>
>> [1] http://s.apache.org/sM
>>
>> ---resolution
>>
>> 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 low latency
>>   queries, and extract, transform and load
>> (ETL) operations for the Hadoop ecosystem.
>>
>>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>   (PMC), to be known as the "Apache Tajo Project" be and hereby is
>>   established pursuant to Bylaws of the Foundation; and be it further
>>
>>   RESOLVED, that the Apache Tajo Project be and hereby is responsible
>>   for the creation and maintenance of software
>> related to low latency queries, and extract, transform and load
>> (ETL) operations for the Hadoop ecosystem; and be it further
>>
>>   RESOLVED, that the office of "Vice President, Apache Tajo", 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 Tajo Project, and to have primary responsibility for
>> management of the projects within the scope of responsibility
>>   of the Apache Tajo 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 Tajo
>>   Project:
>>
>> Alex Karasulu 
>> Eli Reisman 
>> Henry Saputra 
>> Hyunsik Choi 
>> Jakob Glen Homan 
>> Chris Mattmann 
>> Owen O'Malley 
>> JaeHwa Jung 
>> Jinho Kim 
>> Jihoon Son 
>> Keuntae Park 
>> Roshan Sumbaly 
>> Sangwook Kim 
>> Yi Liu 
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hyunsik Choi be appointed
>> to the office of Vice President, Apache Tajo, 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 Apache Tajo Project be and hereby is tasked with
>> the migration and rationalization of the Apache Incubator Tajo
>> podling; and be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Tajo podling encumbered upon the Apache Incubator Project are
>> hereafter discharged.
>>
>>
>>
>>
>>
>>
>> -
>> 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] Graduation of Apache Tajo from the Incubator

[sebb]

On 23 February 2014 06:58, Hyunsik Choi  wrote:
> Hi Sebb,
>
> Thank you for your checking. We updated the incubation status of Tajo as
> follows:
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/tajo.xml
>
> The first item of distribution rights was verified when Tajo entered ASF
> incubation.
> The second item was verified when we made the first Tajo release.
>
> The web page of the incubation status will be updated after a while.
> http://incubator.apache.org/projects/tajo.html

It can be updated immediately, if you use the publish step as described below

http://incubator.apache.org/guides/website.html#create-status-page

See step 9.

> Best regards,
> Hyunsik
>
>
>
> On Sat, Feb 22, 2014 at 7:24 PM, sebb  wrote:
>
>> The Incubation status page has one incomplete section:
>>
>> "Verify distribution rights"
>>
>> Seems to me it is fundamental to ensure that this has been done before
>> considering graduation.
>>
>>
>> On 22 February 2014 03:44, Mattmann, Chris A (3980)
>>  wrote:
>> > Hi Everyone,
>> >
>> > After a successful community VOTE [1] in which 4 IPMC members
>> > already VOTEd positively for graduation, I'm now calling an IPMC
>> > VOTE to graduate Tajo from the Incubator. Apache Tajo has
>> > seen successful Incubator releases, has added new contributors,
>> > has discussed their project on list and consistent with the
>> > Apache ways. There is a great momentum in the community and
>> > I am wholeheartedly recommending its graduation from the
>> > Incubator.
>> >
>> > Please VOTE below on the graduation of Apache Tajo from the
>> > Incubator. The graduation resolution is pasted below.
>> > I'll leave the VOTE open for at least 72 hours:
>> >
>> > [ ] +1 Graduate Apache Tajo from the Incubator.
>> > [ ] +0 Don't care.
>> > [ ] -1 Don't graduate Apache Tajo from the Incubator because
>> >
>> > Here is my enthusiastic +1 for Tajo's graduation!
>> >
>> > Cheers,
>> > Chris
>> >
>> > [1] http://s.apache.org/sM
>> >
>> > ---resolution
>> >
>> > 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 low latency
>> >   queries, and extract, transform and load
>> > (ETL) operations for the Hadoop ecosystem.
>> >
>> >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> >   (PMC), to be known as the "Apache Tajo Project" be and hereby is
>> >   established pursuant to Bylaws of the Foundation; and be it further
>> >
>> >   RESOLVED, that the Apache Tajo Project be and hereby is responsible
>> >   for the creation and maintenance of software
>> > related to low latency queries, and extract, transform and load
>> > (ETL) operations for the Hadoop ecosystem; and be it further
>> >
>> >   RESOLVED, that the office of "Vice President, Apache Tajo", 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 Tajo Project, and to have primary responsibility for
>> > management of the projects within the scope of responsibility
>> >   of the Apache Tajo 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 Tajo
>> >   Project:
>> >
>> > Alex Karasulu 
>> > Eli Reisman 
>> > Henry Saputra 
>> > Hyunsik Choi 
>> > Jakob Glen Homan 
>> > Chris Mattmann 
>> > Owen O'Malley 
>> > JaeHwa Jung 
>> > Jinho Kim 
>> > Jihoon Son 
>> > Keuntae Park 
>> > Roshan Sumbaly 
>> > Sangwook Kim 
>> > Yi Liu 
>> >
>> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hyunsik Choi be appointed
>> > to the office of Vice President, Apache Tajo, 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

Re: [VOTE] Release Apache Tez-0.3.0-incubating RC0

[sebb]

On 23 February 2014 19:31, Hitesh Shah  wrote:
> Hello folks,
>
> I have created a tez-0.3.0-incubating release candidate (rc0). This is the 
> second release for Tez.
>
> GIT source tag: 
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
> Staging site: 
> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
> Nexus Staging URL: 
> https://repository.apache.org/content/repositories/orgapachetez-1002
>
> PGP release keys: 
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
> KEYS file also available at 
> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS

Very good set of links.
Provides everything needed for reviewers to check the release contents.
Ideally the GIT hash should also be included, as tags are not immutable.
And for the mail archives it would be useful to include the SVN
revision for the dist/dev/ tag.

One minor point - the NOTICE file still says 2013; that should be
updated for the next release (assuming substantive changes have been
made in 2014)

> One can look into the issues fixed in this release at: 
> https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look at 
> the CHANGES.txt in the release tarball.
>
> Vote will be open for at least 72 hours ( until the required number of IPMC 
> votes are obtained ).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For folks not familiar with vetting a release, please refer to 
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>
> thanks
> -- Hitesh
> -
> 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 of Apache Phoenix 2.2.3 incubating

[sebb]

On 24 February 2014 18:25, Andrew Purtell  wrote:
> On Mon, Feb 24, 2014 at 10:20 AM, Henry Saputra 
> wrote:
>
>> Are you saying it is ok to contain compiled executed binaries if they
>> were signed?
>>
>
> I did not take a position on that.
>
> The how-to-release documentation perhaps has more room for interpretation
> than is desirable.
>
> There had been long discussion in general@ list about what should be contained
>> in release artifacts (with 0.8.1 Spark release) and I believe the
>> conclusion was to avoid executable binaries in the source release
>> artifacts.
>>
>
> I missed this discussion. Probably this conclusion just hasn't surfaced
> into documentation yet.

I think it is implied here

http://www.apache.org/dev/release.html#what (last para)

but I agree it should be make clearer elsewhere.

> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

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

Re: [VOTE] Release Apache Tez-0.3.0-incubating RC1

[sebb]

On 28 February 2014 19:48, Alan Gates  wrote:
> +1
>
> One note is that the signatures given say sha1, but you actually have use 
> openssl sha to get the same values.  If you do sha1sum (which was my first 
> assumption anyway) you get a different non-matching values.  You might want 
> to change the filename to "tez-0.3.0-incubating.tar.gz.sha"

Or better, use SHA-1 rather than SHA (aka SHA-0) which is relatively
weak and not well supported by tools.

I think it would be OK just to replace the sha1 file contents with the
appropriate SHA-1 hash.
No need to respin the release, as it that has not changed, but it
would make sense to get a few people to check the updated hash works
for them.

If you leave the sha1 file with SHA-0 contents, that is potentially
going to cause problems for downloaders; they won't be expecting a
SHA-0 hash in that file.

> Other than that, checked the signatures, looked at LICENSE, NOTICE, 
> DISCLAIMER, built and ran the unit tests.  All looks good.
>
> Alan.
>
> On Feb 28, 2014, at 11:28 AM, Mahadev Konar  wrote:
>
>> +1 (binding)
>>
>> - verified signatures and ran some sample test jobs.
>>
>>
>>
>> Mahadev Konar
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>>
>> On Fri, Feb 28, 2014 at 8:05 AM, Jason Lowe  wrote:
>>> +1 (non-binding)
>>>
>>> - Verified signatures
>>> - Built from source, installed on single-node cluster
>>> - Ran  some sample Tez jobs
>>>
>>> Jason
>>>
>>>
>>> On 02/25/2014 06:28 PM, Hitesh Shah wrote:

 Hello folks,

 I have created a tez-0.3.0-incubating release candidate (rc1). This is the
 second release for Tez.

 The previous RC was cancelled due to a bug discovered when the RC was
 tested against downstream projects.

 GIT source tag:
 https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc1
 ( commit hash 6987e18f6b3c5358e1eb125bc2d63be39f71e892 )
 Staging site:
 https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc1/ 
 (
 svn revision 4508 )
 Nexus Staging URL:
 https://repository.apache.org/content/repositories/orgapachetez-1003

 PGP release keys:
 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
 KEYS file also available at
 https://dist.apache.org/repos/dist/release/incubator/tez/KEYS

 One can look into the issues fixed in this release at:
 https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look at
 the CHANGES.txt in the release tarball.

 Vote will be open for at least 72 hours ( until the required number of
 IPMC votes are obtained ).

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)

 For folks not familiar with vetting a release, please refer to
 http://incubator.apache.org/guides/releasemanagement.html#check-list

 thanks
 -- Hitesh
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. 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:

Re: [VOTE] Release Apache Tez-0.3.0-incubating RC1

[sebb]

On 28 February 2014 21:44, Hitesh Shah  wrote:
> Thanks for the suggestion, Sebb. I went ahead and moved the original SHA into 
> .sha file and re-generated the SHA1 into the .sha1 file.
>
> @Alan, @sebb, would either of you mind verifying the modified files?

.sha1 now looks OK.

Not sure its worth keeping the sha (SHA-0) file - I think that will
just be confusing.

> I will follow-up separately with other folks who did their +1's to re-check 
> the files.
>
> thanks
> -- Hitesh
>
> On Feb 28, 2014, at 12:32 PM, sebb wrote:
>
>> On 28 February 2014 19:48, Alan Gates  wrote:
>>> +1
>>>
>>> One note is that the signatures given say sha1, but you actually have use 
>>> openssl sha to get the same values.  If you do sha1sum (which was my first 
>>> assumption anyway) you get a different non-matching values.  You might want 
>>> to change the filename to "tez-0.3.0-incubating.tar.gz.sha"
>>
>> Or better, use SHA-1 rather than SHA (aka SHA-0) which is relatively
>> weak and not well supported by tools.
>>
>> I think it would be OK just to replace the sha1 file contents with the
>> appropriate SHA-1 hash.
>> No need to respin the release, as it that has not changed, but it
>> would make sense to get a few people to check the updated hash works
>> for them.
>>
>> If you leave the sha1 file with SHA-0 contents, that is potentially
>> going to cause problems for downloaders; they won't be expecting a
>> SHA-0 hash in that file.
>>
>>> Other than that, checked the signatures, looked at LICENSE, NOTICE, 
>>> DISCLAIMER, built and ran the unit tests.  All looks good.
>>>
>>> Alan.
>>>
>>> On Feb 28, 2014, at 11:28 AM, Mahadev Konar  wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> - verified signatures and ran some sample test jobs.
>>>>
>>>>
>>>>
>>>> Mahadev Konar
>>>> Hortonworks Inc.
>>>> http://hortonworks.com/
>>>>
>>>>
>>>> On Fri, Feb 28, 2014 at 8:05 AM, Jason Lowe  wrote:
>>>>> +1 (non-binding)
>>>>>
>>>>> - Verified signatures
>>>>> - Built from source, installed on single-node cluster
>>>>> - Ran  some sample Tez jobs
>>>>>
>>>>> Jason
>>>>>
>>>>>
>>>>> On 02/25/2014 06:28 PM, Hitesh Shah wrote:
>>>>>>
>>>>>> Hello folks,
>>>>>>
>>>>>> I have created a tez-0.3.0-incubating release candidate (rc1). This is 
>>>>>> the
>>>>>> second release for Tez.
>>>>>>
>>>>>> The previous RC was cancelled due to a bug discovered when the RC was
>>>>>> tested against downstream projects.
>>>>>>
>>>>>> GIT source tag:
>>>>>> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc1
>>>>>> ( commit hash 6987e18f6b3c5358e1eb125bc2d63be39f71e892 )
>>>>>> Staging site:
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc1/
>>>>>>  (
>>>>>> svn revision 4508 )
>>>>>> Nexus Staging URL:
>>>>>> https://repository.apache.org/content/repositories/orgapachetez-1003
>>>>>>
>>>>>> PGP release keys:
>>>>>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
>>>>>> KEYS file also available at
>>>>>> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>>>>>>
>>>>>> One can look into the issues fixed in this release at:
>>>>>> https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look 
>>>>>> at
>>>>>> the CHANGES.txt in the release tarball.
>>>>>>
>>>>>> Vote will be open for at least 72 hours ( until the required number of
>>>>>> IPMC votes are obtained ).
>>>>>>
>>>>>> [ ] +1 approve
>>>>>> [ ] +0 no opinion
>>>>>> [ ] -1 disapprove (and reason why)
>>>>>>
>>>>>> For folks not familiar with vetting a release, please refer to
>>>>>> http://incubator.apache.org/guides/releasemanagement.html#check-list
>>>>>>
>>>>>> thanks
>&

Re: [VOTE] Release Apache ODF Toolkit 0.6.1-incubating

[sebb]

On 5 March 2014 19:26, Henry Saputra  wrote:
> The ODF Toolkit website [1] does not indicate which ones are the mentors.
>
> Do you mind just listing them in this thread for quick FYI?

The canonical location for podling status is here:

http://incubator.apache.org/projects/odftoolkit.html


> Thanks,
>
> Henry
>
> [1] https://incubator.apache.org/odftoolkit/people.html
>
> On Wed, Mar 5, 2014 at 10:53 AM, Rob Weir  wrote:
>> On Wed, Mar 5, 2014 at 1:35 PM, Henry Saputra  
>> wrote:
>>> Hi Rob, the result Vote within PPMC [1] did not indicate mentor Vote.
>>>
>>> Is there any mentor Vote in favor within ODF dev list Vote thread?
>>>
>>
>> No, there were no votes from mentors.   That's one of our problems,
>> lack of active mentors.  We would benefit greatly from one or two.
>>
>> We're a small, but diverse, podling with no drama.  We recently did a
>> pitch for new developer volunteers and got a good amount of interest.
>> But it is hard to follow up on that without the ability to get a
>> release examined.
>>
>> If any one has been following the recent news in the UK, the
>> government there appears close to expressing a mandate for the use of
>> OpenDocument Format.  Libraries that can process ODF documents, like
>> the ODF Toolkit, will be an important part of supporting widespread
>> use of ODF there and in other places.
>>
>> If anyone is interested, pleased let us know at odf-...@incubator.apache.org
>>
>> Regards,
>>
>> -Rob
>>
>>> Thx,
>>>
>>> - Henry
>>>
>>> [1] 
>>> http://mail-archives.apache.org/mod_mbox/incubator-odf-dev/201402.mbox/%3CCAP-ksogUFy-OkDkdJcNYDjnn8wUf%3DxcJX%2BG2xxQLKzp5PGKEgA%40mail.gmail.com%3E
>>>
>>> On Wed, Feb 19, 2014 at 6:07 AM, Rob Weir  wrote:
 We've had a vote within the PPMC which passed:

 http://mail-archives.apache.org/mod_mbox/incubator-odf-dev/201402.mbox/%3CCAP-ksogUFy-OkDkdJcNYDjnn8wUf%3DxcJX%2BG2xxQLKzp5PGKEgA%40mail.gmail.com%3E


 We're now looking for review and approval by the IPMC.

 Regards,

 -Rob

 --

 RC4 for the ODF Toolkit 0.6.1-incubating release is available at:

 http://people.apache.org/~robweir/odftoolkit-release/odftoolkit-0.6.1-incubating/

 The release candidate is a zip archive of the sources in:

 https://svn.apache.org/repos/asf/incubator/odf/tags/odftoolkit-0.6.1-incubating-RC4/

 We're voting on the odftoolkit-0.6.1-incubating-src.zip.

 Please vote on releasing this package as Apache ODF Toolkit 
 0.6.1-incubating.

 If the vote passes we'll also distribute pre-built binaries and
 JavaDoc as a convenience to users, as well as publish to Maven.

 The vote is open for the next 72 hours and passes if a majority
 of at least three +1 PMC votes are cast.

 [ ] +1 Release this package as Apache ODF Toolkit 0.6.1-incubating
 [ ] -1 Do not release this package because...

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

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

Re: [VOTE] Graduation of Apache Allura from the Incubator

[sebb]

On 7 March 2014 20:16, Dave Brondsema  wrote:
> Hi everyone,
>
> The Apache Allura podling has discussed and voted to graduate from the
> incubator.  We've made two releases, added several PPMC members, have been
> working with Infra to set up forge-allura.a.o, etc.  We would now like the 
> IPMC
> to vote.
>
> Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5
> Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l
> Community results:
>
> +1
> Roberto Galoppini
> Wayne Witzel III
> Cory Johns
> Dave Brondsema (IPMC)
> Rich Bowen (IPMC)
> Simone Gatti
> Stefano Invernizzi
> Alvaro del Castillo
> Jim Jagielski (IPMC)
> Tim Van Steenburgh
>
> +0
> (none)
>
> -1
> (none)
>
>
> Please VOTE below on the graduation of Apache Allura from the
> Incubator. The graduation resolution is pasted below.
> The VOTE will be open for at least 72 hours:
>
> [ ] +1 Graduate Apache Allura from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Allura from the Incubator because
>
>
>
>
> X. Establish the Apache Allura 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 a software development infrastructure
>platform commonly known as a "forge".
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Allura Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Allura Project be and hereby is
>responsible for the creation and maintenance of software
>related to a software development infrastructure platform
>commonly known as a "forge"; and be it further
>
>RESOLVED, that the office of "Vice President, Apache Allura" 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 Allura Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Allura 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 Allura Project:
>
>  * Tim Van Steenburgh 
>  * Wayne Witzel III   
>  * Cory Johns 
>  * Dave Brondsema 
>  * Roberto Galoppini  
>  * Alvaro del Castillo
>  * Stefano Invernizzi 

That's not the correct e-mail AFAICT
I don't think any ASF ids have a "." character in them.

>  * Simone Gatti   
>  * Jim Jagielski  
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema
>be appointed to the office of Vice President, Apache Allura, 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 Allura 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 Allura Project; and be it further
>
>RESOLVED, that the Apache Allura Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Allura podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Allura podling encumbered upon the Apache Incubator
>Project are hereafter discharged.
>
>
>
>
> --
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>   <><
>
> -
> 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] Graduation of Apache Allura from the Incubator

[sebb]

The Allura website does not appear to follow the branding guidelines.

The page footer does not mention Apache Allura and Allura as trademarks
Also the footer date is still 2011

The License link must point to http://www.apache.org/licenses/   - not
to a local copy of the license.

The intro. paragraph starts:

"The Allura Project is forge software "

This does not make sense - a project is not software.

The bug tracker link on the main page is broken.

The page
https://incubator.apache.org/allura/contributors.html
has at least one incorrect Apache id, and one missing id

As noted elsethread, there don't appear to be any download links.

The source code page only includes a git: scheme URL.
It ought to be possible to browse the source without needing to install Git.

The website needs plenty of TLC...

As such, I don't think it's ready to become a TLP.


On 7 March 2014 20:16, Dave Brondsema  wrote:
> Hi everyone,
>
> The Apache Allura podling has discussed and voted to graduate from the
> incubator.  We've made two releases, added several PPMC members, have been
> working with Infra to set up forge-allura.a.o, etc.  We would now like the 
> IPMC
> to vote.
>
> Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5
> Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l
> Community results:
>
> +1
> Roberto Galoppini
> Wayne Witzel III
> Cory Johns
> Dave Brondsema (IPMC)
> Rich Bowen (IPMC)
> Simone Gatti
> Stefano Invernizzi
> Alvaro del Castillo
> Jim Jagielski (IPMC)
> Tim Van Steenburgh
>
> +0
> (none)
>
> -1
> (none)
>
>
> Please VOTE below on the graduation of Apache Allura from the
> Incubator. The graduation resolution is pasted below.
> The VOTE will be open for at least 72 hours:
>
> [ ] +1 Graduate Apache Allura from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Allura from the Incubator because
>
>
>
>
> X. Establish the Apache Allura 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 a software development infrastructure
>platform commonly known as a "forge".
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Allura Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Allura Project be and hereby is
>responsible for the creation and maintenance of software
>related to a software development infrastructure platform
>commonly known as a "forge"; and be it further
>
>RESOLVED, that the office of "Vice President, Apache Allura" 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 Allura Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Allura 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 Allura Project:
>
>  * Tim Van Steenburgh 
>  * Wayne Witzel III   
>  * Cory Johns 
>  * Dave Brondsema 
>  * Roberto Galoppini  
>  * Alvaro del Castillo
>  * Stefano Invernizzi 
>  * Simone Gatti   
>  * Jim Jagielski  
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema
>be appointed to the office of Vice President, Apache Allura, 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 Allura 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 Allura Project; and be it further
>
>RESOLVED, that the Apache Allura Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Allura podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Allura podling encumbered upon the Apache Incubator
>Project are hereafter discharged.
>
>
>
>
> --
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>   <><
>
> ---

Re: [VOTE] Graduation of Apache Allura from the Incubator

[sebb]

Also, the podling status page is not complete.

On 13 March 2014 18:34, sebb  wrote:
> The Allura website does not appear to follow the branding guidelines.
>
> The page footer does not mention Apache Allura and Allura as trademarks
> Also the footer date is still 2011
>
> The License link must point to http://www.apache.org/licenses/   - not
> to a local copy of the license.
>
> The intro. paragraph starts:
>
> "The Allura Project is forge software "
>
> This does not make sense - a project is not software.
>
> The bug tracker link on the main page is broken.
>
> The page
> https://incubator.apache.org/allura/contributors.html
> has at least one incorrect Apache id, and one missing id
>
> As noted elsethread, there don't appear to be any download links.
>
> The source code page only includes a git: scheme URL.
> It ought to be possible to browse the source without needing to install Git.
>
> The website needs plenty of TLC...
>
> As such, I don't think it's ready to become a TLP.
>
>
> On 7 March 2014 20:16, Dave Brondsema  wrote:
>> Hi everyone,
>>
>> The Apache Allura podling has discussed and voted to graduate from the
>> incubator.  We've made two releases, added several PPMC members, have been
>> working with Infra to set up forge-allura.a.o, etc.  We would now like the 
>> IPMC
>> to vote.
>>
>> Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5
>> Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l
>> Community results:
>>
>> +1
>> Roberto Galoppini
>> Wayne Witzel III
>> Cory Johns
>> Dave Brondsema (IPMC)
>> Rich Bowen (IPMC)
>> Simone Gatti
>> Stefano Invernizzi
>> Alvaro del Castillo
>> Jim Jagielski (IPMC)
>> Tim Van Steenburgh
>>
>> +0
>> (none)
>>
>> -1
>> (none)
>>
>>
>> Please VOTE below on the graduation of Apache Allura from the
>> Incubator. The graduation resolution is pasted below.
>> The VOTE will be open for at least 72 hours:
>>
>> [ ] +1 Graduate Apache Allura from the Incubator.
>> [ ] +0 Don't care.
>> [ ] -1 Don't graduate Apache Allura from the Incubator because
>>
>>
>>
>>
>> X. Establish the Apache Allura 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 a software development infrastructure
>>platform commonly known as a "forge".
>>
>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>Committee (PMC), to be known as the "Apache Allura Project",
>>be and hereby is established pursuant to Bylaws of the
>>Foundation; and be it further
>>
>>RESOLVED, that the Apache Allura Project be and hereby is
>>responsible for the creation and maintenance of software
>>related to a software development infrastructure platform
>>commonly known as a "forge"; and be it further
>>
>>RESOLVED, that the office of "Vice President, Apache Allura" 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 Allura Project, and to have primary responsibility
>>for management of the projects within the scope of
>>responsibility of the Apache Allura 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 Allura Project:
>>
>>  * Tim Van Steenburgh 
>>  * Wayne Witzel III   
>>  * Cory Johns 
>>  * Dave Brondsema 
>>  * Roberto Galoppini  
>>  * Alvaro del Castillo
>>  * Stefano Invernizzi 
>>  * Simone Gatti   
>>  * Jim Jagielski  
>>
>>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Brondsema
>>be appointed to the office of Vice President, Apache Allura, to
>>serve in accordance with and subject to the direction of the
>>Board of Directors and the Bylaws of the Foundation until
&

Re: [VOTE] Graduation of Apache Olingo from the Incubator

[sebb]

The website does not appear to have a License link.

This must link to http://www.apache.org/licenses/

On 13 March 2014 12:41, Dave Fisher  wrote:
> Hi (I flipped the reply-to to be  general@i.a.o)
>
> +1 (binding, Mentor)
>
> Regards,
> Dave
>
> On Mar 13, 2014, at 2:17 AM, Florian Müller wrote:
>
>> Hi all,
>>
>> The Apache Olingo community has VOTEd to graduate from the incubator [1][2].
>>
>> Apache Olingo entered the Incubator in July 2013, has done two releases,
>> has added new contributors, received code contributions, and has an
>> active community.
>>
>> Please find the proposed board resolution below.
>>
>>
>> Please VOTE below on the graduation of Apache Olingo from the
>> Incubator. The graduation resolution is pasted below.
>> I'll leave the VOTE open for at least 72 hours:
>>
>> [ ] +1 Graduate Apache Olingo podling from Apache Incubator
>> [ ] +0 Indifferent to the graduation status of Apache Olingo podling
>> [ ] -1 Reject graduation of Apache Olingo podling from Apache Incubator
>> because ...
>>
>>
>>
>> My vote is +1 (binding).
>>
>>
>> Thanks,
>>
>> Florian
>>
>>
>>
>> [1] http://s.apache.org/olingo-graduation-vote
>> [2] http://s.apache.org/olingo-graduation-vote-result
>>
>>
>> Resolution:
>>
>>   Establish the Apache Olingo 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 providing an implemention of the
>>   OASIS OData (Open Data Protocol) specifications, in
>>   server and client form.
>>
>>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>   Committee (PMC), to be known as the "Apache Olingo Project",
>>   be and hereby is established pursuant to Bylaws of the
>>   Foundation; and be it further
>>
>>   RESOLVED, that the Apache Olingo Project be and hereby is
>>   responsible for the creation and maintenance of software
>>   related to providing an implemention of the OASIS OData
>>   (Open Data Protocol) specifications, in server and client
>>   form; and be it further
>>
>>   RESOLVED, that the office of "Vice President, Olingo" 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 Olingo Project, and to have primary responsibility
>>   for management of the projects within the scope of
>>   responsibility of the Apache Olingo 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 Olingo Project:
>>
>> * Florian Mueller   
>> * Dave Fisher   
>> * Christian Amend   
>> * Francesco Chicchiriccò
>> * Jens Huesken  
>> * Michael Bolz  
>> * Stephan Klevenz   
>> * Tamara Boehm  
>> * Challen He
>> * Chandan V A   
>> * Eduard Koller 
>>
>>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Klevenz
>>   be appointed to the office of Vice President, Olingo, 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 Olingo 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 Olingo Project; and be it further
>>
>>   RESOLVED, that the Apache Olingo Project be and hereby
>>   is tasked with the migration and rationalization of the Apache
>>   Incubator Olingo podling; and be it further
>>
>>   RESOLVED, that all responsibilities pertaining to the Apache
>>   Incubator Olingo podling encumbered upon the Apache Incubator
>>   Project are hereafter discharged.
>>
>>
>>
>
>
> -
> 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] Graduation of Apache Allura from the Incubator

[sebb]

On 13 March 2014 22:10, Rich Bowen  wrote:
> To be clear, are you voting -1 on this? I feel like most of these are
> cosmetic issues that could be addressed in a weekend.

I imagine the issues could be addressed in a weekend.
However I don't regard them as cosmetic issues.
So until this is done, I don't think the podling is ready to graduate.

> The Allura software is a software development forge and as such it makes
> sense for it to be self hosted. This may result in some metaphors that are
> a little unfamiliar on the website

No idea what you mean by that paragraph.

> As to the project being forge software, rather than being a projecy which
> develops forge software, that feels like semantic pickiness, but we will
> address that immediately.

AIUI this is an important part of the branding.
Unless the Allura brand is clearly associated with a particular type
of software, it may be difficult to defend Allura as a trademark of
the ASF.

> --
> Rich Bowen, mobile edition
> rbo...@rcbowen.com
> Please forgive top posting.
> On Mar 13, 2014 2:35 PM, "sebb"  wrote:
>
>> The Allura website does not appear to follow the branding guidelines.
>>
>> The page footer does not mention Apache Allura and Allura as trademarks
>> Also the footer date is still 2011
>>
>> The License link must point to http://www.apache.org/licenses/   - not
>> to a local copy of the license.
>>
>> The intro. paragraph starts:
>>
>> "The Allura Project is forge software "
>>
>> This does not make sense - a project is not software.
>>
>> The bug tracker link on the main page is broken.
>>
>> The page
>> https://incubator.apache.org/allura/contributors.html
>> has at least one incorrect Apache id, and one missing id
>>
>> As noted elsethread, there don't appear to be any download links.
>>
>> The source code page only includes a git: scheme URL.
>> It ought to be possible to browse the source without needing to install
>> Git.
>>
>> The website needs plenty of TLC...
>>
>> As such, I don't think it's ready to become a TLP.
>>
>>
>> On 7 March 2014 20:16, Dave Brondsema  wrote:
>> > Hi everyone,
>> >
>> > The Apache Allura podling has discussed and voted to graduate from the
>> > incubator.  We've made two releases, added several PPMC members, have
>> been
>> > working with Infra to set up forge-allura.a.o, etc.  We would now like
>> the IPMC
>> > to vote.
>> >
>> > Discuss thread: http://markmail.org/message/wdddve3kxceqvgj5
>> > Vote thread: http://markmail.org/message/4g54fcxwb4xxys5l
>> > Community results:
>> >
>> > +1
>> > Roberto Galoppini
>> > Wayne Witzel III
>> > Cory Johns
>> > Dave Brondsema (IPMC)
>> > Rich Bowen (IPMC)
>> > Simone Gatti
>> > Stefano Invernizzi
>> > Alvaro del Castillo
>> > Jim Jagielski (IPMC)
>> > Tim Van Steenburgh
>> >
>> > +0
>> > (none)
>> >
>> > -1
>> > (none)
>> >
>> >
>> > Please VOTE below on the graduation of Apache Allura from the
>> > Incubator. The graduation resolution is pasted below.
>> > The VOTE will be open for at least 72 hours:
>> >
>> > [ ] +1 Graduate Apache Allura from the Incubator.
>> > [ ] +0 Don't care.
>> > [ ] -1 Don't graduate Apache Allura from the Incubator because
>> >
>> >
>> >
>> >
>> > X. Establish the Apache Allura 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 a software development infrastructure
>> >platform commonly known as a "forge".
>> >
>> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> >Committee (PMC), to be known as the "Apache Allura Project",
>> >be and hereby is established pursuant to Bylaws of the
>> >Foundation; and be it further
>> >
>> >RESOLVED, that the Apache Allura Project be and hereby is
>> >responsible for the creation and maintenance of software
>> >related to a software developmen

Re: [VOTE] Graduation of Apache Allura from the Incubator

[sebb]

t; documentation living elsewhere is an inherent problem, but it gives me
>>> pause.
>>>
>>> Individually I don't know that any of these are problematic; but I am
>>> curious what the mentors take on it is.
>>>
>>> --David
>>
>>
>> And it's just dawned on me what's happening.
>> The project is using http://forge-allura.apache.org/p/allura as it's
>> home page instead of http://incubator.apache.org/allura which appears
>> to have all of the appropriate content (according to a google cache)
>> but is down right now. It's making more sense; is the intention to
>> make that the project home page? (e.g. allura.apache.org)
>>
>
> You got it!  (And bad timing that it was down for several hours today -
> its back up now).
>
> Roman and sebb had similar comments to yours, so I'll respond in a
> single email.
>
> We are self-hosting at http://forge-allura.apache.org/p/allura so that
> is really our "home page".  It has a clear download link, and git browse
> link, and the text doesn't equate the project == the software.  But it
> is missing a link to http://www.apache.org/licenses/LICENSE-2.0.  (Note
> this domain forge-allura.a.o also has the future potential to be a
> project hosting platform for other interested Apache projects besides
> Allura itself)
>
> http://incubator.apache.org/allura is not maintained as is obvious.
> That should just go away or be redirected to
> forge-allura.apache.org/p/allura  Similarly when we're a TLP,
> allura.apache.org can just redirect there.
>
> We should update http://sf.net/p/allura to remove the SF logo, and
> clearly identify it as Apache Allura and incubating, so it adheres with
> Apache branding guidelines.
>
> The docs at http://allura.sourceforge.net/docs/ could be moved to live
> at a URL like http://forge-allura.apache.org/p/allura/docs with a little
> work.  No reason not to.
>
> Tickets are the other item still on SourceForge.  We do want to move
> them over to the forge-allura.a.o host, but to be frank its going to be
> quite a lot of work and we haven't gotten to it.  The SourceForge ticket
> tracker is configured to send ticket activity to the allura-dev list so
> there is visibility and transparency to ticket activity.  We didn't
> think it'd be a graduation blocker to have tickets on a different host.
>  As has been mentioned, other projects have tickets elsewhere too.
>
> I hope this helps clarify the situation.  We will work on polishing up
> the remaining rough edges (perhaps everything except tickets location)
> in the next few days and then provide an update again on this thread.
>
> Thanks
>
> --
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
><><
>

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

Re: [VOTE] Graduation of Apache Olingo from the Incubator

[sebb]

Thanks, but although the license is an ASF license, what's important
to end-users is the license for Olingo itself.

I think it needs to be a top-level link, and should be headed
"License" not "Licenses"

Just noticed that there is a problem with the page footers as well.
They currently say:

>>
© Copyright 2013 The Apache Software Foundation, Licensed under the
Apache License, Version 2.0. Apache, the Apache feather logo and the
project logo are trademarks of The Apache Software Foundation.
<<

The footer must claim Apache Olingo and Olingo as trademarks of the
ASF.  See for example the Tomcat footer [1]

>>
Copyright © 1999-2014, The Apache Software Foundation
Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache
Tomcat project logo are trademarks of the Apache Software Foundation.
<<

It helps to have the text centred and spread over two lines as is done
by Tomcat (and the ASF site, etc)

[1] http://tomcat.apache.org/

On 14 March 2014 07:08, Klevenz, Stephan  wrote:
> Thanks for pointing out this.
>
> It is fixed [1,2].
>
> Regards,
> Stephan
>
> [1] https://issues.apache.org/jira/browse/OLINGO-208
> [2] http://olingo.incubator.apache.org
>
> On 13.03.14 19:39, "sebb"  wrote:
>
>>The website does not appear to have a License link.
>>
>>This must link to http://www.apache.org/licenses/
>>
>>On 13 March 2014 12:41, Dave Fisher  wrote:
>>> Hi (I flipped the reply-to to be  general@i.a.o)
>>>
>>> +1 (binding, Mentor)
>>>
>>> Regards,
>>> Dave
>>>
>>> On Mar 13, 2014, at 2:17 AM, Florian Müller wrote:
>>>
>>>> Hi all,
>>>>
>>>> The Apache Olingo community has VOTEd to graduate from the incubator
>>>>[1][2].
>>>>
>>>> Apache Olingo entered the Incubator in July 2013, has done two
>>>>releases,
>>>> has added new contributors, received code contributions, and has an
>>>> active community.
>>>>
>>>> Please find the proposed board resolution below.
>>>>
>>>>
>>>> Please VOTE below on the graduation of Apache Olingo from the
>>>> Incubator. The graduation resolution is pasted below.
>>>> I'll leave the VOTE open for at least 72 hours:
>>>>
>>>> [ ] +1 Graduate Apache Olingo podling from Apache Incubator
>>>> [ ] +0 Indifferent to the graduation status of Apache Olingo podling
>>>> [ ] -1 Reject graduation of Apache Olingo podling from Apache Incubator
>>>> because ...
>>>>
>>>>
>>>>
>>>> My vote is +1 (binding).
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Florian
>>>>
>>>>
>>>>
>>>> [1] http://s.apache.org/olingo-graduation-vote
>>>> [2] http://s.apache.org/olingo-graduation-vote-result
>>>>
>>>>
>>>> Resolution:
>>>>
>>>>   Establish the Apache Olingo 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 providing an implemention of the
>>>>   OASIS OData (Open Data Protocol) specifications, in
>>>>   server and client form.
>>>>
>>>>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>>   Committee (PMC), to be known as the "Apache Olingo Project",
>>>>   be and hereby is established pursuant to Bylaws of the
>>>>   Foundation; and be it further
>>>>
>>>>   RESOLVED, that the Apache Olingo Project be and hereby is
>>>>   responsible for the creation and maintenance of software
>>>>   related to providing an implemention of the OASIS OData
>>>>   (Open Data Protocol) specifications, in server and client
>>>>   form; and be it further
>>>>
>>>>   RESOLVED, that the office of "Vice President, Olingo" 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 Olingo Project, and to have primary responsibility
>>>> 

Re: [VOTE] Graduation of Apache Olingo from the Incubator

[sebb]

Home page looks good.

However other pages don't have the new footer and header. Possibly
just need rebuilding.

BTW, it's now 2014

Minor nit: the link for the "Apache Olingo tm" header item probably
ought to point to the home page rather than using "#" which only takes
one to the top of the page.


On 14 March 2014 13:22, Klevenz, Stephan  wrote:
> Ok, it's all changed. Can you please have a look again?
>
> -- Stephan
>
>
> On 14.03.14 13:35, "sebb"  wrote:
>
>>Thanks, but although the license is an ASF license, what's important
>>to end-users is the license for Olingo itself.
>>
>>I think it needs to be a top-level link, and should be headed
>>"License" not "Licenses"
>>
>>Just noticed that there is a problem with the page footers as well.
>>They currently say:
>>
>>>>
>>© Copyright 2013 The Apache Software Foundation, Licensed under the
>>Apache License, Version 2.0. Apache, the Apache feather logo and the
>>project logo are trademarks of The Apache Software Foundation.
>><<
>>
>>The footer must claim Apache Olingo and Olingo as trademarks of the
>>ASF.  See for example the Tomcat footer [1]
>>
>>>>
>>Copyright © 1999-2014, The Apache Software Foundation
>>Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache
>>Tomcat project logo are trademarks of the Apache Software Foundation.
>><<
>>
>>It helps to have the text centred and spread over two lines as is done
>>by Tomcat (and the ASF site, etc)
>>
>>[1] http://tomcat.apache.org/
>>
>>On 14 March 2014 07:08, Klevenz, Stephan  wrote:
>>> Thanks for pointing out this.
>>>
>>> It is fixed [1,2].
>>>
>>> Regards,
>>> Stephan
>>>
>>> [1] https://issues.apache.org/jira/browse/OLINGO-208
>>> [2] http://olingo.incubator.apache.org
>>>
>>> On 13.03.14 19:39, "sebb"  wrote:
>>>
>>>>The website does not appear to have a License link.
>>>>
>>>>This must link to http://www.apache.org/licenses/
>>>>
>>>>On 13 March 2014 12:41, Dave Fisher  wrote:
>>>>> Hi (I flipped the reply-to to be  general@i.a.o)
>>>>>
>>>>> +1 (binding, Mentor)
>>>>>
>>>>> Regards,
>>>>> Dave
>>>>>
>>>>> On Mar 13, 2014, at 2:17 AM, Florian Müller wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> The Apache Olingo community has VOTEd to graduate from the incubator
>>>>>>[1][2].
>>>>>>
>>>>>> Apache Olingo entered the Incubator in July 2013, has done two
>>>>>>releases,
>>>>>> has added new contributors, received code contributions, and has an
>>>>>> active community.
>>>>>>
>>>>>> Please find the proposed board resolution below.
>>>>>>
>>>>>>
>>>>>> Please VOTE below on the graduation of Apache Olingo from the
>>>>>> Incubator. The graduation resolution is pasted below.
>>>>>> I'll leave the VOTE open for at least 72 hours:
>>>>>>
>>>>>> [ ] +1 Graduate Apache Olingo podling from Apache Incubator
>>>>>> [ ] +0 Indifferent to the graduation status of Apache Olingo podling
>>>>>> [ ] -1 Reject graduation of Apache Olingo podling from Apache
>>>>>>Incubator
>>>>>> because ...
>>>>>>
>>>>>>
>>>>>>
>>>>>> My vote is +1 (binding).
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Florian
>>>>>>
>>>>>>
>>>>>>
>>>>>> [1] http://s.apache.org/olingo-graduation-vote
>>>>>> [2] http://s.apache.org/olingo-graduation-vote-result
>>>>>>
>>>>>>
>>>>>> Resolution:
>>>>>>
>>>>>>   Establish the Apache Olingo 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 o

Re: [VOTE] Graduation of Apache Olingo from the Incubator

[sebb]

All looks good now.
Sorry, it was a cache issue.

Thanks for the very prompt attention to these matters.

On 14 March 2014 14:06, Klevenz, Stephan  wrote:
> Hi Sebb,
>
> see my comments below.
>
> Stephan
>
> On 14.03.14 14:46, "sebb"  wrote:
>
>>Home page looks good.
>>
>>However other pages don't have the new footer and header. Possibly
>>just need rebuilding.
>
> This could be a cache issue. If I do a command+shift+R then the current
> version is reloaded.
>
>
>>
>>BTW, it's now 2014
>
> So, to be accurate I have to write 2013-2014 because of Olingo was
> launched in 2013, right?
>
>>
>>Minor nit: the link for the "Apache Olingo tm" header item probably
>>ought to point to the home page rather than using "#" which only takes
>>one to the top of the page.
>
> I'am going to fix this as well...
>
>>
>>
>>On 14 March 2014 13:22, Klevenz, Stephan  wrote:
>>> Ok, it's all changed. Can you please have a look again?
>>>
>>> -- Stephan
>>>
>>>
>>> On 14.03.14 13:35, "sebb"  wrote:
>>>
>>>>Thanks, but although the license is an ASF license, what's important
>>>>to end-users is the license for Olingo itself.
>>>>
>>>>I think it needs to be a top-level link, and should be headed
>>>>"License" not "Licenses"
>>>>
>>>>Just noticed that there is a problem with the page footers as well.
>>>>They currently say:
>>>>
>>>>>>
>>>>© Copyright 2013 The Apache Software Foundation, Licensed under the
>>>>Apache License, Version 2.0. Apache, the Apache feather logo and the
>>>>project logo are trademarks of The Apache Software Foundation.
>>>><<
>>>>
>>>>The footer must claim Apache Olingo and Olingo as trademarks of the
>>>>ASF.  See for example the Tomcat footer [1]
>>>>
>>>>>>
>>>>Copyright © 1999-2014, The Apache Software Foundation
>>>>Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache
>>>>Tomcat project logo are trademarks of the Apache Software Foundation.
>>>><<
>>>>
>>>>It helps to have the text centred and spread over two lines as is done
>>>>by Tomcat (and the ASF site, etc)
>>>>
>>>>[1] http://tomcat.apache.org/
>>>>
>>>>On 14 March 2014 07:08, Klevenz, Stephan 
>>>>wrote:
>>>>> Thanks for pointing out this.
>>>>>
>>>>> It is fixed [1,2].
>>>>>
>>>>> Regards,
>>>>> Stephan
>>>>>
>>>>> [1] https://issues.apache.org/jira/browse/OLINGO-208
>>>>> [2] http://olingo.incubator.apache.org
>>>>>
>>>>> On 13.03.14 19:39, "sebb"  wrote:
>>>>>
>>>>>>The website does not appear to have a License link.
>>>>>>
>>>>>>This must link to http://www.apache.org/licenses/
>>>>>>
>>>>>>On 13 March 2014 12:41, Dave Fisher  wrote:
>>>>>>> Hi (I flipped the reply-to to be  general@i.a.o)
>>>>>>>
>>>>>>> +1 (binding, Mentor)
>>>>>>>
>>>>>>> Regards,
>>>>>>> Dave
>>>>>>>
>>>>>>> On Mar 13, 2014, at 2:17 AM, Florian Müller wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> The Apache Olingo community has VOTEd to graduate from the
>>>>>>>>incubator
>>>>>>>>[1][2].
>>>>>>>>
>>>>>>>> Apache Olingo entered the Incubator in July 2013, has done two
>>>>>>>>releases,
>>>>>>>> has added new contributors, received code contributions, and has an
>>>>>>>> active community.
>>>>>>>>
>>>>>>>> Please find the proposed board resolution below.
>>>>>>>>
>>>>>>>>
>>>>>>>> Please VOTE below on the graduation of Apache Olingo from the
>>>>>>>> Incubator. The graduation resolution is pasted below.
>>>>>>>> I'll leave the VOTE open for at least 72 hours:
>>>>>>>>
>>>>>>>&g

Re: [VOTE] Graduation of Apache Allura from the Incubator

[sebb]

On 14 March 2014 20:16, Cory Johns  wrote:
> Ok, I think we've addressed all of the issues.  Namely:
>
> * The status page (http://incubator.staging.apache.org/projects/allura.html)
> has been updated, and now the correct canonical project web page (namely
> https://forge-allura.apache.org/p/allura/), as well as having an improved
> project description, links to the docs, and updated news items
>
> * The aforementioned docs are now hosted at
> https://forge-allura.apache.org/docs/ (which is also linked to from the
> main project page at https://forge-allura.apache.org/p/allura/)
>
> * The footer on https://forge-allura.apache.org/p/allura/ has been fixed
> with the correct trademark and copyright information and links
>
> * All Apache Allura (incubating) references have been corrected on
> http://incubator.staging.apache.org/projects/allura.html,
> https://forge-allura.apache.org/p/allura/, and
> https://sourceforge.net/projects/allura/
>
> Additionally, the unused page at http://incubator.apache.org/allura/ has
> been updated to automatically redirect to the main project page at
> https://forge-allura.apache.org/p/allura/, and its associated (unused)
> download page has been updated with a link to the releases repository, so
> that they are useful for people who may have bookmarked them previously,
> even though they are no longer linked to from anywhere.
>
> This should cover all of the concerns that have been raised thus far, save
> for the location of the issue tracker which, as previously mentioned, is a
> difficult undertaking that will be addressed in the future (and the status
> page indicates this).

Well, there is still the issue of the download page.
There does not seem to be any way to find it from the new site.

Also there are some branding requirements that are missing from the site.

See http://www.apache.org/foundation/marks/pmcs.html

In particular

http://www.apache.org/foundation/marks/pmcs.html#navigation

> With these changes, we are hopeful that we can proceed with and pass the
> graduation vote.
>
>
> On Fri, Mar 14, 2014 at 8:18 AM, sebb  wrote:
>
>> If the home page really is
>>
>> [1] http://forge-allura.apache.org/p/allura
>>
>> then why does the status page
>>
>> [2] http://incubator.apache.org/projects/allura.html
>>
>> point to
>>
>> [3] http://incubator.apache.org/allura/ ?
>>
>> The host [1] is described on the status page [2] as being the Wiki,
>> which is normally separate from the project page.
>>
>> There seems to be very little on [3] that is not on [1] so it could
>> probably be dropped.
>>
>> However the Wiki [1] does not have the correct footer, it only says:
>>
>> "This project is powered by Allura."
>>
>> That should be Apache Allura.
>> And the pages also need the standard trademark attributions.
>> The site [3] does have the following:
>>
>> >>
>> Copyright © 2011 The Apache Software Foundation, Licensed under the
>> Apache License, Version 2.0.
>> Apache and the Apache feather logo are trademarks of The Apache
>> Software Foundation.
>> <<
>>
>> However that fails to mention Apache Allura and Allura as being
>> trademarks of the ASF.
>>
>>
>> On 14 March 2014 04:32, Dave Brondsema  wrote:
>> > On 03/13/2014 10:00 PM, David Nalley wrote:
>> >> On Thu, Mar 13, 2014 at 9:54 PM, David Nalley  wrote:
>> >>> On Thu, Mar 13, 2014 at 1:29 PM, Roman Shaposhnik 
>> wrote:
>> >>>> After looking at it for some time, my optimistic outlook
>> >>>> on the project would be +0 vote at best.
>> >>>>
>> >>>> On the plus side, the community seems to be really active
>> >>>> and reasonably diverse. But if feels, like ASF has not yet
>> >>>> become a true home for the project.
>> >>>>
>> >>>> Here's what I'm talking about: as a casual bystander who
>> >>>> was trying to view Allura as an ASF project -- I had difficult
>> >>>> time. First of all, I couldn't even get to the releases easily
>> >>>> enough: https://incubator.apache.org/allura/downloads.html
>> >>>> When I managed to get there the first thing that the README
>> >>>> instructed me to do is to go to https://forge-allura.apache.org/
>> >>>> What is that? How does it relate to the project?
>> >>>>
>> >>>> In fact, from the dev list it feels like there may be yet another
>> >>>> canonical place for the Allura

Re: [VOTE] Graduation of Apache Allura from the Incubator

[sebb]

On 16 March 2014 03:43, Dave Brondsema  wrote:
> On 3/14/14 8:19 PM, sebb wrote:
>> On 14 March 2014 20:16, Cory Johns  wrote:
>>> Ok, I think we've addressed all of the issues.  Namely:
>>>
>>> * The status page (http://incubator.staging.apache.org/projects/allura.html)
>>> has been updated, and now the correct canonical project web page (namely
>>> https://forge-allura.apache.org/p/allura/), as well as having an improved
>>> project description, links to the docs, and updated news items
>>>
>>> * The aforementioned docs are now hosted at
>>> https://forge-allura.apache.org/docs/ (which is also linked to from the
>>> main project page at https://forge-allura.apache.org/p/allura/)
>>>
>>> * The footer on https://forge-allura.apache.org/p/allura/ has been fixed
>>> with the correct trademark and copyright information and links
>>>
>>> * All Apache Allura (incubating) references have been corrected on
>>> http://incubator.staging.apache.org/projects/allura.html,
>>> https://forge-allura.apache.org/p/allura/, and
>>> https://sourceforge.net/projects/allura/
>>>
>>> Additionally, the unused page at http://incubator.apache.org/allura/ has
>>> been updated to automatically redirect to the main project page at
>>> https://forge-allura.apache.org/p/allura/, and its associated (unused)
>>> download page has been updated with a link to the releases repository, so
>>> that they are useful for people who may have bookmarked them previously,
>>> even though they are no longer linked to from anywhere.
>>>
>>> This should cover all of the concerns that have been raised thus far, save
>>> for the location of the issue tracker which, as previously mentioned, is a
>>> difficult undertaking that will be addressed in the future (and the status
>>> page indicates this).
>>
>> Well, there is still the issue of the download page.
>> There does not seem to be any way to find it from the new site.
>
> There's a download button in the middle of the page.

Not sure how I missed that before - I was expecting to find a top-level link.

However there needs to be a link to the KEYS file [1] otherwise users
cannot easily use the signature.

BTW, Allura 1.0.1 should now be removed from the dist area - only the
latest supported release(s) should remain on the main mirrors.

[1] http://www.apache.org/dist/incubator/allura/KEYS

>>
>> Also there are some branding requirements that are missing from the site.
>>
>> See http://www.apache.org/foundation/marks/pmcs.html
>>
>> In particular
>>
>> http://www.apache.org/foundation/marks/pmcs.html#navigation
>
> I've added these links to our main navigation page.  I've also added the (tm) 
> as
> required.
>
> Thanks for your feedback on all this.  Is there anything else we're missing 
> for
> graduation?

Looks a lot better now, thanks!

>>
>>> With these changes, we are hopeful that we can proceed with and pass the
>>> graduation vote.
>>>
>>>
>>> On Fri, Mar 14, 2014 at 8:18 AM, sebb  wrote:
>>>
>>>> If the home page really is
>>>>
>>>> [1] http://forge-allura.apache.org/p/allura
>>>>
>>>> then why does the status page
>>>>
>>>> [2] http://incubator.apache.org/projects/allura.html
>>>>
>>>> point to
>>>>
>>>> [3] http://incubator.apache.org/allura/ ?
>>>>
>>>> The host [1] is described on the status page [2] as being the Wiki,
>>>> which is normally separate from the project page.
>>>>
>>>> There seems to be very little on [3] that is not on [1] so it could
>>>> probably be dropped.
>>>>
>>>> However the Wiki [1] does not have the correct footer, it only says:
>>>>
>>>> "This project is powered by Allura."
>>>>
>>>> That should be Apache Allura.
>>>> And the pages also need the standard trademark attributions.
>>>> The site [3] does have the following:
>>>>
>>>>>>
>>>> Copyright (c) 2011 The Apache Software Foundation, Licensed under the
>>>> Apache License, Version 2.0.
>>>> Apache and the Apache feather logo are trademarks of The Apache
>>>> Software Foundation.
>>>> <<
>>>>
>>>> However that fails to mention Apache Allura and Allura as being
>>>> trademarks of the ASF.
>>>>
>>>>
>&g

Re: [VOTE] Graduation of Apache Allura from the Incubator

[sebb]

On 15 March 2014 01:23, Justin Mclean  wrote:
> HI,
>
> Just a minor thing (IMO). I was just taking a look at [1] and what strikes me 
> is a lack of ASF branding.
>
> While it's clear in the text and from the domain that the project is an ASF 
> one, the subtitles "Forge software for hosting software projects" and 
> "Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh" and lack 
> of links back to the ASF don't immediately give that impression.

That's a good point.

The board decided a long time ago that @author tags were deprecated in
code; partly because they get out of date, but mainly because the ASF
is a community, and code is a co-operative effort.

Seems to me the "Brought to you" sentence has similar problems, and
should be removed.

[There are other ways to attribute contributions, e.g. on a page that
lists committers, in the Maven POM (if used) etc.]

Also I think (almost?) all other TLPs include the ASF feather which
links back to the main ASF page.

> I also looked at where I thought the release should be published [2] and it 
> contains no files. Is that the correct location? That's the path in the 
> release guidelines. [2]

Yes and no - [2] is where RCs can be uploaded for voting; actual
releases are published from [2a], e.g. by moving them from [2].

There are files at [2a].

> It also quite hard for someone outside the project to see what is happing on 
> the mailing list due to the large amount at allure ticket emails. Have you 
> consider having a separate issues list?

+1

> Thanks,
> Justin
>
> 1. 
> https://forge-allura.apache.org/p/allura/wiki/Apache%20Allura%20(incubating)%20Wiki/
> 2. https://dist.apache.org/repos/dist/dev/incubator/allura/

2a. https://dist.apache.org/repos/dist/release/incubator/allura/

> 3. https://forge-allura.apache.org/p/allura/wiki/ASF%20Release%20Guidelines/
> -
> 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] Graduation of Apache Allura from the Incubator

[sebb]

On 17 March 2014 15:17, Cory Johns  wrote:
> On Mon, Mar 17, 2014 at 6:58 AM, sebb  wrote:
>
>> On 15 March 2014 01:23, Justin Mclean  wrote:
>> >
>> > While it's clear in the text and from the domain that the project is an
>> ASF one, the subtitles "Forge software for hosting software projects" and
>> "Brought to you by: brondsem, masterbunnyfu, rbowen, vansteenburgh" and
>> lack of links back to the ASF don't immediately give that impression.
>>
>> That's a good point.
>>
>> The board decided a long time ago that @author tags were deprecated in
>> code; partly because they get out of date, but mainly because the ASF
>> is a community, and code is a co-operative effort.
>>
>> Seems to me the "Brought to you" sentence has similar problems, and
>> should be removed.
>
>
> Well, I should note that the "Brought to you by" line is actually
> automatically generated from the project permissions, so there is little
> chance of it getting out of date.

What about when people move on from Allura and no longer have permissions?
That does not necessarily mean that their contribution to the project
is no longer important.
Even if their code has been entirely replaced by later changes, they
still contributed to the software.

> That said, it will be more useful as we
> move more of the Allura work (specifically, ticket activity) over from the
> old SourceForge location to the Apache hosted Allura instance, as is the
> plan.

Same issue; the ASF is about community-developed code, not individual coders.
Individuals come and go; the ASF hopeully will outlast us all!

>
>>
>>
> Also I think (almost?) all other TLPs include the ASF feather which
>> links back to the main ASF page.
>>
>>
> I have updated the page at https://forge-allura.apache.org/p/allura/ to
> include the ASF feather logo which links to
> http://www.apache.org/foundation/

The ASF feather is normally present in the header, not just the home page.
Is it possible to add it there?

>
>> > It also quite hard for someone outside the project to see what is
>> happing on the mailing list due to the large amount at allure ticket
>> emails. Have you consider having a separate issues list?
>>
>> +1
>
>
> This has been raised before and some things have been done to improve the
> tracker notifications on the mailing list (combining status change and
> comment notifications, fixing threading, etc) and it was decided at the
> time that it was reasonable to continue to include that traffic (with
> improvements) on the list.  However, I believe the possibility of splitting
> it in the future was left open, should anyone continue to feel it was a
> problem.
>
> Still, this doesn't seem to me like something that should block graduation,
> as the tracker communications are indeed related to Allura development.

Agreed the destination of tracker notifications is not a blocker to graduation.
But could perhaps become a blocker to community growth, so needs to be
monitored.

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