Skip to content
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

New lead maintainer required #243

Open
latentflip opened this issue May 20, 2016 · 6 comments
Open

New lead maintainer required #243

latentflip opened this issue May 20, 2016 · 6 comments

Comments

@latentflip
Copy link
Contributor

Hey folks, responding to this comment by @cdaringe to say that I've pretty much removed myself from ampersand, as I haven't the time or energy to contribute helpfully any more.

I was the lead maintainer on this repo at one point, but definitely shouldn't be, so it'd be great it someone could step up to take my place.

@cdaringe or anyone else up for it?

@cdaringe
Copy link
Member

i'm in the same boat, @latentflip.

&-state is still, IMHO, one of the best x-env js Model utilities out there. per npm-stats, it still has a big user base too.

hopefully someone can volunteer to shepherd it! i know @dhritzkiv hasn't done much in &-state specifically, but he has been absolutely instrumental in improving so many of our packages, I wonder if he'd have interest in joining up. :)

@dhritzkiv
Copy link
Member

dhritzkiv commented May 20, 2016

:) Thanks for considering me. I have a fair bit of free time to contribute to ampersand, and I use the framework regularly, so I'm certainly invested in its success; I'd be interested in helping maintain the ampersand family.

Other than helping with reviewing PRs, submitting dep. updates + fixes, and releasing when needed, are there any other potential responsibilities to be mindful of?

@latentflip
Copy link
Contributor Author

Sounds about right!

Philip Roberts

On 20 May 2016, at 22:41, Daniel Hritzkiv [email protected] wrote:

:) Thanks for considering me. I have a fair bit of free time to contribute to ampersand, and I use the framework regularly, so I'm certainly invested in its success; I'd be interested in helping maintain the ampersand family.

Other than helping with reviewing PRs, submitting dep. updates + fixes, and releasing when needed, are they any other potential responsibilities to be mindful of?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@cdaringe
Copy link
Member

cdaringe commented May 20, 2016

@AmpersandJS/community-leaders @AmpersandJS/core-team 👀 would you support inviting @dhritzkiv to the team?

@dhritzkiv, i think that's pretty much it. :) obviously you're familiar with the contribution guidelines/rules/etc. the only other todo would be having us assign npm rights and updating the &-js webpage. if a couple teamsters give their blessing and you're willing, let's do it!

@fyockm
Copy link
Member

fyockm commented May 20, 2016

+1 thanks for stepping up @dhritzkiv

@samhashemi
Copy link
Contributor

samhashemi commented May 24, 2016

Is the lead maintainer suppose to be on the README of each repo? A quick review:

Project Maintainer
ampersand-app no maintainer listed
ampersand-router no maintainer listed
ampersand-class-exted no maintainer listed
ampersand-sync no maintainer listed
ampersand-collection no maintainer listed
ampersand-collection-lodash-mixin @klaemo
ampersand-collection-rest-mixin no maintainer listed
ampersand-filtered-subcollection @wraithgar
ampersand-view @cdaringe
ampersand-events no maintainer listed
ampersand-model no maintainer listed

It seems like clarity around ownership and active maintenance would help, as in this ampersand-state example.

9 of my lodash v4 PRs are in limbo, and I have no idea who I should be working with to get them merged and released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants