guido wrote: > > Hmm. Is there a good place to start listing these todo items? One = that we > > can truly use for communicating this info? In Apache, we have a file = named > > STATUS that everybody uses for dropping ideas, patch references, = critical > > bugs, etc. As that file gets changed, we see it in the -checkins = alias, so > > everybody is aware of the suggested changes/problems/available = patches/etc. > > It also holds people's votes on particular changes. > >=20 > > Can we institute something similar? Possibly Misc/STATUS? Should I = post > > Apache's STATUS file as an example? >=20 > Possibly, but I'm somewhat skeptical. I used to have a large TODO > file -- still have it -- but it's so full of long-term ideas that > never happened that I rarely look in it any more. instead of a file, I suggest taking a look at ?!ng's Roundup (once 1.6 final is out, of course). </F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4