Re: [BackupPC-users] Does BackupPC need a bug tracker?

2016-05-24 Thread Carl Wilhelm Soderstrom
On 05/24 09:14 , Mauro Condarelli wrote: > Hi Adam, > what You say makes a lot of sense. I agree. > Agreed, but perhaps this particular topic is interesting for users. > If we do not hear any scream from them I think we should assume github is OK. I'm quite ok with github. I use it at work, and

Re: [BackupPC-users] Does BackupPC need a bug tracker?

2016-05-24 Thread Mauro Condarelli
Hi Adam, what You say makes a lot of sense. IMHO we should try to keep low profile and use *one* new tool at a time (github, as is). There are a lot of specific tools for ticket management, but they are usually geared for very large user base. If and when we get there we will have to chose one an

Re: [BackupPC-users] Does BackupPC need a bug tracker?

2016-05-24 Thread Lars Tobias Skjong-Børsting
I agree with what Adam said. On 24/05/16 01:30, Adam Goryachev wrote: > I think there are a lot of things that could be better, but up until > now, we only had the mailing list, and that wasn't managed well at all. > I would suggest we focus as much as possible on using the tools that are > ava

Re: [BackupPC-users] Does BackupPC need a bug tracker?

2016-05-23 Thread Adam Goryachev
I think there are a lot of things that could be better, but up until now, we only had the mailing list, and that wasn't managed well at all. I would suggest we focus as much as possible on using the tools that are available, because adding workload to manage additional tools won't help the deve

Re: [BackupPC-users] Does BackupPC need a bug tracker?

2016-05-23 Thread Iain Hallam
The tools I've seen that use GitHub for development also use its issue tracker. I've seen very little in the way of complaints about it. For larger feature development the team might prefer something like Trello.com or Asana.com, but issues seem to be good for many things. - Iain. On 23 May 2016

[BackupPC-users] Does BackupPC need a bug tracker?

2016-05-23 Thread Juergen Harms
BackupPC 3.3.1 has amazingly few bugs to be fixed, handling them as "issues" on github can be a satisfactory way of keeping track. Nevertheless, I suggest to have a short discussion whether, in the long run, some tool specifically designed for bug-tracking (for instance Bugzilla) should be cons