Package Maintenance

[mynameismon]

As one can infer from the history, this package has not been updated since 2016. In the meantime, some great community forks have popper up, the more prominent of them being:

• https://github.com/pneff/whoarder
• https://github.com/karlicoss/whoarder

Would it be possible to merge all those changes to create a new version of the package that will hopefully be more up to date?

[ronjouch]

Hi @mynameismon , author here. Indeed, I'm no longer maintaining or using whoarder. See my answer to #1 (comment) . As you'll see there, I'm willing to merge things and cut a new release, but I don't want to be the one spelunking for changes to bring back from forks.

→ If you have the time, can you do the work of sorting out what should be brought back from forks, get in touch with fork authors, and ask them to publish PRs here?

Thanks for your interest.

[mynameismon]

I wouldn't be able to do everything, can you perhaps take a part of that up? Maybe contacting people for PRs, and then I could take it forward from there.

[ronjouch]

I wouldn't be able to do everything, can you perhaps take a part of that up? Maybe contacting people for PRs, and then I could take it forward from there.

@mynameismon contacting fork authors for PRs would be awesome. Thanks 🙂.

[mynameismon]

(p.s. if possible, can the parser be split from the HTML generator? The parser is fantastically good and I want to use it one of my side projects)

[ronjouch]

(p.s. if possible, can the parser be split from the HTML generator? The parser is fantastically good and I want to use it one of my side projects)

If "splitting the parser" means making a new pip package, no. Just copy-paste it in your side project? Or extract it into a new project that you maintain and publish to pip.

[mynameismon]

Not a separate project, but a separate repository? This way I would be able to include it as a submodule.

[mynameismon]

Hi @ronjouch, any updates regarding this?

Would it also be possible to review my PR (#2)

[ronjouch]

Hi @ronjouch, any updates regarding this?

I did reply to you about the parser split. Copy / fork it and be the maintainer of it.

Would it also be possible to review my PR (#2)

Yes, will come to it, haven't forgotten about it.

[mynameismon]

I did reply to you about the parser split. Copy / fork it and be the maintainer of it.

Apologies. I meant this: #3 (comment)

[ronjouch]

I did reply to you about the parser split. Copy / fork it and be the maintainer of it.

Apologies. I meant this: #3 (comment)

@mynameismon ooooooooh. I misread your sentence, I read it as "I, Monish, will get in touch with forks, then once PRs are submitted, you Ronan can take it forward from here (reviewing and merging)". My mistake, sorry. But so, to sum up: I will only do minimal work on this library.

If you push me PRs or succeed at convincing fork authors to submit their patches, I will review them and merge them when they { make sense, are tested }. But I will not take time to haul people and ask for patches.