On Thu 07 July 2011, Chenthill wrote:
> On Fri, 2011-07-01 at 23:33 +0200, Christian Hilberg wrote:
> > Since neither my kernel concepts evolution-kolab team mates nor myself
> > have done upstream integration for an Evolution plugin yet, I would like
> > to know how we should best proceed from here. If there is any reading we
> > should have done prior to further acting, we'll gladly accept pointers
> > to the relevant documents. David (or anyone else involved there), I
> > heard that you did the same with your EWS team recently, so if there are
> > any lessons-learned which we should heed to, we will also be happy to
> > know. Long story short, we will just be happy for any directing through
> > this process so we can get through it smoothly.
> You could create a package naming eg: evolution-kolab and create a new
> repository in git.gnome.org. http://live.gnome.org/Git/NewRepository
> has all the details required.

Let's see what http://live.gnome.org/ProjectPrerequisites says:

   1. The project must be free/open source software.
   2. It must use GTK+/GNOME technologies.
   3. It must be maintained, and already have had at least one public release.
   4. To the best of your knowledge, it must not infringe on patents (most
      gnome.org servers are in the US).
   5. If copyright assignment is required, please first read our policy on
      copyright assignments; it's simpler to not have any copyright

For evolution-kolab:

1. [ok] we're all LGPL
2. [ok] it is an Evo/EDS plugin
3. [ok] see http://evolution-kolab.sf.net/
4. [ok] we're confident about that
5. [ok] should be no trouble, we're LGPL, no other copyright assignments apply

I will thus proceed and create an evolution-kolab Git repo at gnome.org.



kernel concepts GbR        Tel: +49-271-771091-14
Sieghuetter Hauptweg 48
D-57072 Siegen

Attachment: signature.asc
Description: This is a digitally signed message part.

evolution-hackers mailing list
To change your list options or unsubscribe, visit ...

Reply via email to