IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

Commit e0bd26e7 authored by Ida Sim's avatar Ida Sim
Browse files

Update CONTRIBUTING.md

parent a89f2ff9
Pipeline #155 passed with stage
in 12 seconds
......@@ -31,13 +31,13 @@ If the project team solicits further work on the issue, see below the section ab
To participate in the IEEE Working Group (WG), please follow the instruction on the website to [join the listserv](https://sagroups.ieee.org/1752/)
Starting in July 6, 2021, the WG's activity will be driven by the Project Authorization Request [(PAR) P1752.2](https://sagroups.ieee.org/1752/)
Starting on July 6, 2021, the WG's activity will be driven by the Project Authorization Request [(PAR) P1752.2](https://sagroups.ieee.org/1752/)
## Merge request criteria
We greatly appreciate it if your merge request met the following criteria
1. Your merge request should be associated with an issue that defines the bug your merge requests fixes or the feature it adds.
1. Your merge request should be associated with an issue that defines the bug your merge request fixes or the feature it adds.
2. Your merge request should include a test or tests (please note that submitting tests that confirm a bug is a great contribution in and of itself even if you aren't able to provide a fix for a given bug)
3. Your merge request should update any relevant or impacted documentation
4. Try to keep the amount of changes you make in a single merge request as small as possible
......@@ -52,7 +52,7 @@ Please use the following workflow when submitting merge requests:
4. Push the commit(s) to your working branch in your fork.
- squash commits into a small number of logically organized commits, keeping the commit history intact on shared branches
- please try to have fewer than 15 commit messages per merge request
5. Submit a merge request (MR) to our projects default branch
5. Submit a merge request (MR) to our project's default branch
- merge request title should describe the change you wish to make
- merge request description should give the reason for the change
- use complete URLs to issues and other merge requests
......@@ -85,7 +85,7 @@ For examples and additional explanation of these seven rules, please read Chris
## Communicating with us
Communication witht the project team should be done through issues. Should you have additional questions, you can contact the IEEE 1752 Secretary at [simona@openmhealth.org]
Communication with the project team should be done through issues. Should you have additional questions, you can contact the IEEE 1752 Secretary at [simona@openmhealth.org]
## Project governance and new maintainer process
......@@ -105,7 +105,7 @@ Shiv Hiremath, Temple University
* The 1752 Working Group votes and the site maintainers implement the Working Group's decisions.
* The process above occurs quarterly.
* The 1752 Working Group meets virtually. Invitations are sent to the 1752 listserv. To [join the listserv](https://sagroups.ieee.org/1752/) follow the instructions. Participation is open to all. Voting is restricted to voting members. Voting membership is established according to the current 1752 Policies & Procedures
* Slide deck andminutes of each 1752 Working Group call are posted on the [public website](https://sagroups.ieee.org/1752/meeting-agenda-minutes/)
* Slide deck and minutes of each 1752 Working Group call are posted on the [public website](https://sagroups.ieee.org/1752/meeting-agenda-minutes/)
We welcome participation and contributions to the project
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment