Il 12/02/2014 13:38, Olivier Dalang ha scritto:
Multiline descriptions in the metadata are allowed, newlines are not
converted to BR in the HTML though...
Good to know ! Is it ok to use HTML then ? Does the same apply to the
changelog ? ...
BTW: could we set up a checklist for
On 13-02-14 10:35, Paolo Cavallini wrote:
Il 12/02/2014 13:38, Olivier Dalang ha scritto:
Multiline descriptions in the metadata are allowed, newlines are not
converted to BR in the HTML though...
Good to know ! Is it ok to use HTML then ? Does the same apply to the
changelog ? ...
Hello,
Le jeudi 13 février 2014 12:15:24, Richard Duivenvoorde a écrit :
...[snip]...
Approval:
1) your plugin will not be public until it is approved by a set of
community approvers
2) give approvers some time to do this (after 2 weeks just email to...)
3) to approve we check that
Hi !
I made a quick draft about a potential plugin approval checklist :
https://docs.google.com/spreadsheet/ccc?key=0Ag5xh-UHkkZLdG56V2p4cXRGVkNDb0tYZjhVYjhhcmcusp=sharing
Please extend it or change it !
Olivier
2014-02-13 12:22 GMT+01:00 Vincent Picavet vincent...@oslandia.com:
Hello,
Il 13/02/2014 12:22, Vincent Picavet ha scritto:
There is no choice on the licence a plugin can be distributed under : a
python
import is considered a link, therefore the import qgis.core is enough to
propagate the GPL licence to the plugin.
confirmed.
all the best.
--
Paolo Cavallini -
On 02/13/2014 03:15 AM, Richard Duivenvoorde wrote:
On 13-02-14 10:35, Paolo Cavallini wrote:
Il 12/02/2014 13:38, Olivier Dalang ha scritto:
Multiline descriptions in the metadata are allowed, newlines are not
converted to BR in the HTML though...
Good to know ! Is it ok to use HTML
On 13-02-14 20:23, Alex Mandel wrote:
For the first point (orange block) can we standardize on Github? Can we
ask from the average plugin author to put his code on Github? Because
then an author has both an issuetracker and either a README or a wiki.
We have always stated that any issue
Il 13/02/2014 22:33, Richard Duivenvoorde ha scritto:
So not forcing to some kind of system. Just enforcing at least a public
code repository + email. And preferably a issuetracker and a webpage.
Agreed?
IMHO opinion one repo and one bugtracker are necessary.
any reasonable system will do.
-1 for forcing people to use a single system. I am happy to make a source
repo mandatory, anyone who touches code should know to do that anyway
however I don't want to force people into a system they don't want/like. I
prefer github to our own hub so I would not upload a plugin if forced to
HI,
On Thu, Feb 13, 2014 at 4:57 PM, Nathan Woodrow madman...@gmail.com wrote:
-1 for forcing people to use a single system. I am happy to make a source
repo mandatory, anyone who touches code should know to do that anyway
however I don't want to force people into a system they don't
On 11-02-14 23:40, Alex Mandel wrote:
An alias or a mailing list?
I was thinking of an alias for now.
Regards,
Richard
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Hi !
-1 for making the homepage mandatory...
If it's only to display the plugin's help/readme information, we should
rather have the developpers create some help/readme file for each plugin,
which could be opened directly from within QGIS.
IMO that's much better than a link which opens in the
2014-02-12 13:20 GMT+01:00 Olivier Dalang olivier.dal...@gmail.com:
Hi !
-1 for making the homepage mandatory...
If it's only to display the plugin's help/readme information, we should
rather have the developpers create some help/readme file for each plugin,
which could be opened directly
Multiline descriptions in the metadata are allowed, newlines are not
converted to BR in the HTML though...
Good to know ! Is it ok to use HTML then ? Does the same apply to the
changelog ? ...
The default metadata.txt file should be more explicit about how to format
the entries... A few days
On 12-02-14 13:38, Olivier Dalang wrote:
Good to know ! Is it ok to use HTML then ? Does the same apply to the
changelog ? ...
Docs say no (I also tried):
http://www.qgis.org/en/docs/pyqgis_developer_cookbook/plugins.html#plugin-metadata
Regards,
Richard Duivenvoorde
2014-02-12 14:08 GMT+01:00 Richard Duivenvoorde rdmaili...@duif.net:
On 12-02-14 13:38, Olivier Dalang wrote:
Good to know ! Is it ok to use HTML then ? Does the same apply to the
changelog ? ...
Multiline: yes
HTML: no
UTF8: yes
--
w3: www.itopen.it
Hi Devs,
tl;dr; can we make an email address: approv...@qgis.org for which an
email can be sent to all approvers?
who can arrange this?
I'm busy weeding the long list of unapproved plugins.
Some of them are so old the I just sent the author an email if it is ok
to remove it.
Other have some
An alias or a mailing list?
Long term, finding a way to open tickets on plugin submission would be a
way to track them publicly.
Thanks,
Alex
On 02/11/2014 01:50 PM, Richard Duivenvoorde wrote:
Hi Devs,
tl;dr; can we make an email address: approv...@qgis.org for which an
email can be sent
2014-02-11 22:50 GMT+01:00 Richard Duivenvoorde rdmaili...@duif.net:
Hi Devs,
tl;dr; can we make an email address: approv...@qgis.org for which an
email can be sent to all approvers?
who can arrange this?
I'm busy weeding the long list of unapproved plugins.
Some of them are so old the
Il 12/02/2014 08:12, Alessandro Pasotti ha scritto:
I think that the plugin home page should be a page about the plugin itself.
There are many others like this that I can't recall now.
right. IMHO a home page is nice to have, but not necessary.
bugtracker, code, and some description are.
all
OT, but related :)
I would appreciate a field more in Metadata... a maintainer(s) optional
section. It's not strictly necessary because of trac, but a lot of time the
first Author of the plugin is disappeared or can't invest time in the
plugin, but she(he) still receives issues or mails from
21 matches
Mail list logo
