[liblouis-liblouisxml] Re: Adding comments to issues
- From: "Vic Beckley" <vic.beckley3@xxxxxxxxx>
- To: <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Thu, 17 Oct 2013 10:06:58 -0400
Mesar,
Adding bugs works fine now. The only minor issue I see now is that once you
submit the bug you are left at the page stating that the bug needs moderator
approval. There is no link that I could see to get back to either the bug
you were on or to the main bugs page. I had to go back to the home page and
drill down from there.
On the link at the top that just says Edit, could that be changed to
something like Edit Page.
On the button below the edit field where you add a bug, could the label be
changed to something like Edit Bug. That would more precisely describe what
the button does.
Great job! It looks like it is going to give you a lot of work if the bug
tracker gets very active.
Best regards from Ohio,
Vic
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar Hameed
Sent: Thursday, October 17, 2013 9:43 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Adding comments to issues
Hi,
On Thu 17/10/13,09:10, Vic Beckley wrote:
> Near the top of the page I see an unlabeled edit box. What is this for?
It is a free form full text search field. The default template doesn't seem
to label it, probably to take less space for sighted users, but this can be
altered.
> The first link in the first list is called Edit. I am unclear as to
> what this link does.
edit the current page.
I think the turseness is because it is displayed at the top in a bar, so
visually people probably don't want to put too much text there.
Again, this is possible to change.
> The button to submit the new bug is labeled This should be submit or
> something like this.
At that point, you are only entering the title for the bug which will become
a new page, but you are not actually submitting anything until the full
report is completed.
So edit makes sence.
> On the create a new bug page the edit box where you enter the actual
> bug isn't labeled.
This is fixable.
> How do you add comments to an existing bug? I don't see a link for that.
My bad, i hadn't enabled comments in the config, now done you should be able
to add comments.
> This looks very promising, though. It is very simple and
> straightforward. If John will be posting bugs this way, he had
> mentioned no comboboxes. I was surprised at that, but I am pretty sure
that is what he said.
As you probably saw by the svn email notifications, everything that is done
is reflected in text files in svn, so both John and I don't have to use the
web, we can just edit using a standard text editor and commit as normal,
just like we do when editing code.
> I didn't see a link to sign in. I was unsure of how to do that. Once I
> tried to add a bug it came up with my e-mail address somehow and said
> you wanted to use it in accord with your privacy policy. There was an
> Accept and Decline button at the bottom of the page but both were
> stated as disabled. I pressed enter on the Accept button and it worked
anyway.
This page is controlled by google, or whichever authenticator you chose, so
unfortunately that page is out of my control.
It would have got your email address from googles cookie stored by your
browser.
thanks,
Mesar
> -----Original Message-----
> From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar
> Hameed
> Sent: Thursday, October 17, 2013 8:41 AM
> To: liblouis-liblouisxml@xxxxxxxxxxxxx
> Subject: [liblouis-liblouisxml] Re: Adding comments to issues
>
> Hi Vic, sorry about any overcomplication, I just wanted to give all
> the information in one email.
> Please go to http://liblouis.mesarhameed.info and have a look around.
> If you want to add a bug, click on bugs in the sidebar, and there
> should be a text field called "add new bug titled:"
> You will have to login using google or one of the other providers, or
> create a new account, once that is done you can edit the text and submit
it.
> Looking forward to hearing your feedback.
> thanks,
> Mesar
> On Thu 17/10/13,08:37, Vic Beckley wrote:
> > Mesar,
> >
> > You are making me feel stupid here. I don't understand this message
> > or how this would work. For example, how would I submit an issue or
> > a comment from a Windows PC?
> >
> >
> > Best regards from Ohio,
> >
> > Vic
> >
> >
> > -----Original Message-----
> > From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> > [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of
> > Mesar Hameed
> > Sent: Wednesday, October 16, 2013 7:05 PM
> > To: liblouis-liblouisxml@xxxxxxxxxxxxx
> > Subject: [liblouis-liblouisxml] Re: Adding comments to issues
> >
> > Ok, I have gone ahead and setup a test ikiwiki[1] instance, running
> > reachable at [2].
> >
> > I have used ikiwiki privately and for the nvda community addons
> > website, and it can be used both as a wiki for documentation and a
> > simple and accessible bug tracker.
> > Best of all is that for those that prefer the command line
> > (including
> > me) it is just markdown files in a directory in our vcs.
> > I have currently placed it in a separate branch so that it can be
> > eliminated easely if we chose to go with something else.
> >
> > It allows everyone else using the web to log in using a ton of
> > authentication services, so people don't have to register to create
> > enhancement requests, bugs or add to the wiki.
> > Also no need to solve any graphical or sound captcha.
> > When anything is edited or added, it is automatically committed to
> > the svn, so that no one is forced to go online to action anything.
> > We can lock pages that should not be edited, to allow only admins to
> > edit those.
> > On the other hand if you edit the files in svn and commit, they
> > should come live on the website.
> >
> > learning markdown is straightforward and is probably as close to raw
> > text as we could get.
> > It is very configurable, and our team of nvda translators and addon
> > contributors seem to love it. Ikiwiki is also used for a lot of
> > software and non-software projects, some of wich are listed in [1].
> >
> > This is just another possible solution to evaluate before deciding
> > on what might be most suitable.
> >
> > After creating the original configuration file, there are no
> > databases or anything else to administrate, everything comes with the
repository.
> > So mirroring or moving servers is extremely simple.
> > There is only one additional configuration file that I haven't
> > committed to the svn yet.
> >
> > Markdown can be converted to docbook texinfo or many other formats
> > using pandoc amongst other things.
> >
> > This solution solves our two recent discussions, with hopefully
> > maximum accessibility.
> >
> > At the moment it will commit to the testwiki using my svn
> > authentication, we probably need to create a separate account for
> > web edits. I appologize for the commit mail this will cause while people
test.
> >
> > comments welcome.
> >
> > [1]: http://ikiwiki.info
> > [2]: http://liblouis.mesarhameed.info
> >
> > thanks,
> > Mesar
> >
> > On Wed 16/10/13,09:05, John J. Boyer wrote:
> > > As I said, a simple web form would be acceptable. No captchas! no
> > > Javascript. Combo boxes aren't necessary. they can be replaced
> > > with a series of radio buttons, with a select button at the end.
> > > I've done this in php. A good example of a simple website is
> www.freelists.org .
> > > It even works better in lynx than in elinks or IE.
> > > www.bookshare.org is also a good example, although it has become
> > > rather cluttered. O
> > >
> > >
> > > John
> > >
> > > On Wed, Oct 16, 2013 at 10:03:40AM +0200, Bert Frees wrote:
> > > > No I don't think opening an issue by email is supported out of
> > > > the box, although the Github API would allow it. For changing
> > > > the status it's probably the same story.
> > > >
> > > >
> > > > 2013/10/15 Michael Whapples <mwhapples@xxxxxxx>
> > > >
> > > > > This is what I was thinking of.
> > > > >
> > > > > I did not know about github allowing reply by email. Does it
> > > > > allow opening a issue by email and changing the status of the
> > > > > report by
> > email?
> > > > >
> > > > > While it would require hosting it I know that a system like
> > > > > roundup offers all that.
> > > > >
> > > > > As John said though a simple web interface should be just as
> > > > > acceptable and I would imagine it would be easier to find a
> > > > > hosted solution with a simple web interface. However there
> > > > > does seem to be a trend for web developers to complicate the
> > > > > interface for no apparent reason, other than to show how much
> > > > > javascript/ajax/other web
> > technology they can use.
> > > > >
> > > > > Michael Whapples
> > > > > On 15/10/2013 21:08, Bert Frees wrote:
> > > > >
> > > > > I'm not saying "move to Github", but maybe there is an issue
> > > > > tracker out there that has the same feature, in which case the
> > > > > accessiblity of the web interface is not so crucial.
> > > > >
> > > > > On 15 Oct 2013, at 22:06, Bert Frees wrote:
> > > > >
> > > > > For what it's worth (and I haven't been following the
> > > > > discussion very closely, so maybe someone mentioned this
> > > > > before): the Github issue tracker has an "email reply support"
> > > > > feature[1], which basically means that you can follow and
> > > > > participate in conversations both with email and on the Github
> website.
> > > > >
> > > > > [1] https://github.com/blog/811-reply-to-comments-from-email
> > > > >
> > > > >
> > > > >
> > >
> > > --
> > > 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
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
