Re: Maintenance and future of Guile

[Tim Van den Langenbergh <tmt_vdl@gmx.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2336 bytes --]

On 19/12/2021 21:05, Blake Shaw wrote:
> hi folks, from what I'm seeing here it seems like there are quite a few
> of us who are interested in engaging in steady, organized participation
> in Guile's upkeep, but we're unsure whether we're qualified. At the same
> time Ludo needs to find a replacement and Andy is apparently quite busy,
> and some issues in the ecosystem are apparently starting to show their teeth.
> 
> personally I've been programming for about 15 years now but my career
> has been entirely in new media (video, graphics, audio), so while I've
> worked with plenty of lower-level libraries over the years, I didn't
> start to get an itch for compilers until covid happened. I was also
> doing a PhD in philosophy of mathematics at the time (which I've
> postponed indefinitely to prevent being separated from my partner during 
> covid travel craziness) so I definitely think I have the *potential* to
> contribute to a project like Guile, its just a matter of finding the
> time to read some compiler books (which usually are neither short nor easy!).
> 
> It sounds like others are coming from similar-ish places: you feel
> confident in your abilities to accede to the challenges, but lack the
> background that would enable you to take the initiative. So what are we
> TODO?
> 
> In a situation like this, I would recommend that we form a little
> working group to collectively study the implementation of Guile, and
> with Ludo's suggestions come up with a roadmap for tackling various areas
> of the repo/compiler/infrastructure that need work, which we could then
> divide up among ourselves with each of us creating a presentation on our
> assigned areas, with group hack sessions following each bi-weekly (or
> whatever) presentation. This way we could distribute the knowledge
> aquisicition work in a structured fashion while forming a support group for
> developing a collective understanding of the codebase, as a cohort of
> sorts.  
>  
> wdyt?
> 
> ez,
> blake 
> 

That sounds like a good idea, though I wonder what the best way to organise it would be.

IRC, Mattermost, and Rocket Chat seem like the most obvious options for chat. I don't know what would be best for task management, maybe some out-of-the-box kanban?

Ideas, anyone?

Vale,

-Tim.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]