Let me try and clear things up (note I’m answering these questions from an Outreachy perspective):
- Who’s authorised to approve any issue reported/raised?
OCaml.org is open-source, anyone can raise any issue or bug report and it can be discussed by the maintainers and contributors to see if it makes sense. There’s always a chance it could be rejected later on but so far this is pretty rare. As part of Outreachy the issues mentioned in this thread are supposed to be good first ones. In terms of approving (merging) PRs that would most likely be @avsm (or other maintainers i.e. not me) – I’m trying to get applicants and PRs in a position where they’re ready to be merged before Anil sees them :))
- Who assigns bug to contributors?
From an Outreachy perspective so far that has been me. I try my best but there’s quite a few applicants (10+) and only one of me. Of course, like most open-source project’s it’s completely okay (and encouraged) for contributors to take on any issue they like unless it’s been explicitly given to someone else. There’s a fine balance to be struck here from an Outreachy perspective, because if we leave it as a free-for-all contributors who need a little more time to tackle a problem can sometimes be pressured by other eager contributors who want to work on the problem. At the same time, it can be a lot slower because I have to assign issues. I would also add I don’t think we anticipated the volume of eager and enthusiastic contributors too. This is something we would prepare for better in the future.
Also, I want to suggest that any issue reported should have a label
Totally agree. I would, but I don’t have the permissions. I’ll contact people that do :))
…knowledge of markdown, CSS in markdown and also converting HTML to markdown alongside the knowledge of HTML
So far on Outreachy we have two required skills
HTML and a little
OCaml. I agree, maybe we should add
Markdown too. Perhaps we can pack out the contributing document some more with the build process. Again there’s a balance to be struck here, too many requirements might have driven people away. We’ve already lots of great contributions mainly in fixing HTML/CSS without any work on the OCaml glue that builds the site.
I believe more guidance introduced into the CONTRIBUTING.md would help newcomers navigate and contribute to the project with much lesser confusion…
Sounds fantastic! Please just open a PR on the repo with your ideas and we can work on them there.
Thank you so much for your willingness and help to improve the user experience.