I honestly don’t understand* the brouhaha about notification summaries. The only way to deal with notifications is turning them off, with fire of need be, except for meetings about to begin. I get like two notifications a day, three if it’s a meeting heavy Tuesday.
Try it. Turn them off.
*I understand that summaries are shit, but the solution is not lossy compression, it’s less input.
@Infoseepage you need to factor in land, electrical infra and battery storage to get to similar behaviour, that will reduce the multiplier by quite a bit, but it will still be substantial :)
> The ASF is Hiring a Senior Engineer, Tooling to develop important foundation tools to improve the secure supply chain for ASF releases, along with delivering software systems to help streamline foundation operations, such as the Board Agenda tool.
—
You’ll be hard pressed to find a more impactful position that is paid and open source. Please come and help us :)
Had a git workflow epiphany this morning because it went (mildly) badly for the second or third time and I’m finally seeing the pattern:
Very early on in a project, when folder structure, naming conventions and little test-spike-code are all being tried out, a PR based workflow is worse because the nature of the changes will likely make the PRs long running, because lots has to be nailed down before it is “good”…
… but it will definitely make integrating all PRs take forever because they touch so much structure.
The alternative is everyone committing to main/trunk and forbidding force pushes. The trade-off is that everybody has to deal with everybody else’s changes, but it will be a net benefit because those integration decisions happen closer to the changes and and committers likely working time overlapping for out of band coordination.
25 years on the web.Makes CouchDB, PouchDB & Offline First.CEO at @neighbourhoodie.ASF Member & CouchDB PMC Chair.Made JSConf EU, Greenkeeper, Hoodie, Mustache.js.Dissatisfied with the status-quo.Soft Boy. Likes birds, bikes & bees.:zeldalink: