On 2024-02-29 02:00, savannah-hackers-requ...@gnu.org wrote:
Message: 1 Date: Wed, 28 Feb 2024 16:01:58 +0000 From: Ineiev <ine...@gnu.org> To: savannah-help-pub...@gnu.org Subject: Re: Extremely large change wave? Message-ID: <20240228160158.GA7755@manas> Content-Type: text/plain; charset="utf-8"On Tue, Feb 27, 2024 at 05:48:47PM -0700, Bob Proulx wrote:> I believe the most important change from Savannah admins' viewpoint > wasn't in fact in the code....That's a good example of a fundamental change which had no communication nor coordination. Though it is a change that I would generally support. But the result is that it leaves everyone else lost at sea without any footing. > I did it on Jan, 31, when migrating to frontend2, and I mentioned > I was going to do that even earlier, when the fundraiser was > running. This detail must have been missed in the communications.That's true, I'm a lousy communicator. I beg for indulgence.
Please try to do better. I'm not good at communications myself either and I'm finding ways to improve.
[...]
The files you work with in your local sandbox may have been there for years and no one else will have been able to see them, to view them, to comment upon them, or even to know if they are happening at all. Those private dates do not matter. The only dates that matter are the dates when they become visible to us.... I'm glad you recognize that. I have no habit of working on Savane privately, I rarely push later than the same day I write the commit. and in particular, preliminary but functional versions of the commit I mentioned, 9fd58ef254ab, and the subsequent 91cf0c8012, were in the official Savane repository on 2023-09-19 or earlier (I've just checked the oldest occasional backup I have). IIRC Jing Luo commented upon them in December, and I don't recall reports for any issues with finding the development sources. And I hope your note applies to other people to a degree.
Please don't drag me into this. I have been working on my own local repo (branch i18n) since late November. When the savane repo is updated, at first I would pull and merge from upstream i18n, but then the force updates would disrupt everything I was working on. Rebase or cherrypick would not be a plausible option either. I suspected that Ineiev force pushes to i18n so as to discourage contributions, I even thought i18n was an abbreviation of "Ineiev" because someone seems to own that branch to himself.
As long as any branch is force pushed, the only dates matter to me are the ones showing in "git log". They are re-written everyday as i18n is force pushed everyday. I won't be able to look at any pending changes before they are merged to "master" or now the new branch "frontend". It's just full of surprises when I refresh the savane.git cgit page.
Also, if I didn't mention this earlier, please do NOT call me my full legal name. Only my parents do that, and it's very unpleasant.
-- Jing Luo About me: https://jing.rocks/about/ PGP Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC
signature.asc
Description: OpenPGP digital signature
