I have a large public todo list for tmux (it is even distributed in the
portable tarball), and I don't actually mind helping people, so long as
they make some effort. Even so I get very very few contributions for
todo list items, most stuff I get is from people who specifically want a
feature or hit a bug.

So I am a bit sceptical about the value of todo lists.

People have suggested it would help if I added more detail or put them
in a bug tracker or something, but who has time for that when nobody
even emails to ask about what is there already?

If there are small ideas from developers (or users) scattered over the
mailing lists, there is nothing stopping someone else collecting them
together and making a todo list...


On Mon, Apr 19, 2010 at 03:02:17PM -0300, Christiano F. Haesbaert wrote:
quoted text
> I know this has been discussed before, yet I call for your attention.
> 
> This post seems like a genuine attempt on getting pointers on starting
> hacking in OpenBsd. I remember doing the same a while ago.
> 
> How about having a very simple per-developer(or project) wish-list/todo-list ?
> 
> I guess this would encourage people to code, usually the first step is
> the hardest after you code some stuff you can can usually walk by
> yourself.
> 
> For example, Claudio once said that not needing a route for multicast
> addresses would be nice, but that's somewhere on the mailing lists
> archives so very few people are aware of that, having it explicit in a
> todo-list could speed things up IMHO.
> 
> I also know he (as every developer) is busy with more important
> things, so "publishing" these small tasks would also give the
> developers more time to focus on the big/important issues.
> 
> No, I'm not trolling, just an idea.