[liblouis-liblouisxml] Re: Issue tracker and notification emails
- From: Aaron Cannon <cannona@xxxxxxxxxxxxxxxxxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Sat, 12 Oct 2013 09:11:53 -0500
Hi all.
At work, before we switched to Jira, we used an issue tracker called trac.
While I definitely can't recommend Jira for its accessibility, I can recommend
trac as being reasonably accessible.
I don't know what browser John uses, but it's a pretty simple interface.
I would be happy to help to set up a test instance, so we can try it out. It's
written in Python, and runs best under Linux.
Let me know if this is of interest.
Thanks.
Aaron
--
This message was sent from a mobile device
> On Oct 12, 2013, at 6:50 AM, "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
> wrote:
>
> Mesar,
>
> Thanks for your well-thought-out message. This project is growing. It
> started ten years ago with just a few people on the list. I've learned a
> lot since then and I'm ready to learn more.
>
> John
>
>> On Sat, Oct 12, 2013 at 01:36:45PM +0200, Mesar Hameed wrote:
>> Hi,
>>
>>> On Fri 11/10/13,17:33, Michael Whapples wrote:
>>> When a file is attached to a issue report using the issue tracker on
>>> the GoogleCode project pages, the file can be found using the web
>>> interface of the issue tracker. It appears that the files will not
>>> be attached to the notification emails and there is no setting to
>>> allow files to be attached to the notification emails. Those dealing
>>> with bug reports will have to use the web interface to obtain these
>>> files.
>>
>> This makes sence, the person investigating the issue has to download the
>> file, instead of filling everyones inbox with email attachments.
>>
>>> I know that some feel that the topic of issue trackers has taken
>>> more time and effort than it should,
>>
>> Any project that wants to be taken seriously and is not a hobby project
>> should have a bug tracker.
>> instead of spending time/effort discussing why we should/why we shouldnt
>> have one, I think it might be best to concentrate on finding a tracker that
>> will work for all.
>> Yes there is no problem discussing bugs on the list, but the ticket
>> should be the authoritative location for the bug.
>>
>> Using a mailing list means that the bug reports can be intertwined in a
>> thread and one can easely get sidetracked on something and forget a
>> particular bug,
>> as has happend several times on this list.
>>
>> @John, by using a bug tracker, it is much more likely that people will
>> contribute bits and peaces, without having to monitor the list and work
>> out for themselves what needs doing, and if deciding to do something,
>> not to step on anyones toes/duplicate work.
>> It also helps end users to understand how to communicate with the
>> project team in a constructive way.
>>
>>> however sometimes ignoring a
>>> problem and hoping it will go away will simply not work, you
>>> sometimes actually need to deal with the problem which exists and
>>> solve it.
>>
>> Absolutely agree.
>>
>>> Should we decide not to use issue tracker tools, then those wanting
>>> that please answer the question of how people who want to work on
>>> liblouis/liblouisutdml/brailleblaster would be able to find out what
>>> tasks need doing and are not being worked upon by other people? This
>>> tracking of the state of known bugs and a simple way to find out
>>> what bugs need work is one of the biggest advantages to issue
>>> trackers.
>>
>> Personally as one of the other regular contributors, I have no firm idea what
>> others are working on, which confirms your understanding of lack of
>> direction and overview.
>>
>> Mesar
>>
>>> Sorry to drag this topic out, but I do feel that these problems have
>>> not really been addressed and that there is just a hope that the
>>> problem will go away by itself. As I said my oppinion is that they
>>> will not just go away.
>>>
>>> Michael Whapples
>
>
>
> --
> 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
Other related posts:
