documentation of the development process

[Daira Hopwood]

On 05/08/15 23:34, Lukas Pirl wrote:
> 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.

Please do.

> *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?

We're distributed across time zones (and sleep schedules), so I would suggest
just asking a question and staying in the channel as long as it takes for a
response.

-- 
Daira Hopwood ⚥

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20150807/b1d0e9d2/attachment.pgp>