Re: Teams

Re: Teams

[jgart]

On Tue, 14 Jun 2022 08:47:37 -0400 guix-devel-request@gnu.org wrote:

Hi Guixers,

Count me in for any packaging on teams. 

I'd like to help out with python and/or rust.

all best,

jgart

Teams

[Ricardo Wurmus]

Hi Guix,

this is not a new idea[1]: let’s add a page to the website that lists teams
and a mail alias for each of the teams.

For example, the “R team” consists of people familiar with how R
packaging works in Guix, e.g. Simon and myself.  There would be an alias
“guix-team-r@gnu.org”.  People with questions about R in Guix could
write an email to that alias.

Mumi could also send email to guix-team-r@gnu.org to remind them about
patches relating to R / Bioconductor / CRAN, etc.

Maintainers could write to these teams before releases to ask if there
are any obstacles to a release.

As a first step I’d suggest collecting teams, setting up the email
aliases, and updating the website to show the existing teams.  Here’s
a draft of three teams:

* R team
Simon Tournier
Ricardo Wurmus

* Java team
Julien Lepiller

* Rust team
Efraim Flashner
Aleksandr Vityazev
Arun Isaac
John Soo
Maxim Cournoyer
Nicolas Goaziou
Tobias Geerinckx-Rice

What do you think?


-- 
Ricardo

[1]: https://lists.gnu.org/archive/html/guix-devel/2021-12/msg00224.html

Re: Teams

[Maxime Devos]

[-- Attachment #1: Type: text/plain, Size: 403 bytes --]

Ricardo Wurmus schreef op za 04-06-2022 om 14:07 [+0200]:
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:
> 
> [...]

You can add me to the Rust team and to a new Minetest team.
Maybe Vivien Kraus would be interested in joining the Minetest team.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

Re: Teams

[Ekaitz Zarraga]

> Hi Guix,
>
> this is not a new idea[1]: let’s add a page to the website that lists teams
> and a mail alias for each of the teams.
>
> For example, the “R team” consists of people familiar with how R
> packaging works in Guix, e.g. Simon and myself. There would be an alias
> “guix-team-r@gnu.org”. People with questions about R in Guix could
> write an email to that alias.
>
> Mumi could also send email to guix-team-r@gnu.org to remind them about
> patches relating to R / Bioconductor / CRAN, etc.
>
> Maintainers could write to these teams before releases to ask if there
> are any obstacles to a release.
>
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams. Here’s
> a draft of three teams:
>
> * R team
> Simon Tournier
> Ricardo Wurmus
>
> * Java team
> Julien Lepiller
>
> * Rust team
> Efraim Flashner
> Aleksandr Vityazev
> Arun Isaac
> John Soo
> Maxim Cournoyer
> Nicolas Goaziou
> Tobias Geerinckx-Rice
>
> What do you think?
>
>
> --
> Ricardo
>
> [1]: https://lists.gnu.org/archive/html/guix-devel/2021-12/msg00224.html


If you want to add a Bootstrapping team, feel free to add me there.

Thanks for this effort. It's really interesting.

Cheers,
Ekaitz

Re: Teams

[Tobias Geerinckx-Rice]

On 4 June 2022 12:07:15 UTC, Ricardo Wurmus <rekado@elephly.net> wrote:
>* Rust team
[...]
>Tobias Geerinckx-Rice

OK what the hell.

I'll also join Leo on a kernel/module/initrd team if they're interested.

I think we should also have (natural) language 'teams' who can be pinged when, e.g., a news item lands, through a single guix-translators@ meta-alias, and who can co-ordinate before releases.

I'll take -nl.  Maxime?

Ricardo,

Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.

Re: Teams

[Maxime Devos]

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

Tobias Geerinckx-Rice schreef op za 04-06-2022 om 14:50 [+0000]:
> I think we should also have (natural) language 'teams' who can be pinged when, e.g., a news item lands, through a single guix-translators@ meta-alias, and who can co-ordinate before releases.
> 
> I'll take -nl.  Maxime?

Ok sure.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

Re: Teams

[david larsson]

> On 4 June 2022 12:07:15 UTC, Ricardo Wurmus <rekado@elephly.net> wrote:
>> * Rust team
> [...]
>> Tobias Geerinckx-Rice
> 
> OK what the hell.
> 

Would you wanna create and be the Bash team person as well? :)

Best regards,
David

Re: Teams

[pelzflorian (Florian Pelz)]

On Sat, Jun 04, 2022 at 02:50:49PM +0000, Tobias Geerinckx-Rice wrote:
> I think we should also have (natural) language 'teams' who can be
> pinged when, e.g., a news item lands, through a single
> guix-translators@ meta-alias, and who can co-ordinate before
> releases.

If we do so, please add me too for -de.

Regards,
Florian

Re: Teams

[Thiago Jung Bauermann]

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:

> On Sat, Jun 04, 2022 at 02:50:49PM +0000, Tobias Geerinckx-Rice wrote:
>> I think we should also have (natural) language 'teams' who can be
>> pinged when, e.g., a news item lands, through a single
>> guix-translators@ meta-alias, and who can co-ordinate before
>> releases.
>
> If we do so, please add me too for -de.

I'd be happy to be in a -pt team.

-- 
Thanks
Thiago

Re: Teams

[Josselin Poiret]

Hello everyone,

Ricardo Wurmus <rekado@elephly.net> writes:

> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.

I think an installer team would be good too (which I would gladly join).
WDYT of the following teams:
* Installer (which I'd gladly join);
* System;
* Home;
* Internals?

Maybe that would add too many teams, but I think the first three could
be pretty useful.

How do we automatically make Mumi understand which team a patch should
notify?  I've just started using public-inbox/lei and the `dfn:` search
term is pretty useful, it lets you select only patches that change
specific files.  For example, `dfn:gnu/installer*` would match all
patches that touch the installer.

Best,
-- 
Josselin Poiret

Re: Teams

[Ludovic Courtès]

Hi!

Josselin Poiret <dev@jpoiret.xyz> skribis:

> WDYT of the following teams:
> * Installer (which I'd gladly join);
> * System;
> * Home;
> * Internals?

I think these are good ideas.

Count me on the System, Home, and Internals/Core teams!

Ludo’.

Re: Teams

[Andrew Tropin]

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On 2022-06-05 10:19, Josselin Poiret wrote:

> Hello everyone,
>
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> As a first step I’d suggest collecting teams, setting up the email
>> aliases, and updating the website to show the existing teams.
>
> I think an installer team would be good too (which I would gladly join).
> WDYT of the following teams:
> * Installer (which I'd gladly join);
> * System;
> * Home;
> * Internals?
>
> Maybe that would add too many teams, but I think the first three could
> be pretty useful.
>
> How do we automatically make Mumi understand which team a patch should
> notify?  I've just started using public-inbox/lei and the `dfn:` search
> term is pretty useful, it lets you select only patches that change
> specific files.  For example, `dfn:gnu/installer*` would match all
> patches that touch the installer.
>
> Best,

I'm not in a guix-maintainers yet, but I would like to join Home team.

-- 
Best regards,
Andrew Tropin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: Teams

[Blake Shaw]

[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]

I think I could join the Home team as well, at least for now, as I started
using it a month ago and have been having a blast. I also have some
home-services to upstream after a bit of polish (Guile EDSL for
Herbstluftwm configuration if anyone is interested), and some plans to work
on the documentation.

I found the documentation to be a bit confusing (understandably, as its
new), but once the workflow snapped together its been amazing to see how
easy it is to create new services. And I now I have my entire desktop
environment contained in a single text file! Being able to ftp a text file
to a fresh Debian linode and get to work with all my tools ready within 10
minutes has been magic.

It also demonstrates a lot of Guile's strengths in one place: you can
easily wrap interfaces in Guile, and the expressive power it adds (at least
in the case of a window manager) is immediately evident.

Very excited about it, great work :)

On Tue, Jun 14, 2022, 18:31 Andrew Tropin <andrew@trop.in> wrote:

> On 2022-06-05 10:19, Josselin Poiret wrote:
>
> > Hello everyone,
> >
> > Ricardo Wurmus <rekado@elephly.net> writes:
> >
> >> As a first step I’d suggest collecting teams, setting up the email
> >> aliases, and updating the website to show the existing teams.
> >
> > I think an installer team would be good too (which I would gladly join).
> > WDYT of the following teams:
> > * Installer (which I'd gladly join);
> > * System;
> > * Home;
> > * Internals?
> >
> > Maybe that would add too many teams, but I think the first three could
> > be pretty useful.
> >
> > How do we automatically make Mumi understand which team a patch should
> > notify?  I've just started using public-inbox/lei and the `dfn:` search
> > term is pretty useful, it lets you select only patches that change
> > specific files.  For example, `dfn:gnu/installer*` would match all
> > patches that touch the installer.
> >
> > Best,
>
> I'm not in a guix-maintainers yet, but I would like to join Home team.
>
> --
> Best regards,
> Andrew Tropin
>

[-- Attachment #2: Type: text/html, Size: 2701 bytes --]

Re: Teams

[Lars-Dominik Braun]

Hi Ricardo,

> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:

* Python Team
Lars-Dominik Braun

* Haskell Team
Lars-Dominik Braun

Anyone interested to join these with me?

Cheers,
Lars

Re: Teams

[zimoun]

Hi Ricardo,

On Sat, 04 Jun 2022 at 14:07, Ricardo Wurmus <rekado@elephly.net> wrote:

> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:

Well, a team per build system would fit more or less the needs, I
guess.  It is not a big deal if there are some overlaps.

For what is it is worth, I would suggest that people with commit access
appear at least once in one team, if possible.


> * R team
> Simon Tournier
> Ricardo Wurmus

In addition, add me to:

* Julia team


Cheers,
simon

Re: Teams

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

If we make a team per build system, I'd be in ant, maven, ocaml and dune :)

I think there was also interest in formal methods, it could be a team.

On June 5, 2022 11:51:20 AM GMT+02:00, zimoun <zimon.toutoune@gmail.com> wrote:
>Hi Ricardo,
>
>On Sat, 04 Jun 2022 at 14:07, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> As a first step I’d suggest collecting teams, setting up the email
>> aliases, and updating the website to show the existing teams.  Here’s
>> a draft of three teams:
>
>Well, a team per build system would fit more or less the needs, I
>guess.  It is not a big deal if there are some overlaps.
>
>For what is it is worth, I would suggest that people with commit access
>appear at least once in one team, if possible.
>
>
>> * R team
>> Simon Tournier
>> Ricardo Wurmus
>
>In addition, add me to:
>
>* Julia team
>
>
>Cheers,
>simon
>

[-- Attachment #2: Type: text/html, Size: 1439 bytes --]

Re: Teams

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

On Sun, Jun 05, 2022 at 11:51:20AM +0200, zimoun wrote:
> Hi Ricardo,
> 
<snip>
> 
> > * R team
> > Simon Tournier
> > Ricardo Wurmus
> 
> In addition, add me to:
> 
> * Julia team

I can do the Julia team too.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Teams

[Andreas Enge]

Hello,

Am Sat, Jun 04, 2022 at 02:07:15PM +0200 schrieb Ricardo Wurmus:
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:

if something like this makes sense, I would be interested in joining a team
around algebra.scm and maths.scm. Or maybe a C team :)

Andreas

Re: Teams

[Eric Bavier]

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

Hi,

On Sun, 2022-06-05 at 11:51 +0200, Andreas Enge wrote:
> Hello,
> 
> Am Sat, Jun 04, 2022 at 02:07:15PM +0200 schrieb Ricardo Wurmus:
> > As a first step I’d suggest collecting teams, setting up the email
> > aliases, and updating the website to show the existing teams. 
> > Here’s
> > a draft of three teams:
> 
> if something like this makes sense, I would be interested in joining
> a team
> around algebra.scm and maths.scm. Or maybe a C team :)

I like the Teams idea.  It might help me focus and add just enough
accountability.

I'd add myself to an algebra.scm and maths.scm team.

`~Eric

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: Teams

[indieterminacy]

FWIW,

I just want to commend whoever is packaging TexLive.

My last update covered March of this year - no mean feat given that it 
is a 3.4GB package aggregate.

(sorry I cant do more direct contributions for Guix atm, looking forward 
to such an honour eventually)

On 04-06-2022 14:07, Ricardo Wurmus wrote:
> Hi Guix,
> 
> this is not a new idea[1]: let’s add a page to the website that lists 
> teams
> and a mail alias for each of the teams.
> 
> For example, the “R team” consists of people familiar with how R
> packaging works in Guix, e.g. Simon and myself.  There would be an 
> alias
> “guix-team-r@gnu.org”.  People with questions about R in Guix could
> write an email to that alias.
> 
> Mumi could also send email to guix-team-r@gnu.org to remind them about
> patches relating to R / Bioconductor / CRAN, etc.
> 
> Maintainers could write to these teams before releases to ask if there
> are any obstacles to a release.
> 
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:
> 
> * R team
> Simon Tournier
> Ricardo Wurmus
> 
> * Java team
> Julien Lepiller
> 
> * Rust team
> Efraim Flashner
> Aleksandr Vityazev
> Arun Isaac
> John Soo
> Maxim Cournoyer
> Nicolas Goaziou
> Tobias Geerinckx-Rice
> 
> What do you think?

-- 
Jonathan McHugh
indieterminacy@libre.brussels

Re: Teams

[Mathieu Othacehe]

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]


Hello Ricardo,

I would suggest to extend a bit the scope of this idea. What about
creating an etc/tutors.scm file as the one attached.

This way people would run something like:

--8<---------------cut here---------------start------------->8---
git send-email $(get-tutors.scm HEAD^^) *.patches
--8<---------------cut here---------------end--------------->8---

The get-tutors.scm command would take a git reference as argument. From
this git reference the list of edited files would be extracted. Once
matched with the modules field of tutors.scm, the ML & tutors that
should be CC'ed would be returned.

For the previous example, if the patches are modifying (gnu packages
bioconductor), the command would be:

--8<---------------cut here---------------start------------->8---
git send-email --to guix-patches@gnu.org --cc guix-r-patches@gnu.org
--cc rekado@elephly.net --cc zimoun.toutoune@gmail.com *.patches
--8<---------------cut here---------------end--------------->8---

People could subscribe to the relevant ML if they want to follow
specific subjects. If someone wants to become a tutor, a patch could be
sent against the tutors.scm file.

Being listed in the tutors.scm file would imply some duties, such as
trying to review part of the traffic for the tutored parts.

We could then turn this tutors.scm file into a website page,
transforming the tutors SEXP into an HTML table.

WDYT?

Thanks,

Mathieu

[-- Attachment #2: tutors.scm --]
[-- Type: application/octet-stream, Size: 1769 bytes --]

;;; Copyright © 2022 Mathieu Othacehe <othacehe@gnu.org>

(tutors
 (version 0)

 (entry (name "R tutors")
        (members
         "R patches <guix-r-patches@gnu.org>"
         "Ricardo Wurmus <rekado@elephly.net>"
         "Simon Tournier <zimon.toutoune@gmail.com>")
        (modules
         "gnu/packages/bioconductor.scm"
         "gnu/packages/bioinformatics.scm"
         "gnu/packages/cran.scm"
         "guix/build/r-build-system.scm"
         "guix/build-system/r.scm"))

 (entry (name "Java tutors")
        (members
         "Java patches <guix-java-patches@gnu.org>"
         "Julien Lepiller <julien@lepiller.eu>")
        (modules
         "gnu/packages/java.scm"
         "gnu/packages/java-*.scm"
         "gnu/packages/maven*.scm"
         "guix/build/maven-build-system.scm"
         "guix/build/maven/*"
         "guix/build-system/maven.scm"))

 (entry (name "Rust tutors")
        (members
         "Rust patches <guix-rust-patches@gnu.org>"
         "Efraim Flashner <efraim@flashner.co.il>"
         "Aleksandr Vityazev <avityazev@posteo.org>"
         "Arun Isaac <arunisaac@systemreboot.net>"
         "John Soo <jsoo1@asu.edu>"
         "Maxim Cournoyer <maxim.cournoyer@gmail.com>"
         "Maxime Devos <maximedevos@telenet.be>"
         "Nicolas Goaziou <mail@nicolasgoaziou.fr>"
         "Tobias Geerinckx-Rice <me@tobias.gr>")
        (modules
         "gnu/packages/rust*.scm"
         "guix/build/cargo*.scm"
         "guix/build-system/cargo.scm"))

 (entry (name "Installer tutors")
        (members
         "Installer patches <guix-installer-patches@gnu.org>"
         "Josselin Poiret <dev@jpoiret.xyz>"
         "Mathieu Othacehe <othacehe@gnu.org>")
        (modules
         "gnu/installer.scm"
         "gnu/installer/")))

Re: Teams

[Ludovic Courtès]

Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

> I would suggest to extend a bit the scope of this idea. What about
> creating an etc/tutors.scm file as the one attached.
>
> This way people would run something like:
>
> git send-email $(get-tutors.scm HEAD^^) *.patches

Nice idea, I like that!

To get the ball rolling though, I’d suggest starting with a dumb
structured web page like Ricardo proposes (I’m happy to give a hand if
needed).

From there we can enhance it by making the tutors file you propose the
canonical source of info, and providing a script to read it.

Ludo’.

Re: Teams

[Maxim Cournoyer]

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

[...]

> * Rust team
[...]
> Maxim Cournoyer
[...]

I don't think I'm specially fit for Rust packaging (I have little
experience/interest in packaging *apps/libraries* with it -- I've only
looked into shortening the Rust bootstrap out of necessity :-)).

I'd be happy to be on a Python/Emacs packaging team though.

Thanks for the initiative!

Maxim

Re: Teams

[Ryan Prior]

On Saturday, June 4th, 2022 at 12:07 PM, Ricardo Wurmus <rekado@elephly.net> wrote:

> let’s add a page to the website that lists teams
> and a mail alias for each of the teams

That sounds great. What do you think about encouraging each team to write a dedicated intro to Guix from the perspective of that team as well? For example, I assume people who are on the Home or System teams use different workflows than I typically do, and I'd love to learn them.

Teams I could contribute to:
- python, ruby, golang
- DevOps/Docker

Cheers,
Ryan

Re: Teams

[Vagrant Cascadian]

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

On 2022-06-04, Ricardo Wurmus wrote:
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:

I'm almost afraid to volunteer... but maybe architecture specific teams?

If I were to put my very highly optimistic hat on, I might be up for
aarch64, riscv64 and armhf...

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

Re: Teams

[Ludovic Courtès]

Vagrant Cascadian <vagrant@debian.org> skribis:

> On 2022-06-04, Ricardo Wurmus wrote:
>> As a first step I’d suggest collecting teams, setting up the email
>> aliases, and updating the website to show the existing teams.  Here’s
>> a draft of three teams:
>
> I'm almost afraid to volunteer... but maybe architecture specific teams?

There could also be an “embedded” team for people who take care of
packages like U-Boot, cross-compilation to ARM, platform definitions,
and all these things you’re familiar with.

> If I were to put my very highly optimistic hat on, I might be up for
> aarch64, riscv64 and armhf...

That too!

Ludo’.

Re: Teams

[Thiago Jung Bauermann]

Hello,

Ludovic Courtès <ludo@gnu.org> writes:

> Vagrant Cascadian <vagrant@debian.org> skribis:
>
>> On 2022-06-04, Ricardo Wurmus wrote:
>>> As a first step I’d suggest collecting teams, setting up the email
>>> aliases, and updating the website to show the existing teams.  Here’s
>>> a draft of three teams:
>>
>> I'm almost afraid to volunteer... but maybe architecture specific teams?
>
> There could also be an “embedded” team for people who take care of
> packages like U-Boot, cross-compilation to ARM, platform definitions,
> and all these things you’re familiar with.

I'm assuming the teams are for committers, so because of that and
also — or even especially — because of my time availability I would
be interested in being a lurker/occasional helper on an embedded team,
if it would be possible to have such a thing.

>> If I were to put my very highly optimistic hat on, I might be up for
>> aarch64, riscv64 and armhf...
>
> That too!

Ditto for ppc64le and even aarch64 teams.

-- 
Thanks
Thiago

Re: Teams

[Arun Isaac]

Hi Guix,

I like the idea of teams. And, it's nice to see so many volunteers raise
their hands!

> * Rust team
> Efraim Flashner
> Aleksandr Vityazev
> Arun Isaac
> John Soo
> Maxim Cournoyer
> Nicolas Goaziou
> Tobias Geerinckx-Rice

However, I know very little about Rust, and I'm not a good fit for this
team. I could easily be a part of the python, emacs lisp, common lisp,
scheme teams, etc if necessary.

But, what I'd really like is to be part of a mumi+tooling team. Maybe we
should have such a team?

Also, since we have so many ideas for teams, can we have some structured
way to suggest teams, and add or remove them as needs change?

Regards,
Arun

Re: Teams

[Blake Shaw]

[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]

Hi folks,

I'm just getting back to the list after finishing a gig, but want to raise
my hand to join both the scheme team and perhaps something like an A/V team
if folks think that would be a desirable team to put together. I think an
A/V team would look after:

#+begin_example scheme
 (gnu packages gstreamer)
 (gnu packages gl) ;; Maybe games could handle this?
 (gnu packages video)
 (gnu packages graphics)
 (gnu packages music)
#+end_example

Which is quite a lot! So maybe some of this should be split up with the
"games" team.

On another note, I'll be getting back to the Guile Docs soon, and before
that I plan on taking a stab at refactoring the patch submission criteria,
which I think could use some work. As it is currently, it personally
becomes a hurdle of a checklist when I want to quickly submit a patch,
which has lead me to running a hotfix branch so that I can quickly fix an
issue and move on, therefore contributing what I should be. I think it
could express all the same requirements in less rules, making it easier to
ensure what you're handing in is in order. But I still need to take a stab
at it and see.

Best,

On Fri, Jun 10, 2022, 03:29 Arun Isaac <arunisaac@systemreboot.net> wrote:

>
> Hi Guix,
>
> I like the idea of teams. And, it's nice to see so many volunteers raise
> their hands!
>
> > * Rust team
> > Efraim Flashner
> > Aleksandr Vityazev
> > Arun Isaac
> > John Soo
> > Maxim Cournoyer
> > Nicolas Goaziou
> > Tobias Geerinckx-Rice
>
> However, I know very little about Rust, and I'm not a good fit for this
> team. I could easily be a part of the python, emacs lisp, common lisp,
> scheme teams, etc if necessary.
>
> But, what I'd really like is to be part of a mumi+tooling team. Maybe we
> should have such a team?
>
> Also, since we have so many ideas for teams, can we have some structured
> way to suggest teams, and add or remove them as needs change?
>
> Regards,
> Arun
>
>

[-- Attachment #2: Type: text/html, Size: 2635 bytes --]

Re: Teams

[raingloom]

I'd definitely love to see an A/V or graphics production team, making
Guix more suitable for artists has been on my TODO list for a while,
even made some tentative steps towards packaging Blender addons.
Personally, I'd love to help out with testing and/or developing Blender
stuff.

On Mon, 13 Jun 2022 13:38:16 +0000
Blake Shaw <blake@sweatshoppe.org> wrote:

> Hi folks,
> 
> I'm just getting back to the list after finishing a gig, but want to
> raise my hand to join both the scheme team and perhaps something like
> an A/V team if folks think that would be a desirable team to put
> together. I think an A/V team would look after:
> 
> #+begin_example scheme
>  (gnu packages gstreamer)
>  (gnu packages gl) ;; Maybe games could handle this?
>  (gnu packages video)
>  (gnu packages graphics)
>  (gnu packages music)
> #+end_example
> 
> Which is quite a lot! So maybe some of this should be split up with
> the "games" team.
> 
> On another note, I'll be getting back to the Guile Docs soon, and
> before that I plan on taking a stab at refactoring the patch
> submission criteria, which I think could use some work. As it is
> currently, it personally becomes a hurdle of a checklist when I want
> to quickly submit a patch, which has lead me to running a hotfix
> branch so that I can quickly fix an issue and move on, therefore
> contributing what I should be. I think it could express all the same
> requirements in less rules, making it easier to ensure what you're
> handing in is in order. But I still need to take a stab at it and see.
> 
> Best,
> 
> On Fri, Jun 10, 2022, 03:29 Arun Isaac <arunisaac@systemreboot.net>
> wrote:
> 
> >
> > Hi Guix,
> >
> > I like the idea of teams. And, it's nice to see so many volunteers
> > raise their hands!
> >  
> > > * Rust team
> > > Efraim Flashner
> > > Aleksandr Vityazev
> > > Arun Isaac
> > > John Soo
> > > Maxim Cournoyer
> > > Nicolas Goaziou
> > > Tobias Geerinckx-Rice  
> >
> > However, I know very little about Rust, and I'm not a good fit for
> > this team. I could easily be a part of the python, emacs lisp,
> > common lisp, scheme teams, etc if necessary.
> >
> > But, what I'd really like is to be part of a mumi+tooling team.
> > Maybe we should have such a team?
> >
> > Also, since we have so many ideas for teams, can we have some
> > structured way to suggest teams, and add or remove them as needs
> > change?
> >
> > Regards,
> > Arun
> >
> >