Am 18.10.2016 um 13:43 schrieb Johannes Berg <johannes@xxxxxxxxxxxxxxxx>: > On Tue, 2016-10-11 at 15:53 +0200, Johannes Berg wrote: >>> >>> >>> Related question: I have some sequence diagrams, and just found the >>> seqdiag sphinx plugin. How should we manage adding extensions? Or >>> would you prefer not to add any at all? >> >> Example here: >> https://johannes.sipsolutions.net/files/80211/mac80211.html#connection-flow > > Coming back to this - sadly, it appears that this software (blockdiag, > seqdiag) is completely unmaintained, with open pull requests dating > back to 2012 and the last commit dating back to 2015-08-22. > > I'd want/need feature improvements in it too, but if I can't feed those > back to upstream (since it appears dead), there's little point. > > Perhaps we can ship plugins for this as part of the kernel sources? > Shouldn't be too difficult to reimplement something like this, after > all. Here are my thoughts ... Every extension which is not a part of the sphinx distro brings new external dependencies and the development of such extensions is IMO far of kernel development's scope. ATM, there are not many use cases for diagram generators, so why not be KISS and creating diagrams with the favorite tool only adding the resulting (e.g.) PNG to the Kernel's source? Before we add new dependencies / complexity, we should get rid of the DocBook build. -- Markus -- > johannes > -- > To unsubscribe from this list: send the line "unsubscribe linux-doc" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
