[wp-hackers] Discontinuing a plugin on WordPress.org

[Nikola Nikolov]

I'm aware that I can download the previous versions of the plugin(well most
users are probably not though), but the thing is that you shouldn't have to
do that.

Otto - I guess it's probably more headaches than it's worth, but what about
reverting the last commit(or just moving the code back to /trunk or the
stable tag) and changing the readme to state that the plugin is no longer
going to be supported.
You then revoke access to the plugin's repository(so that the authors can
no longer do the same thing).

Ultimately I think that if there's a list of plugins that are no longer
supported by their authors and are put up "for adoption" by other
developers everyone could benefit(not sure if that's fair/possible?). Yes,
you can just fork the plugin and upload it as a new one, but the users of
the old plugin probably won't be aware that there's a new version of the
plugin.

Anyway, just some thoughts.


On Fri, Aug 8, 2014 at 3:23 PM, Otto <otto at ottodestruct.com> wrote:

> Yes, that is a terrible way to discontinue a plugin, but people do it
> anyway. When we find them, we close them so that listing is removed.
>
>
> -Otto
>
>
> On Fri, Aug 8, 2014 at 6:36 AM, Nikola Nikolov <nikolov.tmw at gmail.com>
> wrote:
>
> > Hi everyone,
> >
> > I was working with a client that was using the Fundify WordPress theme,
> > which was powered by a combination of Fundify Crowdfunding(
> > https://wordpress.org/plugins/appthemer-crowdfunding/ ) and EDD.
> >
> > I wanted to download the source of the plugin to my computer to easily
> > navigate through the codebase. On the plugin page they've added "(Moved)"
> > to the name of the plugin.
> > Once I extracted the archive, there was nothing but an empty .php file
> and
> > a readme.txt file.
> >
> > My question in this case is - is this allowed and isn't that a terrible
> way
> > of discontinuing a plugin? What if someone updates the plugin and their
> > site stops working? Or someone installs the plugin and nothing happens...
> >
> > Is there anything the WordPress.org plugins team can do about it?
> >
> > Best regards,
> > Nikola
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>