Skip to content
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.

JSR358-66: Modify Process Document to simplify the transition of a JSR from one Spec Lead (or Maintenance Lead) to another #47

Open
apastsya opened this issue Apr 8, 2014 · 5 comments
Labels

Comments

@apastsya
Copy link
Member

apastsya commented Apr 8, 2014

Jira issue originally created by user pcurran:

Sections 2.1.1 and Section 5.1.1 address the transfer of JSRs from one Spec Lead (or Maintenance Lead) to another. Can we add anything here to make the transition simpler?

Should we insert language encouraging the outgoing SL or ML to transfer IP to the new lead since without this it will effectively be impossible for someone else to take over? (Whether or not this is necessary will depend on how the output of the JSR is licensed.)

@apastsya
Copy link
Member Author

apastsya commented Apr 1, 2015

Comment created by pcurran:

If IP vests immediately it is contributed and we have a flat IP-flow whereby rights are passed directly from the contributor to whoever is developing the JSR then we may not need anything else.

@apastsya
Copy link
Member Author

Comment created by ivar_grimstad:

I think it is actually section 3.2.2.5 in the Process Document that mentions transfer?

@apastsya
Copy link
Member Author

Comment created by ivar_grimstad:

Since licensing models and organizations are different, this is probably different from spec
to spec. The heaviest load of a transfer is probably on the current owner of the spec, and
that is where the JCP probably should support an supervise the most.

As the receiving part in a transfer, the real work starts after the transfer. E.g. my involvement
in the transfer of JSR 371 has been minimal up to now. Just answering a question now and then.
It would be nice to get a plan from the current owner of the spec for what to expect and when. Maybe that is something that could be specified in more detail. Currently I think it says that
the transfer must be made within 30 days. Maybe specify which items a transfer consist of? Code, web site, Twitter handle, Issue tracker, CI jobs? We probably can't be to specific either, so it has to be kept general.

@apastsya
Copy link
Member Author

Comment created by ivar_grimstad:

A template for the legal transfer documents, or at least what it should contain, could possibly be an idea?

@apastsya apastsya added the bug label Jun 22, 2017
@heathervc
Copy link
Member

We will add some language in the MR for JSR 364 and also work on a case study for the Spec Lead Guide.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants