dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

link to affinity teams on firt reference

This commit is contained in:
Ben Balter 2016-03-10 11:44:40 -05:00
parent 2240d52338
commit 61e549d317
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/_posts/2016-03-11-making-it-easier-to-contribute-to-jekyll.md
View File

@ -12,6 +12,6 @@ If you've been looking to get involved with the Jekyll community, but didn't kno
First, we've completely rewritten [the project's contributing guidelines](https://jekyllrb.com/docs/contributing/), outlining [the various ways you can contribute](https://jekyllrb.com/docs/contributing/#ways-to-contribute), and including better instructions for [submitting proposed changes via GitHub.com](https://jekyllrb.com/docs/contributing/#submitting-a-pull-request-via-githubcom) or for [submitting your first code improvement](https://jekyllrb.com/docs/contributing/#code-contributions). If you have any feedback, we'd love to hear it! Simply click the "improve this page" button in the top right corner of the contributing documentation.
Second, this week, we created six community interest groups, we're calling Jekyll affinity teams. If you're interested in a particular aspect of the project (or just want to learn more), you can join any one of these team (or two, or three), to participate in discussions about potential bugs and proposed improvements. And the best part is there's no commitment. If you just want to listen, or if at any point you want to leave (or switch teams), that's totally fine. We won't say a thing. As of today, the teams are "build", "documentation", "ecosystem", "performance", "stability", and "windows". To learn more about the various affinity teams, or to join one (please do!), visit [teams.jekyllrb.com](https://teams.jekyllrb.com/).
Second, this week, we created six community interest groups, we're calling [Jekyll affinity teams](https://teams.jekyllrb.com). If you're interested in a particular aspect of the project (or just want to learn more), you can join any one of these team (or two, or three), to participate in discussions about potential bugs and proposed improvements. And the best part is there's no commitment. If you just want to listen, or if at any point you want to leave (or switch teams), that's totally fine. We won't say a thing. As of today, the teams are "build", "documentation", "ecosystem", "performance", "stability", and "windows". To learn more about the various affinity teams, or to join one (please do!), visit [teams.jekyllrb.com](https://teams.jekyllrb.com/).
We hope these changes will make it easier for you to make your first (or second, or third) contribution to Jekyll today. Thanks for helping to make Jekyll awesome!