On 23/06/16 02:57, Daniel Curran-Dickinson wrote:
Hi Ted,

On Wed, 2016-06-22 at 19:06 -0400, Ted Hess wrote:
Daniel -

Subject to a few more folk's OKs and an up-coming adm meeting, I think we are 
going to go forward with Flyspray. There is no other
proposed systems on deck for testing, so this is it unless someone proposes an 
alternative for further testing, etc.

If you need any help getting at the Flyspray data directly, I can help you out 
there. The backend is a MySQL DB and regular sync'd
backups of it could be available on the mirror site. Otherwise, you can pull your data 
from the existing "export" feature and/or the
lede-bugs mailing-list. I am working on implementing Flyspray backup so this 
would be a good time to discuss.
I'm actually more interested in any REST or similar HTTP API calls I can
use AJAX in a Luci app to automatically populate a ticket for a bug
report generated on-device (which I want to use to include information
from the device subject to user edits/approval; that edit/approval part
will have Luci-side); preferably with the ability to create an on
account for first time users (or least link to the account creation
page), and a chance to review the report in the usual web interface
before submitting.


+1 API

_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Reply via email to