If that is the decision of this PMC then I'll be unable to vote +1 without
matching the source back against svn.
Mike, do you agree with the outline of steps required which I posted some days
ago? How do you satisfy yourself that the source is properly licensed? That is,
what steps do you take?
Ari
On 27/08/10 3:47 AM, Mike Kienenberger wrote:
Legally, PMC members are required to verify that the source code is properly
licensed. Most of this generally takes place when the file is committed,
but some diligence is also required for a release.
A release is completely independent of the svn repository, so there's no
need to match something against svn. As a convenience, it's nice to note
how you could pull the files back out of svn for any particular release, but
certainly no requirement.
On Thu, Aug 26, 2010 at 3:50 AM, Aristedes Maniatis<[email protected]>wrote:
On 26/08/10 5:00 PM, Andrus Adamchik wrote:
Please evaluate and cast your votes.
Given the previous discussion, I am unclear about what the PMC's consensus
is about what we are voting on. I posted an email about this a few days
ago... are others in agreement with the general ideas in that?
If PMC decides that each voter needs to verify that the source code is
properly licensed and matches the svn repository, then I don't know how to
do that.
Regards
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
