Re: Looking to open source software that uses gwlib

Because I know that gwlib serves more purposes than just Kannel: How about
creating a seperate CVS tree for it and distribute it independantly?
 
Just a thought.
 
Rene Kluwen
Chimit
 
> ----- Original Message -----
> From: "Paul Bagyenda" <[email protected]>
> To: <[email protected]>
> Sent: Monday, January 17, 2005 8:55 AM
> Subject: Looking to open source software that uses gwlib
> 
> 
> > Hi,
> >
> >   We've used kannel in a variety of settings and have even in the past
> > posted changes to the list (incl. OMA OTA provisioning and a bunch of
> > other changes). Some of the changes made it into the code, others are
> > waiting.
> >
> >   We have a product we've developed that we are looking to open source
> > fairly shortly. It uses gwlib in part, but we also added some stuff
> > (fairly benign, in the cfg.def file primarily). My question is: How
> > best should be handle this. Should only the gwlib changes be
> > contributed/incorporated to the kannel project itself? Should we put
> > this new product under kannel.org control or should we create a related
> > project that both groups can benefit from?  The trouble is that this
> > product deviates pretty hugely from kannel's core focus, so we are not
> > sure it properly fits under the kannel umbrella.
> >
> >   Whatever the choice we intend to fully acknowledge kannel's
> > contribution.
> >
> > Please let me have your thoughts
> >
> > Thanks
> >
> > Paul.
> >
> >
> > -----------------------------
> > P. A. Bagyenda
> > Digital Solutions
> > P.O.Box 23833
> > 58 Bukoto Str.
> > Kampala, UGANDA
> >
> > Tel: +256-41-540143
> > Mob: +256-75-507743
> > Web: http://www.dsmagic.com
> > -----------------------------
> >
> >
> > This email and any files transmitted with it are confidential, and may
> > also
> > be legally privileged. If you are not the intended recipient, you may
> > not
> > review, use, copy, or distribute this message. If you receive this
> > email in
> > error, please notify the sender immediately by reply email and then
> > delete
> > this email.
> >
> >
> >
> >
>