Re: [jgit-dev] Shallow fetching

[Vineet Sinha <vineet@xxxxxxxxxxxxx>]

I will confirm with them about the EDL. But, assuming that - a couple of questions (I am trying to expedite things by not having them be the bottleneck):

1. Do they need to fill out any extra forms?

2. Can I submit the patch to Gerrit, or do they need to do it themselves?

3, Can you do a quick scan of the code and let me know how far it is from ready (does it take the right approach)? And if someone else from the community can do the necessary fixes, so that the code can be pushed into JGit?

-Vineet

On Mon, Apr 16, 2012 at 12:18 PM, Shawn Pearce <spearce@xxxxxxxxxxx> wrote:

On Mon, Apr 16, 2012 at 09:13, Vineet Sinha <vineet@xxxxxxxxxxxxx> wrote:
> I head back from the Atlassian guys (see here:
> https://github.com/atlassian/org.eclipse.jgit-atlassian/commit/e28f504193673b3b7ffebc868f17b43ae982e80b#commitcomment-1216657 ).
>
> They did confirm writing the code while working for Atlassian, and that
> Atlassian is interested in licensing the contributions under the Eclipse
> License.

Under the Eclipse Development License (EDL) or the Eclipse Public
License (EPL)?

JGit and its contributions must be under the Eclipse Development
Liencse (EDL), which is just a renamed new-style 3-clause BSD.

The terms of the Eclipse Public License (EPL) are very different, and
cannot be accepted in JGit.