Meetings issueshttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues2022-05-02T14:01:30Zhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/42Process for Removing an Inactive Project or Group2022-05-02T14:01:30ZBeth HancockProcess for Removing an Inactive Project or Group**Estimated time:** 10 - 15 minutes
I can be available on March 16th to present or would appreciate it if someone else would be willing to lead an earlier review.
**Description:** The Community Advisory Group drafted on a [Process for ...**Estimated time:** 10 - 15 minutes
I can be available on March 16th to present or would appreciate it if someone else would be willing to lead an earlier review.
**Description:** The Community Advisory Group drafted on a [Process for Removing an Inactive Project or Group]( https://opensource.ieee.org/community-advisory-group/draft-removing-an-inactive-group-or-project/-/blob/main/README.md ). The goal of this process is to maintain an organized and sustainable platform.
We would greatly appreciate the input of the Technical Advisory Group on this policy.Beth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/44OSCom Naming Guidelines Review2022-03-16T22:24:29ZBeth 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 ...
**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).
I can be available to present this for the March 16th meeting, but not tomorrow's meeting (March 2nd).Beth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/41Schedule and Open Up Proposal Deeper Dive Meeting2022-01-31T21:48:40ZSonia SantanaSchedule and Open Up Proposal Deeper Dive MeetingSonia SantanaSonia Santanahttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/26IEEE SA Open platform update and release of infra version 0.1.02022-01-31T21:35:39ZJosh Gayj.gay@ieee.orgIEEE SA Open platform update and release of infra version 0.1.0Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Technical Advisory Group meeting. Please include an estimated time for presentation and discussion. The description is welcome, but optional.
...Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Technical Advisory Group meeting. Please include an estimated time for presentation and discussion. The description is welcome, but optional.
**Estimated time:** 15 minutes
**Description:** The IEEE SA Open platform underwent a major upgrade to the architecture and the software and services that architectures hosts. @lisa will provide an overview of the new features and functionality as well as a brief update on the *infra* project itself, which seeks to open source our operations code and configuration management code of the IEEE SA Open platform.Lisa MaginnisLisa Maginnishttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/38TAG branding/ social media contribution2022-01-31T21:35:08ZEmily BrownTAG branding/ social media contribution
**Estimated time:** 5
**Description:**
Let's strategize on how we can contribute to branding/ social media strategy within respective AG topics/roles. Please add suggestions or recommendations for posts, communities to join, opinions...
**Estimated time:** 5
**Description:**
Let's strategize on how we can contribute to branding/ social media strategy within respective AG topics/roles. Please add suggestions or recommendations for posts, communities to join, opinions, processes needed, or any other useful input for us to move forward. Thank you!
Current Social Channels:
StackOverflow: IEEE SA OPEN
Reddit: IEEE SA OPENEmily BrownEmily Brownhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/403NWeb, why/what it is, and group to make formalized standards2022-01-19T00:33:08ZMikalai Birukou3NWeb, why/what it is, and group to make formalized standardsUse the title of this issue for the agenda item you'd like to share or discuss at an upcoming Technical Advisory Group meeting. Please include an estimated time for presentation and discussion. The description is welcome, but optional.
...Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Technical Advisory Group meeting. Please include an estimated time for presentation and discussion. The description is welcome, but optional.
**Estimated time:**
20 minutes.[ieee_notes.pdf](/uploads/e4a89733116b2049af89c0e1b7fcfb42/ieee_notes.pdf)
**Description:**
- Introduce 3NWeb, why&what this is. [RFC 8890, "The Internet is for End Users"](https://www.rfc-editor.org/rfc/rfc8890.txt) is a formal starting "why".
- Outline scope of formal standards that can be here for the benefit of different implementors.
- Opening for questions about 3NWeb and IEEE SA process.http://opensource.ieee.org/technical-advisory-group/meetings/-/issues/31Community Handbook Input2021-11-11T17:14:31ZBeth HancockCommunity Handbook InputHowdy 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 Technical Advisory Gro...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 Technical 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/technical-advisory-group/meetings/-/issues/36Ways to Contribute to the Community Document2021-11-11T17:14:11ZKatie SchuethsWays to Contribute to the Community Document**Estimated time:** 15
**Description:** Community Badging made a document about ways to contribute to the community. At the request of the CAG, @beth made a [template](https://opensource.ieee.org/community-advisory-group/ways-to-contrib...**Estimated time:** 15
**Description:** Community Badging made a document about ways to contribute to the community. At the request of the CAG, @beth made a [template](https://opensource.ieee.org/community-advisory-group/ways-to-contribute/-/blob/main/README.md) of it. This may be a good outline for other groups to use to show volunteers how they can get involved.Beth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/32Tool Evaluation Rubric ( Maturity Model )2021-09-29T21:09:28ZThomas GilmourTool Evaluation Rubric ( Maturity Model )http://opensource.ieee.org/technical-advisory-group/meetings/-/issues/35Link to Security analysis for BBB2021-09-29T21:03:00ZThomas GilmourLink to Security analysis for BBBhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/34Cost analysis for BBB2021-09-29T20:59:08ZThomas GilmourCost analysis for BBBhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/33Provide link to BBB Feature requirements/ Comparison grid.2021-09-29T20:52:43ZThomas GilmourProvide link to BBB Feature requirements/ Comparison grid.http://opensource.ieee.org/technical-advisory-group/meetings/-/issues/29How to Create a Subgroup2021-07-29T20:45:31ZBeth HancockHow to Create a SubgroupThomas GilmourThomas Gilmourhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/28Proposed Agenda Item for 7/21 TAG2021-07-28T15:02:24ZGerald ArditoProposed Agenda Item for 7/21 TAGMeeting with SA Open Education Group
**Estimated time:** 30 minutes
**Description:**
To provide TAG an understanding of our working group, how we're different from other sort of communities, and lastly to begin listing how IEEE SA-Ope...Meeting with SA Open Education Group
**Estimated time:** 30 minutes
**Description:**
To provide TAG an understanding of our working group, how we're different from other sort of communities, and lastly to begin listing how IEEE SA-Open might be able to assist us and where they can't assist us.http://opensource.ieee.org/technical-advisory-group/meetings/-/issues/25Review proposed "Dormant Sub-Group Policy" from CAG2021-06-22T20:07:38ZKarsten WadeReview proposed "Dormant Sub-Group Policy" from CAGUse the title of this issue for the agenda item you'd like to share or discuss at an upcoming Technical Advisory Group meeting. Please include an estimated time for presentation and discussion. The description is welcome, but optional.
...Use the title of this issue for the agenda item you'd like to share or discuss at an upcoming Technical Advisory Group meeting. Please include an estimated time for presentation and discussion. The description is welcome, but optional.
**Estimated time:**
10 minutes
**Description:**
https://opensource.ieee.org/community-advisory-group/meetings/-/issues/8
The CAG has drafted this policy for what to do when a sub-group appears to be stalled or actually goes dormant.
We think it would be good to adopt a common policy across all of the Advisory Groups, and propose this draft for your review, and eventual consideration for adoption.
Please review and comment on that issue for any changes, thoughts, etc. to this draft.http://opensource.ieee.org/technical-advisory-group/meetings/-/issues/23TAG Event in June2021-06-22T20:07:04ZThomas GilmourTAG Event in Junehttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/21TAG Breakout Session during MAGic on May 4th2021-06-08T23:23:14ZThomas GilmourTAG Breakout Session during MAGic on May 4thhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/11Using the Subgroup reporting guidelines template2021-05-13T22:20:04ZBeth HancockUsing the Subgroup reporting guidelines template
Estimated time: 5 minutes
Description:
[This](https://opensource.ieee.org/documentation-and-templates/community-sample-templates/subgroup-reporting-guidelines/-/blob/main/subgroup-reporting-guidelines.md) is complete. How should we u...
Estimated time: 5 minutes
Description:
[This](https://opensource.ieee.org/documentation-and-templates/community-sample-templates/subgroup-reporting-guidelines/-/blob/main/subgroup-reporting-guidelines.md) is complete. How should we utilize the Reporting Guidelines template?
Should we add it as an agenda item board issue template?
Link that Agenda Item board issue template somewhere for easy access?Beth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/9Use Badging platform for distributed (communal) Integration testing based on ...2021-04-26T20:23:07Zjulia longtinUse Badging platform for distributed (communal) Integration testing based on file format, and intended use.I've had a 'bad idea', and it involves badging, and a way to encourage projects to test with one another (integration testing).
Create one badge, for ```<IEEE SA: Accepts <format> for <use>>```. requires a 'github-action-like-thing' tha...I've had a 'bad idea', and it involves badging, and a way to encourage projects to test with one another (integration testing).
Create one badge, for ```<IEEE SA: Accepts <format> for <use>>```. requires a 'github-action-like-thing' that accepts a file in that format, and returns success or failure.
when a merge to <specified branch> is tested, we call each of the projects that generate the format, and ask for a file. if all the files pass, the badge stays green. if some tests pass, it's yellow. if no tests pass, it's red.
Create one badge, for ```<IEEE SA: Generates <format> for <use>>```. requires a 'github-action-like-thing' that generates a file in that format.
when a merge to <specified branch> is tested, we ask the built binary to generate data in the format, and send it to each of the projects that accept that format. if all the files pass, the badge stays green. if some tests pass, it's yellow. if no tests pass, it's red.
Create one badge, for ```<IEEE SA: <format> for <use> Maintainer>```, who would get a badge, be linked to by the page the other badges point to when you click on them, and who could recieve requests to be a producer / consumer. They are responsible for working with products consuming / producing the format, to ensure compliance.
For an example, the 3D printing community uses .STL format for objects. There are many programs that produce this format, many that consume it, and some than "lint check" it.
Who would (want to) obtain such badges
1> someone who cares that files generated adhering to a standard are highly interoperable. I'd love to do "STL for 3D modeling", for instance, since i have a producer and consumer that i maintain.
What are the necessary achievements to attain the badge
2> Let anyone create a "standard" people can subscribe to (format * use), and issue a badge when a number of projects have signed up to become consumers/producers.
What would be the issuing 'authority' and how would it verify the achievements?
3> IEEE SA, and verify by counting?julia longtinjulia longtinhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/8Alternating times for TAG meeting (earlier for every other week)2021-04-12T20:14:49ZMike NolanAlternating times for TAG meeting (earlier for every other week)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 often have trouble attending the TAG mee...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 often have trouble attending the TAG meeting because it's at 9pm GMT. I know that IEEE is an American organization but it would still be great to have it a bit earlier if possible so I can join and contribute :)Mike NolanMike Nolan