On Sat, 2016-10-22 at 18:37 +0200, Markus Heiser wrote:
> Yeah, I thought something similar. But is the import of the extension
> a sufficient criteria?
>
> About ".. math::"; I guess we have to check if math extension AND
> pdflatex is installed.
>
> What do you suppose?
TBH, I only considere
Am 21.10.2016 um 23:19 schrieb Johannes Berg :
> On Fri, 2016-10-21 at 18:11 +0200, Markus Heiser wrote:
>
>> Yes and No. It depends on the tools (toolchains) we want to use.
>> As far as I can see from a abstract POV it should by simple for
>> math:: / since we already use/need LaTeX for PDF, f
On Fri, 2016-10-21 at 18:11 +0200, Markus Heiser wrote:
> Yes and No. It depends on the tools (toolchains) we want to use.
> As far as I can see from a abstract POV it should by simple for
> math:: / since we already use/need LaTeX for PDF, for other tools
> I have to look.
Not sure if we were ta
> I general I think, we should not include Java into our toolchains
> even if it is optional. Thats, why I won't vote for
> http://plantuml.com/
Keep in mind though that such a vote may well end up being a vote not
just against plantuml, but also against having sequence diagrams to
start with - a
Am 21.10.2016 um 15:04 schrieb Johannes Berg :
>> I had the same conclusion for math:: directives pulling in latex
>> dependency [1]. Hopefully Markus can help here.
>
> Yeah, good one.
>
> Maybe it's actually simple? Depending on where sphinx will look for
> plugins first, we could just ship t
> I had the same conclusion for math:: directives pulling in latex
> dependency [1]. Hopefully Markus can help here.
Yeah, good one.
Maybe it's actually simple? Depending on where sphinx will look for
plugins first, we could just ship the plugins with a no-op
implementation (pass through the text
On Fri, 21 Oct 2016, Johannes Berg wrote:
>> >https://pythonhosted.org/sphinxcontrib-aafig/
>> >
>> > I've not actually played with it at all, but I like the idea that
>> > we'd have readable diagrams in the source docs as well...
>>
>> Well, maybe. I agree having it readable in the source d
> > https://pythonhosted.org/sphinxcontrib-aafig/
> >
> > I've not actually played with it at all, but I like the idea that
> > we'd have readable diagrams in the source docs as well...
>
> Well, maybe. I agree having it readable in the source docs as well is
> nice, but for sequence diagram
On Tue, 2016-10-18 at 17:52 -0600, Jonathan Corbet wrote:
> In summary, I think we can consider taking on a module if it's what
> we need to do the docs right. And if somebody agrees to maintain it!
> :)
:)
I think for the ones that we carry, they're probably specific?
> I've heard others say
On Wed, 19 Oct 2016, Markus Heiser wrote:
> Am 18.10.2016 um 16:52 schrieb Jani Nikula :
>
>>> *Only* adding the PNG would be awful, I'd have to keep track of the
>>> corresponding source elsewhere, and perhaps couldn't even GPL it
>>> because then I couldn't distribute the PNG without correspondi
Am 18.10.2016 um 16:52 schrieb Jani Nikula :
>> *Only* adding the PNG would be awful, I'd have to keep track of the
>> corresponding source elsewhere, and perhaps couldn't even GPL it
>> because then I couldn't distribute the PNG without corresponding
>> source...
>>
>> Adding the source text wo
On Tue, 18 Oct 2016 13:43:41 +0200
Johannes Berg wrote:
> > 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 reques
> This could probably be argued either way...
Yeah, I guess it could :)
> My view has been all along that we should prefer to use existing
> extensions written and maintained by others. Perhaps we (the kind of
> royal "we" of which I'm personally really not part of) could take on
> maintainershi
On Tue, 18 Oct 2016, Johannes Berg wrote:
> On Tue, 2016-10-18 at 15:51 +0200, Markus Heiser wrote:
>> Here are my thoughts ...
>>
>> Every extension which is not a part of the sphinx distro brings new
>> external dependencies
>
> I agree.
>
>> and the development of such extensions is IMO
>> fa
On Tue, 2016-10-18 at 15:51 +0200, Markus Heiser wrote:
> Here are my thoughts ...
>
> Every extension which is not a part of the sphinx distro brings new
> external dependencies
I agree.
> and the development of such extensions is IMO
> far of kernel development's scope.
Arguably, having good
Am 18.10.2016 um 13:43 schrieb Johannes Berg :
> 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 a
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.sipsoluti
17 matches
Mail list logo
