Skip to content

Latest commit

 

History

History
50 lines (37 loc) · 3.51 KB

README.md

File metadata and controls

50 lines (37 loc) · 3.51 KB
Raw

ABOUT US

BPIT Open Source Community (B.O.S.C/BPIT Org.) is the official Open source organization of Bhagwan Parshuram Institute of Technology Delhi. As a part of the Institute Technical Council, we aim to provide a gateway for the students in our institute to join the coding community. We create a platform which allows students to gain assistance and mentorship to enhance their coding ability. Our aim is to propagate the enthusiasm for coding in the institute and especially amongst freshmen. We believe that every student here at BPIT should have an opportunity to learn how to code and develop a passion for it. The secret of getting ahead is getting started and we aim to provide every student with the right start.

JOIN US 👨‍💻 👩‍🎓

Eligibility to be a community member

  • You must be a Student or a Faculty member at Bhagwan Parshuram Institute Of Technology.
  • For a student you must be currently enrolled into any of the program/course at BPIT.
  • For People who are not a part of BPIT are also most welcome to contribute to us. Since we are an internal college organisation therefore the privilage of getting into the community cannot be granted. Still you become a part of our organization by joining the slack community at http://bosc.ml.

Contribution Guidelines

Contributing

When contributing to any repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Please take a minute to read Contributors guide

Pull Request Process

  1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
  3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is SemVer.
  4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
  • For Newbies to git.
    • Search for the project of your interest.
    • Fork the repository.
    • Go through the project and try to spot a bug or suggest any improvement. Else work on current issues of the repository if any.
    • Open an issue to the current repository for your improvements or the bug you found.
    • Ask the moderator to assign you the task.
    • Engaging yourself in the task which is assigned to other individual is strictly discoureged.
    • Do engage in a issue or a task only if you feel you can do it.
    • Once you are done doing these open a pull request and get your code verified and merged through the moderator.
    • Once the pull request has been merged send me your details of enrollment and the pull request to get your invitaion to the community.

For Experienced

  • Drop me an email at [email protected] with your statement of purpose and your valid proof of enrollment in BPIT. Finding it relevent I shall soon send you an email with the joining invitation.

Contributor Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.