+1 from me (not that my opinion should count for much here)
From: Manfred Moser <manf...@simpligility.ca> Date: Monday, 6 January 2025 at 16:51 To: dev@maven.apache.org <dev@maven.apache.org> Subject: Re: Using git forks This email was sent to you by someone outside the University. You should only click on links or attachments if you are certain that the email is genuine and the content is safe. Hi all, Let me chime in as Maven committer (mostly inactive but involved on various external fronts) and core maintainer of Trino. Trino had over 200 separate contributors in our repo in 2024. We only have about a dozen maintainers and none of us really has the time to worry about branches in the main repo and mgt. We do distributed development with git. Everyone has at least a personal fork and and also probably works on one or more other private forks for companies. Maintainers (like committers in Maven) have the right to create branches but we nearly never do because that forces noise on all other maintainers and all other contributors (simple git pull for example). It is more convenient to do for CI runs that require secrets but even there we avoid the overhead and use personal forks with a custom feature to run PRs from forks with secrets. Maintaining and managing a public repo for a big project like Maven or Trino is a LOT of work. I hope everyone can do their part by keeping their work in their own fork and only exposing anyone else to it when required for review purposes. GitHub makes managing your own forks very easy. Let's use git as intended to all our benefit. The core Maven repos for the project should be as slim and simple as possible and not contain any personal branches or features or tags or whatever. Manfred On 2025-01-06 8:02 a.m., Tamás Cservenák wrote: > Howdy, > > This is all nice and dandy with you explaining how things are done in > companies, but this is NOT one of them, this is an open source > project. > > Somewhere in the future, when you are gone from the project, NOBODY > will know what these branches are for (unless they do some archaeology > exploration, that again, is time consuming, on a project with already > scarce resources). There is no "management" who will instruct new > members "clean up Elliotte branches, please", there is nobody who > "tracks the work progress" or "manages" this project. We are all pawns > on the table. > > Thanks > T > > On Mon, Jan 6, 2025 at 4:53 PM Tamás Cservenák <ta...@cservenak.net> wrote: >> Howdy, >> >> And I guess fixing the mailing list will also take care of all your >> branches in canonical repo, if a bus hits you tomorrow... >> >> On Mon, Jan 6, 2025 at 4:40 PM Elliotte Rusty Harold <elh...@ibiblio.org> >> wrote: >>> On Mon, Jan 6, 2025 at 3:33 PM Tamás Cservenák <ta...@cservenak.net> wrote: >>>> This is just utterly silly: I am NOT interested at all in your branches: >>>> >>> I don't expect you to be. Ignore them. The problem is not that the >>> branches exist. It is that the mailing list is bothering you with >>> them. Fix the mailing list. >>> >>> -- >>> Elliotte Rusty Harold >>> elh...@ibiblio.org >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
