search

emaculation / macemu

Basilisk II and SheepShaver Macintosh emulators, maintained
74 stars 14 forks source link

use makrdown, fix typo #5

Closed retokromer closed 5 years ago

ianfixes commented 5 years ago

We should just delete this file after converting its contents to GitHub issues. I can set up some labels for that... There seem to be a lot of todos in the documentation scattered throughout the directories.

retokromer commented 5 years ago

Hmm… It would give an inflation of issues, in my personal opinion. Yet it’s up to you!

ianfixes commented 5 years ago

What do you mean by inflation?

I'm not suggesting that all of these would become priorities by logging issues, just that for organization's sake we should put them into a more native form (for tracking, commenting, labelling, referencing in PRs, etc.).

retokromer commented 5 years ago

I mean an enormous number of issues (which make the list tedious to parse and to use). I personally would create formal issues only when there is the time and the energy to resolve them in a reasonable timeframe. Yet, as said, do it the way it’s most useful for you.

ianfixes commented 5 years ago

I understand. I can always close the issues later, but in any case (whether we have the time and energy to resolve them as formal issues or not) they won't be useful while stored in this file.

For the stuff that does have supporters with time & energy, I'd be glad to set up some milestones to track those. I am in complete agreement that an unparseable list is an antipattern here.