-
Notifications
You must be signed in to change notification settings - Fork 35
WG and Vote System Updates + General wording fixes #466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WG and Vote System Updates + General wording fixes #466
Conversation
Updated language across the site to reflect the results of the recent charter changes that were approved by vote at the recent May 15-16 2024 OMF Members Council meeting at Wageningen University in the Netherlands. - One vote per Working Group, and Early Career Scholars and Cyberinfrastructure groups are now full WG's - Removed or moved associated sections as needed to reflect these changes, and keep language consistent across the site. - This update contains all changes associated with the "Revise working group description and voting" Pull Request openmodelingfoundation#457 which can be closed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, thanks @CharlotteTill !
I have a few minor consistency changes to make to the language that I'll layer in as an additional commit soon (e.g., consistent capitalization of Working Group, ECS -> ECSWG
, and a minor typo to remove develope -> develop
) but the main change I would suggest for the future is to follow the conventional commits specification for git commit messages: https://www.conventionalcommits.org/en/v1.0.0/
Doing so will ensure that the footer has a succinct and to-the-point text as it links to the commit. The PR + commit stream will also have better and easier to follow formatting.
I'll run a git commit --amend
to update the commit log to provide a hopefully useful example of this.
Thank you @alee! I didn't know about the footer issue - I apologize for this extra work - I will note this for future changes (thank you for the link and information) and be more astute to correct practices and correct terms - though I may ask you in the future what would be best depending on the changes/additions being made |
- use `aspell` to catch a few minor speling errors - update automatic issue assignees for sitewide issues
Working Groups meet as needed at least once per year either virtually or in person. | ||
Working Groups self-organize and meet as needed at least once per year either virtually or in person. | ||
|
||
Working Groups are led by their chair(s), nominated by the Executive Committee, and approved by the Members Council. Working Groups can be led by multiple co-chairs. However, each Working Group only has a single vote within the Executive Committee. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this verbiage still doesn't address #465 but perhaps it is best left to each WG to determine how to allocate their single vote?
These are nice improvements. I wonder if it would be easier for all if there is a form for OMF affiliates like for the working groups that automatically populates a spreadsheet? |
Updated language across the site to reflect the results of the most recent charter vote - one vote per WG, and ECS and C groups are now full WG's. Started with the edits from issue (457) and expanded to cover other areas that were not covered by those changes.
Removed or moved associated sections as needed to reflect approved charter changes, and keep language consistent across the site. Tightened language, and corrected inconsistencies relating to group or individual names or roles.
This update contains all changes associated with the current issue "Revise working group description and voting #457" - that existing change can be removed - this edit includes all those noted changes (in 457) , and more.
Edits have been checked locally and appear sound as of the time of publishing.