1. 16

  2. 6

    This is a very nice idea, and like issues, ties you into the infrastructure.

    The problem I have with this is that - like issues - it now separates out the code from the discussions about the code in not a nice way.

    Ideally, the infrastructure would be a nice GUI on top of a data structure either embeded in git (like commits, tags, etc) or closely allied with it such that when I mirror the code to other infrastructure, or to my local machine, the issues and discussions come with it.

    Currently, for example, I will have commits in the code that reference issue #12 and github’s infrastructure does a wonderful job of cross-linking and tooltipping and what not. I move to gitlab. BOOM! All gone.

    One could argue that when github disappears we will all be pretty old, and our antique code will only be seen in museums because all the kids are using AIs to program, or the AIs are programming the kids, either way.

    But, you know, I have a code base from sourceforge (yeah, remember that, kids?) that is now 15 years old. The commit messages have survived just fine (migrated from CVS or SVN I forget) but not the issues. Were there any important design decisions based on the issues and the discussions around the issues. Yeah, yeah, I should have put them in the commit, but I’m human. And why must I repeat information?

    -Yours in elderly (not that elderly!) rantiness

    1. 3

      I have not used it myself, but Fossil has issues, a wiki, etc. built in and might be worth checking out.

      1. 2

        Similarly, Red Hat’s Pagure does much the same on top of git.

      2. 2

        I hear you.

        Ideally I think issues/bugs can be handled by something like bugseverywhere - they live in git/hg/etc so updating/closing and committing is synced. It needs a decent web UI though. One of these days…

        Notes/discussions I’m not aware of anything but it would be an interesting problem to solve.

        Long form docs can be handled as markdown/similar in a directory and rendered via something like Gollum or even a static site generator if you don’t need browser based updates.

      3. 3

        As if it’s the tools that are the main obstacle for effective communication… And not people who drop conversations, ignore all but the single topic in an email, reply with empty ideas in the hopes that it’s someone else whose job is to understand and organize everyone’s thoughts. Or the people who turn every code review into a War of Programming Paradigms starting with something as minute as a variable name. But yes, I sure hope yet another integrated system is going to beat sense into everyone. Because integrated. And because GitHub.