I did start an internal email discussion with SLE Product management about the proposal. I did also mention this proposal on today's openSUSE Board meeting.

Hi Luboš,
thanks for taking the initiative, so far I have started the work here, where I package some of the relevant packages...

https://github.com/CardanoOS/Factory

I'll write today a short introduction to the idea on factory@lists.opensuse.org with proposal to setup a mailing list e.g. crypto in case that there would be more interested contributors.

I can't see anything on Factory list, but I think specific list would be super cool... I am sort-of out of touch with the mailing lists for now, because I am migrating to new mail server and my mstopka@opensuse.org alias which I use for mailing-lists needs to be updated, so I am waiting for Heroes to do that =)

To me this seeks like multiple proposals all in one with a common theme

1) turis omnia support for Leap Micro we could use some particular usecase and how it fits the cardano theme

2) Github / OBS integration is something that's outside of Leap (my domain). That's something specifically for autobuild team. A task can be openned here https://github.com/openSUSE/open-build-service/issues

3) CardanoOS based on openSUSE is something I'm not sure if we can help with. That's esentially another distribution. That sounds similar to getckolinux, which is outside of the openSUSE project.
If this would be something like Leap Micro's spin with specific packages that's a whole different story.

Board invited me to today's discussion so I'll see what is their stand point and understanding behind the request.

To me this seeks like multiple proposals all in one with a common theme

1) turis omnia support for Leap Micro we could use some particular usecase and how it fits the cardano theme

2) Github / OBS integration is something that's outside of Leap (my domain). That's something specifically for autobuild team. A task can be openned here https://github.com/openSUSE/open-build-service/issues

3) CardanoOS based on openSUSE is something I'm not sure if we can help with. That's esentially another distribution. That sounds similar to getckolinux, which is outside of the openSUSE project.
If this would be something like Leap Micro's spin with specific packages that's a whole different story.

Board invited me to today's discussion so I'll see what is their stand point and understanding behind the request.

ad 3) ideally I think it would be so that we would agree on a common cross-over theme / branding to enable both communities to grow from the partnership in their respective areas (openSUSE + Cardano "corporate identity") and exactly as you said, it would be openSUSE + an Cardano specific packages across all platforms frankly, each for a different use-case from the "edge router", to the desktop, and perhaps even mobile eventually, I think the overall goal of Project Catalyst (https://projectcatalyst.org/) is / should be (to improve both time to market and leverage synergistic alliances) to partner with existing open source projects.

Currently we have 1m2 USD allocated towards "Open Source Development Ecosystem", for next three months, so we may put some initial proposals there, and if it takes off, we would go towards Grow openSUSE, Grow Cardano sort of direct enablement challenge, as the Cardano community, we certainly have software, hardware and business processes to develop and integrate, I see no reason why not do so by sort of a community partnership.

Okay so we have agreed steps

Step (0), create a ticket with heroes to setup a new mailing list around cardano community where @m4r3k would be moderator. I suggested some names in the ticket, @m4r3k is in cc, I leave the final name on him.

Step (1) recommended by Board @m4r3k will introduce the project (CardanoOS), and announce newly forming openSUSE community around cardano with pointer to mailing list on factory@lists.opensuse.org. In fact this should be the default for every new community/project.

Step (2) Lubos will track the Turis Omnia hardware enablement for Leap Micro/SLE Micro as a separate ticket (in this queue) and will pass it over to SUSE. For that I've already created a placeholder ticket and will require some usecase and requirements from @m4r3k https://code.opensuse.org/leap/features/issue/61

Step (3) OBS/GitHub integration
I've agreed with Adrian and Board that @m4r3k should open a new request in
https://github.com/openSUSE/open-build-service/issues and describe what does that mean. Adrian was interested in the requirements for Secure Build Chain, commit signatures, etc more than in the monetary aspect.

openSUSE Board has explicitly asked for a separate individual requests in ticket queue for openSUSE Board https://code.opensuse.org/board/tickets/issues for any openSUSE trademark usage, and pointed to guidelines for openSUSE Trademark usage https://en.opensuse.org/openSUSE:Trademark_guidelines

Also a highlight that openSUSE project can not accept any funds/donations. So any monetary donation from Catalyst could be processed only by SUSE.

Ad 0) thank you, I will follow-up.

Ad 1) I will follow-up on that, and run point on Cardano community side.

Ad 2) Will follow-up.

Ad 3) Feature request raised on GitHub https://github.com/openSUSE/open-build-service/issues/12200, we certainly will need verification of commit sugnatures, and complete trusted build environment. I would love to consult Adrian as to his experience with trusted build environments.

Ad Trademark, we will certainly coordinate with you on that.

Ad funding; I am certain we can fund openSUSE community members directly for their effort, as well as SUSE as an organization for work performed by SUSE employees, I would not see that as any issue.

verification of commit signatures is supported in obs-service-obs_scm. See this package for an example:

https://build.opensuse.org/package/show/OBS:Server:Unstable/build

(The new native git support will also get verification mechanics, but these don't exist yet)

Dropping openSUSE Board tags as those are to be handled as separate tickets.

Rejecting based on the inactivity.