unofficial mirror of guix-devel@gnu.org 
 help / color / Atom feed
From: Leo Famulari <leo@famulari.name>
To: brettg@posteo.net
Cc: Guix devel <guix-devel@gnu.org>
Subject: Re: Returning to the project
Date: Fri, 26 Jun 2020 23:00:29 -0400
Message-ID: <20200627030029.GA26245@jasmine.lan> (raw)
In-Reply-To: <04d0baf90ed7955cf5f93eeddcd40fee@posteo.net>

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

On Sat, Jun 27, 2020 at 12:59:36AM +0200, brettg@posteo.net wrote:
> I think some of you may member me. I am a committer to the Guix project who
> took a hiatus after my son was born. I am returning from that hiatus and
> would love to begin contributing again.

Welcome back!

Please upload your new key to your account on Savannah:

https://savannah.gnu.org/users/brettgilio

> I have a new set of PGP keys, and am curious about the method to get back
> into a position where contributions can be made. If anybody can help guide
> me in the right direction it would be appreciated!

The contribution workflow is mostly the same, but here are the two
noteworthy changes I can think of:

First, the cutoff between the 'staging' and 'core-updates' branches was
increased from 1200 to 1800 package rebuilds [1].

Second, the signatures of the Git commits are used in more parts of Guix
than before [2]. You'll need to make some tweaks related to this.

The pre-push Git hook has improved from simply checking that commits are
signed. It now also makes sure those signatures were made by approved
committers. So make sure you're using the latest version of the hook
script found at 'etc/git/pre-push' in our Git repo, in order to avoid
mistakes.

The hook runs the new `make authenticate` Makefile target, which is
worth getting to work before needing to push. You'll need to fetch the
'keyring' Git branch and keep it around in your copy of the repo.

The HACKING file turned into a chapter in the manual, and item #4 has
some more info about these GPG-related changes [3]. Also more info at
the end of Building From Git [4].

[1] See item #8:
https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html

[2]
https://issues.guix.gnu.org/issue/22883#89

[3]
https://guix.gnu.org/manual/en/html_node/Commit-Access.html

[4]
https://guix.gnu.org/manual/en/html_node/Building-from-Git.html

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

  parent reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 22:59 brettg
2020-06-27  0:16 ` John Soo
2020-06-27  3:00 ` Leo Famulari [this message]
2020-06-28 20:48 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200627030029.GA26245@jasmine.lan \
    --to=leo@famulari.name \
    --cc=brettg@posteo.net \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

unofficial mirror of guix-devel@gnu.org 

Archives are clonable:
	git clone --mirror https://yhetil.org/guix-devel/0 guix-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-devel guix-devel/ https://yhetil.org/guix-devel \
		guix-devel@gnu.org
	public-inbox-index guix-devel

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.devel
	nntp://news.gmane.io/gmane.comp.gnu.guix.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git