Hi,
Tomek has filled in the ip clearance document and has a couple of
questions related to it.
AFAIK, the contribution has to be managed by an ASF officer or member,
and I am neither. Therefore I would like to ask someone to guide the
final steps of this contribution.
Thanks,
Robert
On Thu, Jul 10, 2014 at 2:02 PM, Tomek Rękawek
<[email protected]> wrote:
> Hello Robert,
>
> I filled the template - please find it attached. I didn't know how to fill
> the "Copyright" and "Verify distribution rights" sections and I also don't
> know who is the ASF office or member managing the donation (maybe it's you?
> :) Could you take a look on the document and provide me with guidance?
>
> Thanks for your help!
>
> Best regards,
> Tomek
>
>
> On Wed, Jul 9, 2014 at 11:19 AM, Robert Munteanu <[email protected]> wrote:
>>
>> Sorry for the delay Tomek. I just reviewed the contribution and it's
>> sizeable enough to require the IP clearance process. From past
>> experience, once the document is submitted it's enough to let the 72
>> hours pass and then incorporate it.
>>
>> I ran a verify with the 'rat' profile to check for license headers and
>> it checks out fine - README.md and CHANGELOG.md are missing headers,
>> plus a sample json file.
>>
>> IMO none of these actually need it so there's no need to resubmit.
>>
>> Thanks,
>>
>> Robert
>>
>> On Tue, Jul 1, 2014 at 4:23 PM, Robert Munteanu <[email protected]>
>> wrote:
>> > Just sent a reminder to the list, will try directly if no one picks this
>> > up.
>> >
>> > On Mon, Jun 30, 2014 at 12:38 PM, Tomek Rękawek
>> > <[email protected]> wrote:
>> >> Hello Robert,
>> >>
>> >> it seems that the SlingQuery contribution is blocked cause no one
>> >> answers
>> >> the question on the dev-sling. Maybe we should ask someone directly?
>> >> Maybe
>> >> Bertrand would be a good choice?
>> >>
>> >> Regards,
>> >> Tomek
>> >>
>> >>
>> >> On Sun, Jun 22, 2014 at 9:19 PM, Robert Munteanu <[email protected]>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> In SLING-3667 [1] Tomek Rękawek was kind enough to submit the
>> >>> SlingQuery library to the Sling project.
>> >>>
>> >>> I am not certain whether this contribution needs to go through the
>> >>> extra process described at [2] or not, so I'd appreciate if someone
>> >>> with more experience can weigh in on this issue.
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Robert
>> >>>
>> >>> [1]: https://issues.apache.org/jira/browse/SLING-3667
>> >>> [2]: https://www.apache.org/dev/committers.html#code-import
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Tomek Rękawek
>> >> Senior Software Engineer
>> >>
>> >> Cognifide Polska Sp. z o.o.
>> >> skype: trekawek
>> >>
>> >> www.cognifide.com
>
>
>
>
> --
> Tomek Rękawek
> Senior Software Engineer
>
> Cognifide Polska Sp. z o.o.
> skype: trekawek
>
> www.cognifide.com
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<title>SlingQuery Codebase Intellectual Property (IP) Clearance Status</title>
</properties>
<body>
<section id="SlingQuery+Codebase+Intellectual+Property+%28IP%29+Clearance+Status">
<title>SlingQuery Codebase Intellectual Property (IP) Clearance Status</title>
</section>
<section id="Description">
<title>Description</title>
<p>SlingQuery extension is a jQuery-inspired repository traversal tool for Apache Sling.</p>
</section>
<section id="Project+info">
<title>Project info</title>
<ul>
<li>Apache Sling PMC will be responsible for the code</li>
</ul>
<ul>
<li>This contribution will be placed under contrib/extensions</li>
</ul>
<ul>
<li>Officer or member managing donation:</li>
</ul>
<p>
<em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em>
</p>
<section id="Identify+the+codebase">
<title>Identify the codebase</title>
<table>
<tr>
<th>date</th>
<th>item</th>
</tr>
<tr>
<td>2014-06-13</td>
<td>source code provided as a zip package on SLING-3667 (https://issues.apache.org/jira/secure/attachment/12650338/sling-query.zip).</td>
</tr>
</table>
<p>
MD5 or SHA1 sum for donated software: SHA1= 4a0488f00ac81f6ce29eb87e15255418b39bd5a4.
</p>
<section id="Copyright">
<title>Copyright</title>
<table>
<tr>
<th>date</th>
<th>item</th>
</tr>
<tr>
<td>....-..-..</td>
<td>Check and make sure that the papers that transfer rights to
the ASF been received. It is only necessary to transfer
rights for the package, the core code, and any new code
produced by the project.</td>
</tr>
<tr>
<td>....-..-..</td>
<td>Check and make sure that the files that have been donated
have been updated to reflect the new ASF copyright.</td>
</tr>
</table>
<p>
Identify name recorded for software grant: <em>the name of the grant as record
in the grants.txt document so that the grant can be easily identified</em>
</p>
</section>
<section id="Verify+distribution+rights">
<title>Verify distribution rights</title>
<p>
Corporations and individuals holding existing distribution rights:
</p>
<ul>
<li>
<em>Tomasz Rekawek</em>
</li>
</ul>
<table>
<tr>
<th>date</th>
<th>item</th>
</tr>
<tr>
<td>....-..-..</td>
<td>Check that all active committers have a signed CLA on
record.</td>
</tr>
<tr>
<td>....-..-..</td>
<td>Remind active committers that they are responsible for
ensuring that a Corporate CLA is recorded if such is
required to authorize their contributions under their
individual CLA.</td>
</tr>
<tr>
<td>....-..-..</td>
<td>Check and make sure that for all items included with the
distribution that is not under the Apache license, we have
the right to combine with Apache-licensed code and
redistribute.</td>
</tr>
<tr>
<td>....-..-..</td>
<td>Check and make sure that all items depended upon by the
project is covered by one or more of the following approved
licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or
something with essentially the same terms.</td>
</tr>
</table>
<p>Generally, the result of checking off these items will be a
Software Grant, CLA, and Corporate CLA for ASF licensed code,
which must have no dependencies upon items whose licenses that
are incompatible with the Apache License.</p>
</section>
</section>
<section id="Organizational+acceptance+of+responsibility+for+the+project">
<title>Organizational acceptance of responsibility for the project
</title>
<p>
Related VOTEs:
</p>
<ul>
<li><em>The VOTE thread accepting the donation may happen either
before or after IP clearance. Adoption by lazy concensus is acceptable but
not recommended.</em></li>
</ul>
</section>
</section>
</body>
</document>
