Try   HackMD

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
Executive Committee Meeting Notes

Agenda Conversation:

To-do:

  • announce to resbaz plan to establish governance
    • establish need (opencollective)
    • establish formal line of communication
    • establish next steps
      • invite to draft
      • establish accountability
    • affirm entire community participation in future voting steps
  • create github project within https://github.com/resbazaz/organization
  • draft initial and ask for feedback
    • loomio: not doing this for now (non-free, requires learning a new interface)
    • Probably better way to vote (already a github app): https://github.com/cncf/gitvote
    • collaborative doc
      • starting from initial draft that is requirements-based (e.g. what does opencollective NEED)

suggested Timeline

  • Friday, May 12
    • Send the Slack message below (to @everyone in #general)
  • Wednesday, May 17
    • The drafting task force creates a shared document
    • This timeline is posted to the Github repository
  • Friday, May 19
    • Task force formed
      Image Not Showing Possible Reasons
      • The image file may be corrupted
      • The server hosting the image is unavailable
      • The image path is incorrect
      • The image format is not supported
      Learn More →
    • Any task force member can initiate intermediate adjustments to things like:
      • "how do we want to vote?"
      • "what threshold do we require to proceed?"
      • revisions to this timeline
        …by creating a /vote on a:
      • Github issue, and/or
      • ideally, a Github pull request that:
        • edits the timeline document
        • edits .gitvote.yml with an updated voting policy
  • May 26 deadline for gov committee to draft individual contriubtions
    • Work together to merge contributions into v0.8
  • Friday, June 2
    • Initial draft community commentary period begins on governance v0.8
  • Friday, June 16
    • Task force agrees on community commentary to develop governance v0.9
  • Friday, June 30
    • Final community commentary period on governance v0.9
  • Friday, July 14
    • Task force agrees on community commentary to develop final governance v1.0
  • Friday, July 28
    • Voting on the final document
      • In a Github pull request with community voting mechanism
      • Details of this vote (i.e. what threshold of assent do we require, duration of voting, etc.) should be determined as part of the governance doc drafting process
    • We get out the vote via our second @everyone on #general message
  • (When a doc finally passes)
    • We submit the governance doc to OpenCollective

Feedback on Slack message

  • Also mention on Meetup.com, Twitter, and at in-person events.

Slack communication

Hello ResBaz-ers,

We have completed a rough draft of our future governance here.

At this time, we invite the ResBaz community to provide feedback on this first draft. This window for commentary will be open until Friday, June 9. Then, we will work on comments, and ask for more feedback.

You'll notice a number of [TODO] items in the draft on which we would appreciate your input.

Please provide feedback by opening a new issue within the GitHub repository for each comment thread. (For those without Github knowledge: Log into / create your Github account, click the 'edit this file' pencil symbol on the top right of the governance doc, edit away, then click 'commit changes' and then 'propose changes' in the dialogue. Please give a meaningful name to your changes, so others can comment on them in the pull request section).

If you need any technical support, please let us know. Note that we will only be able to take comments and changes on Github and not other channels

References

Last changed by 
 
Julian Pistorius
0
2
134
Published on HackMD