Dear *, in the context of a project at my university, I want to do find out some details about the development processes in open-source projects.
Since I am lurking on this active and open community for quite a while, I have the feeling that TahoeLAFS would be an ideal candidate. It is a rather sophisticated product! I'd love to ask you a few questions about the formalities or informalities that are not obvious through the structure, the tools in use or the Wiki. *What is in for Tahoe*? Of curse, I am willing to contribute back. I could create a Wiki page (or update an existing one) with information that could be interesting for other users or new developers, respectively. Is there a time when the core developers can usually be met in the IRC? It's probably more interactive and less formal and clumsy in comparison to looong emails. Cheers! Lukas _______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
