glsdk-devel

[Glsdk-devel] Patch submission guidelines and accepting contributions

[H. H. <hen...@gm...>]

There has been one contribution so far which I have accepted to our code
base and others who have offered their work for our use. The contribution
was Orhun Birsoy's glmMatInverse4f implementation which was very good and he
may contribute more for the GLM.

We need to write some sort of guidelines for patch submission. What issues
should these guidelines address? Code conventions, styles, line endings etc.

Also how are we going to give credit for the contributors? Should we create
some file where we list each contributor and his/her effort or should I list
the people in the source files? ATM I have not yet written Orhun's name into
anywhere until we get these issues decided.

We should probably start using Sourceforge's tracker systems for feature
requests and bugs so that people could see what kind of patches we need.

-- 
Henri 'henux' Häkkinen

Re: [Glsdk-devel] Patch submission guidelines and accepting contributions

[Branan R. <br...@gm...>]

Since the zlib license we're using requires the copyright notice be
duplicated, we should have a centralized file with the license and a
copyright listing for all contributors. It's also nice to credit each
person in the file so there's a better idea of who did what.

If we were on a self-hosted SVN, we could just put copyright notices
in the files and use a hook script to generate the global license
file. Unfortunately, I can't do that on SF.net.

I'd say we create a global copyright file, and do credits in each file.

On Thu, Aug 28, 2008 at 9:48 AM, Henri Häkkinen <hen...@gm...> wrote:
> There has been one contribution so far which I have accepted to our code
> base and others who have offered their work for our use. The contribution
> was Orhun Birsoy's glmMatInverse4f implementation which was very good and he
> may contribute more for the GLM.
>
> We need to write some sort of guidelines for patch submission. What issues
> should these guidelines address? Code conventions, styles, line endings etc.
>
> Also how are we going to give credit for the contributors? Should we create
> some file where we list each contributor and his/her effort or should I list
> the people in the source files? ATM I have not yet written Orhun's name into
> anywhere until we get these issues decided.
>
> We should probably start using Sourceforge's tracker systems for feature
> requests and bugs so that people could see what kind of patches we need.
>
> --
> Henri 'henux' Häkkinen
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Glsdk-devel mailing list
> Gls...@li...
> https://lists.sourceforge.net/lists/listinfo/glsdk-devel
>
>

Re: [Glsdk-devel] Patch submission guidelines and accepting contributions

[H. H. <hen...@gm...>]

Yes. I think we should create a LICENSE file in the root directory and
perhaps list copyrights for each library in the README along with
contributors? Or should we choose a separate file for the copyrights and
contributes from the README? I can do this minor task. I will also setup
some SF.net tracker issues for the GLM (see my other post).

On Thu, Aug 28, 2008 at 7:55 PM, Branan Riley <br...@gm...> wrote:

> Since the zlib license we're using requires the copyright notice be
> duplicated, we should have a centralized file with the license and a
> copyright listing for all contributors. It's also nice to credit each
> person in the file so there's a better idea of who did what.
>
> If we were on a self-hosted SVN, we could just put copyright notices
> in the files and use a hook script to generate the global license
> file. Unfortunately, I can't do that on SF.net.
>
> I'd say we create a global copyright file, and do credits in each file.
>
> On Thu, Aug 28, 2008 at 9:48 AM, Henri Häkkinen <hen...@gm...>
> wrote:
> > There has been one contribution so far which I have accepted to our code
> > base and others who have offered their work for our use. The contribution
> > was Orhun Birsoy's glmMatInverse4f implementation which was very good and
> he
> > may contribute more for the GLM.
> >
> > We need to write some sort of guidelines for patch submission. What
> issues
> > should these guidelines address? Code conventions, styles, line endings
> etc.
> >
> > Also how are we going to give credit for the contributors? Should we
> create
> > some file where we list each contributor and his/her effort or should I
> list
> > the people in the source files? ATM I have not yet written Orhun's name
> into
> > anywhere until we get these issues decided.
> >
> > We should probably start using Sourceforge's tracker systems for feature
> > requests and bugs so that people could see what kind of patches we need.
> >
> > --
> > Henri 'henux' Häkkinen
> >
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> > Build the coolest Linux based applications with Moblin SDK & win great
> > prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the
> world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Glsdk-devel mailing list
> > Gls...@li...
> > https://lists.sourceforge.net/lists/listinfo/glsdk-devel
> >
> >
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Glsdk-devel mailing list
> Gls...@li...
> https://lists.sourceforge.net/lists/listinfo/glsdk-devel
>



-- 
Henri 'henux' Häkkinen