Meetings issueshttp://opensource.ieee.org/community-advisory-group/meetings/-/issues2022-05-18T17:45:08Zhttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/23OSCom Operations Manual Changes2022-05-18T17:45:08ZBeth HancockOSCom Operations Manual ChangesOSCom is now considering adopting several updates to the Open Source Operations Manual. They have specifically requested that the main AGs review these.
A [clean copy]( https://opensource.ieee.org/oscom/meetings/-/blob/master/Supportin...OSCom is now considering adopting several updates to the Open Source Operations Manual. They have specifically requested that the main AGs review these.
A [clean copy]( https://opensource.ieee.org/oscom/meetings/-/blob/master/Supporting%20Documentation/DRAFT_OSCOM_Operations_Manual_20220303__2_.docx ) of the Operations Manual including the proposed changes is available for review.
You can also view a [redlined version]( https://opensource.ieee.org/oscom/meetings/-/blob/master/Supporting%20Documentation/DRAFT_OSCOM_Operations_Manual_20220303_Redlined__1__2.docx ) or take a look at the [current version]( https://standards.ieee.org/wp-content/uploads/import/documents/other/OSCOM_Operations_Manual.pdf ).
Please leave feedback in the public comments area of the OSCom GitLab [issue]( https://opensource.ieee.org/oscom/meetings/-/issues/9 ).2022-05-11http://opensource.ieee.org/community-advisory-group/meetings/-/issues/22OSCom Naming Guidelines Review2022-03-16T22:12:23ZBeth HancockOSCom Naming Guidelines Review**Estimated time:** 10 - 15 minutes
**Description:** The Naming Ad Hoc of the Open Source Committee (OSCom) that governs the IEEE SA OPEN Community, has created a set of guidelines to help people as they name their projects and groups o...**Estimated time:** 10 - 15 minutes
**Description:** The Naming Ad Hoc of the Open Source Committee (OSCom) that governs the IEEE SA OPEN Community, has created a set of guidelines to help people as they name their projects and groups on the IEEE SA OPEN platform. OSCom is requesting feedback from our community on [these guidelines](https://opensource.ieee.org/oscom/meetings/-/blob/master/Supporting%20Documentation/proposed-naming-guidelines.md) prior to April 1, 2022.
Please provide feedback in email to [opensource@ieee.org](opensource@ieee.org) or as a comment in the [associated GitLab issue](https://opensource.ieee.org/oscom/meetings/-/issues/7).Beth HancockBeth Hancockhttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/20Moving Advisory Group Roadmap Workshop2022-01-31T22:10:38ZBeth HancockMoving Advisory Group Roadmap WorkshopMoving the AG Roadmap Workshop.
Time: 5 minsMoving the AG Roadmap Workshop.
Time: 5 minsKatie SchuethsKatie Schuethshttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/19Social Media for Community Support2022-01-31T22:11:05ZBeth HancockSocial Media for Community Support5 minutes to speak and gather feedback on this issue from the CAG.5 minutes to speak and gather feedback on this issue from the CAG.Emily BrownEmily Brownhttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/18Suggest Ways to Contribute Document2022-01-31T22:10:49ZKatie SchuethsSuggest Ways to Contribute DocumentInstructions: Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Community Advisory Group meeting. No need to to add a description to this issue.
https://opensource.ieee.org/community-advisory-...Instructions: Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Community Advisory Group meeting. No need to to add a description to this issue.
https://opensource.ieee.org/community-advisory-group/community-badging/about/-/blob/main/ways-to-contribute.mdKatie SchuethsKatie Schuethshttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/17DEI Guild Meetup Kickoff , Subgroup meetings2022-01-31T22:10:56ZJayashree ArunkumarDEI Guild Meetup Kickoff , Subgroup meetingsIdentified 2 guest speakers for our guild meetup kickoff. Dates will be finalised during the meeting
Need to discuss about the volunteers for the subgroupIdentified 2 guest speakers for our guild meetup kickoff. Dates will be finalised during the meeting
Need to discuss about the volunteers for the subgrouphttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/16DEI charter -Initial Meeting with IEEESA project leads2021-11-29T20:12:02ZJayashree ArunkumarDEI charter -Initial Meeting with IEEESA project leadsGuild meetup kickoff with IEEESA project leadsGuild meetup kickoff with IEEESA project leadshttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/15Community Handbook Topics2021-11-11T17:15:13ZBeth HancockCommunity Handbook TopicsHowdy all! The Documentation and Curation Subgroup has been working on ideas for a Community Handbook for IEEE SA OPEN. We need your help! Can we please add this topic to an upcoming meeting?
We'd like to get the Community Advisory Gr...Howdy all! The Documentation and Curation Subgroup has been working on ideas for a Community Handbook for IEEE SA OPEN. We need your help! Can we please add this topic to an upcoming meeting?
We'd like to get the Community Advisory Group's feedback.
* What is important to you and to our community?
* What other topics do we need to include?
* What processes are missing?
We've started sketching things out below.
## IEEE SA Open Community Handbook
Themes we want to explore:
* Create Buy-In
* Tool Stack
* Topics Covered
* Writing Style and Guidelines
* How updates are handled
### Topics We Want to Cover
#### About
* Mission, Vision & Values (inclusivity is part of our values)
* History
* Governance model
* Code of Conduct
* Community Guidelines
* How we communicate
* Terminology
#### Community
These are processes that are relevant to the whole community.
* Recommendations for having meetings
* How to use the handbook
* Handbook guidelines (getting started page, contributing authors, etc)
* Writing Style and Guidelines
#### Participating
1. Getting Started
* Different pathways
* Forming a new group
* Stopping a new group
* How to use GitLab
* Path to Leadership (TBD within IEEE SA Open)
2. Advisory Groups
* Community Advisory Group
* Documentation and Curation
* Community Badging
* Diversity Equity and Inclusion
* Open Community Development Models
* Education
* Technical Advisory Group
* Security
* Data Governance
* Marketing Advisory Group
* Open Source Intelligence
* Metrics
* How to Market Open Source
* Event Production
3. Hosted Groups/Projects
4. Standards Groups/Projects
#### Social
* How to meet other community members and tools you use to communicateBeth HancockBeth Hancockhttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/12DEI charter2022-01-31T22:10:50ZGeorg LinkDEI charterInstructions: Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Community Advisory Group meeting. No need to to add a description to this issue.Instructions: Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Community Advisory Group meeting. No need to to add a description to this issue.Jayashree ArunkumarJayashree Arunkumarhttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/10Community AG BigBlueButton Room Usage2021-06-21T18:10:30ZBeth HancockCommunity AG BigBlueButton Room UsageWe'd like to discuss how the Community advisory Group and its subgroups can support one another in the usage of the shared Big Blue Button room.
Time: 5-10 minutesWe'd like to discuss how the Community advisory Group and its subgroups can support one another in the usage of the shared Big Blue Button room.
Time: 5-10 minutesBeth HancockBeth Hancockhttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/9Microsite draft of content2021-05-25T13:21:31ZEmily BrownMicrosite draft of contentInstructions: Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Community Advisory Group meeting. No need to to add a description to this issue.
I do not want to speak, I would just like to b...Instructions: Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Community Advisory Group meeting. No need to to add a description to this issue.
I do not want to speak, I would just like to bring attention to content needed for micrositeshttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/8Review of "Subgroup Lifecycle at Advisory Groups Policy"2021-09-08T12:30:58ZBeth HancockReview of "Subgroup Lifecycle at Advisory Groups Policy"[UPDATED June 23, 2021 during CAG meeting]
Here is a new draft, that incorporates some feedback, but probably not all. Please respond with comments and suggestions.
---
# Subgroup Lifecycle at Advisory Groups Policy
# 1. Subgroups
Ad...[UPDATED June 23, 2021 during CAG meeting]
Here is a new draft, that incorporates some feedback, but probably not all. Please respond with comments and suggestions.
---
# Subgroup Lifecycle at Advisory Groups Policy
# 1. Subgroups
Advisory Groups may establish subgroups to focus work on specific topics. This policy outlines requirements and best practices for healthy and sustainable subgroups.
**Types of Subgroups:**
* Project: formed to create a specific deliverable; limited term but can be extended
* Standing subgroup: needs an ongoing purpose
## 1.1 Forming subgroup
Before establishing a subgroup, an advisory group needs to ensure the need for a separate subgroup and the commitment from potential subgroup members.
* When more work is needed than can be done as part of the advisory group, start with informal meetings to advance the topic
* Have discussions about the topic for the subgroup within the advisory group
* Before forming a subgroup, the following conditions need to be met:
- 3+ volunteers engaged consistently in informal meetings and commit to continue engaging after subgroup is formed
- An elevator pitch was created that describes the goal of the subgroup
* In the process of creating the subgroup:
- A GitLab group is created for the work of the subgroup (TODO: we might want to create a template for a subgroup)
- A regular meeting schedule is established and calendar invites are sent out (TODO: currently we require a Leadingbit employee to open the room of a meeting and start the recording)
- A Mattermost channel is created for the subgroup
- A subgroup leader and co-leader are appointed
## 1.2 Maintaining subgroup
A subgroup should have sustained efforts to advance its topic.
* The lead and co-lead are responsible for:
- Facilitating regular meetings and saving meeting minutes
- Reporting to the advisory group on progress and blockers
* When regular attendance at meetings drops below 3 volunteers
- Lead and co-lead may consider how to get more engagement (e.g., encourage asynchronous engagement, reduce frequency of meetings, change time of meeting to accommodate volunteers who could make it at a different time; recruit new subgroup members)
- Lead and co-lead may consider taking a hiatus or disbanding the sugroup
* When lead or co-lead become inactive or unresponsive, they vacate their position
- A first approach is to try reaching the volunteers to understand why they are absent and whether they'd be coming back
- As long as either lead or co-lead are active, they can find a replacement for the vacant position
* When lead and co-lead are inactive or unresponsive, the subgroup is without leadership
- Other subgroup members may step up to assume leadership position
- The advisory group, that the subgroup belongs to, may appoint a new lead and co-lead
## 1.3 Taking a hiatus
Subgroup volunteers may decide to put the work of the subgroup on hold, for example during summer vacation time or Christmas and New Years celebrations.
* A Subgroup that goes on hiatus has to inform the advisory group about its "hiatus" status and when work is planned to resume
## 1.4 Disbanding subgroup
Subgroups may be disbanded for a variety of reasons, including:
* The subgroup, especially project, reached its original goal and is no longer needed
* Engagement in the subgroup is too low to sustain work and no further attempts are planned to revive the subgroup
Dispanding a subgroup involves:
* Informing the advisory group that the subgroup plans to disband and coordinating following steps
* Ideally, provide a report to the advisory group about the progress made by the subgroup and reason for disbanding it
* Delete or archiving its Mattermost channel
* Delete the standing calendar invite
* Archive the GitLab organization, add a notice on all READMEs2021-06-23http://opensource.ieee.org/community-advisory-group/meetings/-/issues/5Project Intake Form2021-03-31T18:54:20ZBeth HancockProject Intake FormThe Technical Advisory Group has been discussing gathering information and Tom has created this [Project Intake Form](https://opensource.ieee.org/technical-advisory-group/draft-project-intake-form). We would greatly appreciate having the...The Technical Advisory Group has been discussing gathering information and Tom has created this [Project Intake Form](https://opensource.ieee.org/technical-advisory-group/draft-project-intake-form). We would greatly appreciate having the Community AG look over this to make sure that the language is clear and easily understandable.
Tom can be reached at @tomg2012 in the Technical AG Mattermost Team or I can help with organizing time.
Estimated time for this would be 5-10 minutes.Beth HancockBeth Hancockhttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/4OSINT SubGroup2021-03-10T17:25:21ZSarah WomerOSINT SubGroupAn Introduction to the OSINT SubGroup and a Mind Meld of Referral IdeasAn Introduction to the OSINT SubGroup and a Mind Meld of Referral Ideashttp://opensource.ieee.org/community-advisory-group/meetings/-/issues/3Understanding the connection between IEEE and open source2021-02-18T16:41:10ZAndrew OramUnderstanding the connection between IEEE and open sourceThe IEEE has many established practices and even established meanings for words such as "committee" and "minutes." How do these map to our GitLab platform and practices? We will get guidance on this issue from IEEE experts.The IEEE has many established practices and even established meanings for words such as "committee" and "minutes." How do these map to our GitLab platform and practices? We will get guidance on this issue from IEEE experts.http://opensource.ieee.org/community-advisory-group/meetings/-/issues/2Agenda Item: Structure of CAG repositories2021-02-01T15:10:08ZGeorg LinkAgenda Item: Structure of CAG repositoriesUpdate on restructuring the CAG repositories that @andyo was working on.Update on restructuring the CAG repositories that @andyo was working on.http://opensource.ieee.org/community-advisory-group/meetings/-/issues/1Confer with Andy from Clover about integration with MM.2021-02-09T15:48:10ZBeth HancockConfer with Andy from Clover about integration with MM.Silona BonewaldSilona Bonewald