Who are maintainers of Hoopl? about hoopl HOT 13 CLOSED

I've got interested in contributing to Hoopl mostly last year, so I didn't take part in any discussions about maintainership before. I wouldn't mind being something like a secondary maintainer/contributor (the caveat is that the amount of time I can spend on things like Hoopl can vary quite a bit, e.g., I didn't have time to do anything with Hoopl in months and only now trying to pick it up again).

from hoopl.

This should be discuss in a separate email.

from hoopl.

Not sure why this is not a good place for a discussion, but please remember to update the .cabal file once the matter has been settled. Actually, wouldn't it be better to keep this ticket open as a reminder?

from hoopl.

It's not an issue of the library per se, and not all maintainers look at
the github notifications.

On 1/18/2016 10:59 PM, Jan Stolarek wrote:

Not sure why this is not a good place for a discussion, but please remember to update the .cabal file once the matter has been settled. Actually, wouldn't it be better to keep this ticket open as a reminder?

---

Reply to this email directly or view it on GitHub:
#26 (comment)

from hoopl.

not all maintainers look at the github notifications.

Then how do they maintain the library if they don't get notifications about reported bugs? Remember that for some time now hoopl is officially developed on github and this issue tracker is the official one. And I think it actually is issue of the library, as information about maintainers is given on hackage. Ning, you seem to be the most (only?) active maintainer, yet you are listed as the last person in the cabal file entry. If the other two maintainers are not active then the cabal file entry is really misleading.

from hoopl.

This is an administrative issue. However, I agreed with Jan on this: the maintainer's job is to serve the community and the discussion about maintainer-ship change should be a public record, so I reopened it.

I'm glad to see Michal is working on improving the performance of hoopl. It will only make hoopl more useful. I have no objections to adding Michal as another maintainer.

If anyone has any comments, please chime in, otherwise I close this issue this Sunday.

from hoopl.

I think that Norman and Andreas are now out of the loop. Ning would you like to write to them (do copy me) to ask if they want to continue to be maintainers? I suspect they will (gratefully) say no.

from hoopl.

Norman still cares about hoopl albeit he does not merge pull requests.
I'm happy to have him around.

I haven't heard anything from Andreas recently. I will check if he
still wants to be a maintainer.

On 1/27/2016 1:18 AM, simonpj wrote:

I think that Norman and Andreas are now out of the loop. Ning would you like to write to them (do copy me) to ask if they want to continue to be maintainers? I suspect they will (gratefully) say no.

---

Reply to this email directly or view it on GitHub:
#26 (comment)

from hoopl.

Hi Norman and Andreas,

Michal Terepeta (Jan Stolarek's student) volunteers to maintain
hoopl. I'm Ok with it. What are you thoughts?

Andreas, are you still interested in being a maintainer of hoopl?

Ning

On 1/27/2016 1:18 AM, simonpj wrote:

I think that Norman and Andreas are now out of the loop. Ning would you like to write to them (do copy me) to ask if they want to continue to be maintainers? I suspect they will (gratefully) say no.

---

Reply to this email directly or view it on GitHub:
#26 (comment)

from hoopl.

@mlite @jstolarek Just to clarify - I'm not Jan's student.

from hoopl.

I'm still very interested in Hoopl. I'm actively using it in a compiler project that I'm working on. So I'd really like for hoopl to be well-maintained and improve over time.

Unfortunately in the last year I've had almost no time to contribute to hoopl. I do try to catch up on the conversations, and I really appreciate everyone's recent efforts to clean things up. I hope I'll have a bit more time this year to help out.

Given that, it seems that it might be more appropriate if I'm considered a contributor rather than a maintainer. That way I can help when possible, but I won't block progress by other folks.

-Andi

from hoopl.

It's great you also use hoopl. Let's just add Michal to the maintainers.

On 1/30/2016 11:00 AM, Andreas Voellmy wrote:

I'm still very interested in Hoopl. I'm actively using it in a compiler project that I'm working on. So I'd really like for hoopl to be well-maintained and improve over time.

Unfortunately in the last year I've had almost no time to contribute to hoopl. I do try to catch up on the conversations, and I really appreciate everyone's recent efforts to clean things up. I hope I'll have a bit more time this year to help out.

Given that, it seems that it might be more appropriate if I'm considered a contributor rather than a maintainer. That way I can help when possible, but I won't block progress by other folks.

-Andi

---

Reply to this email directly or view it on GitHub:
#26 (comment)

from hoopl.

I updated the .cabal file, since the issue was marked as closed but the fix has not been published. @michalt, you need to be given write permission to the repo. I don't have sufficient privileges to do this. @mlite, are you able to give Michal write permissions? I suspect that you might be in the same situation as I, in which case we would need @hvr's help.

from hoopl.