Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024.07.29 #23

Open
4 tasks done
seanmcilroy29 opened this issue Jul 29, 2024 · 1 comment
Open
4 tasks done

2024.07.29 #23

seanmcilroy29 opened this issue Jul 29, 2024 · 1 comment

Comments

@seanmcilroy29
Copy link
Contributor

seanmcilroy29 commented Jul 29, 2024


2024.12.16 Agenda/Minutes


Time 1700 (BST) - See the time in your timezone

  • Co-Chair - Pindy Bhullar (UBS)
  • Co-Chair - Sean O'Keefe (Microsoft)
  • Convener – Sean Mcilroy (Linux Foundation)

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:

  • Full Name, Affiliation, (optional) GitHub username

Agenda

  • Approve agenda
  • Approve previous Meeting Minutes

Note: Workshop participants have been invited to discuss the latest updates to the project with the project team.

Review Implementation Pillar - Miroboard Review

  • Provide input on the output templates and checklists that should be included in the guidance document.
  • Explore the sustainable IT.org framework and share any relevant information that could be incorporated into the TOSS framework.
  • Investigate the possibility of automating certain aspects of the TOSS framework using technology like APIs.
  • Explore the idea of a "paved path" approach, where one department's implementation can be replicated for other departments.

Next Meeting

  • 2024.12.13

Adjourn

  • Motion to adjourn

Documentation

@seanmcilroy29
Copy link
Contributor Author

Summary meeting notes

The meeting focused on refining a framework for organisational software sustainability. Key points included the creation of a document with bite-sized sections on strategy, implementation, operations, and compliance, accompanied by adaptable templates. The team discussed the need for a user-friendly interface to streamline the process and the potential use of software to assist in decision-making. They emphasised the importance of defining essential levels and using a maturity matrix to assess organisational readiness. The conversation also touched on the challenges of exporting decision trees from Miro and the need for consistent numbering in the document for clarity.

Meeting Minutes

Document Overview and Structure
Pindy introduces the document, emphasising its bite-sized format along with sections on strategy, implementation, operations, and compliance. The document includes a checklist and templates for organisations to adopt, allowing flexibility for specific needs. Pindy notes the absence of diagrams in the document due to technical issues. Sean discusses the aim of making the document adaptable to individual company profiles and highlights the importance of templates for clarity and administrative efficiency.

Framework and Practical Approaches
Pindy clarifies that the framework is not rigid but flexible, allowing organisations to tailor it to their specific needs. The strategy pillar is highlighted as a practical starting point, emphasising the need for objectives, governance, and measurement. Implementation details involve understanding processes, data collection, and choosing tools like the impact framework or

SCI calculation methods.
The document aims to provide a comprehensive view, featuring sections on AI, hosting options, and procurement, encouraging organisations to think broadly. It seeks to deliver a holistic perspective, with components on AI, hosting options, and procurement, prompting organizations to consider the bigger picture.

Maturity Matrix and Proof of Concept
Birthe proposes defining essential levels or a maturity matrix to aid organisations in implementing the framework effectively. Pindy agrees and highlights the maturity matrix developed by Anne as a valuable tool for evaluating organisational readiness. The concept of proof of concept is introduced, using the SCI methodology as an example for UBS to test and pinpoint gaps. Various starting points for organisations are discussed, including vendor requirements, regulatory mandates, and procurement angles.

Feedback and Future Updates
Sean highlights the significance of utilising the framework and gathering feedback to identify gaps and enhance it. The necessity for a tool to streamline the process and update the framework as changes arise is underscored. Sean notes the forthcoming change in structure and the possible contributions from the hardware standards working group. The discussion encompasses the importance of concentrating on hardware selections and the evolving character of hardware options in the cloud.

Review and Implementation Challenges
Birthe expresses challenges in reviewing decision trees due to export limitations in the current tool. Pindy and Sean discuss the necessity for a consistent numbering system to enhance clarity and logic in the document. The significance of feedback from voluntary organizations for testing the framework is highlighted. Sean mentions the need for a planning session in January to conclude the current section and begin preparations for the following year.

Final Remarks and Personal Updates
The meeting concludes by focusing on the next steps, which include reviewing the document, defining levels, and planning future actions. The team agrees to continue developing the framework and gathering feedback to enhance it. The importance of collaboration and input from various stakeholders is emphasised to ensure the framework's effectiveness.

Action Items

  • @sean Mcilroy - Explore the software tool mentioned to help streamline the framework implementation.
  • Define the maturity levels and proof-of-concept options to help organisations start.
  • Revise the numbering and formatting of the document for better consistency.
  • Review the document and provide feedback on the flow, clarity, and numbering.
  • Reach out to potential organisations to trial the framework and provide feedback.
  • Schedule a planning session in January to wrap up this work and plan the next steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant