1. 10
  1. 5

    Sounds interesting, might solve a problem I have at work, too bad it’s coupled to github =(

    1. 3

      What would you prefer it to use as the underlying storage? (I am trying to understand what people actually want.)

        1. 4

          I was thinking of storing everything, including the comments in a git instance, which would work independently of what git frontend you are using, but then I would have to speak git protocol from the browser which sucks. I may have a look at git.js

          1. 3

            Looking at git.js documentation :(

            “I’ve been asking Github to enable CORS headers to their HTTPS git servers, but they’ve refused to do it. This means that a browser can never clone from github because the browser will disallow XHR requests to the domain.”

            1. 1

              Anything self-hosted would be viable, but everything on git would be even better, although probably more complicated. We use gerrit at work (which sucks at several levels), and mostly anything third-party is very much disallowed. Maybe you could create an abstraction that would speak Github API to github and git protocol to other servers where this would work?

              The other possibility could be a sort of optional backend/proxy, so, if the git server doesn’t have CORS, you could spin that optional server.

              1. 2

                After thinking about it some more, there’s a lot that GitHub offers that I would have to reimplement myself. Authentication, for one thing. If it was used in a stand-alone mode in enterprise, some kind of authentication would be still needed. People would probably want SSO. Then there are notifications. GitHub sends you an email when you are mentioned in a bug. I would have to somehow interact with company’s mail server. And so on. This is my hobby project and I don’t really have time to go into that amount of complexity.

                1. 1

                  Sure, makes sense. It’s still a cool project, nonetheless, so, congrats =)

            2. 2

              sounds like a job for the backend

          2. 1

            The only issue that I have with it is sharing my organization details. Although you could do it manually, I’m always a bit annoyed about this.

        2. 4

          I would like to try this out, but I can’t auth the shopping list demo to Github because it wants access to both private and public repos, and those of my employer. I understand this might be a limit on Github’s side (maybe the permissions options aren’t granular enough) but unfortunately that makes it a hard pass for me.

          1. 2

            There’s a scope to authorize the app only for public repos. But that in turn would make it impossible to use on private repos. It’s starts to look like GitHub API, as it doesn’t support granting per-repo access, is not designed to support this kind of scenario (application running in brower, impersonating the user).

          2. 3

            I’ve wanted something like this for a while - the idea of mixing documentation/checklists and a record of going through them really appeals to me.

            Not sure about GitHub-as-storage, but I can see how other approaches might be more work. I was expecting it to be more like a wiki (self-hosted, database backend) on first glance, but I’m not sure if that would actually be an improvement rather than just what I’m used to.

            1. 2

              Yes, checklisted documentation is helpful, but also notice the context-collection capabilities via comments on steps. The motivation use case: A person is working on a complex process for several months, then leaves the company. Another person takes over and has to get up speed quickly. By looking at the graph they can immediately understand what have been done, what haven’t been done and what’s blocking what. By looking at individual unfinished step they can read the comments and understand what was already done.

            2. 1

              I can’t seem to get any of the examples to load workout errors.

              1. 1

                Replied on the issue.

              2. 1

                gives me an idea for an ifttt checklist mashup.