public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry D <jvdelisle2@gmail.com>
To: gfortran <fortran@gcc.gnu.org>
Subject: MatterMost Workspace Features
Date: Thu, 26 Jan 2023 18:38:19 -0800	[thread overview]
Message-ID: <bdc0bd66-df39-7889-bb3e-f0452f42a6db@gmail.com> (raw)

Built into Mattermost is a feature called Playbooks.

https://docs.mattermost.com/guides/playbooks.html

For those of you who have accepted invitations and have access, I p;an 
to create a Playbook to capture our workflow.

Our workflow in my mind obviously included email for patch approvals and 
Bugzilla for bug tracking. These in my mind are good tools.

Now as an example of how folks are currently using Mattermost, Paul has 
posted preliminary patches for Finalization on that channel and others 
have chimed in with test cases. It is a dialog that is efficient and to 
the topic. It provides a focused discussion not cluttered by emails 
coming in on numerous other topics, that you have to filter out as you 
scan emails.

Vincent has linked the gtk-fortran GitHub repository. This allows issues 
and such show up for those interested without having to go out to GitHub 
and look.

I have a Board setup that I am using to help me keep track of a lot of 
Steve's patches hiding around in Bugzilla. Helpful to me, and others can 
look to see my progress. Certainly others can use the board and take on 
some of those.

I am hoping the Playbook will help new people to understand and follow 
our work flow as well.

I will occasionally ask here if anyone would like to join the 
MatterMost.  I am not looking for lurkers, I am looking for 
contributors, either testing, helping to understand bugs, interpreting 
Fortran Standards, and of course contributing patches.

Regards to all,

Jerry

                 reply	other threads:[~2023-01-27  2:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bdc0bd66-df39-7889-bb3e-f0452f42a6db@gmail.com \
    --to=jvdelisle2@gmail.com \
    --cc=fortran@gcc.gnu.org \
    /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).