stsquad,
@stsquad@mastodon.org.uk avatar

It seems the topic of vs based workflows in software is a topical subject so I thought it an opportunity to generate a blog post: https://www.bennee.com/~alex/blog/2023/10/22/comparing-forge-based-and-email-based-workflow-for-open-source-projects/#comparing-forge-based-and-email-based-workflow-for-open-source-projects

You can comment by replying to this thread.

penguin42,
@penguin42@mastodon.org.uk avatar

@stsquad I think some of the cons of the email based systems are that you can easily lose a patch with no one reviewing or merging it; most of the forge based systems are better at tracking patches in flight. The forge based systems should be doing line-by-line review most do don't they?

stsquad,
@stsquad@mastodon.org.uk avatar

@penguin42 yeah this is where tooling helps. helps tame the mess of searching your email feed to find series missing reviews.

When I talk about line by line I mean at the commit level. In most forges I end up reviewing stuff on the PR diff view which is fine if PRs are small and self contained. We do suffer somewhat in by having some mega-cleanup series which is a lot to wade through.

penguin42,
@penguin42@mastodon.org.uk avatar

@stsquad Yes, the forges seem to be quite opinionated about whether you should be working at PR or commit level; which is a shame since it varies by task. Geritt is quite nice at the individual commit level but has very little at a PR layer. I find Gitlab the opposite - flexibility would be nice. I didn't find patchew helped me that much.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • email
  • DreamBathrooms
  • mdbf
  • ngwrru68w68
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • osvaldo12
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • InstantRegret
  • tacticalgear
  • anitta
  • ethstaker
  • provamag3
  • cisconetworking
  • tester
  • GTA5RPClips
  • cubers
  • everett
  • modclub
  • megavids
  • normalnudes
  • Leos
  • JUstTest
  • lostlight
  • All magazines