Green-Software-Foundation / toss

Transforming Organisational Software Sustainability (TOSS) - Using software emission calculation data for organisational decision making during the development and use of technology applications.
Other
4 stars 0 forks source link

2024.02.07 #7

Closed seanmcilroy29 closed 7 months ago

seanmcilroy29 commented 9 months ago

2024.02.07 Agenda/Minutes


Time 1600 (GMT) - See the time in your timezone

Antitrust Policy

Joint Development Foundation meetings may involve participation by industry competitors, and the Joint Development Foundation intends to conduct all of its activities in accordance with applicable antitrust and competition laws. It is, therefore, extremely important that attendees adhere to meeting agendas and be aware of and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

If you have questions about these matters, please contact your company counsel or counsel to the Joint Development Foundation, DLA Piper.

Recordings

WG agreed to record all Meetings. This meeting recording will be available until the next scheduled meeting. Meeting recording

Roll Call

Please add 'Attended' to this issue during the meeting to denote attendance.

Any untracked attendees will be added by the GSF team below:

Agenda

Welcome New Members

Review & Approve Project Scope

Supporting Docs

Timeline - Confirmation

Next Steps

Dependencies

AOB

Future meeting Agenda submissions

Next Meeting

Adjourn

Meeting Action Items / Standing Agenda / Future Agenda submissions

PindyBhullar commented 9 months ago

Attended

sk16-dev commented 9 months ago

Attended

seanmcilroy29 commented 9 months ago

Summary meeting notes

Project alignment and naming. Pindy and Sean had a discussion about a new project named "Rubrik". It is currently being developed by a company called Indeed. During their conversation, Pindy suggested that Rubrik could be used as a testbed for the Matrix project. They also brainstormed possible names for the project, such as SSS and Torso DOGS. Pindy proposed "Transforming Organisational Software Sustainability" as the name for the project since it aligns with the current industry buzzwords like "digital transformation". Pindy emphasized that the project's focus should be on implementation rather than decision-making. Sean agreed with Pindy on the project's implementation strategy. They further discussed timelines for a research project, with potential delays due to volunteer involvement.

Designing a visual representation of a complex system. Sean and Pindy had a conversation about the GSF development process. They discussed the need for a visual representation of the process instead of a document. Sean suggested a pictorial representation, such as a wiring diagram or flowchart, to help understand the input and output of the process. They also discussed designing a course, using visual aids, and troubleshooting audio issues.

Developing a new standard for a GSF project. During a discussion between Sean M and Sean 'O', they discussed reducing the scope and improving the project's accessibility. Sean 'O' expressed his interest in policy shoring up. Sean Mcilroy plans to contact Namrata to create a PR blog and inform GSF members about the project updates. Additionally, he will involve Sophie in the discussion regarding accelerator requirements. They are considering possibly having a workshop in March or April to finalize their ideas.

Pindy and Sean M discussed creating a visual representation of the project scope document for a workshop. Pindy suggests they start by creating a Miro diagram, and Sean offers to help with the review and editing process. Pindy and Sean discuss scheduling meetings with potential participants, including Muhammad and Amadeus.

Action Items [ ] Give project update at next Standards Working Group meeting [ ] Add Mohammad/Indeed project to the list to monitor potential overlap [ ] Create an initial visual/diagram of the framework [ ] Update project name to "Transforming Organizational Software Sustainability." [ ] Change email distribution list name [ ] Reach out to Namrata for PR/accelerate program [ ] Bring Sophie into the next meeting to discuss accelerated program requirements [ ] Notify GSF members of project updates via newsletter, article, steering committee [ ] Send Shawn and Pindy access to the Miro board [ ] Review and finalize the scope document