-
Notifications
You must be signed in to change notification settings - Fork 171
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
Comments
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:
|
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 Already covers the transfer of domains, and says
But not entirely sure what a logomark is. @MylesBorins would that have been intending to cover Trademarks? |
I do wonder about it saying the transfer should be done before the final vote, that might apply to a number of the steps. |
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" |
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. |
#380 (comment) is definitely a failure mode I'm concerned about. |
@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. |
See #378. |
…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.
* 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.
* 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>
We should ensure that the assets which must be transferred to the Foundation as a project joins are clearly documented.
The text was updated successfully, but these errors were encountered: