[bruce511]

I would suggest that the goals of the author matter here. Obviously across so many authors you get different goals, and hence different requirements.

Part of this is understanding what your goals -are-. It's really important because without that target it's easy to be subsumed by other people's goals.

Are you writing this for you? Or you want to build a large user base? Or you want lots of contributors? Or it's a marketing exercise for your startup? Or.....?

For example, if your goal is to write code and post it, then you're done. If your goal is marketing then really you'll spend more time marketing the project than writing it. If your goal is a huge user base, well you better fix bug reports Pronto and so on.

If your goal is to get an income from this and go full-time then that's the problem you need to solve first (before you start writing code.) Have a plan for income - nake that clear from the start.

Of course goals change, that's OK. But make sure what you are doing lines up with your goals. That's the only way to succeed.