Oops, just to be clear, I meant we will each sign the Software Grant referencing the same file.
On Sun, Sep 14, 2014 at 10:15 PM, Mahmoud Ali <mudd...@gmail.com> wrote: > We do work together at the same company, but all the work was done during > our spare time, as two people contributing on GitHub, with no involvement > of our company. > > I think in our case we should each sign the ICLA and reference the same > ZIP file, since we both worked together on this. > > I'm just confused about how to send the zip file containing the source > code. I created a branch on our GitHub project which I'll be updating in > order to remove any files that won't be donated. Once I'm done, should I > generate a ZIP file to send in the email to the Secretary with all the > signed forms? > > Thanks for taking the time helping us on this. > > On Sun, Sep 14, 2014 at 2:41 AM, Alex Harui <aha...@adobe.com> wrote: > >> One other note: I found at the bottom of [3] the following: >> >> ----- >> The software grant requires that "Licensor owns or has sufficient rights >> to contribute the software source code...". In the case where there are >> multiple entities involved that only together have sufficient rights (for >> example in the case of an existing external project with multiple >> contributors), there are basically two possibilities to continue: >> >> 1. All entities sign the same software grant together and submit one >> software grant form. This is preferred but obviously can complicate the >> process considerably. >> 2. The alternative is that each party sign its own software grant while >> everyone references the same contribution (designated by a URL and an MD5 >> hash over the ZIP file representing the contribution). It is recommended >> that the software grant form is modified in order to have a line for each >> party so the completeness of the paperwork can be verified upon receipt. >> ----- >> >> There are two relevant points in there: >> A) If you don't have the authority to sign for the other contributor then >> you can both sign or each fill out a grant form. >> B) It isn't required to attach the donated software to a JIRA ticket. >> Adobe has not done so for past donations. For Radii8, a branch and tag >> was provided. Judah could have also provided a zip on some server he >> controls and the MD5 hash. >> >> It probably doesn't matter in this case because Justin already did a quick >> scan so we don't expect to find things that need further adjustment before >> actually being accepted, but in the general case, sometimes things do need >> to change. And then the risk is that if folks see it in JIRA they can >> start grabbing it before it has been truly cleared for use by Apache. It >> is one thing for you to say it is ok to donate, but another thing for >> Apache to accept every file. For example, you can donate a SWF, but >> Apache does not accept compiled source, it only wants source code. Only >> the PMC needs to see the donated package anyway and what finally goes in >> the Apache repo will probably be slightly different, so you have the >> option to tell us where the files are on a less public channel than dev@ >> or JIRA + issues@, or we'll see it in the grant form when the Secretary >> files it. >> >> Looking ahead, here are the steps that follow once you send in the >> software grant form to the Secretary: >> >> 1) We'll get notification from the Secretary that the grant has been >> filed. >> 2) The PMC members can have a look at the files. >> 3) Justin or I will take the files and prepare it to be acceptable for an >> Apache repo. We may need to change headers and/or adjust or add the >> LICENSE and NOTICE files, remove compiled sources, etc. >> 4) Justin or I fill out the IP Clearance form as described in [3]. >> 5) At least one representative from the Apache Incubator reviews the files >> that we claim are acceptable for an Apache repo >> 6) More adjustments are made if other issues are found. >> 7) Once approved, we can commit the files to either a new repo or one of >> the existing repos. >> >> Once again, thank you for taking the time and effort to donate FlatSpark. >> I'm really looking forward to making it work in FlexJS. >> >> -Alex >> >> >> >> [3] http://incubator.apache.org/ip-clearance/ >> >> On 9/13/14 9:16 PM, "Alex Harui" <aha...@adobe.com> wrote: >> >> >Hi Mahmoud, >> > >> >Each of you should file your own ICLA [1]. Just to make sure, none of >> >this work was done for a corporation or while you were employed by a >> >corporation? >> > >> >The software grant [2] is a legal document like [1], but while [1] is >> >about an individual independent of any business, [2] is business >> contract. >> > So, the question is what kind of business relationship, if any, exists >> >between the two of you, and who would sign any other contract on behalf >> of >> >these assets? At Adobe, I don't sign the grant, my boss can't, and >> >neither can his boss, it has to be a VP. If you two are equal partners >> or >> >just two people contributing to GitHub, then both of you should sign the >> >software grant form. >> > >> >HTH, >> >-Alex >> > >> >[1] http://www.apache.org/licenses/icla.txt >> >[2] https://www.apache.org/licenses/software-grant.txt >> > >> >On 9/13/14 12:32 PM, "Mahmoud Ali" <mudd...@gmail.com> wrote: >> > >> >>Since FlatSpark is made by two people, should we both sign the forms? If >> >>so, is there a special form for more than one contributor or should I >> >>just >> >>copy-and-paste when necessary? >> >> >> >>On Sat, Sep 13, 2014 at 12:09 AM, Justin Mclean >> >><jus...@classsoftware.com> >> >>wrote: >> >> >> >>> Hi, >> >>> >> >>> > Regarding the other custom components, should I remove them too on >> >>>the >> >>> zip >> >>> > file I'll be sending? >> >>> >> >>> >> >>> I'd leave them in, they are basically boilerplate and only a few lines >> >>>of >> >>> code. >> >>> >> >>> Justin >> > >> >> >
