suse-projects / source Goto Github PK

Only featured items have a visible description, but many other projects have one in the YAML. If we show that description on hover, we can tell people more about the project without them having to click on anything.

add the open source policy from opensource.suse.com into this page

Hello team,

Leap or generally openSUSE (Including Tumbleweed) is one of the largest aggregator of opensource work and the largest opensource projects SUSE has. Yet it didn't make it to the top. What about to put on some score based ordering?

I do not want to be the person to put it into the first row. But contribution wise, it would be the case.
Comming up with some score based ordering could help.

Otherwise I'm happy that its visible without scrolling at least on my computer.

my 2 cents.

This repository no longer appears to be used to generate the open source portal. Please archive it to indicate that.

SUSE already has https://suse.github.io which redirects to https://opensource.suse.com. That page is currently very bare-bones and has not been touched in 3 years. URL-wise though, it would seem like a nicer place to host this page.

I am wondering if for example we should add projects from https://github.com/os-autoinst/ to this page, e.g. https://github.com/os-autoinst/openQA/ . One reason for hestitation is that I am not sure if we should say that "SUSE has created" openQA. Likely it was mainly if not 100% SUSE colleagues which at that time were IIRC members of a "openSUSE team" so it could be that the creation of the project was actually done by "openSUSE" as an entity, not SUSE. Also, despite the main contributions done by SUSE colleagues there are many contributions by non-SUSE members. I hope this can be clarified in this project here and maybe a disclaimer along the lines of "Listing a project by no means tries to diminuish any contribution regardless if project members are colleagues of SUSE or not". I am sure there can be better phrasing :)

It's not clear that the featured projects are featured.

Cannot configure password police in openSUSE 12 LDAP can anyone help fix this issue?

There is already https://github.com/SUSE which seems like a much better fit than a custom organization.

I don't see any license text in this repository. At least for logos copied from the referenced projects, the license has to be clearly visible.

I see https://static.redhat.com/libs/redhat/redhat-font/2/webfonts/red-hat-font.css being loaded by the page. It's also trying to load RH's Overpass font from fonts.googleapis.com.

Categories are a good start but sometimes projects fall into several categories and it's not really clear where to place them. Labels (multiple labels allowed) could help with that.

Labels could help also to say, e. g. there is a commercial offering, or that we are hiring, or that we have open community hours.

E. g. Uyuni does infrastructure, provisioning, operations (systems management), virtualization, monitoring, SecOps, has a paid-for supported option (SUSE Manager), etc:

labels: infrastructure, operations, virtualization, monitoring, security, commercial, hiring, community-hours

#17 was rejected with:

We intentionally want to limit this to projects that SUSE created. Otherwise it will become a list of hundreds of projects where SUSE made any commit, and that changes the value of the page.

Indeed this does change values. Before we valued upstream first ( see https://opensource.suse.com/suse-open-source-policy ) over creation of new projects for the sake of distinct projects. There are situations were it is useful to create new projects even when existing projects could be made to fit. But this goes one step further and generally valuing it more, without inspecting the case. Can you explain what benefit new projects / distinct projects have that makes them more valuable than upstream first?

Six featured projects, featured statically, seems a bit short. What about adding a carousel to be able to display more featured projects?

Please note I am not saying all projects should be featured but that the subset of featured projects is probably going to be more than 6.

I. e.
Total suse-projects = N
Total featured projects = M (where N > M)
Total displayed featured projects = 6 (where M > 6, hence there's a case for a carousel)