New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2 roadmap #3

kyzn opened this Issue Aug 17, 2018 · 0 comments


1 participant

kyzn commented Aug 17, 2018


  • Rename to be more generic
  • Add following
  • 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 ""
    • Location of code of conduct file
      • Default to "both repository and build"

To follow up

  • FreeBSD doesn't specify a license.
  • doesn't specify a license.
  • 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 ""?


  • 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.


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! 🎉

@kyzn kyzn self-assigned this Aug 17, 2018

@kyzn kyzn referenced this issue Aug 17, 2018


Add alternative CoCs #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment