[liblouis-liblouisxml] Re: Code priorities for liblouis and liblouisutdml
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Sat, 5 Oct 2013 03:35:14 +0000
We use RT at work because it works with Email. It does take a bit to set up
but if APH became more involved in the development it might be something we
could even help with. I don't have the power to say that but I have a good
feeling that Larry would agree with what I just said and he does have that
power. Joseph also mentioned getting UEB transcribers to help with the work.
We have actually talked about this in the office because APH has a great deal
of experts in braille including nemeth etc. So maybe it's time to see what we
can do about supporting this project more seriously.
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples
Sent: Friday, October 04, 2013 4:01 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Code priorities for liblouis and
liblouisutdml
Mentioning difficulties with using issue tracking on Google Code: As I am
looking into other options for hosting the downloads, may be this could be
something also I could look at.
Any oppinions on the SourceForge bug tracker system? What about the one on
BitBucket?
I do remember one bug tracking package where it was possible to do stuff
through an email interface, cannot quite remember what it was and not sure
which project hosting sites might use that (I met it as software for running on
a server).
Michael Whapples
On 04/10/2013 20:56, Mesar Hameed wrote:
> On Fri 04/10/13,21:46, Mesar Hameed wrote:
>>> Nothing is wrong with it. What I do notice though and maybe I am
>>> partly guilty is there is very few issues listed unless I am reading
>>> it wrong. Which means no one is using it. I look at the list of
>>> items changed for the is release and I don't see any of them that
>>> are tied to issues. This means we are all kind of tracking bugs
>>> willy nilly in email mostly unless I am missing something. I will
>>> go through and start putting issues of UEB problems in as soon as I
>>> have time to sit down and do it. Is there an email interface to the
>>> google code issue tracking list?
>> I Agree with Ken,
>> and I think John has said in the past that he has had problems with
>> the google bug tracker.
> Sorry forgot to say, thats why we started to use the trunk/TODO file,
> so that things would be more readable for John.
>
> Of course that is not a real replacement to a bug tracker, and is only
> available for those who have commit access.
>
> Mesar
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:
