2011-01-06, 06:41 AM
Really depends on what you want.
You don't need PR if you...
If you want a good quality open source project, you should do some PR. You don't need to do much, a webpage with information about the project and newest commit/update and a link to the git repository should be enough.
Also, even though this is not a thing most of us would think of, Firefox is an open source project that consist of lots of full-time-jobs. While that's not important for us, it shows that open source has a potential which shouldn't be underestimated (nor overestimated either, of course. Be realistic.)
I cannot say much about your project, but I want to point out certain things:
You don't need PR if you...
- want to work on a project you and only you develop and use
- do not want input or help from others to find bugs, or to document code
- have no interest to tell other developers/programmers that this project might help them (what you might call public gain)
If you want a good quality open source project, you should do some PR. You don't need to do much, a webpage with information about the project and newest commit/update and a link to the git repository should be enough.
Also, even though this is not a thing most of us would think of, Firefox is an open source project that consist of lots of full-time-jobs. While that's not important for us, it shows that open source has a potential which shouldn't be underestimated (nor overestimated either, of course. Be realistic.)
I cannot say much about your project, but I want to point out certain things:
- Idea: I have no clue, you don't describe it.
- PR should be done by one person or by a committee, and the PR-thing should be accepted by everyone. Some people are better than others at PR, so it's natural to let them do the job.
- I don't know what exactly you didn't like about the leadership, but you generally don't have to have a leader in order to contribute to an open source project. Either way, if there are issues between you and a leader, talk to them or quit.