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

Zen

Translation

English type: quotation

Turkish

Needs editing

Skip

	English	Turkish	Actions
	A contributor (who 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}.
	commit access, for developers	geliştiriciler için erişim sağlama
	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.
	Committers are in a position where they enact technical decisions. Such decisions must be made by @emph{actively building consensus} among interested parties and stakeholders. @xref{Making Decisions}, for more on that.
	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	Taahhüt Erişimine Başvurmak
	When you deem it necessary, consider applying for commit access by following these steps:	Gerekli gördüğünüzde, aşağıdaki adımları izleyerek kesin erişim başvurusunda bulunmayı düşünün:
	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}):	GnuPG'yi, 2019'dan beri güvensiz olduğu bilinen dijital imzalar için SHA1 karma algoritmasını asla kullanmayacak şekilde ayarlayın, örneğin aşağıdaki satırı @file{~/.gnupg/gpg.conf} (@pxref{GPG) öğesine ekleyerek Ezoterik Seçenekler,,, gnupg, The GNU Privacy Guard Manual}):
	digest-algo sha512	özet-algo sha512
	Maintainers ultimately decide whether to grant you commit access, usually following your referrals' recommendation.	Bakımcılar, genellikle önerilerinizi dinleyerek, size erişim izni verip vermemeye karar verirler.
	OpenPGP, signed commits	OpenPGP, imzalanmış taahhütler
	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	Önemli
	Before you can push for the first time, maintainers must:	İlk kez push yapman önce, maintainerlar şunları yapmalıdır:
	add your OpenPGP key to the @code{keyring} branch;	OpenPGP anahtarınızı @code{keyring} brachına ekleyin;
	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!	Bu bölümün geri kalanını okuduğunuzdan emin olun ve... kazançlı çıkın!
	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!	Bakımcılar, bir süredir katkıda bulunan ve bir geçmişe sahip kişilere erişim vermekten mutluluk duyarlar --- utangaç olmayın ve işinizi küçümsemeyin!
	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:	Savannah'daki depoya gönderilen tüm taahhütler bir OpenPGP anahtarıyla imzalanmalıdır ve ortak anahtar Savannah'daki kullanıcı hesabınıza ve @code{keys.openpgp.org} gibi ortak anahtar sunucularına yüklenmelidir. Git'i taahhütleri otomatik olarak imzalayacak şekilde yapılandırmak için şunu çalıştırın:
	git config commit.gpgsign true	git config commit.gpgsign true
	# Substitute the fingerprint of your public PGP key. git config user.signingkey CABBA6EA1DC0FF33	# Genel PGP anahtarınızın parmak izini değiştirin. git config user.signingkey CABBA6EA1DC0FF33
	To check that commits are signed with correct key, use:
	@xref{Building from Git} for running the first authentication of a Guix checkout.
	To avoid accidentally pushing unsigned or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.	@file{etc/git/pre-push} konumunda bulunan pre-push Git kancasını kullanarak imzasız taahhütleri yanlışlıkla Savannah'ya gönderilmesini önleyebilirsiniz:
	Commit Policy	Sözleşme Politikası
	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}).	Taahhüt erişimi alırsanız, lütfen aşağıdaki politikaya uyduğunuzdan emin olun (politika tartışmaları @email{guix-devel@@gnu.org} adresinde yapılabilir).
	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.

Loading…

009asto

Translation added

English

Turkish 6 characters edited Current translation Translated

2 years ago

None

String updated in the repository

English

Turkish 0 characters edited Empty

2 years 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	Turkish
No related strings found in the glossary.

10442125 String information

Source string description

type: quotation

Flags

ignore-same, no-wrap

Source string location

guix-git/doc/contributing.texi:2827 • guix-git/doc/guix.texi:722 • guix-git/doc/guix.texi:754 • guix-git/doc/guix.texi:22728 • guix-git/doc/guix.texi:36675 • guix-git/doc/guix.texi:37710

String age

2 years ago

Last updated

13 hours ago

Source string age

4 years ago

Translation file

po/doc/guix-manual.tr.po, string 755

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.