8000 Proposal: Affinity teams and their captains by parkr · Pull Request #5273 · jekyll/jekyll · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Proposal: Affinity teams and their captains #5273

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Aug 24, 2016
Merged

Proposal: Affinity teams and their captains #5273

merged 2 commits into from
Aug 24, 2016

Conversation

parkr
Copy link
Member
@parkr parkr commented Aug 22, 2016 •
edited
Loading

Hey, Jekyll community!

I had a neat chat with @benbalter recently about our affinity teams and all the work the @jekyll/core team has in handling the issues and PR's that come through. He proposed that we ask certain members from affinity teams to become "Team Captains" which would:

  • triage issues and help find solutions
  • review PR's, then pass along to the core team for merge
  • determine correct affinity team if not theirs

@jekyllbot would automatically assign an issue to a random team captain for the mentioned affinity team and it would be their responsibility to ensure the issue is handled according to our guidelines on "Triaging an Issue". @jekyllbot would politely nudge the user to mention an affinity team if they didn't.

This would apply only to jekyll/jekyll for the time being, but could be extended out to plugin repos as well in the future.

I propose we add the following team captains (if you have a ? next to your name, it's because I haven't asked you yet):

What do you think?

@parkr parkr added the team label Aug 22, 2016
@parkr parkr self-assigned this Aug 22, 2016
@ghost
Copy link
ghost commented Aug 22, 2016

i could technically captain for the stability team if anyone else is needed

@PaulFWatts
Copy link

This sounds like a great idea to me. Hopefully I will know enough about Jekyll in the next few months to be able to volunteer and contribute in some way.

@mattr
Copy link
mattr commented Aug 23, 2016

I'll suggest that @mattr- should probably be a build team captain rather than me. No that I don't appreciate the invitation... ;)

@mattr-
Copy link
Member
mattr- commented Aug 23, 2016 •
edited by parkr
Loading

LOL. That stinkin' dash on my user name causes so many problems. 😕

@parkr
Copy link
Member Author
parkr commented Aug 23, 2016

@Fene We'd love that! Done 😄

@PaulFWatts Yes please!! Did you join an affinity team?

@mattr MERP sorryyyyy, I bet that happens more often than not. Thanks for being chill about it. ❤️

@PaulFWatts
Copy link

I've just joined some affinity teams

Kind regards

Paul Watts
Gold Coast, Australia
p:     07 5536 6721
m:    0467 705 464
email:  paul.watts@me.com

On 23 August 2016 at 1:25:26 PM, Parker Moore (notifications@github.com) wrote:

@Fene We'd love that! Done 😄

@PaulFWatts Yes please!! Did you join an affinity team?

@mattr MERP sorryyyyy, I bet that happens more often than not. Thanks for being chill about it. ❤️

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@envygeeks
Copy link
Contributor

I would like to be placed into Windows as I do handle Windows problems here and I do know a lot about Windows internals even if I am a die hard Linux user. I guess it's my fault for doing systems.

@parkr parkr mentioned this pull request Aug 23, 2016
Closed
@parkr
Copy link
Member Author
parkr commented Aug 23, 2016

I would like to be placed into Windows as I do handle Windows problems here and I do know a lot about Windows internals even if I am a die hard Linux user. I guess it's my fault for doing systems.

@envygeeks Done.

@parkr
Copy link
Member Author
parkr commented Aug 23, 2016

@jekyll/core: Could I get 2 "LGTM"'s, please? 😄

@envygeeks
Copy link
Contributor

LGTM.

@mattr-
Copy link
Member
mattr- commented Aug 23, 2016

LGTM

@parkr
Copy link
Member Author
parkr commented Aug 24, 2016

Thanks!

@jekyllbot: merge +dev

@jekyllbot jekyllbot merged commit bcedf20 into master Aug 24, 2016
@jekyllbot jekyllbot deleted the affinity-teams-and-their-captains branch August 24, 2016 00:19
jekyllbot added a commit that referenced this pull request Aug 24, 2016
@jekyllbot
Update history to reflect merge of #5273 [ci skip]
7c6fde1
@jekyll jekyll locked and limited conversation to collaborators Jul 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees

@parkr parkr

Labels
fix frozen-due-to-age internal team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@parkr @PaulFWatts @mattr @mattr- @envygeeks @jekyllbot
0