Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure documentation covers assets that must be transferred from Foundation #380

Closed
mhdawson opened this issue Oct 25, 2019 · 8 comments · Fixed by #386
Closed

Ensure documentation covers assets that must be transferred from Foundation #380

mhdawson opened this issue Oct 25, 2019 · 8 comments · Fixed by #386

Comments

@mhdawson
Copy link
Member

We should ensure that the assets which must be transferred to the Foundation as a project joins are clearly documented.

@brianwarner
Copy link
Contributor

With the caveat that there may be extremely unusual corner cases that have to be handled by the Board on an exception basis, this could be a starting point for the text:

Assets to be transferred to the Foundation include any registered trademarks related to the open source project, and the project's domain. From that point forward, the Foundation will be responsible for renewing and managing the trademarks and the domain.

To begin the process of transferring a registered trademark, please reach out to legal-questions@lists.openjsf.org. To begin the process of transferring a domain, please reach out to operations@openjsf.org.

@mhdawson
Copy link
Member Author

This would imply that the transfer occur before the final Vote by the Voting members: https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#process

https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#process

Already covers the transfer of domains, and says

Transfer logomark to the OpenJS Foundation

But not entirely sure what a logomark is. @MylesBorins would that have been intending to cover Trademarks?

@mhdawson
Copy link
Member Author

I do wonder about it saying the transfer should be done before the final vote, that might apply to a number of the steps.

@knolleary
Copy link
Contributor

If a legal transfer is required prior to the vote, we could end up in a situation where the vote fails but the assets have already moved. Is that the scenario that makes you wonder about it @mhdawson ?

Perhaps it should be something like "all relevant assets have been identified and their transfer agreed in principle, subject to the final vote"

@knolleary knolleary reopened this Oct 29, 2019
@brianwarner
Copy link
Contributor

Good point @knolleary, maybe it's a good faith commitment to do so within a reasonable time period. Domain registrations can be done pretty quickly, but trademark registrations can take much longer.

@ljharb
Copy link
Member

ljharb commented Oct 29, 2019

#380 (comment) is definitely a failure mode I'm concerned about.

@mhdawson
Copy link
Member Author

@knolleary , @brianwarner, @ljharb that is defintely what I was thinking about. I'd agree that it should be "agreement do so in good faith" . We probably need a post-vote checklist in addition to the checklist for what needs to be in place before the vote.

@tobie
Copy link
Contributor

tobie commented Oct 29, 2019

See #378.

tobie added a commit to tobie/cross-project-council that referenced this issue Oct 31, 2019
…ists

* Split onboarding checklist to move formal IP transfers
  and related tooling post-graduation.
* Add commitment to IP transfer to onboarding checklist.
* Use the term trademark instead of logomark.
* Update related issue template
* Create additional issue template for post-graduation checklist.

Closes openjs-foundation#378, closes openjs-foundation#380.
tobie added a commit to tobie/cross-project-council that referenced this issue Oct 31, 2019
* Include formal IP transfers and related tooling, which cannot happen
  before project has formally graduated from incubation
* Modify onboarding checklist so that IP related tasks are limited to
  listing related assets and committing to post-graduation transfer.
* Use the term trademark instead of logomark.
* Update related issue template
* Create additional issue template for post-graduation checklist.

Closes openjs-foundation#378, closes openjs-foundation#380.
tobie added a commit that referenced this issue Mar 24, 2020
* Include formal IP transfers and related tooling, which cannot happen
  before project has formally graduated from incubation
* Modify onboarding checklist so that IP related tasks are limited to
  listing related assets and committing to post-graduation transfer.
* Use the term trademark instead of logomark.
* Update URLs in comments to point to new location of issue templates.

Closes #378, closes #380.

Co-Authored-By: Dhruv Jain <dhruvjainpenny@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants