Meetings issueshttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues2022-05-23T16:46:26Zhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/51Social Media Outreach Platforms2022-05-23T16:46:26ZBeth HancockSocial Media Outreach PlatformsWe want to reach out to the Open Source community through social media. How can we best reach you and your colleagues? Are there specialized platforms you use to get information about Open Source or your specialization (coding, security,...We want to reach out to the Open Source community through social media. How can we best reach you and your colleagues? Are there specialized platforms you use to get information about Open Source or your specialization (coding, security, hardware, etc.)?Thomas GilmourThomas Gilmourhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/50Community Platform Primer2022-05-23T16:46:22ZBeth HancockCommunity Platform Primer**Estimated time:**
10 minutes
**Description:**
Raul will present the work that the Security subgroup has been doing to create a [Community Platform Primer](https://opensource.ieee.org/technical-advisory-group/security/community-platfo...**Estimated time:**
10 minutes
**Description:**
Raul will present the work that the Security subgroup has been doing to create a [Community Platform Primer](https://opensource.ieee.org/technical-advisory-group/security/community-platform-primer/-/blob/main/README.md).Raul PinedaRaul Pinedahttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/49OSCom Operations Manual changes2022-05-09T19:28:06ZBeth 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/technical-advisory-group/meetings/-/issues/46Discuss Badging Generation Tool2022-04-11T16:41:09ZMatt SnellDiscuss Badging Generation Tool**Estimated time:**
5 min
**Description:**
I'd like to propose an idea for a tool that we can use to generate badges on the platform.
Sorry about my lateness with this one! We just discussed this in the badging meeting.
UPDATE: I wil...**Estimated time:**
5 min
**Description:**
I'd like to propose an idea for a tool that we can use to generate badges on the platform.
Sorry about my lateness with this one! We just discussed this in the badging meeting.
UPDATE: I will wait for the next TAG 3/30 to bring this one uphttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/45Invite New Groups/Projects to Present at TAG2022-03-14T20:23:29ZSonia SantanaInvite New Groups/Projects to Present at TAGJosh Gayj.gay@ieee.orgJosh Gayj.gay@ieee.orghttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/43Recruitment Strategy from TAG prospective2022-03-03T16:55:41ZEmily BrownRecruitment Strategy from TAG prospectiveUse 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:**
This issue is to help MAG create best practices and guidance on recruitment. We are seeking the input of TAG members to help us learn what is needed from their perspective.Emily BrownEmily Brownhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/37Open Up2022-01-31T21:48:22ZJosh Gayj.gay@ieee.orgOpen UpUse 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 mins
**Description:**
Open Up is a new IEEE SA OPEN project. One purpose of Open Up is to serve as an upstream version of our platform/infrastructure configuration management scripts and tools (e.g., other scripts, bots, etc, used across our platform). It will also be the project we will use for testing new tool integration with our platform.
One reason we are creating Open Up is to make it easier for us (and others) to created custom branded versions of the IEEE SA Open Community edition platform.
Down the road, Open Up could be expanded to included more than just configuration management scripts and integration/productivity tools, such as templates or guides. Our hopes is to eventually transition the project from a staff-run project to a more community run one.Josh Gayj.gay@ieee.orgJosh Gayj.gay@ieee.orghttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/27Data Governance Next Steps2021-09-29T17:02:22ZBeth HancockData Governance Next StepsLet's take a second look at @lreimer's [slides](https://opensource.ieee.org/technical-advisory-group/meetings/-/blob/master/Supporting%20Documentation/Open_Data_sub-committee_structure.pptx) and discuss where we would like to go next wit...Let's take a second look at @lreimer's [slides](https://opensource.ieee.org/technical-advisory-group/meetings/-/blob/master/Supporting%20Documentation/Open_Data_sub-committee_structure.pptx) and discuss where we would like to go next with this project/subgroup.LaVonne ReimerLaVonne Reimerhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/24Microsite draft of content2021-05-27T21:14:51ZEmily BrownMicrosite draft of contentUse 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:**
5 mins
**Description:**
I do not want to speak, I would just like to bring attention to content needed for micrositeshttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/22Utilize badging to encourage the community to integration test their file for...2021-05-24T21:14:21Zjulia longtinUtilize badging to encourage the community to integration test their file formats.# Community Request Form
Use this form to help the Technical Advisory Group and the greater community to understand the idea you are presenting, how it fills the needs of the IEEE SA OPEN Community, and provide adequate information for ...# Community Request Form
Use this form to help the Technical Advisory Group and the greater community to understand the idea you are presenting, how it fills the needs of the IEEE SA OPEN Community, and provide adequate information for participant developers or members of our engineering teams to develop a "Proof of Concept". Please fill out all appropriate sections.
_____
## Proposal
Provide a brief overview of your project proposal (200 words or less). Please include answers to the following if possible.
- What problem are you trying to solve for the community?
- Why do you feel this is important for the community?
- Are there any existing technologies you're aware of that currently provide this functionality?
- What kind of tests/metrics would tell us we were successful?
- Is there anything else you would like us to know about your request?
FOSS projects have a lot of file formats they deal in. many of these have poor implementations, and problems interfacing between tools.
I've had an idea for an enhancement to our platform. Tt involves using badging to encourage projects to test with one another (integration testing).
## Use Cases and Details
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 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 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 receive 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.
If you have more information regarding future use cases or specifics of the new functionality you are requesting, please include it.
**Improvements to Features or Workflow**
*What is the workflow / feature you feel could be improved?*
(Example: When I try to... (describe current flow) I expect to see... (Describe desired behavior) but instead see (describe actual behavior from system).
No workflow changes.
**New Functionality**
*What are the new features or abilities you would like to see implemented?*