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

governance: getting permission to attend meetings #56

Merged
merged 7 commits into from
Feb 25, 2020

Conversation

MylesBorins
Copy link
Contributor

This is a basic policy for getting consensus around attending standards
meetings.

PTAL

This is a basic policy for getting consensus around attending standards
meetings.
@MylesBorins MylesBorins added the standards-agenda To be discussed in bi-weekly meeting label Jan 14, 2020
@dtex
Copy link
Contributor

dtex commented Jan 14, 2020

Is this something that should happen before every in person meeting and phone call?

@timmywil
Copy link

@dtex That sounds tedious. I suggest that getting permission to attend the same recurring meeting regularly is enough. Also, the language implies there's a difference between attending a meeting and attending a meeting as a delegate of the OpenJS Foundation.

@MylesBorins
Copy link
Contributor Author

I think that there should likely be an issue for every meeting if the individual is planning to attend as an OpenJS delegate and is requesting funds from travel fund. They can point the CPC at the issue as proof that their travel is approved... it is also a place where we we can centralize discussion about intentions + goals for the meeting.

I guess maybe it could be better frame as halfway between permission and co-ordination... which can maybe be better outlined in the governance. We can also make an issue template for this if it is helpful.

@timmywil
Copy link

and is requesting funds from travel fund

So is this only necessary when requesting funds? If that's the case, it should probably be noted in this PR.

If a member would like to attend a meeting as a delegate of the OpenJS Foundation and is requesting funds

@MylesBorins
Copy link
Contributor Author

@timmywil I think there are two bits that need to be checked

  • Representing OpenJS
  • Requesting funding

it is possible that for the former we can sign off once for perpetual representation... but we likely should have a tracking issue for each meeting so folks have an opportunity to get involved / share thoughts / plan

GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated
* The OpenJS Foundations relationship to this standards organization
* The date and location of the meeting
* If they will be attending in person or remotely
* The estimated cost of their particiaption
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Include something about scope of the work.

GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
MylesBorins and others added 4 commits February 25, 2020 14:19
Co-Authored-By: Eemeli Aro <eemeli@gmail.com>
Co-Authored-By: Eemeli Aro <eemeli@gmail.com>
Co-Authored-By: Eemeli Aro <eemeli@gmail.com>
GOVERNANCE.md Outdated Show resolved Hide resolved
@MylesBorins MylesBorins merged commit 558c0b9 into openjs-foundation:master Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
standards-agenda To be discussed in bi-weekly meeting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants