maildev@lists.thunderbird.net

Thunderbird email developers

View all threads

Thunderbird communication channels consolidation

MM
Magnus Melin
Fri, May 15, 2020 7:32 AM

Currently Thunderbird communication channels are a bit scattered. Some
consolidation has been discussed on various forums, but no decisions
have been made so far. I'm writing this to get a wider feedback on some
of the changes up for discussion.

tb-planning mailing list https://mail.mozilla.org/listinfo/tb-planning

  • Would remain/become the main channel of general communication.
  • Would preferably be moving to topicbox like many of our other lists
    https://thunderbird.topicbox.com/groups(topicbox is a mailing list
    system too, but with nicer web UI then mailman lists)

maildev mailing list
https://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

  • Most if not all of the maildev members are also on tb-planning.
  • The list hasn't had too much traffic, since whether to choose this
    or tb-planning is not easy.
  • Its original purpose of serving as a more moderated forum for
    technical discussion has proven generally non-feasible: details of
    technical decisions are better discussed on specific bugs with the
    people who have, or are gaining knowledge about the specifics involved.

Thunderbird discourse https://discourse.mozilla.org/c/thunderbird

mozilla.dev.apps.thunderbird newsgroup
news://news.mozilla.org/mozilla.dev.apps.thunderbird

  • Could remain (IMO).
  • Could consider having it a pure newsgroup and kill the mailinglist
    gateway, which when used makes usage a mess out of conversations
    there...

cc:ing maildev - let's continue the discussion on tb-planning though!

 -Magnus

Currently Thunderbird communication channels are a bit scattered. Some consolidation has been discussed on various forums, but no decisions have been made so far. I'm writing this to get a wider feedback on some of the changes up for discussion. tb-planning mailing list <https://mail.mozilla.org/listinfo/tb-planning> * Would remain/become the main channel of general communication. * Would preferably be moving to topicbox like many of our other lists <https://thunderbird.topicbox.com/groups>(topicbox is a mailing list system too, but with nicer web UI then mailman lists) maildev mailing list <https://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net> * Most if not all of the maildev members are also on tb-planning. * The list hasn't had too much traffic, since whether to choose this or tb-planning is not easy. * Its original purpose of serving as a more moderated forum for technical discussion has proven generally non-feasible: details of technical decisions are better discussed on specific bugs with the people who have, or are gaining knowledge about the specifics involved. Thunderbird discourse <https://discourse.mozilla.org/c/thunderbird> * Would be discontinued. * The addons topicbox <https://thunderbird.topicbox.com/groups/addons> is flourishing and a number of people have expressed frustration with discourse. The value in keeping it seems low. mozilla.dev.apps.thunderbird newsgroup <news://news.mozilla.org/mozilla.dev.apps.thunderbird> * Could remain (IMO). * Could consider having it a pure newsgroup and kill the mailinglist gateway, which when used makes usage a mess out of conversations there... cc:ing maildev - let's continue the discussion on tb-planning though!  -Magnus
JK
Jörg Knobloch
Fri, May 15, 2020 7:56 AM

On 15/05/2020 09:32, Magnus Melin wrote:

maildev mailing list

  1. Most if not all of the maildev members are also on tb-planning.
  2. The list hasn't had too much traffic, since whether to choose this or tb-planning is not easy.
  3. Its original purpose of serving as a more moderated forum for technical discussion has proven generally non-feasible: details of technical decisions are better discussed on specific bugs with the people who have, or are gaining knowledge about the specifics involved.

Point 1: These lists have different moderation rules.

Point 2: These lists have very different purposes: For example, if you want to discuss the pitfalls of Mork-removal, then tb-planning is *not* the right list.

Point 3: Not-feasible? Why? We had a few useful discussions here. Not all the technical people follow all the bugs. Also, please refer to

https://mail.mozilla.org/pipermail/tb-planning/2017-July/005610.html

Jörg.

KE
Kai Engert
Fri, May 15, 2020 8:14 AM

On 15.05.20 09:32, Magnus Melin wrote:

cc:ing maildev - let's continue the discussion on tb-planning though!

Please follow Magnus' request and send replies to tb-planning, not here.

Thanks
Kai

On 15.05.20 09:32, Magnus Melin wrote: > > cc:ing maildev - let's continue the discussion on tb-planning though! Please follow Magnus' request and send replies to tb-planning, not here. Thanks Kai
BB
Ben Bucksch
Fri, May 15, 2020 8:44 AM

On 15.05.20 09:56, Jörg Knobloch wrote:

On 15/05/2020 09:32, Magnus Melin wrote:

maildev mailing list
https://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

  1. Most if not all of the maildev members are also on tb-planning.
  2. The list hasn't had too much traffic, since whether to choose
    this or tb-planning is not easy.
  3. Its original purpose of serving as a more moderated forum for
    technical discussion has proven generally non-feasible: details
    of technical decisions are better discussed on specific bugs with
    the people who have, or are gaining knowledge about the specifics
    involved.

Point 1: These lists have different moderation rules.

And the lists have different audiences. tb-planning includes the
community, whereas maildev is strictly for developers and code topics.

Point 2: These lists have very different purposes: For example, if you
want to discuss the pitfalls of Mork-removal, then tb-planning is
not the right list.

Exactly.

We need a place where we can discuss code and development related
subjects that affect the whole project and not just a specific bug. We
had a few of those, and they were important to discuss among the
developers. Bugzilla is not suited for that.

Point 3: Not-feasible? Why? We had a few useful discussions here. Not
all the technical people follow all the bugs.

ditto

Seconded, for the reasons Jörg mentioned.

On 15.05.20 09:56, Jörg Knobloch wrote: > On 15/05/2020 09:32, Magnus Melin wrote: >> maildev mailing list >> <https://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net> >> >> >> 1. Most if not all of the maildev members are also on tb-planning. >> 2. The list hasn't had too much traffic, since whether to choose >> this or tb-planning is not easy. >> 3. Its original purpose of serving as a more moderated forum for >> technical discussion has proven generally non-feasible: details >> of technical decisions are better discussed on specific bugs with >> the people who have, or are gaining knowledge about the specifics >> involved. >> > Point 1: These lists have different moderation rules. > And the lists have different audiences. tb-planning includes the community, whereas maildev is strictly for developers and code topics. > Point 2: These lists have very different purposes: For example, if you > want to discuss the pitfalls of Mork-removal, then tb-planning is > *not* the right list. > Exactly. We need a place where we can discuss code and development related subjects that affect the whole project and not just a specific bug. We had a few of those, and they were important to discuss among the developers. Bugzilla is not suited for that. > Point 3: Not-feasible? Why? We had a few useful discussions here. Not > all the technical people follow all the bugs. > > Also, please refer to > > https://mail.mozilla.org/pipermail/tb-planning/2017-July/005610.html > ditto Seconded, for the reasons Jörg mentioned.