Replies: 4 comments 1 reply
-
If you want to contribute something to our upcoming security policy, please get involved in #365 |
Beta Was this translation helpful? Give feedback.
-
I just watched https://www.youtube.com/watch?v=Z7ppp_DrxyM which was organized by GitHub and provided the following inspiring resources related to contribution guides: |
Beta Was this translation helpful? Give feedback.
-
For code of conduct I just found out about https://www.contributor-covenant.org/ which seems to be a widely adopted thing for open source and looks like a good "minimum" to have. (PR is welcome) |
Beta Was this translation helpful? Give feedback.
-
GitHub just published https://github.blog/2023-08-04-a-checklist-and-guide-to-get-your-repository-collaboration-ready/ and I added the related checklist to the original discussion post. If you disagree with a status or my additions to it, please raise the topic here or where you think it fit's best. |
Beta Was this translation helpful? Give feedback.
-
What kind of contributions are we talking about?
Everything, there are issues to investigate/clarify, documentation to write, strategic decisions to be discussed, pull requests to review, features to suggest, ...
What is keeping people from contributing?
I believe the main reason currently is uncertainty. About a lot of things.
That's why I created this discussion. We want to collect the topics that keep people from contributing, and at the same time find people that are willing to invest time into these topics, providing their experience, knowledge, opinions, etc.
But there is not even ...!?
Yes, this discussion can be very "meta" (we need to resolve those step by step, without them being in place), we hope it will be very constructive and fruitful anyways, so the list get's shorter over time and people feel encouraged to contribute right away.
Here is a checklist published by GitHub and how far we are into making this a place that people feel confident to contribute to:
italic text is added by me
requires Automate release process #451 to be solved
this is why I started this discussion
most likely only makes sense when there is more then one active maintainer?
see Automate release process #451
(enterprises) configure Merge Queuesnot sure how this would help us?
only for security issues so far, needs more (reliable capacity)
to reflect curent status towards milestones, see https://github.com/xmldom/xmldom/blob/master/docs/RELEASE.md
Let's try to keep this discussion helpful by creating a single thread per "topic".
Thank you for reading this, we are looking forward to your contribution.
Beta Was this translation helpful? Give feedback.
All reactions