You can add me.

@tarsius Hey mate, I currently maintain Node-Fetch and would be happy to help. You can count me in.

Hey @dickmao and @NotMoni, thanks for offering your help!

Could you please say a few words about your experience maintaining elisp packages and also what kind of help you can and intend to offer here.

I intend to review all commits for a while at least. Past experience has shown that I might have to intervene occasionally but I'll try hard to stay out of your way.

Hey, @tarsius I am a nodeJS dev, but i can review basic pr and common issues.

@NotMoni I was really hoping for an experienced elisp developer but issue triage is also useful.

You already have the necessary permissions, feel free to begin work.

I had a quick look and feel that many old issues can be closed. It's probably best if you provide a one sentence for why you close an issue, except in extreme cases such as #481.

I sent emails to the address listed on your github profile, and I suspect they went to spam.

Could you re-extend the Collaborator invite? The first one seems to have expired.

Thanks. I generally work best with full Admin access, however.

I sent emails to the address listed on your github profile, and I suspect they went to spam.

I got your messages but I did not fully understand your first message and was a bit busy at the time so I put of replying. I understood what you said (I believe) but I was confused as to whether that meant that you did not want help maintain auto-complete after all. You had also let the invitation to this repo run out by then so I assumed that that was what it meant.

You talked about the value you see in auto-complete and how it relates to company-mode. This is of interest to other people as well, since they might want to know how the maintainers feel about the package. I think you should post that or something similar here.

Thanks. I generally work best with full Admin access, however.

I would like to wait with that for a while and review all changes. In the past I have given more far reaching access right away and that did not always work out so well.

You are not closing every issue right now, are you?

You are not closing every issue right now, are you?

No, some cling to relevancy, but just barely.

You should have discussed this with me first. I would have asked you to use a less aggressive (close fewer issues), more careful (spend more time investigating each issue, twenty seconds is not enough), and more explicit (above I already asked for a short explanation in most cases) approach.

I agree. Several issues I was following were closed without explanation, or simply because "I don't plan to work on this" (but why not just leave them open in case someone else does?).

I'll reopen the issues.

No, it's okay.

I would probably have closed the majority of these issues myself but I would have provided a short justification in more cases. Closing many issues wasn't necessarily wrong considering that past maintainers have done a very bad job closing resolved issues and issues that are certain not to lead anywhere.

A few of these issues shouldn't have been closed, but now that they are closed we can leave them closed. Reopening issues that should remain closed also wouldn't be desirable.

If someone feels that a particular issues should be reopened, then they just have to ask.

@dickmao I just told you to NOT reopen the issues.

Very sorry! I didn't get your message in time!

Well, I guess we're in no worse a state than we were four hours ago.

Very sorry! I didn't get your message in time!

This is now the second time that you just acted without giving someone else a few minutes to react first. You might want to avoid that in the future.

Well, I guess we're in no worse a state than we were four hours ago.

I disagree. This is worse than a few hours ago. Going forward I will not only hesitate to give someone write access but even just triage rights.

Well, I think this is goodby. This and #510 does not look like this project is going to get any useful contributions from you. I feel a bit bad saying it like this but I don't want to waste any time on this either.

@dickmao Bro chilll

@tarsius Can I maintain popup.el? Since my config and some of my packages are rely on this package, I would like to maintain this package to just in case it doesn't break in the future and also keep the package as stable as possible! Thanks! :)

I've invited you to the organization. Once you have accepted that I can assign you to the repository.

Joined! Thanks for the invite! :)

I may have time for this package now! I am not too confident to maintain this package since the code base is quite complicated and not modular. But I would still like to give this package a try, and maybe start reading some code base and do basic review PRs; answering issue, etc.

@tarsius Can you assign me to this repo? Thanks!

@tarsius Ping! You there? :)

Slightly busy.

I've given you access now.

Thanks! Sorry for pinging you while you are busy!

Naaa, that's okay.

@NotMoni are you actually doing any triaging? Asking because you have the rights to do so.