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.

Sign up for GitHub

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

Jump to bottom

Undraft the bylaws: IP Policy [due Oct 27] #178

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Undraft the bylaws: IP Policy [due Oct 27] #178

wants to merge 3 commits into from
+21 −22

Conversation

ebullient
Copy link
Member

@ebullient ebullient commented Jul 19, 2024 •
edited by haus-rules-bot bot
Loading

🗳️ Vote progress

Continuing with our reviews: the Intellectual Property policy.

voting group: @commonhaus/cf-egc

Do one of the following:

  • Approve the PR or react with 👍 (:+1:) if it looks good to you
  • Review with Comments or react with 👀 (:eyes:) if you're "ok" with it (it may not be your favorite)
  • If you think it needs discussion or revision
    • Create a review, add your comments and require changes
    • Use the +- button to make a suggestion (instead of just adding a comment).

@ebullient ebullient requested a review from a team as a code owner July 19, 2024 23:27
@haus-rules-bot haus-rules-bot bot added the notice Notice (review, announcement) label Jul 19, 2024
@ebullient ebullient added the vote/open Vote open label Jul 19, 2024
@haus-rules-bot haus-rules-bot
Copy link

haus-rules-bot bot commented Jul 19, 2024 •
edited
Loading

✅ 12 of 13 members of @commonhaus/cf-egc have voted (reaction or review, quorum=2/3).

Reaction Total Team Voting members
approve 12 11 aalmiray, cealsair, cowtowncoder, dandreadis, ebullient, evanchooly, gavinking, henri-tremblay, kenfinnigan, marc0der, velo
ok 1 1 maxandersen

Additional input (🙏 🥰 🙌):
JooHyukKim(👍)

The following votes were not counted (duplicates):
cealsair(👍), aalmiray(👍), JooHyukKim(👍)

A vote manager comment containing vote::result will close the vote.

maxandersen
maxandersen reviewed Jul 21, 2024
View reviewed changes
policies/ip-policy.md Outdated
> All code contributions must align with the project’s license and come with a promise (DCO) from contributors that they have the right to contribute under these terms.

All new code contributions to any Project shall be made under the Project Code License accompanied by a Developers Certificate of Origin (DCO, available at <http://developercertificate.org/>), which will bind the individual contributor and, if applicable, their employer to the Project Code License.
All new code contributions to any Project must be made under the Project Code License. Contributions must be accompanied by either a Developer Certificate of Origin (DCO available at <http://developercertificate.org/>) or a Contributor License Agreement (CLA), as determined by the project’s technical governing body. The DCO or CLA binds the individual contributor and, if applicable, their employer to the Project Code License.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming it is implied that all projects have either a dco or cla in effect for any new contributors?

If it is - should it not be explicitly stated as reading this a project don't need one - just that if it has either dco or cla those are in effect.

Copy link
Member Author

@ebullient ebullient Jul 22, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure what is unclear.

All new code contributions to a CF project must follow the project code license and be accompanied by either the DCO or a CLA (as chosen by the project).

I don't think there is anything in that text that says "neither" or "none" is a valid option. A Project must choose one or the other (or both).

@ebullient ebullient changed the title Undraft the bylaws: IP Policy [due 2 Aug] Undraft the bylaws: IP Policy [due 17 Aug] Aug 5, 2024
@ebullient
Copy link
Member Author

extending deadline for detailed review

@ebullient ebullient changed the title Undraft the bylaws: IP Policy [due 17 Aug] Undraft the bylaws: IP Policy Sep 10, 2024
@ebullient
Copy link
Member Author

Setting due date to end of October.

@ebullient ebullient changed the title Undraft the bylaws: IP Policy Undraft the bylaws: IP Policy [due Oct 27] Oct 9, 2024
@haus-rules-bot haus-rules-bot bot added the vote/quorum Vote has quorum of electronic responses label Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@maxandersen maxandersen maxandersen left review comments

@aalmiray aalmiray aalmiray approved these changes

@velo velo velo approved these changes

@evanchooly evanchooly evanchooly approved these changes

@cealsair cealsair cealsair approved these changes

@JooHyukKim JooHyukKim JooHyukKim approved these changes

Assignees
No one assigned
Labels
notice Notice (review, announcement) vote/open Vote open vote/quorum Vote has quorum of electronic responses
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@ebullient @aalmiray @maxandersen @velo @evanchooly @cealsair @JooHyukKim