I'll use coding separate from bfw. Need to get used to it and later contribute back codes to them.
On Tue, Jul 6, 2010 at 1:42 PM, Raja Iskandar Shah <[email protected]> wrote: > assuming your application is modular / your files are separate from the bfw > files / bfw is used as a libary / but your app is dependent on the bfw files > : should acknowledge bfw (like our ida application) > > if your application is packaged together with the bfw as a component but > files are separate > must acknowledge use of bfw like example: > This software includes SQLite 3.6.22. > EMX sprintf and sscanf methods by Eberhard Mattes > Copyright © 1990-1998 Eberhard Mattes. > Portions of this software are copyright © 1996-2004 The FreeType Project. > All rights reserved. > Zlib compression library > Developed by Jean-loup Gailly and Mark Adler: (Copyright © 1995-2004 by > Jean-loup Gailly and Mark Adler) > > if you are adding lines to the bfw source codes / making a fork / making a > derivative product - then it depends on the open source licensing: the gpl > requires that you make it gpl also; bsd/mit is more permissive to do > whatever you wish. personally i recommend you do a fork, then inform the bfw > project team about it, and email them to your codes. > > http://en.wikipedia.org/wiki/Fork_%28software_development%29 > > -- Join Open Source Developers Club Malaysia http://www.osdc.my/ Facebook Fan page http://www.facebook.com/group.php?gid=98685301577 http://www.facebook.com/OSDC.my You received this message because you are subscribed to the Google Groups "OSDC.my Mailing List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/osdcmy-list?hl=en
