Closed vinkla closed 5 years ago
Ah, good catch! 👍
Can you also update the link in the README?
Should we maybe close this PR and use organization-wide community health files instead?
Oh sorry, I only checked your first link. I don't think we should use organization-wide community health files.
The primary reason behind that is we're hoping that we can get some third-party package developers to move their packages into our organization. These existing packages might already have their own their own development practices that they would want to continue to follow (which is totally fine).
It would be great if the transition was seamless. We don't want to constrain other developers to follow the approaches that @appelgriebsch and I have decided to use on some of these packages.
So - I think we should rename Development.md to CONTRIBUTING.md and call it good for now.
I've gone ahead and updated the README.
Will merge once CI has finished successfully.
:tada: This PR is included in version 0.2.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This way we can take advantage of the contributing guidelines feature.
https://github.blog/2012-09-17-contributing-guidelines/
Since many of these package will behave in similarly we could use the new organization-wide community health files feature. What do you think?