Meetings issueshttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues2021-01-20T23:19:58Zhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/1Team Agreement - 2020 01 06 Mtg2021-01-20T23:19:58ZBeth HancockTeam Agreement - 2020 01 06 MtgThomas GilmourThomas Gilmourhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/2TAG Purpose Statement2021-03-15T19:35:02ZBeth HancockTAG Purpose StatementBeth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/3Agenda Items Board and process for gathering Agenda Items2021-02-01T21:09:43ZBeth HancockAgenda Items Board and process for gathering Agenda ItemsThe proposed process for gathering agenda items is to send agenda notice prior Wed, reminder on Friday, accept items through EOD Sunday. Draft agenda will normally be created on Monday and link sent out to TAG. Agenda reviewed/discussed/...The proposed process for gathering agenda items is to send agenda notice prior Wed, reminder on Friday, accept items through EOD Sunday. Draft agenda will normally be created on Monday and link sent out to TAG. Agenda reviewed/discussed/approved in meeting.Beth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/4Agenda Jan 20 TAG2021-01-11T21:25:10ZThomas GilmourAgenda Jan 20 TAGhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/5Member Access Recommendations2021-03-15T19:35:16ZThomas GilmourMember Access RecommendationsBeth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/6Group Reporting Guidelines2021-02-01T21:52:12ZThomas GilmourGroup Reporting GuidelinesThomas GilmourThomas Gilmourhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/7Decision-making process for TAG2021-04-12T20:14:39ZThomas GilmourDecision-making process for TAGThomas GilmourThomas Gilmourhttp://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 Nolanhttp://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/10"Mattermost authorization message not appearing"2021-03-15T19:55:29ZJosh Gayj.gay@ieee.org"Mattermost authorization message not appearing" "To fix this I needed to open web developer and look at the traffic. When you run the slack command you will see an "execute" command is run in the traffic. You click on that and look at the http header response. The header response wil... "To fix this I needed to open web developer and look at the traffic. When you run the slack command you will see an "execute" command is run in the traffic. You click on that and look at the http header response. The header response will have a message telling you to give gitlab permissions to run the command using your account. You then take the URL and paste it into a new tab and it will bring you to the right page. Then you can just click approve. "http://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/12Production Readiness2021-04-12T20:14:07ZThomas GilmourProduction ReadinessThomas GilmourThomas Gilmourhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/13Project Intake from Community2021-04-12T20:13:51ZThomas GilmourProject Intake from Communityhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/14Update the meeting invite to reflect the new 2pm Eastern time and announce th...2021-03-30T18:25:06ZSonia SantanaUpdate the meeting invite to reflect the new 2pm Eastern time and announce the change in MattermostBeth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/15Add Project Intake Form draft to Gitlab2021-03-29T18:35:23ZSonia SantanaAdd Project Intake Form draft to GitlabThomas GilmourThomas Gilmourhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/16Production Readiness - Longer Discussion2021-03-18T15:30:32ZSonia SantanaProduction Readiness - Longer Discussionhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/17Request time on the CAG agenda for review of the Project Intake form2021-03-30T18:24:51ZSonia SantanaRequest time on the CAG agenda for review of the Project Intake formBeth HancockBeth Hancockhttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/18BigBlueButton2021-04-12T20:13:36ZMicky MettsBigBlueButtonI love being able to offer an alternative to zoom - here is my blog on that:
https://agaric.coop/blog/why-we-resist-zoom-and-choose-bigbluebutton-video-chat
I am a member of http://meet.coop and we are building a cooperative of BigBlueB...I love being able to offer an alternative to zoom - here is my blog on that:
https://agaric.coop/blog/why-we-resist-zoom-and-choose-bigbluebutton-video-chat
I am a member of http://meet.coop and we are building a cooperative of BigBlueButton hosts/hubs around the world. Wondering if anyone has an interest in joining the BigBlueButton issue queue, it is pretty active.
https://github.com/bigbluebutton/bigbluebutton/issueshttp://opensource.ieee.org/technical-advisory-group/meetings/-/issues/19Workflow for tools addtion2021-04-12T20:14:35ZRaul PinedaWorkflow for tools addtionPresent Workflow for tools additions to the platform at TAGPresent Workflow for tools additions to the platform at TAGhttp://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 4th