While working part-time in the IT department of the University as a Linux/Unix administrator I was tasked with the job of making unix and windows systems talk together for file sharing and most importantly printer sharing purposes. Samba was the obvious tool.

As I am naturally very curious I shortly started wondering how Samba accomplished to bridge the architectural differences between a Unix and a Windows system, especially from an Identity point of view. I knew both architectures and they are very different in some key areas. I started asking questions on the users mailing lists, and I was quickly told that the details were only in the source code.

Being very naive I started reading the code thinking I could grasp everything in a short time. Soon I realized the code was much more complex then I expected but also realized the beauty of some of the challenges in that code, I was hooked.

I started working on the passdb subsystem (the one that manages Identities in samba) and shortly saw the first few patches applied to the development tree. After some time I was contributing regularly and was gifted with the status of Team member.

I think that "community" is an ambiguous term in the FOSS case, I see this world as a set of sets. Real communities exists only at the project level, and they are not necessarily very well defined at that level either. Usually the project community is composed by a more or less stable core set of developers, often employed by some company, and then a wide range of other people that contribute to a minor degree, or just uses the code and provide a lot of good feedback.

The broader "FOSS community" is more or less the superset of all the single project communities. Not everybody recognize himself in this broader super-community, and some people tend to split it into something artificial like the Free Software vs the Open Source communities. What matters at a higher scale is the set of licenses used on one side and the field a project operates in on the other. Where the licenses are compatible we see a lot more interaction, when they are not a bit less and also some tension when two projects in the same filed need or try to interact. These interactions are the links that define the super-community, more or less, with obviously blurred edges.