Delete Plugin on SVN please

[Bueltge]

I hope this is the right adress here.
Please, delete the svn-folder for the plugin
http://wordpress.org/extend/plugins/phpmyvisites/
I will not supportet this and now its give newer and better solutions.

Thanks and best regards
Frank

http://bueltge.de : frank@...
http://wpengineer.com : frank@...
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Dion Hulse (dd32)]

The correct way to handle this would be to mearly post an update to the  
readme along the lines of "Please note, Support for this plugin ended  
xx-xx-xxxx. Development has ceased, If someone would like to take over,  
Contact xxxxxx"..

Removing the plugin all together isnt exactly in the open source model,  
Its already out here, So just let it rot, You dont hide/remove all traces  
of non-supported items..

On Wed, 04 Nov 2009 20:53:35 +1100, Frank Bueltge <frank@...> wrote:

> I hope this is the right adress here.
> Please, delete the svn-folder for the plugin
> http://wordpress.org/extend/plugins/phpmyvisites/
> I will not supportet this and now its give newer and better solutions.
>
> Thanks and best regards
> Frank
>
> http://bueltge.de : frank@...
> http://wpengineer.com : frank@...
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Bueltge]

Yes, i have change the readme and copy the files in the folder tags
for other people to use this.
I think it is very hard for user to find a plugin for an keyword. I
will not develop this plugin for next time.



On Wed, Nov 4, 2009 at 11:19 AM, Dion Hulse (dd32) <wordpress@...> wrote:

> The correct way to handle this would be to mearly post an update to the
> readme along the lines of "Please note, Support for this plugin ended
> xx-xx-xxxx. Development has ceased, If someone would like to take over,
> Contact xxxxxx"..
>
> Removing the plugin all together isnt exactly in the open source model, Its
> already out here, So just let it rot, You dont hide/remove all traces of
> non-supported items..
>
> On Wed, 04 Nov 2009 20:53:35 +1100, Frank Bueltge <frank@...> wrote:
>
>> I hope this is the right adress here.
>> Please, delete the svn-folder for the plugin
>> http://wordpress.org/extend/plugins/phpmyvisites/
>> I will not supportet this and now its give newer and better solutions.
>>
>> Thanks and best regards
>> Frank
>>
>> http://bueltge.de : frank@...
>> http://wpengineer.com : frank@...
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers@...
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Ken Newman-3]

On 11/4/2009 5:56 AM, Frank Bueltge wrote:
> Yes, i have change the readme and copy the files in the folder tags
> for other people to use this.
> I think it is very hard for user to find a plugin for an keyword. I
> will not develop this plugin for next time.
>
>    
I think this brings up a good point about the state of the repositories.
Deleting

"...the plugin all together isnt exactly in the open source model"

but I do think that all the abandoned and junk plugins are reducing the
usability of the repositories. Perhaps we can clean it up with a new
tag/filtering system? For example, anything explicitly abandoned can be
marked and filtered out of most searches, but available for developers
who may be interested in resurrection a particular project.

Also, we could filter out plugins and themes that are out-of-date, say
compatible only up to 2.7 or whatever. The plus is it would encourage
plugin devs to keep up with the latest version of WP; similarly, the
minus is it would encourage other devs to just update the tag and not
bother actually testing it, therefor by-passing the filter. I believe
there are less of the latter than the former, but some consideration is
probably due there.

Tangently related is security review of submitted plugins. Should there
be some minimal cursory inspection of plugins to prevent malicious code
being added to the repos? I don't know how the submission process works,
so sorry if this is already done by someone, but if not, should someone
be doing this? I certainly don't have enough info on this subject but
would like to know more about its implications/considerations.

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[mark waterous]

> Perhaps we can clean it up with a new
> tag/filtering system? For example, anything explicitly abandoned can be
> marked and filtered out of most searches, but available for developers
> who may be interested in resurrection a particular project.

+1 for that. There's a lot of hidden gems in there, but at present tracking
down specifics can be a time consuming process. Placing some extra
responsibility on the developer to maintain their plugin or mark it
abandoned would be a good start - perhaps adding an advanced search
capability would help the end user though? Just a few options where you
could filter out plugins by their compatibility, last date updated, etc.

Plugins that haven't been updated since 2007 probably shouldn't be coming
back very high on the search results.
-Mark

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Glenn Ansley]

I'd love to be able to flag a couple of mine for deletion or as
'inactive' or 'no longer supported'... like one that was misspelled
and never had any files committed to it.

Glenn Ansley
http://twitter.com/glennansley
http://fullthrottledevelopment.com

On Wed, Nov 4, 2009 at 4:01 PM, mark waterous <mark@...> wrote:

>> Perhaps we can clean it up with a new
>> tag/filtering system? For example, anything explicitly abandoned can be
>> marked and filtered out of most searches, but available for developers
>> who may be interested in resurrection a particular project.
>
> +1 for that. There's a lot of hidden gems in there, but at present tracking
> down specifics can be a time consuming process. Placing some extra
> responsibility on the developer to maintain their plugin or mark it
> abandoned would be a good start - perhaps adding an advanced search
> capability would help the end user though? Just a few options where you
> could filter out plugins by their compatibility, last date updated, etc.
>
> Plugins that haven't been updated since 2007 probably shouldn't be coming
> back very high on the search results.
> -Mark
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Peter Westwood]

On 4 Nov 2009, at 21:01, mark waterous wrote:

>> Perhaps we can clean it up with a new
>> tag/filtering system? For example, anything explicitly abandoned  
>> can be
>> marked and filtered out of most searches, but available for  
>> developers
>> who may be interested in resurrection a particular project.
>
> +1 for that. There's a lot of hidden gems in there, but at present  
> tracking
> down specifics can be a time consuming process. Placing some extra
> responsibility on the developer to maintain their plugin or mark it
> abandoned would be a good start - perhaps adding an advanced search
> capability would help the end user though? Just a few options where  
> you
> could filter out plugins by their compatibility, last date updated,  
> etc.
>

If you want a plugin removed completely try emailing the support email  
address plugins@...

> Plugins that haven't been updated since 2007 probably shouldn't be  
> coming
> back very high on the search results.
>

Just because a plugin has not been updated since 2007 does not  
necessarily mean that plugin doesn't work.

In fact it is quite possible if the plugin was well coded and used the  
apis available correctly that it still works.

westi
--
Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Ken Newman-3]

On 11/4/2009 4:10 PM, Peter Westwood wrote:
> Just because a plugin has not been updated since 2007 does not
> necessarily mean that plugin doesn't work.
>
> In fact it is quite possible if the plugin was well coded and used the
> apis available correctly that it still works.
>
> westi
That's where I'm hoping that the new compatibility feature could be
used. But I'd still like to get the ones known to not work since 2007
off my search lists ;)
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[chrisbliss18]

This brings up an issue that I have with the plugin repo. I'm not proud
of this, but it has happened a number of times.

I start a plugin project based on a good idea. During one of my moments
of reflecting upon design, implementation, etc, I decide to figure out
the name of the project. I find a good one that isn't taken, and I
register it.

I then invariably get something that swamps me: a big project at work,
some personal stuff is happening that takes away my time, etc. Then when
I'm able to come back to the project, days have gone by and I realize
something. Since the repo system lists new projects based upon the day
that the repo was approved and not based upon the first version being
submitted, my great new plugin idea will be quickly lost due to the lack
of attention on the new plugin list. In other words, if I wait 10 days
from repo approval to push up the first version, then people will have
to go 10 days back in the new plugin list to find my plugin. This
realization has at times caused me to lose interest in a project.

Of course, I could just wait to register a name until the project is
finished, but this has a few other problems: 1) The name may be taken by
the time I finish the project causing me to go and rename everything,
including any promotional/support posts I may have created. 2) I now
have to wait some random number of days until my repo gets approved
before I can push out the version. 3) If I'm busy again when my repo is
approved and don't end up getting back to it in a couple or more days,
I'm back to the same problem I started with.

If there were a way that I could delete repos that I didn't end up
using, I could release those names back into the available pool.

Here's an idea. Plugin repositories that have not had an initial version
commit made to them for a period of time (such as 10 days, a month, six
months, ...) should be automatically removed and freed. This would
prevent dead projects that never got started and name squatters from
removing good names from the pool for no benefit to the community.

Chris Jean
http://gaarai.com/
@chrisjean



Glenn Ansley wrote:
> I'd love to be able to flag a couple of mine for deletion or as
> 'inactive' or 'no longer supported'... like one that was misspelled
> and never had any files committed to it.
>
> Glenn Ansley
> http://twitter.com/glennansley
> http://fullthrottledevelopment.com
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[mark waterous]

> Just because a plugin has not been updated since 2007 does not
> necessarily mean that plugin doesn't work.
>
> In fact it is quite possible if the plugin was well coded and used the
> apis available correctly that it still works.

Agreed, but how often is this the case vs not?

Chances are much higher that a plugin which has not been updated for a few
years will either not take advantage of improvements to Wordpress, or
function properly. Though there are a few, so maybe once again this could
just be added a search filter. "Sort by last updated" would not only allow
people to look for more recent options should they like, but would allow
developers and die-hards the option to flip the results and see what was
done back in the day.
-Mark

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Stephen Rider]

On Nov 4, 2009, at 3:56 PM, mark waterous wrote:

>> Just because a plugin has not been updated since 2007 does not
>> necessarily mean that plugin doesn't work.
>
> Agreed, but how often is this the case vs not?

The question is moot.  The point is: old != inactive.  The system  
should not make assumptions based on date.

I know I use at least one plugin that is quite old, but works fine.  
(A very straightforward plugin, but definitely useful.)

Stephen
_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Eric Marden-2]

On Nov 4, 2009, at 4:19 PM, Chris Jean wrote:

>  then invariably get something that swamps me: a big project at  
> work, some personal stuff is happening that takes away my time, etc.  
> Then when I'm able to come back to the project, days have gone by  
> and I realize something. Since the repo system lists new projects  
> based upon the day that the repo was approved and not based upon the  
> first version being submitted, my great new plugin idea will be  
> quickly lost due to the lack of attention on the new plugin list. In  
> other words, if I wait 10 days from repo approval to push up the  
> first version, then people will have to go 10 days back in the new  
> plugin list to find my plugin. This realization has at times caused  
> me to lose interest in a project.

You need a better strategy. You can announce new plugins (and updated  
plugins) on Web Log Tools collection, which will get your plugin a lot  
more attention then I've ever got on the Plugin DB, even when I  
committed v1 as soon as I got access.




- Eric Marden
__________________________________
http://xentek.net/code/wordpress/





_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Lew Ayotte - Full Throttle Development]

I guess this is semi-related to cleanup...

We've had a developer who tried to submit a plugin on six different
occassions but it never seemed to work. I tried on his behalf (with my
account info) and it worked right off but it gave the plugin name a "-7"
appended as in (http://wordpress.org/extend/plugins/ft-facepress-7/)

I imagine 1 - 6 are in some DB somewhere and if someone were to create
another named "ft-facepress" it would be ft-facepress-8... I guess.

Lew Ayotte
Full Throttle Development, LLC
706.363.0688
478.246.4627
lew@...
http://fullthrottledevelopment.com
http://twitter.com/full_throttle
http://twitter.com/lewayotte


On Thu, Nov 5, 2009 at 11:44 AM, Eric Marden <wp@...> wrote:

> On Nov 4, 2009, at 4:19 PM, Chris Jean wrote:
>
>   then invariably get something that swamps me: a big project at work, some
>> personal stuff is happening that takes away my time, etc. Then when I'm able
>> to come back to the project, days have gone by and I realize something.
>> Since the repo system lists new projects based upon the day that the repo
>> was approved and not based upon the first version being submitted, my great
>> new plugin idea will be quickly lost due to the lack of attention on the new
>> plugin list. In other words, if I wait 10 days from repo approval to push up
>> the first version, then people will have to go 10 days back in the new
>> plugin list to find my plugin. This realization has at times caused me to
>> lose interest in a project.
>>
>
>
> You need a better strategy. You can announce new plugins (and updated
> plugins) on Web Log Tools collection, which will get your plugin a lot more
> attention then I've ever got on the Plugin DB, even when I committed v1 as
> soon as I got access.
>
>
>
>
>
> - Eric Marden
> __________________________________
> http://xentek.net/code/wordpress/
>
>
>
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers@...
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>

_______________________________________________
wp-hackers mailing list
wp-hackers@...
http://lists.automattic.com/mailman/listinfo/wp-hackers