It is easy enough to make those fields required in django, perhaps with
a note/link to where to create them if you don't already have (aka hub).
Trickier but still possible is to modify the django form validation to
verify the links are real.
Even trickier yet, but most useful is to ask the user if they want an
issue tracker/repo created for them and have django interact with
redmine for them.
I won't step on toes, but I can create a patch for the 1st idea if no
one else is available.
Thanks,
Alex
On 03/17/2013 12:28 PM, Paolo Cavallini wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
I see that new plugins are still accepted without a repo and a bugtracker.
I think this is bad practice, and makes the whole process unreliable,
with a bad user experience (e.g. I just spotted serious bug in this
plugins, and I have nowhere to open a ticket).
Could we implement this?
Thanks.
- -------- Messaggio originale --------
Oggetto: A new plugin has been created by mauroalberti.
Data: Sat, 16 Mar 2013 09:15:14 -0000
Mittente: [email protected]
A: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Plugin name is: qProf
Plugin description is: Calculates height and slope profiles
Link: http://plugins.qgis.org/plugins/qProf/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlFGGWUACgkQ/NedwLUzIr7tZQCfTgysYzWBucndWYfNWkfWFHHr
CIEAn1Bzg+6Xq7UcKF/7bJ5FXaf316d0
=E3Kd
-----END PGP SIGNATURE-----
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
