[prev in list] [next in list] [prev in thread] [next in thread]
List: sylpheed
Subject: [sylpheed:27798] Re: About Sylpheed communauty
From: Thomas Cataldo <thomas.cataldo () aliacom ! fr>
Date: 2006-03-31 15:45:29
Message-ID: 1143819929.5928.25.camel () chienne ! aliacom ! local
[Download RAW message or body]
On Wed, 2006-03-29 at 18:32 +0900, Hiroyuki Yamamoto wrote:
> Hello,
>
> On Mon, 27 Mar 2006 13:00:15 +0200
> Thomas Cataldo <thomas.cataldo@aliacom.fr> wrote:
>
> > Then I would like some answers to a few questions :
> > - Are there other developpers with svn commit access ?
>
> No, I'm the only one who has the svn commit access.
>
> > - How are contributions dealt with ?
> > - Would you accept patches for features on the roadmap / not on the
> > roadmap
>
> Both will be accepted if those patches meet the quality I want (is it
> going to be widely used feature? / doesn't it sacrifice stability /
> performance / usability?)
Some of the features we have planned (or need) fit into the "widely used
feature" category (s/mime 3), and some do not (hmtp protocol). We will
have to study sylpheed architecture a bit more to figure out what can be
done as an external plug-in, and what need to be in the main source
tree.
>
> > - Is there any form of copyright assignement or something like that
> > for contributions ?
>
> Currently there is no explicit assignment for contributors. There is
> implicit rules, though:
>
> - The copyright holder of patch itself is the author.
> - The copyright holder of source files newly written by the patch
> author is the author.
> - The copyright holder of the modified files in the source tree will be
> basically kept as is.
Thanks for your input.
Thomas.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic