I think its got something to do with competition law…
(pronounced “ay-triple-see”)
2 Likes
Accepted with 0 votes, the votes are a lie 
2 Likes
Maybe there are ghosts voting!
Probably they just thought it was a good idea and needed someone to point it out to them. Developers are not perfect, even user interface coders.
1 Like
7 Likes
Edit: “directly into TN Scale” 
2 Likes
“directly into TN SCALE Community Edition”
Fixed it 
3 Likes
2 votes: ACCEPTED!!! 
0 votes: ACCEPTED!!!
7,984,195 votes: Still gauging interest from the community. 
3 Likes
Any volunteers?
1 Like
Only after ReiserFS and btrfs.
3 Likes
Didn’t the lead dev of bcachefs get his commit access stripped from the Linux kernel?
Sort of. If I remember correctly, he had to wait until the next development cycle. He kept trying to push major changes late in the current cycle, some of which were not just his BCacheFS code, but other kernel code.
This actually goes back to one thing I think is good about OpenZFS being outside of the Linux kernel tree, freedom. When a file system is under active development, like OpenZFS or BCacheFS, having to work under the Linux kernel timeline can cause conflicts when your file system needs a large fix, but the kernel cycle is closed to large fixes, just testing.
I think this is one reason why BTRFS is more or less a failure. The regular components like LVM, MD-RAID and various files systems were modular enough that they could be worked independent of each other. With BTRFS, (and OpenZFS), doing volume management, RAID and file system duties, it meant that it was hard to work in the changes under the Linux kernel release schedule.
I think their is too much emphasis on being in the Linux kernel source as the final goal for drivers and file systems. In my opinion, (not that it counts), it is actual a hindrance for actively worked projects, like OpenZFS, (and BCacheFS).
2 Likes
Agreed 100%. While it is annoying to be out of tree at times, it also gives a ton more flexibility in terms of what we can do and when. Also how you ship the kernel and userspace bits can now be in lockstep in a unified release
2 Likes
It’s funny that discussions of WifeMurderFS outlive its presence in the Linux kernel.
It’s funny that its presence in the Linux kernel lasted as long as it did.
Its not that funny :-\
1 Like
Since all memes should be archived here and i posted it in a chat with winnielinnie
6 Likes
A friendly reminder to anyone reading this thread:
I made this post as a joke, not as actual advice. 
3 Likes