Re: [bme-develop] Development issues

[Simon T. <sim...@ga...>]

> bme team, 
> 
> > > > What do you think=3F
> > >
> > >Yes, put all of it on sourceforge if you're happy doing that.
> > >
> > Precisely, but do we have to agree on a license before we put it on 
> > sourceforge=3F and how do we post something under a license=3F just 
> > paste 
> > the 
> > license header above the file=3F Or can we restrict the sourceforge 
> > cvs 
> > access 
> > until we've agreed on a license....
> Yes most definitely we need to agree on a license. Honestly I don't 
> know much about open source licenses, GPL, LGPL, and all the others, 
> I 
> will have to do some research on the topic. What are your 
> recommendations=3F And I don't think there is a way to restrict access 
> to 
> the cvs, once it's there, it's for everyone.

For me the GPL is too restrictive. The LPGL is less-so, but still 
fairly complicated.

My choice would be MIT/BSD (I think that's how I registered the project 
on sf, although it's no problem to change it). The license basically 
says - "Here's the code, do anything you want with it, but don't sue us 
if it doesn't work". The problem is it doesn't stop anyone taking all 
of our code and selling it commercially. I really don't think that's 
likely to happen with BeOS software though, so I'd go with the 
simplicity of the MIT license.

I think we just need to add a comment at the top of each file. This is 
from one of the OBOS files:
/* 
** Copyright 2002-2003, Axel D=F6rfler, ax...@pi.... All 
rights reserved.
** Distributed under the terms of the OpenBeOS License.
*/

> > >I will probably start the new GUI from scratch, so maybe we could 
> > > split
> > >the code into folders:
> > >-Network
> > >-OldGUI
> > >-NewGUI
> > >
> > >I think it is quite hard to get stuff deleted from CVS.
> > >
> > >Renaming might also be a problem, so I will ask now: Is there any 
> > >reason for the "B" on the start of the network classes=3F 
> Yes renaming stuff on cvs can be a problem. The reason of the B for 
> the 
> server handlers is that I was going to change everything with a B in 
> front of it. Much like the Be API classes, but I never did it. So I 
> ended up with two standards for class naming. We should decide which 
> one to follow, BMsnClassName or MSNClassName, or leave it as is.

When I write code, I use the "B" to remind me that I'm using one of the 
classes provided by Be. I'd prefer "MsnClassName" or "MSNClassName" 
(don't mind either of those).
 
> > >
> > Mmm, which classes are you gonna start on=3F because the problem is 
> > I'm 
> > also 
> > working on some of those classes...couldn't you change the code of 
> > Daniel's 
> > classes, or would that be too much trouble=3F
> > 
> > >I think other people have mentioned it. I just often get the 
> > > feeling
> > >that less people reply to me when I'm on BeMSN, I guess that's due 
> > > to
> > >messages not arriving.
> > >
> > >Also, mik was on BeOS and I was using MSN 6, and we experienced a 
> > > few
> > >times where we didn't get each others messages.
> > >
> > I doesn't happen too often, I'm using BeMSN almost the whole time 
> > now...since I'm working on BeOS for my M. Sc. now...it's a lot 
> > stabler now, 
> > I'm also getting reports from people at BeShare about that...btw, 
> > we 
> > two 
> > people now, who offered to be beta testers...should I ask them to 
> > join this 
> > list=3F or post their feedback in the forums=3F
> I will say for now to post their feedback in the forums. Let's wait 
> until we are a little more organized on the source, the cvs server, 
> license, and everything else. How about you, what do you think=3F

I agree. Wait until we're a bit more organised.

> Regards
> 
> Daniel

Simon