AW: [wp-hackers] Update of non GPL-Plugins (was Plugin licenses)

[Xavier Borderie]

Promoting open-source is an excellent thing, and I am glad Extend
enforces it: it makes for a very diverse source of code to get
inspiration from.

I have other thoughts on not taking into account developers who prefer
to release their code another way, but do care enough about their user
that they'd like to update the plugin when needed, while still getting
users to update. Sure, they chose to do without auto-update or version
notification, but they just might want users to be aware that WP will
never let them know about a new version.

(not a plugin dev myself, btw)

-xb.

2008/10/24 Glenn Ansley <glenn at glennansley.com>:
> I don't think any such messages should be provided. Only hosting open source
> is a good decision because it encourages plugin developers to release their
> code if publicly they want to take advantage of the perks. If you're going
> to charge for a plugin or not release the code publicly, that's you're
> decision, but it's obviously not the model WordPress has decided to follow.
> Besides... there are other ways to update the user if you're the plugin
> developer. PodPress has been doing it long before 2.5 (not that anyone's
> seen an update in awhile)
>
> BTW, what about zend encoded plugins. I've seen a couple of those... <
> http://wordpress.org/extend/plugins/pics/>
>
> On Fri, Oct 24, 2008 at 9:10 AM, Xavier Borderie <xavier at borderie.net>wrote:
>
>> Agreed. Not being hosted on wp.org or GPL'd doesn't a bad plugin make.
>> I'd be strongly in favor of a minimal message indicating that WP
>> cannot notify user of the latest version of such plugin, and that it
>> needs to be updated manually.
>>
>> Stephen, care to link to your patch, for reference's sake ?
>>
>> -x.
>>
>>
>> 2008/10/24 Stephen Rider <wp-hackers at striderweb.com>:
>> > It's been discussed before.  I made a patch a while back that informed
>> users
>> > which plugins were _not_ checked for updates, so they would at least know
>> > that they have to check those manually.  It requires changes to the data
>> the
>> > update server returns though.
>> >
>> > My personal opinion is in agreement with you.  Making it look as though
>> > those plugins have no updates available is doing a disservice to
>> WordPress
>> > users, _and_ to those plugin authors who, for whatever reasons chose not
>> to
>> > host their plugins on the WP server.
>> >
>> > Stephen
>> >
>> >
>> > On Oct 24, 2008, at 5:36 AM, Philip Hetjens wrote:
>> >
>> >> How would anybody of you (or automattic) explain him, that wordpress
>> >> didn't
>> >> show the version warning of his bought plugin, because he bought it?
>> Come
>> >> on
>> >> guys...
>> >>
>> >> Once again: I don't want, that wp.org promotes theses plugins. I only
>> >> want,
>> >> that it helps updating, because the user will expect it.
>> >
>> > _______________________________________________
>> > wp-hackers mailing list
>> > wp-hackers at lists.automattic.com
>> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>> >
>>
>>
>>
>> --
>> Xavier Borderie
>> _______________________________________________
>> 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
>



-- 
Xavier Borderie