Just to be clear:
There's two different paths needed to implement a system:
1) The Design - This requires a significant amount of knowledge about what needs to be built, and how it integrates with everything else. This usually also has thematic components, a bit of "art" per se.
2) The Code - This usually is done by following some rough guidelines or "spec". Good code tends to be destructively created in that several approaches are tried until the right one is found. The code itself though tends to often try to follow a high level design. The lack of design can often lead you to wondering where to start and a sense of "writer's block" which is what so often happens in these situations.
Right now I'm not particularly in design mode. I may be later, but I'm looking for good ideas to code. Once I have them, and agree with them, things will move rapidly. If I don't get them, I might move into the design phase myself. If I don't get much feedback beyond questions of my commitment though I may end up questioning the value of continuing to contribute.
Instead of getting frustrated with the lack of progress, why don't you focus on how you can be a constructive element to progress. I've seen a lot of back and forth, but this place has lacked a serious design. There's plenty of chatter floating, but no real concrete, actionable tasks that I can work off of when I'm in the mode (which I happen to be). I'll figure out my own route as necessary, but this is a shout out to all of you to also get your asses in gear and help me.
-Once
