fortunately my thesis, rather than collecting dust, continues to inspire others. today i got a mail:
I read your master thesis entitled “A Framework For Open Source Projects”. It struck me in an uncanny way. I recently began working on a project in which the goal is to improve process for open software. My motivation is that I have contributed to projects and was amazed at the poor processes they used, and I think this is a way that I can really help out open source.
The project home page is hoot.tigris.org. The reason I was amazed at your paper is that you point out MANY ideas that I have been thinking about and actually have evidence or references to back them up. In some cases you stated word for word what I have been thinking, and what I want to improve.
I would also like to invite you to be a part of the project, at any level you desire. By that I mean just sitting on the dev list and making comments from time to time, or actually making major decisions and being a member of the “core team of developers”.
when i looked at the open source landscape, the community’s infatuation with tools was readily apparent. everything was basically a tools problem, and if your project sucked, it must be because you were not using the latest and greatest (ftp/web/irc/mail/nntp/scm/bugtracker/forum/wiki) software. efforts to raise the bar by quality-enabling tools are noble and worthy, but i feel they will fail to do much good because only the good developers would use them. this is why i focused on general education about open source processes and pitfalls more than specific instances or tool support, and i still believe there is a bigger gain by educating the masses about some key concepts rather than by making them use better tools without the proper theoretical insights. i will therefore continue to spread my thesis, and probably even help out with commentary on the hoot project, but probably wont tie myself too tightly to it, even though i laud the effort.