[FW: Proposal: Remove GPL boilerplate at the top of every G2 file]
I'm the Debian maintainer for gallery2 and also part of the core gallery
team. Gallery is GPL licensed and currently has a GPL boilerplate (see
http://cvs.sourceforge.net/viewcvs.py/gallery/gallery2/index.php?rev=1.19&view=markup
for an example) in the header of each of its files. Is there any reason
to keep the ~865 byte header in each file?
I'm subscribed to the list - no Cc is necessary.
----- Forwarded message from Bharat Mediratta <bharat@menalto.com> -----
> Date: Mon, 17 Apr 2006 14:56:38 -0700
> From: Bharat Mediratta <bharat@menalto.com>
> To: "gallery-devel@lists.sourceforge.net" <gallery-devel@lists.sourceforge.net>
> Subject: [Gallery-devel] Proposal: Remove GPL boilerplate at the top of every G2 file
> List-Id: <gallery-devel.lists.sourceforge.net>
>
>
> By my estimates, we have 2342 files [1] containing the GPL boilerplate
> at the top of each file (out of 5127 files total [2]). That boilerplate
> is ~865 bytes [3].
>
> The total size of all files is 228M [2], of which 122M is locale files
> [4]. This leaves us with 106M of code files so dropping 2M of
> boilerplate will result in a 1% savings on file size. Every little bit
> helps, and I don't think this comes at a cost for us.
>
> Can anybody tell me why it might be bad to remove this boilerplate? We
> include a LICENSE document with the code, and we can maintain the
> boilerplate for 3rd party libraries. It seems redundant to include this
> in every single file...
>
> -Bharat
>
> ===
> [1]: find . -type f | xargs grep 'Gallery - a web based' | wc -l
> [2]: find . -type f | egrep -v CVS | wc
> [3]: based on looking at a few separate files -- it depends on the
> length of the filename.
> [4]: find . -type f -name '*.mo' -o -name '*.po' | wc
>
----- End forwarded message -----
--
----------------------------
Michael Schultheiss
E-mail: schultmc@debian.org
Reply to: