On Tue, Sep 01, 2020 at 07:03:36PM +1000, Alexis wrote:
> On the basis of my current experiences, it would be No Small Task to convert
> the current, presentationally-based, HTML documentation to markup that's
> sufficiently semantic to enable it to be mechanically converted to
> mdoc/roff. i
On Mon, Aug 31, 2020 at 08:51:34PM +, Laurent Bercot wrote:
> - Unless, of course, someone comes up with the perfect solution (adding
> a DocBook dependency is not a perfect solution, and neither is
> generating HTML from mandoc), in which case, obviously, they would have
> the time and
Casper Ti. Vector writes:
* We negotiate a HTML schema your documentation can be written
in, which
is based on current documentation; existing HTML documentation
will be
converted to the schema, with minimised changes.
On the basis of my current experiences, it would be No Small
Steve Litt writes:
Depends on how the HTML is written ... All I'm saying is don't
assume,
sight unseen, that the current HTML can't easily be converted to
semantic LaTeX or Docbook or whatever.
This is good advice in general; but in this particular case,
there's no "sight unseen"
On Tue, 01 Sep 2020 10:00:22 +
"Laurent Bercot" wrote:
> s6 as a supervision suite? okay, people will use it; but it's
> already perceived as a bit complex, because there are a lot of
> binaries. It's on the high end of the acceptable difficulty range.
I've only used s6 as a supervisor a
* We negotiate a HTML schema your documentation can be written in, which
is based on current documentation; existing HTML documentation will be
converted to the schema, with minimised changes. (The structuredness
of HTML helps; now you also see why knowing some Lisp is beneficial :)
On Tue, Sep 01, 2020 at 10:11:14AM +, Laurent Bercot wrote:
> I'm totally willing to use a HTML schema we can negotiate, to write
> future documentation in. What I don't want to do is:
> - Touch existing documentation, unless I have to rewrite the content of
> a page for some reason. Of
Casper Ti. Vector writes:
May I request a diff (via PM) between your attempt and the
current HTMLs?
That involves ~70 documents. Do you need all of them, or can i
just provide a diff of a few examples? i don't currently have the
HTML sources locally; i'd have to download them all.
On Tue, Sep 01, 2020 at 08:02:34PM +1000, Alexis wrote:
> That involves ~70 documents. Do you need all of them, or can i just provide
> a diff of a few examples? i don't currently have the HTML sources locally;
> i'd have to download them all.
Preferably some representative samples, thanks.
--
I have only seen one new feature committed to the Git repository so
far. Is it too early to ask what are you planning to change?
The new feature is orthogonal - or, rather, it will be used if I end
up *not* redesigning s6-rc.
The trend with distributions is to make service managers reactive
Laurent Bercot writes:
I'm totally willing to use a HTML schema we can negotiate, to
write
future documentation in. What I don't want to do is:
- Touch existing documentation, unless I have to rewrite the
content of
a page for some reason. Of course, if the conversion work is
done by
On 9/1/20 2:24 PM, mobinmob wrote:
2. Which distributions or groups of distributions will find the redesign >
appealing, so that they will adopt it ?
I can't speak for everyone of course, but at least in the perspective of
Artix, this potential redesign idea could be very appealing. If s6-rc
1. There is one **huge** disadvantage for the second option. It is not a
technical one, so it may carry little weight on your final decision.
There already different implementations of init systems based on s6/s6-rc,
some of them successfully used on distributions. They will almost certainly
have
On Tue, 01 Sep 2020 19:03:36 +1000
Alexis wrote:
> Casper Ti. Vector writes:
>
> > * We negotiate a HTML schema your documentation can be written
> > in, which
> > is based on current documentation; existing HTML documentation
> > will be
> > converted to the schema, with minimised
Thank you for taking the time to present the options and the technical
arguments for each of them. I cannot offer a comment on the best way
to proceed on technical grounds, but I can offer my two cents as someone
who tries to bring an s6-rc based solution (66) to a distribution.
1. There is one
15 matches
Mail list logo
