[liblouis-liblouisxml] Re: Issue tracker and web site hosting
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Tue, 8 Oct 2013 11:09:01 +0000
Oh well I am going to stop arguing about this. I will only ask one more thing.
Then I will spend my time on stuff that I can. John you asked what is needed
for the next steps. I want to ask as a developer what can I do to help advance
the code. Note I am a highly skilled programmer that has extra time from time
to time. What should I work on when I do. If the answer is search the email
list for a bug to work on then I will not ask again.
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry
Sent: Tuesday, October 08, 2013 7:05 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Issue tracker and web site hosting
No the main reason for a bug tracker is not to know when they are added and
resolved but to know they exist at all. As with the UEB bugs.
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
Sent: Tuesday, October 08, 2013 6:58 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Issue tracker and web site hosting
Christian,
I'm not keen on off-list conversations either.
I also agree that this whole argument about bug trackers is overblown.
We've gotten along fine with discussing bugs on the list. Insisting that they
should be recorded on a web interface will just take more time.
There are also projects that don't use a tracker. I've never seen a reference
to one on the libxml2 or brltty lists, but there have been plentyof bug reports
on the lists themselves.
The main use of an issue trracker, as far as I can see, is to register when a
bug is discovered and when it is resolved. The actual resolution should be
handled on the list.
The liblouis-liblouisxml and brailleblaster lists ARE development lists.
When we have more people on the brailleblaster list who are users and not
developers or testerrs we can set up a user list. The liblouis-liblouisxml list
will always remain a developer list.
imho, this argument is a waste of time.
John B
On Tue, Oct 08, 2013 at 11:09:16AM +0200, Christian Egli wrote:
> Hi all
>
> I'm not so keen on off-list conversations, so CC the list.
>
> "John Gardner" <john.gardner@xxxxxxxxxxxx> writes:
>
> > Seems to me from list comments lately that our bug tracking
> > procedures need some improvement.
>
> I'm not sure about that. We probably get one bug report every three
> months. And John has never used the bug tracker, so I think this whole
> argument is blown out of proportion. For the amount of bug reports and
> for our usage I think the Google code issue tracker is perfectly fine.
> It is basically just an email gateway to the list and that is fine
> with me. I seriously doubt an elaborate bug tracker would be a good
> use of our time.
>
> > I agree with Keith that it isn't appropriate to copy the list on bug
> > reports.
>
> Given the amount of bug reports we get I think it's perfectly fine.
>
> > let's try to reach a consensus on how to do it for both
> > BrailleBlaster and Liblouisxxx.
>
> I don't know the situation for BrailleBlaster. It might be a different
> story there.
>
> > While we are at it, can we also reach a consensus on what to do with
> > the web site/download site, etc. I don't think we're gonna have to
> > contend with a huge demand for downloads, so mirror sites are not
> > really needed imho.
>
> Let's not throw out the the baby with the bath water. All we need now
> is a way to host downloads. There is no need to change everything (at
> least not right now). It occured to me that we could just host the
> downloads in svn (just like we do it for the online docs, e.g.
> http://liblouis.googlecode.com/svn/documentation/liblouis.html). That
> would provide a solution for the downloads without having to move off
> Google code.
>
> > As I've said, I'm happy for ViewPlus to continue to host the
> > BrailleBlaster.org and liblouis.org sites until/unless APH wants to
> > take over in order to offer more capabilities.
>
> OK, thanks for the offer.
>
> > Excuse my ignorance, but could we not just use those sites but with
> > more complicated needs (bug tracker??) remaining on Google?
>
> Yes we could. That's why I created the static web site (see
> http://liblouis.github.io/). But I think this is not so pressing.
>
> Thanks
> Christian
> --
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
>
> -----
> Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter
> http://online.sbs.ch For a description of the software, to download it
> and links to project pages go to http://www.abilitiessoft.com
--
John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
For a description of the software, to download it and links to project pages go
to http://www.abilitiessoft.com For a description of the software, to download
it and links to project pages go to http://www.abilitiessoft.com
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
