Project Status

[ivanreese]

[Retcon]: Let's have a discussion about the status of the project! See this comment for my thoughts.

[ulgens]

@ivanreese Hey, I'm a follower of the repo and I just got a notification for this issue. I wanted to ask if there is any reason you are creating issues instead of pull requests/content edits? Open issues have a lot of valuable resources that are not accessible via the content itself.

[TodePond]

because it's a todo to add to the repo at some point

[ulgens]

I may be missing what you mean but having 90+ open issues with links made me think there might be a different approach to the repo. If all of them are actually to do notes, it's sad that they are staying as to do notes. @ivanreese Please let us know if there is anything to help.

[jryans]

It simply takes time to do the work of adding things properly to the repo... I have a similar repo tracking lists of links, so I fully understand where @ivanreese is coming from, as I've done precisely the same thing. You want to at least track each thing as an issue so it's not forgotten. Some day eventually, perhaps you have time or work with others to add it properly, but that also takes time.

Personally, I am very happy Ivan continues to tracks things here in whatever form they have time for. It's a valuable community resource.

(We should really discuss this in it's own issue / somewhere that's not here though!)

[TodePond]

here's my opinion

[ivanreese]

@ulgens Yeah, your instincts are correct — the way I'm currently using issues is really suboptimal. I really appreciate the offer to help!

Something I've run into with this project is that the current top-level organization (a bunch of markdown pages) is a really terrible format for the sort of curatorial work I'd like to do. I want something closer to a wiki: quick and easy to capture new additions, edit and improve existing things, and browse / explore. The current system fails at all three of those. Using issues is a temporary way to keep going with the first one while I try to figure out what I want to do next.

I'm thinking I'll do something like I did recently for the Future of Coding wiki, where it leans on github for authentication and browser-based editing but uses a custom build script to generate a nice static site for browsing.

The one thing I want to be sure of is that it doesn't lose anything good about the current repo. That should be a fairly low bar, but I want to be considerate / deliberate about it.

In any event, thanks for inquiring! I'm glad you're enthusiastic about this project — I am too! If you have suggestions for what I should do, even vague inklings or wild wishes, I'd be happy to hear them.