Hey Richard,
On 21.11.22 11:02, Richard Hughes wrote:
On Sun, 20 Nov 2022 at 11:04, Nico Huber nico.h@gmx.de wrote:
Are you suggesting that you didn't keep track in the past three years? What sort of track keeping are you referring to here?
I meant to say I didn't keep track if anything happened to older patches.
I'm a bit confused; I didn't think you were a maintainer anymore?
yes, that's right. It wasn't exactly a formal position but I said I wouldn't do it anymore end of January 2020.
Surely the maintainer team are the ones who decide what the release from which branch?
I don't know an official maintainer team. We tried kind of some grassroots democracy this year. But that didn't work too well, can't even agree on a communication channel.
It seems a bit rich to just walk back in as a contributor and want to undo the last three years of changes...
When I walked back (a little more than a year after I left, IIRC) I simply tried to pick up what nobody else did (releases and such). Didn't work out well because I have no intention to force anybody into anything. I merely try to discuss things on this mailing list. This thread could provide some ideas how to move on or not. If I'd decide to do anything what is discussed here, that doesn't have to mean any- thing for the current master branch. That's not up to me to decide. People can decide to go on there, that's up to them.
Rewinding on another branch doesn't mean anything gets undone. Some- times going a step back can make it easier to eventually move forward. A second branch could also be part of an official solution (e.g. the compromise in [1] or something else), it could eventually pull all the patches from the current master branch once they are ready for a release. There are many ways.
So, Richard, do you want to tell us how you would do it?
Nico
[1] https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.org/thread/3K2ZE...