kyzn/dist-zilla-plugin-contributorcovenant

Add Contributor Covenant as Code of Conduct

Hi there 👋

dist-zilla-plugin-contributorcovenant's Issues

Add alternative CoCs

I gave a lightning talk about this module & Contributor Covenant Code of Conduct today. I was told on irc.perl.org that there are alternative texts such as:

• FreeBSD
• YAPC:NA
• irc.perl.org

that should be also considered as an alternatives. I'm planning to either add alternative modules for each one of those, or repurpose this repository to include multiple options. While there, I can also add old versions of these texts as options.

I'll add details later.

test fail

http://www.cpantesters.org/cpan/report/5983fb60-6bf5-1014-acdf-485bf3b87046

v2 roadmap

TODO

• Rename to be more generic

• Add following

  • Geek Feminism (Public License)
  • Citizen Code of Conduct (CC BY-SA 3.0)
  • Ruby Code of Conduct
  • Technology Transformation Service (CC0 1.0 Universal)
  • perlpolicy (Artistic License or GNU GPL)
    • Dancer (same terms as the Perl 5)
  • Mojolicious (Artistic License 2.0)
  • Django (CC BY 3.0)
  • The Perl Conference (CC BY-SA 3.0)
    • including both SoC and handling SoC incidents
  • No Code of Conduct (CC BY-SA 3.0)

• Put all license templates in a nicely structured folder, don't keep them in perl files

• Accept following arguments at dist.ini

  • License name
    • Default to Geek Feminism
  • Template variables (such as email address, community name).
    • Default to whatever-information-is-available at dist.ini
    • If none available, put generic terms such as "This community" and "Bug Tracker"
  • Filename
    • Default to "CODE_OF_CONDUCT.md"
  • Location of code of conduct file
    • Default to "both repository and build"

To follow up

• FreeBSD, irc.perl.org, Ruby don't specify licenses.
• In addition to having the IRC SOC, is it ok if we clip "community policies" and "reasonable person principle" sections under a new name as "irc.perl.org-community"?

Future

• Accept additional sections to document from dist.ini. This can be a text directly input to dist.ini, or it can be path to a markdown file to be consumed.
• Translations. I'll structure the directories to make this easy.
• Plugin model. (being able to mix and match to produce your own Standards of Conduct)

More references

Click here to see a list of most common Code of Conduct documents.

Thanks

I gave a lightning talk on ContributorCovenant and this very module during last day of The Perl Conference in Glasgow, 2018. I've received a lot of ideas through discussions. I would like to thank mst, Finn, Larry, Gloria, Ruthie and Joelle for their ideas and support. Cheers! 🎉