Login
You're viewing the functional.cafe public feed.
  • Nov 6, 2026, 6:54 AM

    @riverpunk ⁃ Develop and adopt a code of conduct for your project that enshrines tolerance and mutual respect. (See contributor-covenant.org)
    ⁃ Prioritize interoperability and data import/export
    ⁃ Emphasize accessibility
    ⁃ Emphasize ease of use, not just features
    ⁃ Welcome beauty, artistry, fun, and whimsy
    ⁃ Go out of your way to welcome beginner contributors

    All of this is praxis, IMO.

    💬 2🔄 1⭐ 13

Replies

  • 💬 0🔄 6⭐ 7
  • Nov 7, 2026, 4:28 AM

    @drahardja@sfba.social @riverpunk@defcon.social copy and pasting the contributor covenant is not enough though!!

    the contributor covenant is a template, not a document that should be used as is for every project. imo copying it verbatim is worse than not having a code of conduct at all, as it shows very little thought has been put into it. (ive seen lots of projects even copy the note that says to change it!!)

    projects should at the very least change the title to "<project name> code of conduct" and tailor the "addressing and repairing harm" section to what the project will actually do if the CoC is breached.

    the contributor covenant is a great starting point, but tailoring it to the values of a project shows that effort has actually been put into it and it probably isn't just there for show.


    i definitely agree with all your other points though!!

    💬 0🔄 0⭐ 0