Straight.el: Interest in being added as collaborator?

Created on 21 Sep 2020  路  4Comments  路  Source: raxod502/straight.el

Hello @progfolio,

In the last few weeks you've done a lot of excellent work on straight.el -- in fact, more than I have in a while. Apologies again, by the way, for the inconvenient two-week delay in response after you submitted all of your pull requests. Would you be interested in being added as a collaborator / co-maintainer? This role would not include any commitment in particular to work on the project, and I would be happy to continue:

  • advising on good approaches to new features, providing context on design decisions, and doing code review on PRs
  • handling routine tasks such as cutting pseudo-stable snapshots from develop to master, tagging issues, and being "on call" for fixing critical bugs

... but with you as a collaborator, you could feel free to do those things as well, as much or as little as you would like. You would also have the freedom to make fixes, enhancements, or other changes to straight.el, and would only need to consult me if you wanted advice or review. Otherwise, I would trust your judgement.

Let me know what you think!

github meta

Most helpful comment

Fantastic, I've added you. I look forward to continuing to work together!

All 4 comments

In the last few weeks you've done a lot of excellent work on straight.el

Thank you for the kind words! You've done an excellent job with straight and that's a large part of why I see value in contributing to it.

Apologies again, by the way, for the inconvenient two-week delay in response after you submitted all of your pull requests.

Not a problem at all. I understand there are only so many hours in a day.

Would you be interested in being added as a collaborator / co-maintainer?

Sounds good to me! I'll do my best to help when I can. I'm still getting a feel for the code base, so I'll definitely take you up on the advice and reviews. I can lend a hand reviewing other contributors' issues as well.

Fantastic, I've added you. I look forward to continuing to work together!

By the way, in case you are wondering about the waiting on response label: I have a service that automatically looks across all of my repositories and closes anything with waiting on response that has had no activity in three months. This removes the manual work associated with closing abandoned pull requests or issues where the reporter failed to follow up with necessary details to investigate. The service works irrespective of who applies the label, so feel free to use this system if you wish.

I have a horrifying userscript hack, by the way, to establish keyboard shortcuts for adding and removing this label, because I get tired of doing it all the time :P

FYI -- I've just updated the master branch, which I typically do every three months or so along with making releases on my other projects. This isn't as often as I'd like as a user, but doing maintenance takes a bunch of time so I try to strike a balance. Typically what I do is include all the commits from more than a month ago, plus backports of specific commits that seem like safe bugfixes from more recently than a month ago.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

progfolio picture progfolio  路  3Comments

eflanigan00 picture eflanigan00  路  4Comments

yqrashawn picture yqrashawn  路  3Comments

agsdot picture agsdot  路  4Comments

rsbowman picture rsbowman  路  3Comments