Note: This includes content related to both ExpOS (OS Lab) and EXPL (Compiler Lab). Because although they are offered as separate courses at NITC, they are closely related and dependent on each other.
Every year we have seen students come up with interesting content related to both the courses that are worth sharing. For example, a few students came up with Docker scripts for simplifying the installation procedure. Some students had shared vim and vscode extensions for syntax highlighting SPL files.
The official documentation and the repositories are only updated at the end of each semester after rigorous review, to keep them as stable as possible. So we are providing a place here for the students and the community to share their own content. These will not be rigorously reviewed. At the end of the semester we will consider the recognition of well made and popular content as official and maintaining them along with other official material.
The contributers should fork the repo and create a folder corresponding to their github userid inside the /users folder. You can put any type of content there. Scripts, programs, cheat sheets, PDFs, etc. The only requirement is that they should be related to ExpOS or EXPL.
Your content may be either a written material, for example a blog post explaining some concept, or something like a program or a script.
If it is of the latter category, we encourage you to also provide a written material explaining how to use it for your fellow students.
A link to thes written material should be added to posts.html in the repo.
Written material can be in HTML, PDF or formats like Markdown.
If it is HTML or PDF, find out the public link to it. For example: https://exposnitc.github.io/user-contrib/users/happycoder97/my_writeup.html.
Then add this link to posts.html
For Markdown and similar formats you have two options:
If you feel so, you can use frameworks like VueJS or tools like Hugo to create the HTML file.
This will be useful for tools like memory address calculators, or cheat sheets with search option.
After you finish your work, you should send a pull request from your fork to the parent repo.
After you create the pull request, before merging it, you can add the link to the pull request inside your writeup to accept comments and feedback. Users may also vote on your work under the pull request using the 👍 icon.
You are not required to rigorously check the accuracy of the content provided by users.
Any pull requests that only change the user's own folder should be merged without any delay. Changes to other files should be carefully reviewed.