Skip to content

Which platform next? Vote on the candidates #780

Description

@DavidCozens

SolidSyslog ports to a new platform by filling roles, not by editing Core, so a
platform adapter is a self-contained piece of work. Which one gets built next is
decided by demand.

How to vote

Every candidate is an open issue, ordered by votes.

Open the one you need and add a 👍 to it. The reaction button is the small
smiley at the end of the issue description. That thumbs-up is the vote.

If the platform you need isn't listed, open an issue and ask for it.

How the queue is ordered

Votes order it, and a funded engagement moves a platform up it exactly as votes
do. The deciding question is whether we can build and test it ourselves:

  • If we can - freely available tooling, in our CI, on every change - we will
    consider it for free inclusion. It joins the supported platform list and is
    maintained and regression-tested like everything else we ship.
  • If we can't - a toolchain behind a licence server, a proprietary SDK,
    hardware we would have to buy - we will write it for you, or help your team
    write it, with the cost offset against your licence.

Either way we would rather a platform became part of the product, supported and
proven against the role contract on every change, than a fork you maintain
alone.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions