Empathy List Archives

AH

Andrei Hajdukewycz

Tue, Apr 2, 2019 8:20 PM

On 2019-04-01 7:58 p.m., Geoff Lankow wrote:

The article I wrote on RTD was not intended to to contain every minute
detail. Others decided that it should be, which I just don't agree
with, although I didn't complain at the time.

A wiki (not necessarily the one we currently have) is much better
suited as

anyone with an account can edit it.
changes happen immediately and don't need anyone else's input.
headings and bullet points is better for listing the information
than prose.

I don't see anything blocking people from making bullet points on
developer.thunderbird.net? The Markdown for it works fine. Either on the
website editor or in a pull request you can use the standard syntax
https://docs.gitbook.com/content-editing/markdown.

It's true that developer.thunderbird.net requires PR merge whereas a
wiki page doesn't. If you or others want to continue using the Mozilla
wikis for certain pages due to that reason, I don't see a big problem
with it as long as they're linked from developer.thunderbird.net.

On 2019-04-01 7:58 p.m., Geoff Lankow wrote: > > The article I wrote on RTD was not intended to to contain every minute > detail. Others decided that it should be, which I just don't agree > with, although I didn't complain at the time. > > A wiki (not necessarily the one we currently have) is much better > suited as > > 1. anyone with an account can edit it. > 2. changes happen immediately and don't need anyone else's input. > 3. headings and bullet points is better for listing the information > than prose. > I don't see anything blocking people from making bullet points on developer.thunderbird.net? The Markdown for it works fine. Either on the website editor or in a pull request you can use the standard syntax <https://docs.gitbook.com/content-editing/markdown>. It's true that developer.thunderbird.net requires PR merge whereas a wiki page doesn't. If you or others want to continue using the Mozilla wikis for certain pages due to that reason, I don't see a big problem with it as long as they're linked from developer.thunderbird.net.

AH

Andrei Hajdukewycz

Tue, Apr 2, 2019 8:25 PM

On 2019-04-01 11:59 p.m., John Bieling wrote:

Ok, than lets sort this out. What path should we take?

Ryan: Can we host our own wiki with custom css to make it fit into
developer.thunderbird.net? Or can we style the mozilla wiki?

I'm not planning to host our own wiki at this time. It will add
maintenance burden for questionable utility. The purpose of
developer.thunderbird.net was to consolidate documentation somewhat. If
gitbook has too much friction and people would rather use a wiki for
documentation, we can consider replacing it with a wiki. Hosting both
just seems inefficient and likely to encourage the exact kind of
fragmentation we're trying to fix.

Maybe we can try to distill what exact requirements people actually have
and then pick one solution that serves them.

On 2019-04-01 11:59 p.m., John Bieling wrote: > Ok, than lets sort this out. What path should we take? > > 1. Ryan: Can we host our own wiki with custom css to make it fit into > developer.thunderbird.net? Or can we style the mozilla wiki? I'm not planning to host our own wiki at this time. It will add maintenance burden for questionable utility. The purpose of developer.thunderbird.net was to consolidate documentation somewhat. If gitbook has too much friction and people would rather use a wiki for documentation, we can consider replacing it with a wiki. Hosting both just seems inefficient and likely to encourage the exact kind of fragmentation we're trying to fix. Maybe we can try to distill what exact requirements people actually have and then pick one solution that serves them.

RS

Ryan Sipes

Tue, Apr 2, 2019 8:28 PM

Well, the point of developer.thunderbird.net was to have a curated
experience. This way a developer can read through the docs versus
getting lost in them.

But, agreeing with Andrei - we can link out to wiki pages and the like
as needed.

Ryan Sipes
Community and Business Development Manager
Thunderbird https://thunderbird.net

On 4/2/19 2:25 PM, Andrei Hajdukewycz wrote:

On 2019-04-01 11:59 p.m., John Bieling wrote:

Ok, than lets sort this out. What path should we take?

Ryan: Can we host our own wiki with custom css to make it fit into
developer.thunderbird.net? Or can we style the mozilla wiki?

I'm not planning to host our own wiki at this time. It will add
maintenance burden for questionable utility. The purpose of
developer.thunderbird.net was to consolidate documentation somewhat.
If gitbook has too much friction and people would rather use a wiki
for documentation, we can consider replacing it with a wiki. Hosting
both just seems inefficient and likely to encourage the exact kind of
fragmentation we're trying to fix.

Maybe we can try to distill what exact requirements people actually
have and then pick one solution that serves them.

Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Well, the point of developer.thunderbird.net was to have a curated experience. This way a developer can read through the docs versus getting lost in them. But, agreeing with Andrei - we can link out to wiki pages and the like as needed. Ryan Sipes Community and Business Development Manager Thunderbird <https://thunderbird.net> On 4/2/19 2:25 PM, Andrei Hajdukewycz wrote: > On 2019-04-01 11:59 p.m., John Bieling wrote: >> Ok, than lets sort this out. What path should we take? >> >> 1. Ryan: Can we host our own wiki with custom css to make it fit into >> developer.thunderbird.net? Or can we style the mozilla wiki? > I'm not planning to host our own wiki at this time. It will add > maintenance burden for questionable utility. The purpose of > developer.thunderbird.net was to consolidate documentation somewhat. > If gitbook has too much friction and people would rather use a wiki > for documentation, we can consider replacing it with a wiki. Hosting > both just seems inefficient and likely to encourage the exact kind of > fragmentation we're trying to fix. > > Maybe we can try to distill what exact requirements people actually > have and then pick one solution that serves them. > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >

maildev@lists.thunderbird.net

Keep obsolete AddOns Guide obsolete