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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintainers needed #414

Closed
simison opened this Issue Mar 22, 2017 · 41 comments

Comments

Projects
None yet
@simison
Copy link
Member

simison commented Mar 22, 2017

Heyy @rschmukler,

I really like Agenda and I use it a lot! 馃嵒 Just pity that maintaining this package isn't very active anymore. :-(

There seems to be enough interest from community to send pull requests and open issues tho, so perhaps we could find some folks to help with looking after PRs and issues?

WDYT?

Unfortunately I'm already super busy with other open source stuff myself.

Anyone else interested?

@gastonelhordoy

This comment has been minimized.

Copy link

gastonelhordoy commented Mar 22, 2017

I'll be more than willing to help out and contribute if needed. I'm also heavily relying on this project so it would be good to get some progress on PRs and issues.

Let us know your thoughts on this @rschmukler

@Firanolfind

This comment has been minimized.

Copy link

Firanolfind commented Mar 22, 2017

Agree +1

@rschmukler

This comment has been minimized.

Copy link
Collaborator

rschmukler commented Mar 23, 2017

Hey all! I would be ecstatic to get some help maintaining. I deeply apologize for the lack of maintenance. I recently founded a company and have largely transitioned away from Node so my efforts have been limited as late.

How would you all suggest I proceed from here? Just grant access to a few people on the repo?

PS I will publish #395 tonight

@rschmukler

This comment has been minimized.

Copy link
Collaborator

rschmukler commented Mar 23, 2017

Hey all. I just got Node re-set up on my home computer. This means that I should be better equipped to handle maintenance issues around agenda.

That being said, I would still love help maintaining (and even further developing) this package!

If anyone wants to get involved, please feel free to post here or email me at ryan@slingingcode.com. I propose the following: People who want to maintain, please contact me and also start replying to issues / PRs with a LGTM etc. Like I said, I won't being reviewing too much but once we get a consensus going I will keep note of the interested parties who are helping along. From there, I (or you, the community) can pick a few members to get NPM publishing / GitHub write access so that maintenance can continue along at a more rapid speed and is no longer dependent on me as a gate keeper.

PS. Existing maintainers will be kept on (@loris, @nwkeeley and @droppedoncaprica) in case they also want to help contribute.

I'm very excited to get others involved in this, so please don't hesitate to join in!

@bonesoul

This comment has been minimized.

Copy link

bonesoul commented Mar 31, 2017

hope this package can get the love from community that it deserves

@droppedoncaprica

This comment has been minimized.

Copy link
Collaborator

droppedoncaprica commented May 2, 2017

I totally agree that this package needs a more active maintainers to keep this running. I've moved to a new job that uses a completely different back-end myself, so I've not been keeping up with this library's issues / pull requests as much as I have in the past.

If anyone needs help with maintenance, feel free to @ ping me and I'll do my best to take a look at it!

@OmgImAlexis

This comment has been minimized.

Copy link
Member

OmgImAlexis commented May 14, 2017

@rschmukler maybe look at moving this to an org so it's easier to handle others getting merge rights, etc?

Edit: Looks like agenda is free maybe contact Github about getting it moved to an org for you?

@simison

This comment has been minimized.

Copy link
Member

simison commented May 14, 2017

Edit: Looks like agenda is free maybe contact Github about getting it moved to an org for you?

It's possible to transfer the repo for an org from here (at "danger zone"):
https://github.com/rschmukler/agenda/settings

Just create a new org first:
https://github.com/account/organizations/new

Organisation would give a signal to others to work on this, as they won't feel like the project is "owned" by one individual as much.

@OmgImAlexis

This comment has been minimized.

Copy link
Member

OmgImAlexis commented May 14, 2017

@simison what I was suggesting is the username "agenda", it'd be good to have https://github.com/agenda/agenda

@dylanjha

This comment has been minimized.

Copy link

dylanjha commented Jun 14, 2017

@rschmukler thanks for all the work you have done on agenda. I second @OmgImAlexis @simison that I would be happy to help maintain

@OmgImAlexis

This comment has been minimized.

Copy link
Member

OmgImAlexis commented Jun 14, 2017

@rschmukler if you're okay with moving it to an org I'd be more than happy to start clearing out old issues as well as getting all the dev deps updated.

@michelem09

This comment has been minimized.

Copy link
Member

michelem09 commented Jun 14, 2017

I'm in too, if you need.

@jpiepkow

This comment has been minimized.

Copy link

jpiepkow commented Jun 14, 2017

Same I use this in a production application and have had to look into the code more then a couple times.

@simison

This comment has been minimized.

Copy link
Member

simison commented Jun 14, 2017

You all rock! 馃嵒 馃帀

@nwkeeley

This comment has been minimized.

Copy link
Member

nwkeeley commented Jun 14, 2017

Hi,

I am in a place to become more actively engaged with this module. I dropped offline for awhile to handle some family/work stuff but I am back and engaged.. I actually have this module running in production in 4 different applications soon to be 5 ..... so I am extremely vested in its success.

Really great to hear everyone interested in helping Ryan this is a fantastic module he's put together super excited to see it keep growing!

-Nate

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jun 14, 2017

I would also like to move Agendash into the new Org. 馃憤 or 馃憥?

@simison

This comment has been minimized.

Copy link
Member

simison commented Jun 14, 2017

@joeframbach is doing wonderful job with agendash, would you like to move that to new org as well, WDYT? I would probably get more attention like that.

Edit; right, that's what you just said, sorry for repeating. :-)

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jun 14, 2017

Yup, can you create the org and invite me in? I'm not 100% on the process Github has for transferring, or how npm publishing handles it. But I'm sure I can figure it out.

@simison

This comment has been minimized.

Copy link
Member

simison commented Jun 14, 2017

@joeframbach see my comments above: #414 (comment)

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jun 14, 2017

I've sent a request to a human at Github to see if "agenda" is inactive and if we can take the name.

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jun 14, 2017

Good news! I've created the Org https://github.com/agenda and will send invitations shortly. (I'm at work, it'll be over my lunch break so be patient)

@dylanjha

This comment has been minimized.

Copy link

dylanjha commented Jun 14, 2017

thanks @joeframbach!

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jun 14, 2017

@rschmukler I've created the @agenda org and sent invites to anyone above who offered to maintain Agenda. I've invited you as an Owner of the org. Could you transfer Agenda to the org, and I believe that will close this issue :)

@rschmukler

This comment has been minimized.

Copy link
Collaborator

rschmukler commented Jun 15, 2017

Hey all! It has been transferred. Thank you all for your efforts and your help. Closing this issue. Hoping that agenda can get the love it needs.

If you guys need publishing access on NPM, please email me (see my profile) your NPM username so that I can add you. Initially I'd like to keep publishers / release cutters to just a few people, but am happy to bring more on if you guys think otherwise.

PS. I use tj/git-extras for git-changelog and git-release commands which generate the changelog and tagging schema.

@rschmukler rschmukler closed this Jun 15, 2017

@dylanjha

This comment has been minimized.

Copy link

dylanjha commented Jun 16, 2017

Thanks @rschmukler !

@simison

This comment has been minimized.

Copy link
Member

simison commented Jun 20, 2017

@joeframbach I think a lot of people added as contributors still cannot close/edit/merge issues or PRs: I think after adding to people to organisation, you still need to add them to a team and then assign that team to repository.

@dylanjha @nwkeeley @jpiepkow @michelem09 @OmgImAlexis @gastonelhordoy Follow ups here; #441

FYI: I'm too busy myself to do coding for this but never too busy to try inspire others. ;-)

@michelem09

This comment has been minimized.

Copy link
Member

michelem09 commented Jun 20, 2017

I confirm I can't close/edit/merge issue.

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jun 20, 2017

I have created a @agenda/maintainers Team and assigned it Write access to agenda/agenda and agenda/agendash. I don't know if this grants rights to modify issues.

@simison

This comment has been minimized.

Copy link
Member

simison commented Jun 20, 2017

@joeframbach thanks, that worked.

@simison simison changed the title Maintainers needed? Maintainers needed Jun 20, 2017

@michelem09

This comment has been minimized.

Copy link
Member

michelem09 commented Jun 21, 2017

@joeframbach am I in? I still can't do much.

@OmgImAlexis

This comment has been minimized.

Copy link
Member

OmgImAlexis commented Jun 21, 2017

@joeframbach can't edit issues either. I'd like to go and sort open issues with tags so we can try and get it the backlog sorted.

@michelem09

This comment has been minimized.

Copy link
Member

michelem09 commented Jun 21, 2017

Yes the same as @OmgImAlexis I'd like to manage issues to try organise (and possibly close) them.

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jun 21, 2017

Ah, I see. Members of the "organization" are able to push code but can't close issues. Members of the "team" are able to close issues. Silly Github. I've added you both to the team.

@niftylettuce

This comment has been minimized.

Copy link
Member

niftylettuce commented Jul 21, 2017

@joeframbach @rschmukler I'd like to work more on Agenda and would love an invite to @agenda/maintainers. I've done quite a bit of work and have solid fundamental understanding of the codebase per my work in #464. I also was going to do a complete write from scratch of my own job scheduler, but after a battle of patience I decided it'd be best if I focused on contributing instead; helping us get where we need to be with this package. I publish and maintain quite a few other packages and would love to be a part of the Agenda organization so I can more readily contribute and feel welcome. Thanks! 鉂わ笍

@simison

This comment has been minimized.

Copy link
Member

simison commented Jul 21, 2017

@niftylettuce great! I've been inspired by your work on open source for a while already. Great to see you jumping in here, too! 鉂わ笍

Now that we're quite a few working together, I thought of writing a quick "how we work" checklist and code of conduct, please all @agenda/maintainers have a look and feel free to comment/modify!

Always show this to new maintainers so we can ensure common working methods and pace.

If you think it's over the top, feel free to try shorten it to be more concise.

@nwkeeley

This comment has been minimized.

Copy link
Member

nwkeeley commented Jul 21, 2017

@niftylettuce - I also have followed your work. I would be really excited to have you become a maintainer of this project I think you could bring a lot of value.

@joeframbach

This comment has been minimized.

Copy link
Member

joeframbach commented Jul 21, 2017

I have sent an invite to @niftylettuce as a maintainer.

@lushc

This comment has been minimized.

Copy link
Member

lushc commented Jul 21, 2017

@simison thanks for putting that together, it looks perfect to me.

@niftylettuce welcome!

@rschmukler

This comment has been minimized.

Copy link
Collaborator

rschmukler commented Aug 7, 2017

Hey all! Sorry on the delay, again. I've added @simison, @joeframbach, and @niftylettuce as package owners on NPM. I would also be happy to add @lushc and @OmgImAlexis but their NPM user names don't appear to be the same as their github's.

All other maintainers, feel free to add NPM owners freely.

Thanks all!

@niftylettuce

This comment has been minimized.

Copy link
Member

niftylettuce commented Aug 7, 2017

Thank you @rschmukler 馃帀

@niftylettuce

This comment has been minimized.

Copy link
Member

niftylettuce commented Aug 25, 2017

@rschmukler @joeframbach can you please add @OmgImAlexis and I as owners of the org? I've also sent you invites on Slack (once you accept I will make you team owner like the rest of us). #516

Also we need to ensure and enforce that all owners / collaborators have 2FA enabled per #516

We are going to get http://agendajs.com up with documentation per #517 as well.

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