• toastal@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    8 months ago

    There is of course a walled garden for participation and it is an issue

    And if you insist on using Microsoft GitHub, this contribution concern can be mitigated by offering an alternative mirror or a mailing list/email address to send patches. One way to help prevent lock-in would be to use MS GitHub’s repository settings & straight-up disable non-portable features like “Discussions”, “Sponsors” & maybe even the “Issues” tracker favoring a third-party option or the issue tracker of the mirror along with disabling “Actions” choosing a third-party CI option or the CI that comes with the mirror (or require checks ran locally before pushing).

    • coffeeClean@infosec.pub
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      8 months ago

      Having a bug tracker in that walled garden is the biggest problem. It demonstrates what I’m talking about: digital rights being disregarded.