Apache HTTP Server
One of the very popular http servers out there is the Apache Http server. It’s written in C/C++ and supports server side languages such as PHP. The server is open source and governed by the Apache 2.0 License. While navigating through the website, i noticed that they have quite an amount of emails in an email list that have different categories. Categories have emails to use when submitting a bug report, requesting the source code change, discussions, etc. The Apache Foundation’s bug reporting procedure dictates that unless you’re sure that a bug exists, you should use the bug database which is can be found at follows: https://bz.apache.org/bugzilla. They strongly encourage that if you’re not sure about a bug, to contact one of the users which can be found at https://bz.apache.org/bugzilla/. This is probably because they don’t want to get flooded with emails on the Distribution List. They also ask whoever takes ownership of fixing the bug, the person CC’s the DL (one of the emails in the emailing lists on the website) so that everyone is kept in the loop.
One of the recent patches that were deployed on the 11th of September. The bug was reported on the 7th of September so in terms of the time it took to release the patch for it wasn’t too long. The full bug report can be found here: https://bz.apache.org/bugzilla/show_bug.cgi?id=62697#c4. The people that were involved were most likely developers themselves as the person who presented the bug also attached a patch to it
Microsoft Visual Code
Microsoft Visual Code, or VSCode as most call it, is a powerful and popular text editor that supports many different languages and can act like an IDE if configured properly. It is open-source and maintained by Microsoft along with individual developers with an MIT license. The source code for it can be found on Microsoft’s github repos, https://github.com/Microsoft/vscode, along with any bug reporting issues, discussions, wiki, etc. In order to submit a bug for VSCode, the person opens an issue on the github repo and then individuals can assign that issue to themselves or to other people. After fixing a bug, Microsoft requires the developer to sign an online Developer agreement and to also open an issue under the “Pull Requests” page with tags “bug” or “help-wanted” and attach the patch. Then Microsoft analyzes the patch and if the patch affects the core editor negatively (slows performance, etc) then the patch gets rejected. If the patch is approved, it gets merged with the master repo and released.
One of the recent patches that were deployed were related to the “folding icon” in the editor which wasn’t matching the font upon increasing the font size. When the issue was opened, few developers joined the discussion compliment the catch and to bring up similar bugs as well. The issue was opened in 2016 but just until a couple days ago someone assigned the issue to another developer who found the root of the issue and deployed the patch. The patch underwent checks to see if the agreement was signed by the developer and that the patch didn’t negatively impact the editor. After the checks were successful, only that developer was given permission to merge the repo with their patch.
If i were to submit a patch for both communities, i would have to become a contributor and follow the process that they have outlined in order to submit a patch.