This is great. I've been thinking that building a federated issue tracker on top of MIX would be great - since a ticket tend to spawn discussions - but this is a great start and in the absence of MIX we should document this.
Some things you might not have considered: * Tickets are often linked, especially between layers. A UI might link to a library issue, a client issue might link to a server issue, and so on. I've not looked to see if you've considered this, but a federating issue link is an amazing idea. * Tickets sometimes have privacy or security concerns - we should really tidy up XEP-0314, but that's perfect for this approach - just marking a ticket or a comment on it, as being security-sensitive would be very useful. * You might want to look at XEP-0346 (if I recall it right - Forms Distribution Protocol) for raising tickets. I think that ought to align well. On 5 Dec 2017 09:58, "Goffi" <go...@goffi.org> wrote: > Hello everybody, > > I have implemented an experimental ticket/merge request feature in our XMPP > client (Salut à Toi), and I've just written a blog post about it (with a > short demo vidéo): https://www.goffi.org/blog/ > goffi/9555cc02-6a87-4b6b-af85-20f1c0736722 > > I'm planning to propose protoXEP for the node schema feature used there, > beside that it's all standard pubsub. > > > Feedback welcome > > > Thanks and good day > Goffi > _______________________________________________ > JDev mailing list > Info: https://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: jdev-unsubscr...@jabber.org > _______________________________________________ >
_______________________________________________ JDev mailing list Info: https://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: jdev-unsubscr...@jabber.org _______________________________________________
