DEV SESSION 14 Oct --- 2000 UTC+8/1400 CET/1200 GMT

[tpike3]

Where: via Matrix

Proposed Agenda:

-Code of Conduct/Governance
-Small Development Grant and Visualization Improvements
-Mesa-Geo and CSSSA
-PRs and Issues

@rht , @jackiekazil , @Corvince , @wang-boyu , @ankitk50, @rlskoeser

[wang-boyu]

Adding @SongshGeo who may also want to join us

[SongshGeo]

Thanks for your notification. I'd like to be in.

[tpike3]

@SongshGeo Welcome, looking forward to meeting you; Thanks @wang-boyu

[tpike3]

Code of Conduct References:

Overview: https://opensource.guide/code-of-conduct/

Staying positive: https://github.com/jonschlinkert/maintainers-guide-to-staying-positive

Examples:

• https://opensource.com/code-of-conduct
• https://www.contributor-covenant.org/version/2/1/code_of_conduct/
• https://www.apache.org/foundation/policies/conduct
• https://aws.github.io/code-of-conduct

[wang-boyu]

Some references on open-source project governance (I'm interested in how people are organized around a project and how code contributions are reviewed and merged):

• Governance models for open source projects (may need to join the Maintainer Community on GitHub to access it)
• Healthy Open Source: A walkthrough of the Node.js Foundation’s base contribution policy
• Apache Forrest project guidelines
• Governance Models from OSS Watch

[tpike3]

Sorry for the delay on this. We do have a Code of Conduct, but I did make another variation. More importantly and to @wang-boyu we needed a governance document.

Appreciating people won't have time to read this, I would recommend looking at lines 54 -59 and 77-80. Or more broadly the contributor and committer descriptions. The critical point is how do we in place mechanisms that address concerns that have occurred over many years about the timeliness of our merges and the ease of contribution. One element that needs to be added is the expectation of response to a contribution-- 1 week?

Mesa Governance (Draft).md
Mesa Code of Conduct (Draft).md

Let me know what you think.

[rht]

Regarding with the code of conduct, it's more relevant to use NUMFOCUS's instead of PSF's.

We require all NumFOCUS sponsored and affiliated projects to adopt a code of conduct for their project that encourages a productive, respectful environment for all open source contributors and community members.

One element that needs to be added is the expectation of response to a contribution-- 1 week?

This is not an issue. I usually responded to most PR's and issues' within reasonable time, often much less than a week.

[jackiekazil]

All -- I apologize that I was not in the meeting yesterday - I was traveling and it fell off my radar.

@tpike3 thank you for posting these. Can you put them in a branch or PR for easier review and comment?

[tpike3]

@jackiekazil -- done to keep it focused I just did the governance document in a pull request #1836