Re: git: d128a409234d - main - editors/xed: update to 3.2.4
- In reply to: Alexey Dokuchaev : "Re: git: d128a409234d - main - editors/xed: update to 3.2.4"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 05 Jul 2022 13:25:23 UTC
------- Original Message ------- On Tuesday, July 5th, 2022 at 15:04, Alexey Dokuchaev <danfe@freebsd.org> wrote: > > > On Tue, Jul 05, 2022 at 02:38:07PM +0200, Jochen Neumeister wrote: > > Anyone who creates a port is allowed to use that line, even if they > > later give that port to someone else. > > Exactly right. We even try to retain it when deleted port is brought > back from the attic. FreeBSD had traditionally been very careful with > handling author attribution; please do not break this tradition Charlie. It is not the first time I see confusion about how "Created by" lines should be managed. It seems to me that everyone has different opinion on the topic. For example, when I first started contributing (2018 I think) and I was not a committer yet, I had been told those lines were deprecated and the committer that took my new port patch removed my line, which goes against what you just wrote. (Please keep in mind that some years have passed, I might remember the story a bit wrong and as I was a new contributor I might also have misunderstood something.) I believe the only way to fix confusion is to have clear policies: somewhere (porter's handbook?) someone (portmgr?) should write an official way to deal with those lines. I don't think we have such an official policy yet, isn't it? As for the particular issue we have here, I would like to remind everyone: - that this discussion is public: users subscribed to the mailing lists might not be interested in the argument and you might write something by accident that you would not want to leave in the archives; - whatever solution you agree on in the end, we have a version control system, with all the details about who created what; - since we do not have a clear policy about "Created by:" lines (at least as far as I know), if your case is very special, you might solve your issue by agreeing on some different kind of comment, for example you might have "Originally created by: ..." and "Reworked extensively by: ...". Cheers, Lorenzo Salvadore