Update CPC Regular Member Process #1326
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tobie
approved these changes
Jun 28, 2024
|
@bensternthal thanks for putting this together, and also pulling in approach recently discussed around travel fund approvals. |
ctcpip
requested changes
Jul 2, 2024
|
|
||
| ### Means for approval/rejection, if citing project affiliation: (one of the following approvals is required) | ||
| ### How To Apply As A Regular Member |
There was a problem hiding this comment.
Suggested change
| ### How To Apply As A Regular Member | |
| ### How To Apply to Become a Regular Member |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the Regular member joining process to use the google form and takes into account feedback regarding the lazy consensus process outlined in #1324
See #1300