BSD timeline up for grabs

Playing around a bit I’ve decided to make a simple BSD timeline, including the 10 most popular distributions.
Here are the usual PNG, SVG and TAR.BZ2.
Since we don’t have any intention of maintaining it (i.e. adding lots of BSD derivatives), the timeline is up for grabs for those willing to extend and build upon. We will of course offer helpful tips and support.
So anyone can download it, alter it in any way they see fit and publish it wherever they want.
You can also just leave a comment lamenting about how the dark background is ugly.

Join the Conversation


  1. Thanks, should work now!

    Yes, I’m not too happy with the colors myself, though it’s hard to find a good match when the red is fixed and you’re going for a dark theme.
    My hope is that someone is willing to fix it up ;D

  2. Eww…

    I was actually wanting to type ‘cool’. It’s a typo. I like that actually. I love dark color scheme. πŸ™‚

  3. Now we have at least someone who loves it and at least someone who likes it. Great!

  4. Being a user of OpenBSD and NetBSD myself, I might take over maintaining this chart. I need to get to grips with gnuclad, though. Never worked with it before…

  5. I guess BSDT is sort of being forgotten?

    Maybe BSDT (and GLDT) can set up a repository on GitHub? I am sure it would soon get featured on Explore page and there are tons of people eager to submit patches. As long as requiring references for the patches to make sure the data is correct. The only tasks left to be complete are merging and generate the chart and make a release.

  6. We originally figured that most people wouldn’t want to learn git before sending in additions, so we made the ‘submit distribution’ form in the menu.

    Might be worth a try though after the next GLDT release.

  7. Git might be necessary to contribute if you put GLDT there, but now you can edit file content right on GitHub (after you “fork,” same on the website), even renaming/moving files. You don’t even need to know anything about Git if someone absolutely doesn’t want to learn.

    And actually, they don’t need to edit on their own. They can just open an issue with required information and maintainer can take from there. With issues as history, that would be a plus in my opinion.

    Hope I see you there soon!

    Sincerely yours,
    Yu-Jie Lin

  8. Point releases and distribution icons are nice features. Would love to see something like that implemented in GLDT. You guys carry a heavy load.

  9. I agree. But GLDT might only be able to stuff icons in, with those point release numbers, I believe it will be overcrowded and harder to maintain since the CSV will grow much bigger in much faster rate.

    I think GLDT can use sub-project to have each (major) distribution having their own timeline which includes the release number if GLDT wants to do, of course, this really can only be done with lots of contributors.

    If GLDT creates a team on GitHub, the it can has something like GLDT/Debian, GLDT/Ubuntu, GLDT/Fedora, etc. Users of the distributions can freely create a pull request. Who knows the official maintainers of distro might be allowed to join the team, so they can maintain their own distro’s timeline.

  10. So true. Such a task is totally infeasible unless a bigger community effort occurs. I personally try to avoid GitHub and prefer Gitorious over it, but GitHub is nice. I don’t think Git is that difficult, but GitHub web interface certainly makes things friendly.

    After all the distro diversity/fragmentation and analysing FOSS behaviour in general, I feel like GLDT has the potential to show everyone their roots and unite people in the noble task of maintaining a common history.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.