On 5/1/24 10:38 AM, Maciej Barć wrote: > Ionen, I think that regular contributors could skip this altogether. For > example the person I'm mentoring I am sure would follow all requirements > listed by mgorny and me (see my reply).
Regular contributors might not even be submitting via PRs at all. :P >> On a side-note, I have nothing against having .github in the tree. Just >> saying given I know not everyone is happy with that. > > I think we should push more into "conforming" to standard of online > software forges. Reminder that we STILL do not have any form of a README > file. Not even one that would say "Hey look at https://gentoo.org/";. > Also no license link. Afaik all contribs are under GPL-2. Every file has a copyright header: # Distributed under the terms of the GNU General Public License v2 It's not clear to me what more you want than this, or who it would help. A README could be useful to github I guess, but on the other hand the main purpose of a README is to tell people who don't know what a repository is for, what that repository is for. Would it basically duplicate the contents of https://wiki.gentoo.org/wiki/Ebuild_repository or is there something else you want to see in a README? I don't think "Hey look at https://gentoo.org"; is remotely useful as a README, compared to what is already there: [MIRROR] Official Gentoo ebuild repository https://gitweb.gentoo.org/repo/gentoo.git which is already quite explanatory in ways that a noncommittal link to the gentoo homepage is NOT. -- Eli Schwartz
OpenPGP_0x84818A6819AF4A9B.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
