INTECS Open Source - Contribution Guidelines

Types of contributions we're looking for :-

People with enthusiasm to contribute to open source projects to gain knowledge and experience are welcome. (Read the “How to Contribute” section thoroughly before joining the project and post any inquiries regarding the above in the gitter community). Also please go through code of conduct section as well.

Join Gitter Community

Expectations :-

Before we get started, here are a few things we expect from you (and that you should expect from others):

• Be kind and thoughtful in your conversations related to the project. We all come from different backgrounds and projects, hence we are likely to have different perspectives on "how open source is done." So, be respectful of different viewpoints.

• Open Source Code of conduct is published here . You must go through this before participating.

• By participating in this project, you agree to all the terms mentioned in this document.

• Once you open a pull request, please ensure that your contribution passes all tests. If there are test failures, you will need to address them before your contribution is merged.

How to contribute :-

If you would like to contribute, start by searching through the issues. After picking one, please check whether someone else has already started working on the issue. If you get interested. Please follow the succeeding steps to make your contribution

1. Join the gitter community which is mentioned in the project.
2. Add a comment on the selected issue to reserve it for yourself.
3. To know further details regarding a certain issue, you are facilitated to discuss with the mentor who is assigned to that issue through the slack channel.
4. Fork the project to your personal account.
5. Checkout to the “dev” branch.
6. The issue ID should be mentioned in the commit message.
7. When you complete a task and wish to male a pull request, make sure to mention any special comments in the pull request itself.

Rules :-

• If the participant who commented to reserve the issue does not update anything about the tasks within 3 days time on the slack channel or GitHub, the mentor of the particular project has the sole right to open the issue for the others by commenting on that issue.

• The mentor of a particular issue is possessing the sole right of accepting or rejecting a pull request.

API Documentation :-

https://dev-dot-intecs-webapp.el.r.appspot.com/swagger/

Available Scripts :-

1. Install Node Modules:

   $ npm install

2. Serve Locally:

   $ npm start

Create New Controller :-

eg: create user controller:

Create File: src/controllers/User/User.ts

Create New Route :-

eg: create user route:

Create File: src/routes/User/User.ts

INTECS Open Source - Contributor’s Code of Conduct

Our Pledge :

As Contributors and maintainers of INTECS Open Source project, we pledge to make participation in our project a harassment-free, open experience for each and every one of you regardless of seniority, physical disabilities and physical appearance, ethnicity, gender, level of expression, nationality and religion.

Vision :

To inspire young individuals in programming while motivating them to actively contribute to open source projects and gain exposure to the open-source community and ethics.

Our Standards :

INTECS Opensource is open for all the undergraduates of the Faculty of Information Technology, University of Moratuwa. All the participants should adhere to professional conduct and contribute to creating a positive environment. Examples for such behaviour include:

• Use professional and formal speech.
• Being respectful of differing viewpoints and experiences.
• Gracefully accepting constructive criticism.
• Focusing on what is best for the community.
• Showing empathy towards other community members.
• Be responsible for the task undertaken.

Examples of unacceptable behaviour by participants include:

• Trolling, insulting/derogatory comments, and personal or political attacks.
• Abusive or insulting comments between undergraduates or between batches.
• Public or private harassment
• Publishing others' private information, such as a physical or electronic address, without explicit permission
• Other conduct which could reasonably be considered inappropriate in a professional setting

Scope of code of conduct :

This Code of Conduct extends both inside project spaces as well as in public spaces in which a person serves the project or the community.

Enforcement

Instances of abusive, harassing, or otherwise, unacceptable behaviour may be reported by contact INTECS by mail here , which is a shared team inbox. If the incident involves someone who receives that shared inbox, you can also contact an individual maintainer.

Project contributors who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the organizers.