Reply
Thread Tools
jukey's Avatar
Posts: 246 | Thanked: 204 times | Joined on Jun 2007 @ Potsdam (Germany)
#1
Originally Posted by Andre Klapper at community mailing list
http://wiki.maemo.org/Packaging#Bugtracker_location states
"It is possible to [...] use [...] an email address."
No mentioning of size of project.

http://wiki.maemo.org/Extras-testing...rting_database states "An e-mail address for small projects (wallpapers, for example) can be used".

Now which one is correct? (Plus the same topic/info with slight
differences spread on different pages is not cool.)

Asking for clarification because of discussion on
http://maemo.org/packages/package_in...acts/0.9.13-1/

andre
(Source: http://lists.maemo.org/pipermail/mae...st/004380.html )

What do you think regarding this topic?
__________________
-> Join the SailfishOS Meetup Berlin - every first Monday a month <-

Me on twitter
 
MohammadAG's Avatar
Posts: 2,473 | Thanked: 12,265 times | Joined on Oct 2009 @ Jerusalem, PS/IL
#2
Inconsistencies, meh.
Mignight Commander had my email set as the bugtracker, and it was promoted.

In its current situation, I'd rather keep all my packages in extras-devel
 

The Following 2 Users Say Thank You to MohammadAG For This Useful Post:
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#3
Email should be fine IMHO. As long as there is some point of contact for reporting bugs, the package should pass the bugtracker criteria.
 

The Following 3 Users Say Thank You to lma For This Useful Post:
Posts: 415 | Thanked: 732 times | Joined on Jan 2009 @ Finland
#4
Handling bugs in private through email doesn't sound like good open source practices. Using a bug tracker gives better visibility to open bugs and their status so I'd go for a public bug tracker.

That's just my 0.02. At the end of the day it's the developer's decision how to handle bugs.
 

The Following 2 Users Say Thank You to timoph For This Useful Post:
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#5
Originally Posted by timoph View Post
Handling bugs in private through email doesn't sound like good open source practices.
It's not a good software development practice in general, regardless of the licence. Sygic and Opera are a couple of examples from the non-free camp.

That's just my 0.02. At the end of the day it's the developer's decision how to handle bugs.
Exactly. It's a good idea to have a "real" bugtracker for many reasons, but it shouldn't be a blocker for package promotion.
 

The Following 5 Users Say Thank You to lma For This Useful Post:
Jaffa's Avatar
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#6
Originally Posted by lma View Post
Exactly. It's a good idea to have a "real" bugtracker for many reasons, but it shouldn't be a blocker for package promotion.
Indeed. More discussion happening on maemo-developers:

http://lists.maemo.org/pipermail/mae...st/004380.html
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following 2 Users Say Thank You to Jaffa For This Useful Post:
Posts: 1,418 | Thanked: 1,541 times | Joined on Feb 2008
#7
Originally Posted by timoph View Post
Handling bugs in private through email doesn't sound like good open source practices. Using a bug tracker gives better visibility to open bugs and their status so I'd go for a public bug tracker.
Well, first of all, a .deb package does not have to be open-source. There are binary-only packages as well. Secondly, it is up to developer to determine a way how he is going to handle bug reports, if at all. The GPL says nothing about handling bug reports, so developers using GPL are not legally bound to do any bug report handling.
 
Posts: 415 | Thanked: 732 times | Joined on Jan 2009 @ Finland
#8
Originally Posted by fms View Post
Well, first of all, a .deb package does not have to be open-source. There are binary-only packages as well.
I know debs don't have to contain the sources. I could have just as well referred to good practices in general like lma pointed out and was absolutely correct.

Originally Posted by fms View Post
Secondly, it is up to developer to determine a way how he is going to handle bug reports, if at all. The GPL says nothing about handling bug reports, so developers using GPL are not legally bound to do any bug report handling.
Well I did say "At the end of the day it's the developer's decision how to handle bugs."

And my final comment to this thread: GPL doesn't state many things that are considered good practices but people are doing so anyway. If some people don't want to follow good practices then it's really their own choice and loss.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 21:38.