Meetings issueshttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues2021-05-24T21:14:21Zhttp://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?*http://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/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/35Link to Security analysis for BBB2021-09-29T21:03:00ZThomas GilmourLink to Security analysis for BBBhttp://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 Hancock