Hi,
I have gathered some experience from trying to sort out GDAL and Geoserver tickets, some of them pretty old with original reporters disappeared from the community. I can’t give a recommendation what is the best but I share my observations.
I would say that annexed data are very valuable for reproducing issues and the older the ticket gets the more essential the data come. It does not really matter where the attachments are stored but links should stay available for several years and all sort of files should be allowed – binary data, zip files, XML. It would of course make it easier for those who report issues if they would not need to upload attachments to other services with other user accounts.
GDAL is using trac and allows small attachments. GDAL tickets often relate to biggish images or vector data samples. Sometimes external links stay alive amazingly long time but sometimes they disappear within weeks which is not good. By the way, I like the GDAL timeline http://trac.osgeo.org/gdal/timeline. What I do not is that comments in GDAL trac can’t be edited; I tend to do lots of typos.
QGIS seems to run their own Redmine tracker which allows 5 MB sized attachments. Possibility to sort tickets by Last Updated column is very nice is someone wants to check what is generally going on. Some QGIS developers do lot of work by checking their tickets at a few times per year and keep them up-to-date.
Mapserver project is using github issue tracker. Only small image attachments are supported. Mapserver developers do not pay attention to old tickets.
OpenJUMP is using a bug tracker from SourceForge. It supports attachment and other common tracker features but our not so popular project has only 30 open bugs and those could be handled on any piece of paper.
-Jukka Rahkonen-
Andrea Aime wrote:
···
On Sun, Mar 1, 2015 at 9:48 PM, Robert Coup <robert.coup@…1454…> wrote:
I’ve worked with non-profit/OSS organisations before that have used OnDemand - AFAIK you just have to apply and they approve it.
https://www.atlassian.com/software/jira/pricing “Qualified open source projects can receive free subscriptions for Atlassian Cloud offerings.”
Note that the abilities to a) use your own domain (eg. jira.geoserver.org), and b) install most 3rd-party plugins isn’t available with the Cloud/OnDemand offerings.
Interesting indeed. I don’t believe we use plugins right now, but of course it would be nice to
have the DVCS connector to mimic some of the integration GitHub provides on its issues
https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin
Do you know if this is “third party”?
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.