Re: Formalizing teams

Hi David, david larsson skribis: > On 2022-01-03 16:22, Ludovic Courtès wrote: [...] >> This brings a related but slightly different topic: how to let >> people >> filter incoming patches and bug reports in general. >> How does it even work on git*.com? Do they let you subscribe to >> issues/

Re: Formalizing teams

On 2022-01-03 16:22, Ludovic Courtès wrote: I suppose people could explicitly Cc: the team you’re on when they need specific advice or review; that should already help. Having some topic-specific streams I could tap into would allow me to be a little more proactive. This brings a related bu

Re: Formalizing teams

Il giorno lun, 03/01/2022 alle 16.22 +0100, Ludovic Courtès ha scritto: > This brings a related but slightly different topic: how to let people > filter incoming patches and bug reports in general. > > How does it even work on git*.com?  Do they let you subscribe to > issues/merge requests that

Re: Formalizing teams

Ludovic Courtès writes: >> Having some topic-specific streams I could tap into would allow me to be >> a little more proactive. > > This brings a related but slightly different topic: how to let people > filter incoming patches and bug reports in general. On issues.guix.gnu.org we could offer

Re: Formalizing teams

Hi! ⛄ Ricardo Wurmus skribis: > Maxim Cournoyer writes: [...] >> We'd have to include every language/system of importance to that list >> (Python, Ruby, Emacs, LaTeX, Perl, etc.), no? > > No, only those where we already have the people who could form a team. > There is no need for any of this

Re: Formalizing teams

Hello, Filip Łajszczak skribis: > Great idea. As a newcomer who created his first patch in May > https://issues.guix.gnu.org/issue/48289/ that got a review, was fixed > and submitted again, and then disappeared into oblivion, I would be > very happy to be able to ask some "Python packaging" tea

Re: Formalizing teams

Hi Ricardo, > FWIW, mumi also lets you search patches as all contents are indexed: > > https://issues.guix.gnu.org/search?query=%22%28gnu+packages+python-web%29%22+is%3Aopen+tag%3Apatch thanks, I didn’t think about that. I tried searching for python-build-system, but not all patches – especia

Re: Formalizing teams

On Tue, Dec 28, 2021 at 03:44:55PM +0100, Ricardo Wurmus wrote: > > Maxim Cournoyer writes: > > >> Guix is nowhere near the size of the Rust community (yet!), but I can > >> already picture teams and members: > >> > >> co-maintainers (“core team”) > >> community > >> infrastructure > >>

Re: Formalizing teams

Kyle Meyer writes: > Fwiw public-inbox indexes the file name from diffs, so you might find > searching with the "dfn:" against the archive at > useful. For example: > > https://yhetil.org/guix-patches/?q=dfn%3Agnu%2Fpackages%2Fpython-web.scm FWIW, mumi also

Re: Formalizing teams

Lars-Dominik Braun writes: > Hi Maxim, > >> I've grown to like our apparent lack of structure; we interact globally >> on any topic of interest and the discussions all happen in a shared >> space, which makes it easy to stay informed with everything that's going >> on (do we really need more maili

Re: Formalizing teams

Maxim Cournoyer writes: >> Guix is nowhere near the size of the Rust community (yet!), but I can >> already picture teams and members: >> >> co-maintainers (“core team”) >> community >> infrastructure >> internationalization >> security response >> release >> Rust packaging >> R

Re: Formalizing teams

Hi Maxim, > I've grown to like our apparent lack of structure; we interact globally > on any topic of interest and the discussions all happen in a shared > space, which makes it easy to stay informed with everything that's going > on (do we really need more mailing lists to follow? I don't think

Re: Formalizing teams

Hi Ludovic, Ludovic Courtès writes: > Hello Guix! > > I’ve been looking at our guix-patches backlog, at the great > contributions we get but that stick there for too long, certainly > discouraging people, and also at non-code initiatives (meetups, Guix > Days, Outreachy, documentation, etc.) tha

Re: Formalizing teams

Good catch! TBH, I did wonder whether the feudal eptimology of the English word may raise eyebrows. Hartmut Goebel writes: > Am 23.12.21 um 22:51 schrieb Jonathan McHugh: >> I reckon 'coterie' is more elegant a term: > > IMHO we chould not use this term. > > The German translation is "Seilschaf

Re: Formalizing teams

Am 23.12.21 um 22:51 schrieb Jonathan McHugh: I reckon 'coterie' is more elegant a term: IMHO we chould not use this term. The German translation is "Seilschaft", "Klüngel" - both of which have negative meaning: Working together to the benefit of the members of the group only - ignoring comm

Re: Formalizing teams

December 23, 2021 4:13 PM, "Blake Shaw" wrote: > Ludovic Courtès writes: > >> One idea that I like is to bring structure to the group, or rather to >> make structure visible, so that newcomers know who they can talk to to >> get started on a topic, know who to ping for reviews, and so that each

Re: Formalizing teams

Ludovic Courtès writes: > One idea that I like is to bring structure to the group, or rather to > make structure visible, so that newcomers know who they can talk to to > get started on a topic, know who to ping for reviews, and so that each > one of us can see where they fit. Rust has well-defi

Re: Formalizing teams

On 22/12/2021 15.46, Ludovic Courtès wrote: I’ve been looking at our guix-patches backlog, at the great contributions we get but that stick there for too long, certainly discouraging people, [...] One idea that I like is to bring structure to the group, or rather to make structure visible, s

Re: Formalizing teams

Its certainly worth developing more formal clusters. It would be wise to try and make concerns and research interconnected - lest we create silos that communicate with other groups less. Jonathan McHugh Jack Hill writes: > On Wed, 22 Dec 2021, Ludovic Courtès wrote: > >> Hello Guix! >> >> I’v

Re: Formalizing teams

On Wed, 22 Dec 2021, Ludovic Courtès wrote: Hello Guix! I’ve been looking at our guix-patches backlog, at the great contributions we get but that stick there for too long, certainly discouraging people, and also at non-code initiatives (meetups, Guix Days, Outreachy, documentation, etc.) that w

Formalizing teams

Hello Guix! I’ve been looking at our guix-patches backlog, at the great contributions we get but that stick there for too long, certainly discouraging people, and also at non-code initiatives (meetups, Guix Days, Outreachy, documentation, etc.) that we as a project could often support and encourag