Description
Continue with the Hackweek 2024, with focus on reviewing existing processes / ways of working and creating workflows:
Goals
- Check all the processes from [1] and [3]
- move them to confluence [4], make comments, corrections, etc.
- present the result to the SCC team and ask for reviews
Resources
[1] https://github.com/SUSE/scc-docs/blob/master/team/workflow/kanban-process.md [2] https://github.com/SUSE/scc-docs/tree/master/team [3] https://github.com/SUSE/scc-docs/tree/master/team/workflow
Confluence
[4] https://confluence.suse.com/spaces/scc/pages/1537703975/Processes+and+ways+of+working
This project is part of:
Hack Week 24 Hack Week 25
Activity
Comments
-
about 1 year ago by calmeidadeoliveira | Reply
Some progress done https://confluence.suse.com/display/scc/Processes+and+ways+of+working?src=contextnavpagetreemode, but there is still a lot to be checked.
-
about 1 year ago by calmeidadeoliveira | Reply
For Hackweek purposes I would say it was possible to review a lot, but there is still work to be dobe (along this fiscal year).
-
10 days ago by calmeidadeoliveira | Reply
First day Hackweek 2025 - aligned with @lcaparroz to check existing processes described on [4]. While Luis will focus on reviewing "COOTW" part, Christian will check what is needed to include Jira specific information. - We will align again on Dec. 2nd.
-
9 days ago by calmeidadeoliveira | Reply
2nd day - reviewed Luis' PR related to the COoTW https://github.com/SUSE/scc-docs/pull/354 and drafted the high level development workflow
-
8 days ago by calmeidadeoliveira | Reply
3rd day - I was stuck in several meetings, including one related to other Hackweek project (Bugzilla goes AI). I had a chance to align with Luis: we discussed the high level development workflow and shared views on what still needs to be described (mainly the "discovery phase"). Luis will focus on the Epic part.
-
6 days ago by calmeidadeoliveira | Reply
4th day - new Epic workflow (under review) https://lucid.app/lucidchart/9a5751b2-c3b0-4467-8ca6-78a7b327288d/edit?invitationId=inv_1792a8dc-088d-4411-94b3-c31628d18cef - Epic process https://confluence.suse.com/spaces/scc/pages/1963098193/Epic+New+Proposal
Similar Projects
MCP Server for SCC by digitaltomm
Description
Provide an MCP Server implementation for customers to access data on scc.suse.com via MCP protocol. The core benefit of this MCP interface is that it has direct (read) access to customer data in SCC, so the AI agent gets enhanced knowledge about individual customer data, like subscriptions, orders and registered systems.
Architecture
Goals
We want to demonstrate a proof of concept to connect to the SCC MCP server with any AI agent, for example gemini-cli or codex. Enabling the user to ask questions regarding their SCC inventory.
For this Hackweek, we target that users get proper responses to these example questions:
- Which of my currently active systems are running products that are out of support?
- Do I have ready to use registration codes for SLES?
- What are the latest 5 released patches for SLES 15 SP6? Output as a list with release date, patch name, affected package names and fixed CVEs.
- Which versions of kernel-default are available on SLES 15 SP6?
Technical Notes
Similar to the organization APIs, this can expose to customers data about their subscriptions, orders, systems and products. Authentication should be done by organization credentials, similar to what needs to be provided to RMT/MLM. Customers can connect to the SCC MCP server from their own MCP-compatible client and Large Language Model (LLM), so no third party is involved.
Milestones
[x] Basic MCP API setup MCP endpoints [x] Products / Repositories [x] Subscriptions / Orders [x] Systems [x] Packages [x] Document usage with Gemini CLI, Codex
Resources
Gemini CLI setup:
~/.gemini/settings.json:
issuefs: FUSE filesystem representing issues (e.g. JIRA) for the use with AI agents code-assistants by llansky3
Description
Creating a FUSE filesystem (issuefs) that mounts issues from various ticketing systems (Github, Jira, Bugzilla, Redmine) as files to your local file system.
And why this is good idea?
- User can use favorite command line tools to view and search the tickets from various sources
- User can use AI agents capabilities from your favorite IDE or cli to ask question about the issues, project or functionality while providing relevant tickets as context without extra work.
- User can use it during development of the new features when you let the AI agent to jump start the solution. The issuefs will give the AI agent the context (AI agents just read few more files) about the bug or requested features. No need for copying and pasting issues to user prompt or by using extra MCP tools to access the issues. These you can still do but this approach is on purpose different.
Goals
- Add Github issue support
- Proof the concept/approach by apply the approach on itself using Github issues for tracking and development of new features
- Add support for Bugzilla and Redmine using this approach in the process of doing it. Record a video of it.
- Clean-up and test the implementation and create some documentation
- Create a blog post about this approach
Resources
There is a prototype implementation here. This currently sort of works with JIRA only.