aronowski / rhboot-shim-review Goto Github PK

Improving upstream Code of Conduct with mentions that, among others:

• people and organizations who come here and file applications for a review may have different backstories, experiences, etc. and not have the knowledge to file a flawless application the first time. It's natural and there's nothing to be ashamed about. We're here to partake in a venue where we all can learn from the public applications in a sorta safe space to make mistakes as I would name it.
• they may not follow the development of UEFI shim, bootloaders, the Linux kernel, SSL libraries, among others and may not be aware of the venues that take place outside the public Red Hat Bootloader Team's GitHub repositories, as they may just be rebuilding or patching the bootchain components. For instance, they may not know if there already is a solid NX support implementation in the 6.0 kernel family and where to look for clues on this.
• they may have a high-end technology that clones a repository and performs a build in mere seconds, but this is not always the case. The reviewers may work with a limited (speed or transfer-wise) Internet connection, disk space, processing power, etc. Therefore, I pledge to keep a reasonable repository size, rather than letting a reviewer download hundreds of megabytes

and maybe more examples of positive and unacceptable behavior.

Needs rhboot#349 to be resolved first, before the whole document gets finalized.

Do not overwhelm newcomers with a huge README; instead move it do another document and make the README a short, easy-to-follow list of tasks on how to get into the whole venue quite easily.

For example,

• read the application document template casually just to get a grasp on what to expect soon
• read the issue template to see, what is expected (e.g. checking all the boxes in the sense "I've dealt with this, so I'm checking the checkbox." rather than "This is not applicable for me, so I'm leaving the checkbox unchecked.")
• read the successful applications of popular distros to see, how they dealt with the questions
• study (rather than reading casually) all the things learned from these examples and apply them to your case

Needs #1 and #2 to be resolved first.

Review the files in the docs/ directory and check thoroughly for formatting errors. Some may relate to the fact these were migrated from Wiki.

Making the document for a review application more inclusive towards newcomers and easier to follow, e.g. by providing hints, clarifications and simplifying the expressions used.

Needs rhboot#348 to be resolved first.