Upload released version of TracSpamFilter to PyPI

[Ryan J Ollos]

The version of ​TracSpamFilter on PyPI is very out of date (0.2dev-r4489). Also, PyPI has deprecated support for linking from PyPI to another site that hosts the downloads, and the behavior will stop working soon.

I'll contact the Package Index Owner and see if I can get permission to upload a new release.

[Ryan J Ollos]

Previously mentioned in comment:3:ticket:12038.

[Ryan J Ollos]

Replying to rjollos:

I'll contact the Package Index Owner and see if I can get permission to upload a new release.

I sent an email to mgood, and will follow-up if I don't hear from him within a few days.

[Ryan J Ollos]

Still haven't heard anything back from mgood. I will investigate if it's possible to take over an unmaintained package on PyPI when the maintainer is unreachable.

[Simon Fondrie-Teitler]

Hey Ryan,

Were you able to get anywhere with contacting the maintainer or PyPi about taking over the package?

[Ryan J Ollos]

Replying to Simon Fondrie-Teitler:

Hey Ryan,

Were you able to get anywhere with contacting the maintainer or PyPi about taking over the package?

I haven't received any response from the PyPI maintainer.

[Ryan J Ollos]

It would be nice to have the plugin on PyPI so that it has more visibility and can be easily installed. However, the plugin's absence for PyPI shouldn't be a burden to anyone. Rather than pip install tracspamfilter, you can just pip install svn+http://svn.edgewall.com/repos/trac/plugins/1.0/spam-filter.

The other way to resolve this issue would be to move SpamFilter to tracopt, which I tend to prefer. However that needs to be looked at closely, considering issues such as licensing of the TracSpamFilter's dependencies. I plan to eventually propose the change to the trac-dev mailing list when I have time to put together a thoughtful proposal.

[Ryan J Ollos]

Replying to Ryan J Ollos:

Replying to Simon Fondrie-Teitler:

Hey Ryan,

Were you able to get anywhere with contacting the maintainer or PyPi about taking over the package?

I haven't received any response from the PyPI maintainer.

To fully reply to your question … From the requests I see on the ​sourceforge issue tracker for PyPI, it appears they don't hand over maintainership of a page on PyPI without a response from the author. It's very unfortunate if that's the case, because some packages will be doomed to remain stale on PyPI forever. We should look into that more closely.

[Ryan J Ollos]

Coincidentally, I just saw a ​blog post about the PyPI replacement, named warehouse. ​Here is the Trac page on Warehouse. Looks nice.

[Ryan J Ollos]

Replying to Ryan J Ollos:

The other way to resolve this issue would be to move SpamFilter to tracopt, which I tend to prefer. However that needs to be looked at closely, considering issues such as licensing of the TracSpamFilter's dependencies. I plan to eventually propose the change to the trac-dev mailing list when I have time to put together a thoughtful proposal.

Proposed in #12398. I guess we aren't going to get the attention of mgood, so closing this ticket.

[Ryan J Ollos]

Replying to Ryan J Ollos:

Replying to Ryan J Ollos:

Replying to Simon Fondrie-Teitler:

Hey Ryan,

Were you able to get anywhere with contacting the maintainer or PyPi about taking over the package?

I haven't received any response from the PyPI maintainer.

To fully reply to your question … From the requests I see on the ​sourceforge issue tracker for PyPI, it appears they don't hand over maintainership of a page on PyPI without a response from the author. It's very unfortunate if that's the case, because some packages will be doomed to remain stale on PyPI forever. We should look into that more closely.

​PPE-541 proposes a process by which we might be able to reclaim TracSpamFilter on PyPI.