[ENH] Steering Group meeting shareables#102
Merged
sappelhoff merged 8 commits intobids-standard:gh-pagesfrom Mar 17, 2020
Merged
[ENH] Steering Group meeting shareables#102sappelhoff merged 8 commits intobids-standard:gh-pagesfrom
sappelhoff merged 8 commits intobids-standard:gh-pagesfrom
Conversation
update 1/16
updated BEPs that have responded by 1/16 7p PST. also added a new column for communication channels
update 3/12
sappelhoff
reviewed
Mar 13, 2020
Member
sappelhoff
left a comment
There was a problem hiding this comment.
LGTM, thanks for adding this @franklin-feingold . I understand that this is intended to be a bit informal, and I like it --> still I added some points to help you make the document more readable to everybody.
I didn't get the "minutes" section --> aren't all these points already mentioned above?
_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md
Outdated
Show resolved
Hide resolved
_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md
Outdated
Show resolved
Hide resolved
_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md
Show resolved
Hide resolved
_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md
Outdated
Show resolved
Hide resolved
_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md
Outdated
Show resolved
Hide resolved
_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md
Outdated
Show resolved
Hide resolved
Member
|
PS: When making PRs, you can save yourself a lot of trouble by using this workflow:
That will keep the commit history cleaner (1 sensible commit instead of 5 confusing ones) and save you some work. |
Collaborator
Author
|
@sappelhoff incorporated your comments This PR has a few more commits because of previous branch conflicts and remedying. |
Member
A good way for "resolving" all conflicts prior to making a fresh branch is:
This will force your forked |
Collaborator
robertoostenveld
left a comment
There was a problem hiding this comment.
I agree with @sappelhoff that more links would be useful.
_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md
Show resolved
Hide resolved
sappelhoff
reviewed
Mar 14, 2020
Member
sappelhoff
left a comment
There was a problem hiding this comment.
thanks for making some adjustments! I added some final points.
Lastly: If we want to keep the "minutes" section, can you please design it as an unordered list?
- I think it makes more sense
- that way ...
- with thoughts being separated
- on different levels
- (note: this is a bad example, but I hope you get my point 🤣 )
| We discussed the channels through which to share updates to the BIDS specification. | ||
| An issue was opened to start crowdsourcing and collecting this information. | ||
| We will be using this to share the release of v1.2.2 and to request the final rounds of feedback on the Genetic information extension. | ||
| [An issue](https://github.com/bids-standard/bids-specification/issues/415) was opened to start crowdsourcing and collecting this information. |
Member
There was a problem hiding this comment.
Suggested change
| [An issue](https://github.com/bids-standard/bids-specification/issues/415) was opened to start crowdsourcing and collecting this information. | |
| A [GitHub issue](https://github.com/bids-standard/bids-specification/issues/415) was opened to start crowdsourcing and collecting this information. |
| An issue was opened to start crowdsourcing and collecting this information. | ||
| We will be using this to share the release of v1.2.2 and to request the final rounds of feedback on the Genetic information extension. | ||
| [An issue](https://github.com/bids-standard/bids-specification/issues/415) was opened to start crowdsourcing and collecting this information. | ||
| We will be using this list of channels to share the release of v1.2.2 and to request the final rounds of feedback on the Genetic information extension. |
Member
There was a problem hiding this comment.
Suggested change
| We will be using this list of channels to share the release of v1.2.2 and to request the final rounds of feedback on the Genetic information extension. | |
| We will be using the resulting list of communication channels to share the release of v1.2.2 and to request the final rounds of feedback on the Genetic information extension ([BEP018](https://docs.google.com/document/d/1uRkgyzESLKuGjXi98Z97Wh6vt-iLN5nOAb9TG16CjUs/)). |
|
|
||
| We discussed considerations for when to open a repository under the BIDS standard organization on GitHub. | ||
| There should be multiple people committed to the repository (otherwise it is better of under the personal GitHub account), the maintainers should be clearly identifiable (e.g. as a CODEOWNERS file at top level), there should be a code of conduct in the repo that is consistent with that of the BIDS specification, and (as a consequence of the code of conduct) the repository should welcome contributions from others. | ||
| Previously, community members have opened repositories under our BIDS standard organization. |
Member
There was a problem hiding this comment.
Suggested change
| Previously, community members have opened repositories under our BIDS standard organization. | |
| Previously, community members have opened repositories under the BIDS [GitHub organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-organizations) named [`bids-standard`](https://github.com/bids-standard/). |
| There should be multiple people committed to the repository (otherwise it is better of under the personal GitHub account), the maintainers should be clearly identifiable (e.g. as a CODEOWNERS file at top level), there should be a code of conduct in the repo that is consistent with that of the BIDS specification, and (as a consequence of the code of conduct) the repository should welcome contributions from others. | ||
| Previously, community members have opened repositories under our BIDS standard organization. | ||
| We want to codify guidelines to govern this. | ||
| The plan is that there should be multiple people committed to the repository (otherwise it is better of under the personal GitHub account), the maintainers should be clearly identifiable (e.g. as a CODEOWNERS file at top level), there should be a code of conduct in the repo that is consistent with that of the BIDS specification, and (as a consequence of the code of conduct) the repository should welcome contributions from others. |
Member
There was a problem hiding this comment.
Suggested change
| The plan is that there should be multiple people committed to the repository (otherwise it is better of under the personal GitHub account), the maintainers should be clearly identifiable (e.g. as a CODEOWNERS file at top level), there should be a code of conduct in the repo that is consistent with that of the BIDS specification, and (as a consequence of the code of conduct) the repository should welcome contributions from others. | |
| The plan is that there should be multiple people committed to the repository (otherwise it is better of under the personal GitHub account), the maintainers should be clearly identifiable (e.g., as a [CODEOWNERS file](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners) at top level), there should be a code of conduct in the repo that is consistent with that of the BIDS specification, and (as a consequence of the code of conduct) the repository should welcome contributions from others. |
| We want to host another [Community Forum](https://bids.neuroimaging.io/2020/01/02/announcement-community-forum-events.html) (but not too frequent) and potentially a starter kit/demo in the Open Science Room at OHBM. | ||
|
|
||
| Regarding issue [#407](https://github.com/bids-standard/bids-specification/pull/407), we consider Zenodo to be a suitable the location to store historical specification pdfs, also for future versions. | ||
| Regarding discussions on where to host our historical specification pdfs (please refer to issue [#407](https://github.com/bids-standard/bids-specification/pull/407)), we consider Zenodo to be a suitable the location to store our specification pdfs. |
Member
There was a problem hiding this comment.
Suggested change
| Regarding discussions on where to host our historical specification pdfs (please refer to issue [#407](https://github.com/bids-standard/bids-specification/pull/407)), we consider Zenodo to be a suitable the location to store our specification pdfs. | |
| Regarding discussions on where to host our historical specification pdfs (please refer to issue [#407](https://github.com/bids-standard/bids-specification/pull/407)), we consider Zenodo to be a suitable location to store our specification pdfs. |
Atom didn't save my first copy
Collaborator
Author
|
@robertoostenveld @sappelhoff - thank you for the feedback - have applied your thoughts Re: minutes, I kept the top-level discussion with bullet points to show the different subtopics (and subsubtopics) hit during that conversation. I think this makes it easier to follow and interpret the conversation |
Member
|
Thanks @franklin-feingold |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is adding a post to our website to share the Steering Groups: executive summary, action items, and minutes from a previous meeting