The thing I seem to keep hearing over and over from the open source gurus is how important networking is in the open source community. There is a lot of intricate details about how to get projects done the right way, and by right I mean the way that has the highest chance of success. So many details that, try as you might, running a project for the fist time will lead to roadblocks, a lot of them. I have begun to learn first hand how important networking is in all phases of open source development because its the way to get around these roadblocks.
A good example happened today with my project. To move further with the project my team needed to get commit rights to the wiki and git repository for the project. About a week ago, we sent an email to the upstream of transbot and we had yet to get a response. Because we have a short time frame to get working on this project due to class restraints, this was a roadblock that needed to be handled quickly. In this situation being comfortable with contacting the fedora admins(they are hosting the wiki and git repository) to ask for advice on how to proceed let us handle the situation in a matter of about an hour. Because the previous project admin has been inactive for about two years, we were given full rights to the project. Had we avoided networking, our team would have been at the mercy of waiting for the previous admin for an indefinite amount of time.
My advice to anyone starting out for the fist time with an open source project is to make use of what ever meaning of networking you can to benefit your project. IRC, wiki, mailing lists, blogs, email, etc. use them all if you ever mean to be serious about your project.
No comments:
Post a Comment