Stream: fhircast-github
Topic: docs / PR #66 Create code of conduct & governance
Github Notifications (FHIRcast) (Feb 06 2019 at 03:54):
isaacvetter opened PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 06 2019 at 03:54):
isaacvetter requested lbergnehr, daliboz, and NiklasSvenzen for a review on PR #66.
Github Notifications (FHIRcast) (Feb 06 2019 at 03:54):
isaacvetter requested lbergnehr, daliboz, and NiklasSvenzen for a review on PR #66.
Github Notifications (FHIRcast) (Feb 06 2019 at 03:54):
isaacvetter requested lbergnehr, daliboz, and NiklasSvenzen for a review on PR #66.
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr submitted PR Review
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr submitted PR Review
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr created PR Review Comment
We haven't talked much of the FHIRcast API. Should this be specification instead?
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr created PR Review Comment
The current PMC Chair is [Isaac Vetter](https://github.com/isaacvetter).
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr created PR Review Comment
Any existing committer may nominate a contributor as a new committer on the project. The nominee should have a demonstrated history of contributions and commitment. Contributions can come in many forms such as code, issues, documentation, and community engagement. A nominee must receive a unanimous vote from the PMC. Upon being accepted, the PMC Chair will grant the nominee write access to the FHIRcast repositories and announce the new committer to the mailing list.
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr created PR Review Comment
The term wasn't clear to me until reading the GOVERNANCE document. We could link to that section here.
reported by contacting any member of the [Project Management Committee](./GOVERNANCE.md#project-management-committee). All
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr created PR Review Comment
Members of the PMC are committers who are also responsible for governing the FHIRcast project. The PMC has primary responsibility for development of the FHIRcast community. This includes evangelism, organizing Connectathons, and other forms of community building. The PMC also reports progress to the community and defines target feature sets for releases.
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr created PR Review Comment
The community refers to the collective set of individuals and parties contributing to, implementing, or following the FHIRcast project.
Github Notifications (FHIRcast) (Feb 06 2019 at 08:22):
lbergnehr created PR Review Comment
Implementers are those who have implemented the FHIRcast specification. Such implementations can be done locally, in a test environment, or in a production system.
Github Notifications (FHIRcast) (Feb 07 2019 at 19:56):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 19:56):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 19:57):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 19:57):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 19:57):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 19:57):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 19:57):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 19:58):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 20:03):
isaacvetter updated PR #66
from governance to master
Hey @NiklasSvenzen , @daliboz , @lbergnehr ,
Will you please review this proposed code of conduct and governance additions?
I think that this change should require unanimous committer approval.
Isaac
p.s Niklas, are there really no hyphens/apostrophes in your name? (There aren't on your linkedin nor github profiles).
Github Notifications (FHIRcast) (Feb 07 2019 at 20:03):
isaacvetter submitted PR Review
Github Notifications (FHIRcast) (Feb 07 2019 at 20:03):
isaacvetter created PR Review Comment
solid point, @lbergnehr ! Changed.
Also, awesome review! :+1:
Github Notifications (FHIRcast) (Feb 08 2019 at 17:13):
NiklasSvenzen submitted PR Review
Github Notifications (FHIRcast) (Feb 14 2019 at 15:05):
daliboz created PR Review Comment
Out of curiosity, if we're using the "review changes" functionality of the github PR, do we also need to do the +1/-1? Or is approving/request changes good for the +1/-1?
I can see that abstaining, if it needs to be a more solid "op out" than not doing a review, may require a more formal comment.
thoughts?
Github Notifications (FHIRcast) (Feb 14 2019 at 15:05):
daliboz submitted PR Review
Github Notifications (FHIRcast) (Feb 14 2019 at 15:05):
daliboz submitted PR Review
Last updated: Apr 12 2022 at 19:14 UTC
