Hello,
Am Sun, Jul 03, 2022 at 03:04:36PM +0200 schrieb Ricardo Wurmus:
> etc/teams.scm.in is now part of the repository. The configure script
> generates the executable etc/teams.scm.
> Please feel free to add yourself to teams in that file by adding a
> definition like this:
thanks for
On Tue, Jun 21, 2022 at 05:21:11PM +0200, zimoun wrote:
> * Kernel
>
> + Tobias Geerinckx-Rice
Feel free to add my name to the kernel team.
signature.asc
Description: PGP signature
Liliana Marie Prikler writes:
> Am Freitag, dem 01.07.2022 um 12:28 +0200 schrieb Ricardo Wurmus:
>> [...]
>> An example:
>>
>> ./pre-inst-env guile --no-auto-compile -l etc/teams.scm -c '(cc r
>> core)'
>>
>> This prints “git send-email” arguments to Cc members of the R and
>> Core
>>
Am Freitag, dem 01.07.2022 um 12:28 +0200 schrieb Ricardo Wurmus:
> [...]
> An example:
>
> ./pre-inst-env guile --no-auto-compile -l etc/teams.scm -c '(cc r
> core)'
>
> This prints “git send-email” arguments to Cc members of the R and
> Core
> teams when a patch is received by Debbugs.
>
>
Ludovic Courtès writes:
> Ricardo Wurmus skribis:
>
>> Now the question is merely how to represent and present this. It’s not
>> a bad idea to have the team associations in the repository so that we
>> can present the data on the website and also use it with our tools to
>> notify the right
On +2022-06-22 09:56:14 +0300, Efraim Flashner wrote:
> On Wed, Jun 22, 2022 at 12:21:15AM +0200, zimoun wrote:
> > On Tuesday, 21 June 2022, wrote:
> >
> > > On +2022-06-21 17:21:11 +0200, zimoun wrote:
> > > >
> > > > Here below a collection of answers. The teams are more or less. Maybe,
> >
Hi y'all,
This looks great, thanks for putting in the work!
Im getting back into the Guile + Guix documentation, and realize its a
subject the @whereiseveryone and others are also working on, and thus it
could probably use a concentrated team of its own. What do others think?
Best,
Blake
On
Hi,
Ricardo Wurmus skribis:
> Now the question is merely how to represent and present this. It’s not
> a bad idea to have the team associations in the repository so that we
> can present the data on the website and also use it with our tools to
> notify the right people.
Mathieu suggested
Josselin Poiret schreef op wo 22-06-2022 om 14:30 [+0200]:
> Hello,
>
> zimoun writes:
> > Then maybe, we could hook Mumi and add regexps based on commit messages
> > for notifying a specific team. Well, it is a rough approximation with
> > many false-positive but hey the aim is to deal with
Hello,
zimoun writes:
> Then maybe, we could hook Mumi and add regexps based on commit messages
> for notifying a specific team. Well, it is a rough approximation with
> many false-positive but hey the aim is to deal with patches so these
> false-positive do not matter, IMHO.
Maybe we could
Hi Ricardo,
On Wed, 22 Jun 2022 at 09:59, Ricardo Wurmus wrote:
> I also wonder about how / if we should notify teams about relevant
> patches. Will contributors Cc the relevant teams or will we have team
> predicates, e.g. a procedure that spits out the appropriate teams when
> given a patch?
Hi simon,
> Here below a collection of answers. The teams are more or less. Maybe,
> we could join some for having another structure. WDYT?
Thank you for the initiative! I had been meaning to go through the
whole thread and collect and organize all submissions, but you’ve done
all the work
On Wed, Jun 22, 2022 at 12:21:15AM +0200, zimoun wrote:
> On Tuesday, 21 June 2022, wrote:
>
> > On +2022-06-21 17:21:11 +0200, zimoun wrote:
> > >
> > > Here below a collection of answers. The teams are more or less. Maybe,
> > > we could join some for having another structure. WDYT?
> >
> >
On Tuesday, 21 June 2022, wrote:
> On +2022-06-21 17:21:11 +0200, zimoun wrote:
> >
> > Here below a collection of answers. The teams are more or less. Maybe,
> > we could join some for having another structure. WDYT?
>
> Where is the RISC/MES team? :)
>
Embeded / Bootstrap ;-)
On +2022-06-21 17:21:11 +0200, zimoun wrote:
>
> Here below a collection of answers. The teams are more or less. Maybe,
> we could join some for having another structure. WDYT?
Where is the RISC/MES team? :)
caton...@gmail.com writes:
I asked for indications about the process (what magic to use in
the
REPL)
My experience with Guix, in general, is that the REPL isn't
particularly useful for any task beyond very simple testing (eg,
what are the contents of ‘%base-services’). It's a shame, but
Blake Shaw schreef op do 16-06-2022 om 06:20 [+0700]:
> But, perhaps it's just getting late and the matters are now & the
> details are slipping my mind, but im starting to realize im unsure of
> many examples of file-like objects that aren't a file? The email
> where you responded re: packages
caton...@gmail.com writes:
> Ricardo, the general map of the concepts involved in conceiving a
> service is useful
>
> But in my toot I asked for something different
>
> I asked for indications about the process (what magic to use in the
> REPL)
There is no REPL magic. I write the service in
Il giorno mer, 15/06/2022 alle 17.01 +, Blake Shaw ha scritto:
>
> Catonano:
> I think writing a home-service is much easier given that you don't
> need to do produce an entire system generation before you find out
> what you did wrong;
I suspected something like this
This is why I
Thanks for the feedback, abelian groups are a good example because so many
groups are abelian (fields etc).
But, perhaps it's just getting late and the matters are now & the details
are slipping my mind, but im starting to realize im unsure of many examples
of file-like objects that aren't a
Blake Shaw schreef op wo 15-06-2022 om 21:40 [+]:
> On the contrary, lets say I'm writing an intro book on CT. If I'm
> demonstrating something trivial, say the initial object, I'm not
> going to refer to it as "an initial-like object" for the sake of
> generality.
Neither does Guix? If
Blake Shaw schreef op wo 15-06-2022 om 21:40 [+]:
> > AFAIK no relation to GNU.
>
> I thought recalled hearing it used in relation to GNU/Linux. A quick
> search
> brings up this stackexchange discussion[1], which quotes the book
> "Linux
> Philosophy" with the following:
>
> #+begin_example
Blake Shaw schreef op wo 15-06-2022 om 21:40 [+]:
> > Something I dislike about the ‘file AND file-like objects’
> > construction
> > is that it suggests that files and file-like objects are separate
> > and
> > are handled separately, whereas files (as in, 'local-file' or
> > 'computed-file')
Blake Shaw schreef op wo 15-06-2022 om 17:01 [+]:
> Thats very good advice and will be a useful guide in refactoring the
> parts of the system services documentation. I think in general, we
> need to find a nice middle ground between the extremely general and
> the immediately sensible, as I
Ricardo:
Thats very good advice and will be a useful guide in refactoring the parts
of the system services documentation. I think in general, we need to find a
nice middle ground between the extremely general and the immediately
sensible, as I remember when I first got into guix 1.5 years ago,
caton...@gmail.com writes:
> Il giorno mer, 15/06/2022 alle 01.52 +0700, Blake Shaw ha scritto:
>>
>> 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.
>
>
Il giorno mer, 15/06/2022 alle 01.52 +0700, Blake Shaw ha scritto:
>
> 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.
This is something I'm specifically
Il giorno mer, 15/06/2022 alle 01.52 +0700, Blake Shaw ha scritto:
>
> 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.
I'm specifically interested in this
On Tue, 14 Jun 2022 08:47:37 -0400 guix-devel-requ...@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
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
On 2022-06-05 10:19, Josselin Poiret wrote:
> Hello everyone,
>
> Ricardo Wurmus 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
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
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
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
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
Hello,
Ludovic Courtès writes:
> Vagrant Cascadian 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
Vagrant Cascadian 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
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
On Sun, Jun 05, 2022 at 11:51:20AM +0200, zimoun wrote:
> Hi Ricardo,
>
>
> > * R team
> > Simon Tournier
> > Ricardo Wurmus
>
> In addition, add me to:
>
> * Julia team
I can do the Julia team too.
--
Efraim Flashner אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D
"pelzflorian (Florian Pelz)" writes:
> On Sat, Jun 04, 2022 at 02:50:49PM +, 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
On Saturday, June 4th, 2022 at 12:07 PM, Ricardo Wurmus
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
Hi,
Mathieu Othacehe 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
Hi!
Josselin Poiret 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’.
Hi Ricardo,
Ricardo Wurmus 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
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
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,
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 wrote:
>Hi Ricardo,
>
>On Sat, 04 Jun 2022 at 14:07, Ricardo Wurmus wrote:
>
>> As a first step I’d
Hi Ricardo,
On Sat, 04 Jun 2022 at 14:07, 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:
Well, a team per build system would fit more or less the needs,
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
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?
On Sat, Jun 04, 2022 at 02:50:49PM +, 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
Hello everyone,
Ricardo Wurmus 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
On 4 June 2022 12:07:15 UTC, Ricardo Wurmus 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
Tobias Geerinckx-Rice schreef op za 04-06-2022 om 14:50 [+]:
> 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
On 4 June 2022 12:07:15 UTC, Ricardo Wurmus 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,
> 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
>
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.
57 matches
Mail list logo
