Skip to content
Project ideas for Issa Rice (see repo issues)
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
LICENSE
README.md
download_issues.py
issues.json

README.md

Project ideas

Project ideas for Issa Rice. For the actual ideas, see the repo issues.

Each issue is a project idea, and should have exactly one effort label, probably one venue label, and at least one format label. (It looks like only repo contributors can edit labels, so you can just explain this in the issue itself.)

Most of the ideas are for me to work on eventually, but others can work on them as well (in fact, I would prefer that since it means less work for me). Others can also add new ideas to this repo for me to work on (similar to requested answers or "ask to answer" on Quora) or comment on existing ideas. In an ideal world, we would all have repos like this one and we could ask each other for specific kinds of output (and the votes and bounties would help us decide what to prioritize).

Some reasons I have this repo are to:

  • Give people a better idea of what I might work on next. I like to make myself predictable so others can plan according to a good model of how I will act.
  • Tell the world the things I want to see. I think the things in this list are useful to the world, and it doesn't need to be me who does it. It would be great to find out that somebody saw a sufficient need based partly on this repo and decided to make something. This is similar to request for startups or charities.
  • Track the things I want to work on. I often think of things I'd like to work on while daydreaming or working on something else. If I don't put an effort into recording things to work on (and training myself to notice needs that exist in the world), I might forget.
  • Clean out some tasks from orgmode. I have a backlog of tasks in orgmode. A lot of these aren't for me to immediately work on, and they kind of clutter up my orgmode file. If the tasks can be done by somebody that isn't me, why not keep that portion of the todo list public?
  • Give potential funders an idea of what they can fund. If I already want to see something in the world, a modest amount of funding can shift my priorities to work on that thing. By the way, since I tend to be busy with the things I am already working on, it's hard for me to tell whether I can actually work on a different thing even given funding, so I would prefer bounties that I can claim by completing or making progress on a project rather than some sort of pre-commitment to work on a project.
  • Find potential collaborators. Especially for the larger projects, it can be helpful to have other interested parties on board to divide up the work.
  • Give people a better idea of where I'm coming from. This is a broader point that applies to other efforts I have made to be more transparent.

The information in each issue (i.e. project idea) is intended to be helpful in getting a basic idea of the project, but is only suggestive; it is often the case that as a project proceeds, details become clearer or change.

This is not an exhaustive list of project ideas. In particular if I have already done some work on a project and just want to make general improvements to it, I won't usually list it here (all projects can be improved to varying extents, and it would be tedious to list them all). If I have specific improvements, I will try to list them here. If existing projects have their own GitHub repositories, I will try to add issues there.

For the actual ideas, see the repo issues.

Effort labels

Effort can be rated on the following scale. In each case I assume I am the one performing the task (skill-sets vary considerably across people so it would be difficult to provide a good estimate for the general population). I have a good programming and writing ability but I am not exceptional by any means and I expect many people can perform at a comparable level or even better depending on their expertise. (As a side note, even on the project idea generation front I don't think I am exceptional – in fact this repo so far is quite rudimentary and biased toward things I find personally interesting rather than most useful to the world – so I think other people can and should also be more transparent about projects they want to see.) Days here refer to work days, so 8 hour periods. Of course, planning fallacy makes it difficult to estimate how long a project will take, but I list some things I have actually produced in the past to ground myself on the kinds of tasks and their timescales.

  • low_effort: Up to one day (8 hours) of effort. These are relatively quick things that can be done. Examples are Timeline of Carl Shulman publications as of July 13, 2017 (about 7 hours of work) and some global health pages like Amanda Glassman (I think).

  • medium_effort: More than one day and up to two weeks (8–80 hours) of effort. Examples on this level are timeline of MIRI as of July 15, 2017 (75 hours) at the upper end. I think timeline of AMF (33 hours) around the middle.

  • high_effort: More than two weeks (80 hours) of effort. Examples here are my total work so far on the donations list site (as of November 2017) and my total work on Devec wiki (as of November 2017).

Downloading issues

To download the issues in this repository, run the script download_issues.py that is included in this repository:

./download_issues.py

This will save the issues as a JSON in issues.json. It won't save comments, but I think the script can be modified to also download comments.

To make sure all the issues were downloaded, you can count the occurrence of a string that should appear once for each issue, for example:

grep -F '"title":' issues.json | wc -l

See also

External links

You can’t perform that action at this time.