guix/documentation-manual — Finnish @ Fedora Weblate: Important

Zen

	English	Finnish	Actions
	. [ ?: Cuirass ] Build tree-sitter-meson.aarch64-linux on master is fixed. . [ ?: Cuirass ] Build rust-pbkdf2.aarch64-linux on master is fixed. . [ ?: Cuirass ] Build rust-pbkdf2.x86_64-linux on master is fixed.
	where each RSS entry contains a link to the Cuirass build details page of the associated build.
	commit access, for developers
	Everyone can contribute to Guix without having commit access (@pxref{Submitting Patches}). However, for frequent contributors, having write access to the repository can be convenient. As a rule of thumb, a contributor should have accumulated fifty (50) reviewed commits to be considered as a committer and have sustained their activity in the project for at least 6 months. This ensures enough interactions with the contributor, which is essential for mentoring and assessing whether they are ready to become a committer. Commit access should not be thought of as a ``badge of honor'' but rather as a responsibility a contributor is willing to take to help the project. It is expected from all contributors, and even more so from committers, to help build consensus and make decisions based on consensus. By using consensus, we are committed to finding solutions that everyone can live with. It implies that no decision is made against significant concerns and these concerns are actively resolved with proposals that work for everyone. A contributor (which may or may not have commit access) wishing to block a proposal bears a special responsibility for finding alternatives, proposing ideas/code or explain the rationale for the status quo to resolve the deadlock. To learn what consensus decision making means and understand its finer details, you are encouraged to read @url{https://www.seedsforchange.org.uk/consensus}.
	The following sections explain how to get commit access, how to be ready to push commits, and the policies and community expectations for commits pushed upstream.
	Applying for Commit Access
	When you deem it necessary, consider applying for commit access by following these steps:
	Find three committers who would vouch for you. You can view the list of committers at @url{https://savannah.gnu.org/project/memberlist.php?group=guix}. Each of them should email a statement to @email{guix-maintainers@@gnu.org} (a private alias for the collective of maintainers), signed with their OpenPGP key.
	Committers are expected to have had some interactions with you as a contributor and to be able to judge whether you are sufficiently familiar with the project's practices. It is @emph{not} a judgment on the value of your work, so a refusal should rather be interpreted as ``let's try again later''.
	Send @email{guix-maintainers@@gnu.org} a message stating your intent, listing the three committers who support your application, signed with the OpenPGP key you will use to sign commits, and giving its fingerprint (see below). See @uref{https://emailselfdefense.fsf.org/en/}, for an introduction to public-key cryptography with GnuPG.
	Set up GnuPG such that it never uses the SHA1 hash algorithm for digital signatures, which is known to be unsafe since 2019, for instance by adding the following line to @file{~/.gnupg/gpg.conf} (@pxref{GPG Esoteric Options,,, gnupg, The GNU Privacy Guard Manual}):
	digest-algo sha512
	Maintainers ultimately decide whether to grant you commit access, usually following your referrals' recommendation.
	OpenPGP, signed commits
	If and once you've been given access, please send a message to @email{guix-devel@@gnu.org} to say so, again signed with the OpenPGP key you will use to sign commits (do that before pushing your first commit). That way, everyone can notice and ensure you control that OpenPGP key.
	Important	Tärkeää
	Before you can push for the first time, maintainers must:
	add your OpenPGP key to the @code{keyring} branch;
	add your OpenPGP fingerprint to the @file{.guix-authorizations} file of the branch(es) you will commit to.
	Make sure to read the rest of this section and... profit!
	Maintainers are happy to give commit access to people who have been contributing for some time and have a track record---don't be shy and don't underestimate your work!
	However, note that the project is working towards a more automated patch review and merging system, which, as a consequence, may lead us to have fewer people with commit access to the main repository. Stay tuned!
	All commits that are pushed to the central repository on Savannah must be signed with an OpenPGP key, and the public key should be uploaded to your user account on Savannah and to public key servers, such as @code{keys.openpgp.org}. To configure Git to automatically sign commits, run:
	git config commit.gpgsign true
	# Substitute the fingerprint of your public PGP key. git config user.signingkey CABBA6EA1DC0FF33
	To check that commits are signed with correct key, use:
	To avoid accidentally pushing unsigned or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.
	Commit Policy
	If you get commit access, please make sure to follow the policy below (discussions of the policy can take place on @email{guix-devel@@gnu.org}).
	Ensure you're aware of how the changes should be handled (@pxref{Managing Patches and Branches}) prior to being pushed to the repository, especially for the @code{master} branch.
	If you're committing and pushing your own changes, try and wait at least one week (two weeks for more significant changes) after you send them for review. After this, if no one else is available to review them and if you're confident about the changes, it's OK to commit.

Loading…

copperi

Suggestion accepted

English

Finnish 7 characters edited Current translation Translated

a year ago

anonymous

Suggestion added

English

Finnish 7 characters edited Current translation

a year ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Finnish
No related strings found in the glossary.

String information

Source string description

type: quotation

Flags

ignore-same, no-wrap

Source string location

guix-git/doc/contributing.texi:2637 • guix-git/doc/guix.texi:703 • guix-git/doc/guix.texi:735 • guix-git/doc/guix.texi:21762 • guix-git/doc/guix.texi:35267

String age

2 years ago

Last updated

2 days ago

Source string age

3 years ago

Translation file

po/doc/guix-manual.fi.po, string 698