[wp-hackers] Switching from SVN

[Eric Mann]

It might weed out those plug-ins that are obsolete and abandoned by the
original developers.  But some plug-ins aren't being "actively" developed
because they still work and don't need any new features.  Forcing the devs
to resubmit a plug-in that hasn't changed in a year or two would be a major
PITA for some.

On the other hand, maybe culling inactive plug-ins from the repository by
forcing a massive resubmit would be a good thing.  We'd have a better idea
of how many plug-ins are available based on how many are resubmitted.  But
I'd still want to keep the old SVN repo available *somewhere* for archive
purposes ...

On Thu, Dec 9, 2010 at 9:20 AM, William Davis <will.davis at gmail.com> wrote:

>
>> Just wanted to add that there's no reason the plugins would have to be
>> done at the same time as WordPress itself. I'm sure that'll be a huge
>> undertaking.
>>
>> Even just offering an official git mirror of the main repository would
>> be a good place to start, so that people don't have to maintain their
>> own. Then eventually the git mirror can become the official repository,
>> or create a new one, whichever.
>>
>> We couldn't find a git mirror that was up-to-date _and_ had tags so we
>> had to make our own: https://github.com/dxw/wordpress
>>
>
>
> I'm sure this won't be popular, but what if plugin authors had to resubmit
> their plugins? It would probably help weed out a ton of old plugins that are
> no longer relevant.
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>