this post was submitted on 03 Sep 2023
6 points (100.0% liked)

Programming

17450 readers
75 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

I've said this previously, and I'll say it again: we're severely under-resourced. Not just XFS, the whole fsdevel community. As a developer and later a maintainer, I've learnt the hard way that there is a very large amount of non-coding work is necessary to build a good filesystem. There's enough not-really-coding work for several people. Instead, we lean hard on maintainers to do all that work. That might've worked acceptably for the first 20 years, but it doesn't now.

[…]

Dave and I are both burned out. I'm not sure Dave ever got past the 2017 burnout that lead to his resignation. Remarkably, he's still around. Is this (extended burnout) where I want to be in 2024? 2030? Hell no.

you are viewing a single comment's thread
view the rest of the comments
[–] Deathcrow@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

Similarly moving on to a decent issue tracker, Jira’s support for Epic’s/stories/tasks/capabilities and its linking ability is a huge simplifier for long term planning.

Modern ticket system or issue tracker? Yes, absolutely. But Jira? Certainly not, considering Atlassian's business practices. A project like Linux deserves a system where they can maintain some control and it probably should be open source.

Yeah email is ancient and certainly terrible from a usability perspective if you're an outsider to the workflows, but at least it can't be shut off or taken away on a whim. Also it's universal and therefore accessible.

[–] MajorHavoc@lemmy.world 1 points 1 year ago

Yeah. If core Linux teams publicly adopt an open source KanBan board, issue tracker, and code review tool, I am a lot more likely to adopt and help maintain those products.

I have no interest in navigating the politics and history to join any core Linux teams, but I contribute in other parts of open source.

I guess I'm saying the only place I'm really interested in working with the core teams is on whatever DevOps tools they adopt.