CONTRIBUTING.md

Contributing to Digital Public Goods

Looking to contribute something to Digital Public Goods? Here's how you can help.

Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved. Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they will reciprocate that respect in addressing your issue or assessing patches and features.

Nominating Digital Public Goods

We are constantly accepting new nominations for Digital Public Goods. Follow the steps below, for a smooth and streamlined process.

1. Check that the project has not already been nominated

There are two ways to search the list of existing nominees:

• On the navigation bar (navbar) at the very top of this page (or any page within this repo), type the name of the project you wish to nominate and click In this repository. If the search returns any results, double check that are coming from the nominees/ folder. Follow the link from the results of the search to validate that they indeed refer to the same project that you had in mind. While you are at it, review that all the information is correct, and please make any changes if that is not the case.

• Visit https://digitalpublicgoods.net/explore to browse a list of all the projects already nominated, and within that page look for (Ctr + F or command + F) using your browser search functionality for any potential matches.

2. Nominate a new project

The easiest and most convenient way is to use our online webform. Upon submission of the form, a pull request will be created automatically with your answers.

Caveat: If you want your contribution to be counted towards Hacktoberfest, the webform will not work for you (as the PR will not be opened under your GitHub account). If you want your contribution to be counted, use the instructions below.

---

Requirements and Considerations

For those projects that match the initial set of requirements, anyone can open a Pull Request on this repository as a submission following these guidelines:

• The license field is standardized using SPDX identifiers.

From the set of nominee json files, this list of Digital Global Public Goods is automatically generated and kept in sync with the contents of this repo.

2a. Alternate method: Add a new file

Data for each nominee is stored as a JSON file, which is essentially a text file that follows the JavaScript Object Notation (JSON), a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.

Again you have two options:

• You can choose to make your contribution entirely through your browser. Navigate to the nominees folder of this repository, click on the Add file button towards the top right of the page, and select Create new file. Add all required fields to the file according to the instructions given in 3a.

• Alternatively, you can create and edit a new file in your computer after forking and cloning this repository:

  • Go to the unicef/publicgoods-candidates repository on github and click on the Fork button on the top right corner. A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
  • Go to your own Github profile and you will see a repository named publicgoods-candidates. You can now create a local copy of it on your machine by cloning the repository:
    • Using HTTPS:

    git clone https://github.com/<your_github_username>/publicgoods-candidates.git

    • Using SSH:

    git clone git@github.com:<your_github_username>/publicgoods-candidates.git

    Navigate to the nominees/ folder in your local copy, and create the new file there. Add all required fields to the file according to the instructions given in 3a.

The filename must match the name field (see below) in kebab-case, and .json as the extension. For example: wikipedia.json or inlcusion-ukr.json

3a. Provide the required information

Use the template below to include the requested information. Be sure to include the fields marked REQUIRED with the corresponding information, as well as any OPTIONAL fields. Delete any lines marked OPTIONAL that you don't want to include. For the license field, refer to the Specifying Licenses section for the list of approved licenses.

4a. Submit

• If you are making the contribution through the browser, scroll down and accept the suggested field for the commit message Create <filename>, and choose Create a new branch for this commit and start a pull request. Click on Propose new file.
• If you are making the contribution through the local copy on your computer, once you push the changes to your forked repository, click on the Compare & pull request button which will appear at the top in GitHub.

You are taken to a new page where you can leave a comment about the file you are about to propose to add, and finally click on Create Pull Request

5a. Validate your submission

Wait for the green checkmark to say All checks have passed to have confirmation that the file complies with the expected format, and is ready to merge pending a review. If you see that some tests fail, follow the link to the Continous Integration (CI) build, which will provide with the cause of the error. Please correct any errors until you see that all checks pass. The automated tests that are run for all nominee files and instructions to debug common errors in them are given below:

• JSON schema validation
  • This test ensures that all JSON files have the required fields, and each of these fields has the expected data type.
  • The CI build will indicate in which line the error lies. Please ensure that the field names and values entered in that line align with the schema.
  • If you are working on your local machine, run npm run test to run the JSON schema validation.
• Linting
  • This test ensures that there is 2-space identation and a predefined separation of fields line by line.
  • If you are working on your local machine, run npm run lint:fix to automatically fix issues with linting.
  • If you are submitting the file directly through the browser, ensure that you remove all extra spaces and the fields are separated line by line.
• Ensuring consistent file naming
  • This test checks that all data files are named consistely, that is by using the field name in kebab-case.
  • If this test fails, ensure that punctuation is removed and spaces are replaced by single hyphens in the name of your file.
  • If you are working on your local machine, run npm run check:fix to automatically name all the files using the right convention.
• Ensuring consistent order in the fields of JSON files
  • This test checks that the data fields in all JSON files are in a predefined order.
  • Please ensure that all field names in your file are as per the order given in the template.
  • If you are working on your local machine, run npm run order:fix to automatically sort all the fields correctly.

Refer to the development overview for additional information.

Template

{
        "name": "REQUIRED",
        "aliases": "[OPTIONAL: Array of strings - Abbreviations, initialisms, or alternate names, where relevant]",
        "description": "REQUIRED",
        "website": "REQUIRED",
        "license": [REQUIRED, Array of objects (at least one object is required):
                {
                        "spdx": "SDPX identifier for this license",
                        "licenseURL": "Link to the license under which this nominee is released"
                }
        ],
        "SDGs": [REQUIRED, Array of objects (at least one object is required, and either evidenceText or evidenceURL is REQUIRED for each SDG entry):
                {
                        "SDGNumber": "Number of the Sustainable Development Goal",
                        "evidenceText": "provide information to support this relevance",
                        "evidenceURL": "provide links to support this relevance"
                }
        ],
        "sectors": [OPTIONAL: Array of strings - List of sectors that this nominee addresses.],
        "type": [REQUIRED, Array of strings, multiple choice from "software", "data", "standards"],
        "repositoryURL": "OPTIONAL: Link to main repository",
        "organizations": [REQUIRED, Array of objects (at least one object is required):
                {
                        "name": "REQUIRED - Name of the organization",
                        "website": "REQUIRED - Website of the organization",
                        "org_type": "REQUIRED - One of 'owner, 'maintainer', 'funder' or 'implementer',
                        "contact_name": "OPTIONAL - Name of contact individual in the organization",
                        "contact_email": "OPTIONAL - Email for contact individual in the organization"
                }
        ],
        "stage": "REQUIRED: Screening stage of Digital Public Good"
}

Specifying SDGs

Refer to the UN’s 2030 Sustainable Development Goals for details about each SDG.

Specifying Licenses

Licenses for open source software, open content and open data are vetted and approved by third party organizations, and we rely on their criteria in order to include them in our list of approved licenses. On top of it, we use SPDX identifiers to easily, efficiently and uniquely refer to each license.

• Open Content: you are encouraged to use one of the Creative Commons licenses which allow for both derivatives and commercial reuse: CC BY or CC BY-SA, or dedicate content to the public domain (CC0). We also accept the following licenses which do not allow for commercial reuse: CC-BY-NC and CC-BY-NC-SA.
• Open Data: only accepting conformant licenses to the Open Definition from the Open Data Commons.
• Open Source Software: only accepting approved licenses from the Open Source Initiative.

Refer to the current list of approved licenses for additional information.

Specifying Sectors

Similarly to the SDGs field above, the data in the sectors must be from the predefined list below (you should select one or more elements of the following array, where an element is a string):

[
  "Advocacy",
  "Agriculture",
  "Anti-corruption",
  "Big Data",
  "Business Advocacy",
  "Capacity Development",
  "Centers of Excellence",
  "Civil society",
  "Climate",
  "Communication",
  "Conflict Resolution",
  "Consulting",
  "Corporate Partnerships",
  "Corporation and Business Management",
  "Data Collection",
  "Data Management & Policy",
  "Data Security",
  "Demobilization & Reintegration",
  "Democracy",
  "Development Impact",
  "Digital Development",
  "Digital/Data/Tech",
  "Disarmament",
  "Economics/Finance",
  "Education",
  "Emergency Response",
  "Employment",
  "Energy",
  "Engineering",
  "Enterprise Ecosystems",
  "Entertainment",
  "Environment",
  "Fair & Responsible Media",
  "Female Genital Mutilation",
  "Food",
  "Fragile States",
  "Gender and Minority Groups",
  "Governance",
  "Health",
  "Humanitarian",
  "Hunger",
  "Infrastructure",
  "Justice",
  "Livelihoods",
  "Logistics",
  "Management",
  "Media",
  "Membership Associations",
  "Midwifery",
  "Natural Resource Conflicts",
  "NGO",
  "Nutrition",
  "Peace",
  "Platform creation",
  "Religious Engagement",
  "Research",
  "Resource Management",
  "Security",
  "Stability",
  "Supply Chain Solutions",
  "Sustainability",
  "Sustainable Cities",
  "Training & Employment",
  "Transition",
  "Transparency & Accountability",
  "Travel and Hospitality",
  "Violent Extremism",
  "Water and Sanitation",
  "Workforce",
  "World Population",
  "Youth"
]

License

By contributing content or code, you agree to dedicate your works to the public domain under the terms of The Unlicense.