Hey guys,
since there are some rewrite rules which are just working with Apache, the preview site at plugins2.geany.org is broken because it is running on lighttpd and the rules are incompatible, unfortunately.
This actually was the site, a cronjob updated once per day. This doesn't make much sense, thus I enabled the push to live for the cronjob, finally. It took a lot if time to do so, I know. Sorry for that.
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
It would make sense to keep the informations of the README files consistent with the behavior of the plugins the released tarballs actually contain.
Feel free to suggest improvements and give feedback if you like this or not. :)
Regards, Dominic
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf:
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think.
Regards, Dominic
On Sat, 12 Feb 2011 00:04:32 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf:
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think.
I'm thinking about a post-commit hook which is deploying it after tagging (or something like this)
Cheers, Frank
On Sat, 12 Feb 2011 03:05:44 +0100, Frank wrote:
On Sat, 12 Feb 2011 00:04:32 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf:
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think.
Not sure whether every hour is really necessary. It's just that it probably takes some server resources...but to be honest I didn't know what the script does so I can't judge on that at this point.
But as you said in your first mail, plugin authors should keep the information in the READMEs consistent with the released version. This doesn't make much sense to me. The README in SVN should reflect the latest development changes. But I agree to have a version online at the website which fits the released version. So, IMO it's better to adjust your script to generate HTML from the tagged READMEs. And this is just necessary after a release, not every hour. What do you think?
Regards, Enrico
Am Samstag, den 12.02.2011, 12:24 +0100 schrieb Enrico Tröger:
On Sat, 12 Feb 2011 03:05:44 +0100, Frank wrote:
On Sat, 12 Feb 2011 00:04:32 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf:
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think.
Not sure whether every hour is really necessary. It's just that it probably takes some server resources...but to be honest I didn't know what the script does so I can't judge on that at this point.
But as you said in your first mail, plugin authors should keep the information in the READMEs consistent with the released version. This doesn't make much sense to me. The README in SVN should reflect the latest development changes. But I agree to have a version online at the website which fits the released version. So, IMO it's better to adjust your script to generate HTML from the tagged READMEs. And this is just necessary after a release, not every hour. What do you think?
I wouldn't generate the website from tagged releases, since they shouldn't be changed after the release from my point of view. Plugin developers may want to improve other things on their README files, in special when seeing something isn't displayed that optimal on the website, I think it is a more good idea to generate the website from trunk. But this would imply, the informations contained in the README files are consistent with the released tarballs.
Otherwise, if we generate the website from tagged releases, this would mean something would be fucked up until the next release, in the worst case.
few other thoughts to this topic:
* have an additional README.stable * and maybe generate an additional plugins.geany.org/svn/
Regards, Dominic
On Sat, 12 Feb 2011 13:59:27 +0100, Dominic wrote:
Am Samstag, den 12.02.2011, 12:24 +0100 schrieb Enrico Tröger:
On Sat, 12 Feb 2011 03:05:44 +0100, Frank wrote:
On Sat, 12 Feb 2011 00:04:32 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf:
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think.
Not sure whether every hour is really necessary. It's just that it probably takes some server resources...but to be honest I didn't know what the script does so I can't judge on that at this point.
But as you said in your first mail, plugin authors should keep the information in the READMEs consistent with the released version. This doesn't make much sense to me. The README in SVN should reflect the latest development changes. But I agree to have a version online at the website which fits the released version. So, IMO it's better to adjust your script to generate HTML from the tagged READMEs. And this is just necessary after a release, not every hour. What do you think?
I wouldn't generate the website from tagged releases, since they shouldn't be changed after the release from my point of view. Plugin developers may want to improve other things on their README files, in special when seeing something isn't displayed that optimal on the website, I think it is a more good idea to generate the website from trunk. But this would imply, the informations contained in the README files are consistent with the released tarballs.
Otherwise, if we generate the website from tagged releases, this would mean something would be fucked up until the next release, in the worst case.
True. My suggestion was based on your statement, the README content should match the released plugin version. Maybe this isn't necessary at all. I don't see READMEs as the documentation of a plugin and so the README should be as up to date as necessary and should not match a months old release state. Just my 2cents.
few other thoughts to this topic:
- have an additional README.stable
I think this would generate just many redundant information without real benefit. Additional, it could confuse users who are unsure which README to read.
- and maybe generate an additional plugins.geany.org/svn/
Similar as above.
Regards, Enrico
Am Samstag, den 12.02.2011, 14:19 +0100 schrieb Enrico Tröger:
True. My suggestion was based on your statement, the README content should match the released plugin version.
To avoid confusion: I was talking about the informations contained in the README file, not the content. I don't want any plugin developer to fit his README file 1:1 with the released file. I just was suggesting to be consistent with the behavior the actual released plugin behaves. And this is just a suggestion, no requirement. It's still up to the plugin developer how he maintains his README. :)
Maybe this isn't necessary at all. I don't see READMEs as the documentation of a plugin and so the README should be as up to date as necessary and should not match a months old release state. Just my 2cents.
Of course. Consistency with the described behavior and the up-to-dateness don't exclude each other. :)
Regards, Dominic
Am Samstag, den 12.02.2011, 03:05 +0100 schrieb Frank Lanitz:
On Sat, 12 Feb 2011 00:04:32 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf:
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think.
I'm thinking about a post-commit hook which is deploying it after tagging (or something like this)
Guess that won't be possible, unfortunately. Post-commit-hooks have to be implemented on the SVN repository as far as I know... not that I'd knew we have access to the server-side repository at SourceForge.
Regards, Dominic
On Sat, 12 Feb 2011 13:50:21 +0100, Dominic wrote:
Am Samstag, den 12.02.2011, 03:05 +0100 schrieb Frank Lanitz:
On Sat, 12 Feb 2011 00:04:32 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf:
In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC.
Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think.
I'm thinking about a post-commit hook which is deploying it after tagging (or something like this)
Guess that won't be possible, unfortunately. Post-commit-hooks have to be implemented on the SVN repository as far as I know... not that I'd knew we have access to the server-side repository at SourceForge.
We can set port-commit hooks. Though we can only set a mail address to send the commit message mail. But this would be enough, as we already use this for the commits mailing lists and a few additional tasks we do on post-commit actions like announcing the commit in the IRC channel and to sync the GIT mirrors. This is all triggered by the commit mails.
Regards, Enrico