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

Merge staging process into the charter proposal #36

Closed
evanp opened this issue Nov 6, 2024 · 5 comments
Closed

Merge staging process into the charter proposal #36

evanp opened this issue Nov 6, 2024 · 5 comments

Comments

@evanp
Copy link
Contributor

evanp commented Nov 6, 2024

We haven't approved the main CG charter yet. Structuring the staging process as an amendment to the charter is kind of a big hassle. Could we just include it in the main CG charter document and just approve the whole thing at the same time?

@gobengo
Copy link
Contributor

gobengo commented Nov 8, 2024

Structuring the staging process as an amendment to the charter is kind of a big hassle.

Is it? I think this could just be a PR onto the charter and a proposal for consensus to amend charter?

I think it might be more of a hassle to reach full consensus on a staging process in an initial charter. Maybe something simpler and more in line with the decision process that's already in the charter? or, if deviating from that, something that several other CGs have found useful to adopt (a la decision policies with calls for consensus on list as we discussed a while ago)

Personally, my gut is that this issue is not a top priority, and it could instead make sense to prioritize:

  1. reach consensus on any CG charter w/ decision process
  2. unblock CG work on deciding a WG Charter, which I think doesn't require staging process
  3. work on staging process document that includes text on what it would amend the charter decision policy to (e.g. 'this group will not decide to publish documents that have not reached stage 2 on this process')
  4. amend charter, only if work on staging process document deems it's necessary. it may not.

Anyway, just sharing those thoughts async.

Could we just include it in the main CG charter document and just approve the whole thing at the same time?

As the author of #1, I'd be willing to review a PR adding this and otherwise talk more about it, but it's omission wouldn't be a hard blocker for me. Is the reason you're raising this issue that you would block consensus with the potential charter's current decision policy?

@evanp
Copy link
Contributor Author

evanp commented Nov 9, 2024

Structuring the staging process as an amendment to the charter is kind of a big hassle.

Is it? I think this could just be a PR onto the charter and a proposal for consensus to amend charter?

Yes. "A big hassle" is hyperbole. There are a lot bigger hassles in life. I think approving a document when we know that an amendment is coming, and then making the amendment, is incrementally harder than amending the document before you approve it, and approving the whole package once.

I'm not sure how we're going to decide on approving the charter -- see #45 -- but if it's less onerous than the amendment process (30-day vote, 2/3 supermajority), maybe it's easier to do it all as a package.

@evanp
Copy link
Contributor Author

evanp commented Nov 9, 2024

Personally, my gut is that this issue is not a top priority

That's OK! Feel free to ignore issues that are not a priority to you personally. I wouldn't have raised the issue if I didn't think it was important, though.

@bumblefudge
Copy link
Contributor

bumblefudge commented Dec 5, 2024

FWIW i kept FedID's markdown format rather than converting it to a PR on the draft CG charter because I assumed it would just be a stand-alone addendum. I'd be fine to start that 30 day clock minutes after ratifying the CG charter? Or strike the 30day and just the standard 2-week CfC for all amendments, as proposed in #45? I'm easy. But just to clarify, I originally intended it as an amendment (not realizing amendments have a slower ratification process than usual resolutions).

@evanp
Copy link
Contributor Author

evanp commented Dec 6, 2024

Per discussion at CG meeting, we seem to be in consensus to not do this. So, I'm going to close this issue.

@evanp evanp closed this as completed Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants