Textpattern CMS support forum

You are not logged in. Register | Login | Help

#11 2016-07-09 13:08:24

Aeyoun
Member
From: NO
Registered: 2013-06-30
Posts: 15
Website

Re: Update notifications for plugins

Plugins should be required to include `License: <url>` in their meta data. Should be enough, though I think it’s technically required to declare the copyright holder too (name of person or organization, traditionally along with the year). Though this varies by jurisdiction and license.

This should cover everything. Both field can have comma separated values (dual-licensing or multiple authors).

License: <url>,

Copyright: <year> <author>,

Last edited by Aeyoun (2016-07-09 13:09:26)

Offline

#12 2016-07-09 13:12:01

Aeyoun
Member
From: NO
Registered: 2013-06-30
Posts: 15
Website

Re: Update notifications for plugins

Anyway, for auto-update purposes, a third field: `Update-URL: <url>` could be periodically cheeked. URL should contain a text/plain with: <plugin-name>;<version-number>;<download-url>. Textpattern could check these periodically and either download URL automatically or offer a download button. Very simple to implement and deploy on any webserver if it’s just a text-file with info about the current version. No giant infrastructure required and easy to get plugin authors to adopt.

Last edited by Aeyoun (2016-07-09 13:13:12)

Offline

#13 2016-07-09 16:46:28

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,631
Website

Re: Update notifications for plugins

Aeyoun wrote #300252:

for auto-update purposes, a third field: `Update-URL: <url>` could be periodically cheeked. URL should contain a text/plain with: <plugin-name>;<version-number>;<download-url>.

Interesting. Not sure how this best works for people on github and bitbucket, etc. Presumably this means every project will have to have a file available from, for example, github’s ‘raw’ view that we can directly access. Assuming we’re effectively allowed to “hotlink” to such locations. I think it’d be ok. I’d rather people not have to keep it up-to-date by hand though. This info ought to be generated and served automatically if possible. The fewer obstacles we can put in the way, the more likely it is to be adopted.

Thanks for the license insight. I’ll see if we can include that. Not 4.6, but a later version, probably.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#14 2016-07-09 18:38:03

Aeyoun
Member
From: NO
Registered: 2013-06-30
Posts: 15
Website

Re: Update notifications for plugins

Bloke wrote #300258:

Interesting. Not sure how this best works for people on github and bitbucket, etc. Presumably this means every project will have to have a file available from, for example, github’s ‘raw’ view that we can directly access. Assuming we’re effectively allowed to “hotlink” to such locations. I think it’d be ok. I’d rather people not have to keep it up-to-date by hand though. This info ought to be generated and served automatically if possible. The fewer obstacles we can put in the way, the more likely it is to be adopted.

Unless Textpattern wants to host plugins, and setup and maintain a large infrastructure around them; then this is the easiest for everyone. Should work for anyone with pretty much any hosting.

Other suggestions?

Last edited by Aeyoun (2016-07-09 18:38:15)

Offline

Board footer

Powered by FluxBB