Git Product home page Git Product logo

source's Introduction

SUSE Projects

This is the source repo for the SUSE Projects page.

This page is a compilation of open source software that SUSE has created.

Contributing

If you would like to submit a project for inclusion, please fork the repository, make changes as outlined below, and submit a pull request.

Adding A Project

To add a project, please create a YAML file in data/projects/{category} with the name of your project, normalized in lowercase, with - in place of whitespace.

For example, a project named "Rancher Desktop" in the Development category would be saved in data/projects/development/rancher-desktop.yaml.

---
name: Rancher Desktop
repository: https://github.com/rancher-sandbox/rd
twitter:
website:
description: Kubernetes on your desktop.

The project must have, at the minimum, the following fields:

  • name
  • repository

For it to be a Featured project it also needs the description field and a logo (see below). If it does not have a website, the repository URL will be used instead. If it does not have a Twitter handle, it will be dynamically excluded from the card if the project is Featured.

If the project does not have a value for a key, it is not necessary to include the key for any reason other than clarity. Missing keys and keys with no value are ignored.

Project Logos

If your project has a logo, please upload it in SVG (preferred) or PNG to static/logos and name it the same as the project's YAML file (e.g. lowercase, with space replaced by -).

A logo is not required, but only projects with logos can be Featured.

Featuring a Project

NOTE: The list of featured projects is maintained by the PM Team. Please do not set your own project to be Featured.

If the project is to be featured, add it to the featured key in config.yaml. The number of featured projects is set in the featuredLimit variable in config.yaml. Only the first projects up to that limit will appear as featured projects in the cards at the top of the page.

Featured projects must have a logo (see above).

Project Categories

Please place your project in one of the existing category directories. If it fits into more than one category, place it in the one where you think it fits the best. Categories should be broad and inclusive. For example, Operations is better than Package Managers because a package manager is part of an operations workflow.

Try to fit entries into a noun for what the software enables. Kubewarden enables Security for Kubernetes, so although it could go into Kubernetes, it fits better in Security.

If your project doesn't fit into an existing category, please create a new directory and explain your reasons for the new category in your pull request.

Some categories will have characters that won't encode into a directory, such as "AI/ML." In this case, use a - for the special characters. This creates a directory ai-ml. This, however, when sent through humanization, becomes "Ai Ml," which is not what we want.

In this situation, set an override in categoryMap in config.yaml that sets the category key (the directory name) to the name that you would like. If a category exists in the override map, it will not go through humanization and will instead show the map value.

Disabling a Project

Any project can be disabled by adding disabled: true to the YAML. This allows projects to be temporarily removed without having to delete their content entirely.

Previewing Your Changes

If you would like to preview your changes before committing, you can do so by installing Hugo in your local environment. Once installed, run hugo server -D from the root of the repository. This will open a development server on your machine. As you make changes, they will reload live in the browser.

Deployment

Once a PR is merged, the site is built by GitHub Actions and then pushed to the organizational repo. From there GitHub publishes it to the final destination.

Built with

This site was created using Hugo.

Licensing

  • CC BY-SA 4.0 for the displayed page and primary license for this repository.
  • MIT for the JavaScript
  • CC0 for the HTML and CSS

SUSE trademarks and individual project logos are not subject to the above license grants. Usage of these items is restricted by their individual license grants.

This repository is based on RedHatOfficial/RedHatOfficial.github.io.

source's People

Contributors

ancorgs avatar andrii-suse avatar aplanas avatar bashofmann avatar dcermak avatar ddemaio avatar dirkmueller avatar ebauman avatar gionaufal avatar janzerebecki avatar jfehlig avatar m0ses avatar mattfarina avatar mook-as avatar mvarlese avatar nicstange avatar niusmallnan avatar okurz avatar oskapt avatar paususe avatar rjschwei avatar rohitsakala avatar rumch-se avatar stefanotorresi avatar sysrich avatar vestival avatar vmoutoussamy avatar vogtinator avatar votdev avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

source's Issues

Labels

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

Unclear rules for "open source software that SUSE has created"

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 :)

Oredering by project by score / size / number of contributions

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.

Add carousel

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)

Value upstream first over creating new projects

#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?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.