All pages
Powered by GitBook
1 of 3

Loading...

Loading...

Loading...

Code Contribution

Overview

The below recommended Github workflow allows developers to submit code and documentation contributions to eSignet open-source repositories.

Repositories

Setup your development machine

  1. Fork repository of interest.

  2. Clone the fork to your local machine. E.g.:

  3. Set the upstream project as the original from where you forked. E.g.:

  4. Make sure you never directly push upstream.

Code changes

  1. Create a new issue in GitHub.

    1. Follow the issue template provided.

    2. Please provide as much information as possible.

    3. If you want to develop a new feature, please elaborate on the idea and discuss the design before starting development.

3. On your local repo, switch to a branch if you are working on an older release (like the 1.0.0 branch) or stay in main/develop the branch.

You will get a warning from git. Don't worry, our next step will take care of this warning.

4. Create a new issue branch with the name of the issue.

5. Make sure you are up-to-date with the upstream repo.

You should do this quite often to ensure you are up to date.

6. Now feel free to make the change in the code or documentation. Reach out to for any queries. Once done with the work, commit your changes by referring to the Issue ID in the commit message. Eg:

7. Once again, ensure you are up-to-date with the upstream repo as it may have moved forward.

8. Build and test your code. Make sure to follow the coding guidelines. Provide unit test cases for the changes you have built.

9. Push to your forked repo (origin).

10. On your forked remote repository from GitHub, create a pull request using the Contribute button. Direct the pull-request to main or any specific branch upstream.

Most often it's the same branch in the upstream (as in Step 3).

11. Make sure the automatic tests on GitHub for your pull request pass.

12. Reviewers shall review the pull request. Reach out to the for a faster response.

Confirm the origin and upstream.

  • In your local repository, fetch the upstream.

  • our community
    community
    $ git remote -v
    $ git clone https://github.com/<your_github_id>/esignet.git
    $ cd esignet
    $ git remote add upstream https://github.com/mosip/esignet.git
    $ git remote set-url --push upstream no_push
    $ git fetch upstream
    $ git checkout upstream/<branch> 
    $ git switch -c issue-<issue number>
    $ git pull upstream <branch> 
    $ git commit -m "[#1234] Adding new upload feature in eSignet service"
    $ git pull upstream <branch> 
    $ git push --set-upstream origin issue-<issue number>

    Community

    Join the eSignet community!

    eSignet is a product of the combined efforts of multiple stakeholders. Community contributions form the project's backbone, driving its growth and stability.

    Ways the community contributes:

    • Direct code contributions.

    • Design and architecture reviews.

    • Bug identification and fixes.

    • Technology evaluation support.

    • UI/UX design improvements.

    • Documentation.

    How do I contribute?

    For code contributions, refer .

    To engage with us on our community forum and connect with fellow contributors visit .

    here
    here

    Code of Conduct

    Preamble

    eSignet was created to foster an open, innovative, and inclusive community around open source and open standards. To clarify expected behaviour in our communities, we have adopted the Contributor Covenant. This code of conduct has been adopted by many other open-source communities, and we feel it expresses our values well.

    Our Pledge

    We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, colour, religion, or sexual identity and orientation.

    We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

    Our Standards

    Examples of behaviour that contributes to a positive environment for our community include:

    • Demonstrating empathy and kindness toward other people

    • Being respectful of differing opinions, viewpoints, and experiences

    • Giving and gracefully accepting constructive feedback

    • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

    Examples of unacceptable behaviour include:

    • The use of sexualized language or imagery, and sexual attention or advances of any kind

    • Trolling, insulting or derogatory comments, and personal or political attacks

    • Public or private harassment

    • Publishing others' private information, such as a physical or email address, without their explicit permission

    Enforcement Responsibilities

    Community leaders are responsible for clarifying and enforcing our standards of acceptable behaviour and will take appropriate and fair corrective action in response to any behaviour that they deem inappropriate, threatening, offensive, or harmful.

    Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct and will communicate reasons for moderation decisions when appropriate.

    Scope

    This Code of Conduct applies within all community spaces and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

    Enforcement

    Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported to the community leaders responsible for enforcement at . All complaints will be reviewed and investigated promptly and fairly.

    All community leaders are obligated to respect the privacy and security of the reporter of any incident.

    Enforcement Guidelines

    Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

    1. Correction

    Community Impact: Use of inappropriate language or other behaviour deemed unprofessional or unwelcome in the community.

    Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behaviour was inappropriate. A public apology may be requested.

    2. Warning

    Community Impact: A violation through a single incident or series of actions.

    Consequence: A warning with consequences for continued behaviour. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

    3. Temporary Ban

    Community Impact: A serious violation of community standards, including sustained inappropriate behaviour.

    Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

    4. Permanent Ban

    Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behaviour, harassment of an individual, or aggression toward or disparagement of classes of individuals.

    Consequence: A permanent ban from any sort of public interaction within the community.

    Attribution

    This Code of Conduct is adapted from the , version 2.1, available at .

    Community Impact Guidelines were inspired by .

    For answers to common questions about this code of conduct, see the FAQ at . Translations are available at .

    Focusing on what is best, not just for us as individuals, but for the overall community

  • Other conduct which could reasonably be considered inappropriate in a professional setting

  • MOSIP
    Contributor Covenant
    https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
    Mozilla's code of conduct enforcement ladder
    https://www.contributor-covenant.org/faq
    https://www.contributor-covenant.org/translations
    GitHub - mosip/esignet-mock-services: Repository contains mock implementation of auth for e-signetGitHub
    GitHub - mosip/esignet-signupGitHub
    GitHub - mosip/esignet-plugins: Repository hosting source code for esignet java runtime dependencies pluginsGitHub
    GitHub - mosip/esignet: Open ID based e-Signet service for large scale verification & authentication.GitHub
    Logo
    Logo
    Logo
    Logo