Re: Github


Quentin Christensen
 

As mentioned, if you want to create a ticket, submit an issue or generally report something that isn't working / could work better / should be implemented etc, what you want to do is create a new issue.  The link to the issues section is https://github.com/nvaccess/nvda/issues

Unless you are writing code yourself, you can mostly ignore the other sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to search for the issue you want to report.  (the first one searches code and other things, you want to search issues).  So, if someone reported a problem with footnotes in Word 2016 for instance, I'd search for "word 2016 footnotes" or similar in that second edit box.  There are two types of issues, open and closed. Open issues are either new issues that haven't been triaged yet (that is, no one has looked at them to see how serious they are, whether the issue has already been reported etc), or issues which are being worked on, or waiting to be worked on.  Closed issues are issues which have either been fixed, or which are duplicates of other issues, or sometimes things which can't or won't be fixed.  If the problem with footnotes is that you want them to appear at the top of the page for instance, then that isn't something related to NVDA.  That's a feature request for Word itself and you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump straight there with https://github.com/nvaccess/nvda/issues/new

When you create a new issue, there is a block of text in the "comment" prompting you for the kinds of information that are useful in diagnosing the issue.  Please try and include: steps to reproduce the issue, attach any files which might help (eg if Word crashes every time you try and check formatting in this particular file, if you can share it, that would help), what should happen and what actually happens, and your system configuration (Windows version, application version, NVDA version and whether installed or portable), and anything you've done to try and resolve or get more information (eg tried different version of NVDA or other program).  Don't stress if you don't have every piece of that information or if you aren't sure if the issue has been filed before.  When someone goes to triage the issue, they will ask for more information if needed.  If the issue has been filed previously, they will link to it (and likely close the duplicate issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@...> wrote:

Good point sir. Ive seen Get Hub's pages in the past and its confusing as heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site.  I haven't signed up yet but it looks easy to do so and to create a pull request, which I assume is what is generally referred to on this list as a ticket.  But many people may find the page confusing. Is there a way that some sort of short help information can be inserted after the navigation links on the page, instructing people what to do to create what are called tickets, perhaps also how to search for tickets and how to create an account?  If tickets are desired from the widest variety of users, this process should be somehow explained and done so in a place that those wishing to create tickets will be likely to see the explanation.
 
Gene 




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 

Join nvda@nvda.groups.io to automatically receive all group messages.