Project Talk:GURU/Information for Contributors

From Gentoo Wiki
Jump to:navigation Jump to:search
Note
Before creating a discussion or leaving a comment, please read about using talk pages. In particular, sign comments using ~~~~ and add new discussions at the bottom of the page. New discussions should be made visible with {{Talk|date = 2024-05-22}}.
== Discussion title ==

{{Talk|date = 2024-05-13}}

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 11:29, 14 May 2024 (UTC)
:: Another reply [[User:Larry|Larry]] 12:57, 22 May 2024 (UTC)
:: Your reply ~~~~

Navigate to first:

@gentoo.org mail address

Talk status
This discussion is still ongoing.

A short information or reference to such information about how to apply for the @gentoo.org email adress wich is needed for Generating GLEP-63-based OpenPGP keys would be very helpful.
--Charles17 (talk) 10:49, 30 March 2020 (UTC)

Become a Gentoo developer. That's the only way to get a gentoo.org email. --Grknight (talk) 12:33, 30 March 2020 (UTC)
So becoming a contributor to GURU requires being a Gentoo developer? '...following GLEP 63 rules is recommended: 6. UID using your @gentoo.org e-mail included in the key.' --Charles17 (talk) 13:12, 30 March 2020 (UTC)
In this context, I would have interpreted that contributors should use the preferred e-mail address specified in the access request they filed (where bug mail and other communications would be sent to), but let's see what developers say — GuillermoDH (talk) 14:57, 31 March 2020 (UTC
When reading that, I interpreted "following GLEP 63 rules is recommended" to mean "following GLEP 63 rules as much as possible is recommended." I think the wording should be clarified to say something along those lines since non-devs won't be able to get an @gentoo.org email. The main project page, section The regulations already has a similar "try your best to follow the official standards"-vibe:

3. While following Gentoo ebuild policies and quality standards is recommended, it will not be strictly enforced.

xxc3nsoredxx (talk) 21:49, 23 February 2021 (UTC)
Thanks, I've updated it to say that. Michał Górny (talk) 06:48, 24 February 2021 (UTC)

git rebase --preserve-merges is deprecated

Talk status
This discussion is still ongoing as of 2020-04-05.
warning: git rebase --preserve-merges is deprecated. Use --rebase-merges instead.

This should be updated.--Charles17 (talk) 13:09, 5 April 2020 (UTC)

DCO_SIGNED_OFF_BY is deprecated

Talk status
This discussion is done.

DCO_SIGNED_OFF_BY is deprecated in favor of SIGNED_OFF_BY (See make.conf(5)). --Tastytea (talk) 14:09, 11 April 2020 (UTC)

Done. Michał Górny (talk) 14:00, 26 February 2021 (UTC)

Repoman is deprecated and therefore is SIGNED_OFF_BY in make.conf

Talk status
This discussion is still ongoing.

We changed instructions to use pkgdev in favor of repoman, as repoman is deprecated and will be removed soon. Pkgdev does not look into make.conf for SIGNED_OFF_BY, it only takes this configuration from the git config. (See Pkgdev#pkgdev_doesn.27t_sign-off_my_commits) I think this also applies to PORTAGE_GPG_KEY. -- Schievel (talk) 11:41, 15 October 2022 (UTC)