public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benson Muite <benson_muite@emailplus.org>
To: Jerry D <jvdelisle2@gmail.com>, gfortran <fortran@gcc.gnu.org>
Subject: Re: Team Collaboration Considerations
Date: Thu, 8 Dec 2022 07:12:04 +0300	[thread overview]
Message-ID: <c522c5f0-3260-9f34-bad0-b7ae91f6eae5@emailplus.org> (raw)
In-Reply-To: <e15d6bc6-e87b-8219-86bc-7d182423011f@gmail.com>

On 12/8/22 04:54, Jerry D wrote:
> Other than Benson, I have received no sign of any interest from gfortran 
> developers to adopt a teaming/collaboration platform.  I am a bit 
> disappointed. Maybe my intent was misunderstood.  I am not suggesting 
> replacing the email approval process but there are many other features 
> of these platforms, in particular, communication efficiency that would 
> be very helpful.
There is a discourse site https://fortran-lang.discourse.group that 
caters to Fortran in general.

> 
> I know many software developers who use these tools regularly. Honestly 
> I do not know why gcc.gnu.org does not adopt one of these as a whole. 
> Perhaps it is simply resistance to change.

Maybe it is helpful to bridge Mattermost and IRC? Interoperability is 
good and minimizes the cost of having multiple clients running.  The 
chat applications are great for enabling focus, for example adding git 
commit notifications in a separate channel.

https://quassel-irc.org seems like it may also be helpful.
> 
> I will keep the Mattermost workspace.  If anyone want to join send me 
> your email and I will send you an invite.
> 
> Well, as always, best regards,
> 
> Jerry
> 
> On 12/4/22 6:16 AM, Benson Muite wrote:
>> On 12/4/22 06:52, Jerry D via Fortran wrote:
>>
>>> 3. Mattermost looks pretty good and was easy to set up.  The free
>>>     version is a bit better than Slacks. GCC C++ uses it.
>> This server application runs well. The desktop application is a little 
>> resource heavy, however there is also a Qt based desktop application:
>> https://github.com/nuclear868/mattermost-qt
>>
>> It is possible to bridge Mattermost and IRC:
>> https://github.com/42wim/matterbridge
>> https://github.com/42wim/matterircd
>>
>>>
>>
> 


  reply	other threads:[~2022-12-08  4:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04  3:52 Jerry D
2022-12-04 14:16 ` Benson Muite
2022-12-08  1:54   ` Jerry D
2022-12-08  4:12     ` Benson Muite [this message]
2022-12-08 16:27     ` Steve Kargl
2022-12-08 17:25       ` Tobias Burnus
2022-12-10 18:15         ` Jerry D
2022-12-08 19:14       ` Holcomb, Katherine A (kah3f)
2022-12-09 19:36         ` Toon Moene
2022-12-09 21:56           ` Paul Richard Thomas
2022-12-09 22:10             ` Toon Moene
2022-12-10 20:10         ` Jerry D
2022-12-10 21:09           ` Steve Kargl
2022-12-11 17:37             ` Holcomb, Katherine A (kah3f)
2022-12-10 21:11         ` Thomas Koenig
2022-12-13  8:10 ` Janne Blomqvist
2022-12-13 12:22   ` Jerry D
2022-12-26 10:19   ` NightStrike
2023-01-19  5:00     ` Benson Muite
2023-01-19 12:28       ` NightStrike
2023-01-19 12:46         ` Toon Moene
2023-01-19 12:52           ` NightStrike
2023-01-19 18:33             ` Bernhard Reutner-Fischer
2023-01-19 19:03               ` NightStrike
2023-01-20  6:11                 ` Bernhard Reutner-Fischer
2023-01-20  6:21                 ` Benson Muite
2023-01-21  4:50                   ` Jerry D
2022-12-08 21:27 Harald Anlauf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c522c5f0-3260-9f34-bad0-b7ae91f6eae5@emailplus.org \
    --to=benson_muite@emailplus.org \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).