On 1/19/23 10:21 PM, Benson Muite via Fortran wrote:
On 1/19/23 22:03, NightStrike wrote:
On Thu, Jan 19, 2023, 13:33 Bernhard Reutner-Fischer
mailto:rep.dot@gmail.com>> wrote:
On 19 January 2023 13:52:55 CET, NightStrike via Fortran
mailto:fortran@gcc.gnu.org>> wrote:
>Yo
On 1/19/23 22:03, NightStrike wrote:
>
>
> On Thu, Jan 19, 2023, 13:33 Bernhard Reutner-Fischer
> mailto:rep.dot@gmail.com>> wrote:
>
> On 19 January 2023 13:52:55 CET, NightStrike via Fortran
> mailto:fortran@gcc.gnu.org>> wrote:
>
> >You can, and people naturally do this, and
On 19 January 2023 20:03:38 CET, NightStrike wrote:
>The problem is that patch tracking is unsustainable. You could go the other
>way and have a patch tracker automatically echo messages to the mailing
>list.
Currently it's the other way round. Patchwork collects the patches sent to the
list. E
On Thu, Jan 19, 2023, 13:33 Bernhard Reutner-Fischer
wrote:
> On 19 January 2023 13:52:55 CET, NightStrike via Fortran <
> fortran@gcc.gnu.org> wrote:
>
> >You can, and people naturally do this, and I think it's great, but
> >there's usually a response from someone saying "post that to the
> >mai
On 19 January 2023 13:52:55 CET, NightStrike via Fortran
wrote:
>You can, and people naturally do this, and I think it's great, but
>there's usually a response from someone saying "post that to the
>mailing list instead".
The mailing list has a 20-30 year history with reasoning about what curre
On Thu, Jan 19, 2023 at 7:46 AM Toon Moene wrote:
>
> On 1/19/23 13:28, NightStrike via Fortran wrote:
>
> > On Thu, Jan 19, 2023, 00:01 Benson Muite via Fortran
> > wrote:
> >
> >> The GCC workflows is quite different from other open source projects
> >> being primarily email based and not using
On 1/19/23 13:28, NightStrike via Fortran wrote:
On Thu, Jan 19, 2023, 00:01 Benson Muite via Fortran
wrote:
The GCC workflows is quite different from other open source projects
being primarily email based and not using a bug tracker.
There's a bug tracker. I think you mean there isn't a p
On Thu, Jan 19, 2023, 00:01 Benson Muite via Fortran
wrote:
> The GCC workflows is quite different from other open source projects
> being primarily email based and not using a bug tracker.
>
There's a bug tracker. I think you mean there isn't a patch tracker (or at
least not a system where you
On 12/26/22 13:19, NightStrike via Fortran wrote:
> On Tue, Dec 13, 2022, 03:10 Janne Blomqvist via Fortran
> wrote:
>
>> But in general, yes, I do think IRC is showing its age in an
>> increasingly multi-device and mobile world.
>>
>
> Tools like irccloud help here. I guess that doesn't qualify
On Tue, Dec 13, 2022, 03:10 Janne Blomqvist via Fortran
wrote:
> But in general, yes, I do think IRC is showing its age in an
> increasingly multi-device and mobile world.
>
Tools like irccloud help here. I guess that doesn't qualify as open source
though.
>
On 12/13/22 12:10 AM, Janne Blomqvist wrote:
--- snip --
Any thoughts from all?
Hi,
I haven't commented earlier as I haven't been active in GFortran
development for a couple of years (new job, kids, etc. etc.). So don't
take my opinions too seriously.
But in general, yes, I do think IRC is sh
On Sun, Dec 4, 2022 at 5:53 AM Jerry D via Fortran wrote:
> 1. Slack has adopted some limitations on being able to go back and look
> at older posts. Functionally it is quite good and integrates well
> with github.
> 2. I looked at Element and Fractal which use the Matrix protocols.
>
Fortran
; Benson Muite ; Harald Anlauf
Subject: Re: Team Collaboration Considerations
On Sat, Dec 10, 2022 at 12:10:20PM -0800, Jerry D wrote:
> On 12/8/22 11:14 AM, Holcomb, Katherine A (kah3f) via Fortran wrote:
> > I was thinking I might try to contribute when I retire, though th
Hi Katherine,
Is there some kind of "getting started" guide?
There's https://gcc.gnu.org/wiki/GFortranHacking which has some
pointers. It could also use a bit of an update (file names are now
.cc instead of .c :-)
Best regards
Thomas
On Sat, Dec 10, 2022 at 12:10:20PM -0800, Jerry D wrote:
> On 12/8/22 11:14 AM, Holcomb, Katherine A (kah3f) via Fortran wrote:
> > I was thinking I might try to contribute when I retire, though that may be
> > in a year or two. But it's been a very long time since I dove into a large
> > softwa
On 12/8/22 11:14 AM, Holcomb, Katherine A (kah3f) via Fortran wrote:
I was thinking I might try to contribute when I retire, though that may be in a year or
two. But it's been a very long time since I dove into a large software project and it's
intimidating. I do know C (really C++, I haven't
On 12/8/22 9:25 AM, Tobias Burnus wrote:
Hi,
On 08.12.22 17:27, Steve Kargl via Fortran wrote:
On Wed, Dec 07, 2022 at 05:54:40PM -0800, Jerry D via Fortran wrote:
Other than Benson, I have received no sign of any interest from
gfortran
developers to adopt a teaming/collaboration platform. I
On 12/9/22 22:56, Paul Richard Thomas wrote:
One really helpful collaborative activity would be to update the
gfortran wiki. For a good long while that, together with the gfortran
list, did serve as our collaborative focus.
Another thing I might have tons of time for beyond 20230827.
Kind re
Hi Jerry and everybody else,
I am with Tobias on this. Between work, gfortran, RSPCA, club and
neighbourhood activities I am "channelled" up to the eyeballs. Adding
another wouldn't make any great odds but I couldn't pay much more attention
to it than many of the others - sorry!
At the present, I
On 12/8/22 20:14, Holcomb, Katherine A (kah3f) via Fortran wrote:
I was thinking I might try to contribute when I retire, though that may be in a year or
two. But it's been a very long time since I dove into a large software project and it's
intimidating. I do know C (really C++, I haven't u
Hi Jerry, all,
as already said, the basic issue appears to be the low number
of contributors, most (all?) of which are working on gfortran
in their spare time (like me). I think it is not likely that
they will commit to being available regularly.
I have used IRC once for a discussion that was r
uot; guide?
Katherine Holcomb
UVA Research Computing https://www.rc.virginia.edu
ka...@virginia.edu434-982-5948
-Original Message-
From: Fortran On Behalf Of
Steve Kargl via Fortran
Sent: Thursday, December 8, 2022 11:27 AM
To: Jerry D via Fortran
Cc: Benson Muite
Subject: Re: Team C
Hi,
On 08.12.22 17:27, Steve Kargl via Fortran wrote:
On Wed, Dec 07, 2022 at 05:54:40PM -0800, Jerry D via Fortran 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
On Wed, Dec 07, 2022 at 05:54:40PM -0800, Jerry D via Fortran 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
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 ma
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 platfo
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 deskto
Hi all,
Some of you may recall way back when I established the gfortran IRC
channel to facilitate collaboration on gfortran development.
I have had some discussions with a few people about advancing to newer
technology. One thing I have learned is that the gcc C++ team has
adopted the Matte
28 matches
Mail list logo
