7 Oct 2004 16:25
11 Oct 2004 23:52
Must ALL or SOME source code dists have license notice in each file?
Geka M <gekacheka <at> yahoo.com>
2004-10-11 21:52:26 GMT
2004-10-11 21:52:26 GMT
Preview Firefox releases strip the license block from included source js and xul files. Mozilla Public License 1.1 says: [MPL1.1 sec3.5] You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. [MPL1.1 sec1.11] "Source Code" means the preferred form of the Covered Code for making modifications to it, ... The Source Code can be in a compressed or archival form... (Note that the exception, "If it is not possible to put such a notice in a particular Source Code file due to its structure", does not apply to any text source code syntax that allows multiple comment lines.) Does sec3.5 mean A. ALL distributions of source code must have the license block in each file of the source code, or B. SOME distribution of source code must have the license block in each file of the source code ? In other words, is it ok to distribute source code where the license block has been stripped out of source files (say, to save space and bandwidth), as long as you also make available source code where the license block has not been stripped out? Arguments for 'A' and against 'B': Spirit: distributing copies of the source code without the owner's license in each file makes it more likely that source code will be illegally redistributed. (Someone who as only a copy without the license blocks is more likely to modify and redistribute it without understanding they need to get and distribute source with the license blocks, or to redistribute just part of the source and inadvertently leave out the license.) (Marketing: some paranoid organizations may shun all the code for fear of misusing source that wasn't clearly identified...) (Technical: stripping the license block messes up the code line numbers in error reports.) An argument for 'B' and against 'A': Technical: Distributing copies of the source code without the owner's license permits smaller executable distributions that include source code (such as xul and js files), at least using compression technology that does not compress across files (such as individual zip/jar files). (A workaround is to a create a zip (jar) file whose entries are not compressed, and then compress the whole zip [jar] file together inside another zip [xpi] file, so strings that are shared across file entries are discovered and compressed. This reduces xpi size, at expense of larger installed jar size.) Xul and js files in preview Firefox jars have the license block stripped out which assumes 'B', but that might be an oversight by FF developers. The discussions of section 3.5 in n.p.m.license seem only to say that the intent is to include the license block on every file, and do not discuss stripping license blocks from js and xul files for runtime distribution.
14 Oct 2004 13:02
Re: Must ALL or SOME source code dists have license notice in each file?
Gervase Markham <gerv <at> mozilla.org>
2004-10-14 11:02:14 GMT
2004-10-14 11:02:14 GMT
Geka M wrote: > [MPL1.1 sec1.11] "Source Code" means the preferred form of the > Covered Code for making modifications to it, ... The Source Code can > be in a compressed or archival form... I would say that the XUL and JS, as shipped with the preview release, is not the preferred form for making modifications. For example, the Windows build has all the MAC OS X-specific bits stripped out by the same preprocessor which removes the license blocks. So we should make the full source code available, as the license requires, but the shipped versions do not need it. Having said that, I designed the new machine-readable license blocks so that they have a summary line which can be retained by any stripping mechanism. It's rather sad that this isn't happening. I suspect, though, that it requires changes to the preprocessor. Gerv
15 Oct 2004 08:59
Re: Must ALL or SOME source code dists have license notice in each file?
Daniel Veditz <dveditz <at> cruzio.com>
2004-10-15 06:59:17 GMT
2004-10-15 06:59:17 GMT
Gervase Markham wrote: > > I would say that the XUL and JS, as shipped with the preview release, is > not the preferred form for making modifications. For example, the > Windows build has all the MAC OS X-specific bits stripped out by the > same preprocessor which removes the license blocks. Yes, definitely the *.jar files are not "source" code, they are processed and packaged. It's confusing that it looks like source, though. Perhaps it could be easily solved by putting a copyright/license file at the top of each archive, or a copyright comment in the zip archive itself (zip -z "This file copyright Mozilla Foundation. Source available under the MPL at..."). I don't know how many people would notice an archive comment, an obvious explanatory file at the top level might be best. Double-plus good because we'd then have a place to describe the copyright and trademark status of the images in the file. -Dan Veditz
15 Oct 2004 18:59
Re: Using MPL covered components in application
Gervase Markham <gerv <at> mozilla.org>
2004-10-15 16:59:56 GMT
2004-10-15 16:59:56 GMT
Marko Lahtinen wrote: > I was thingking about putting a splashscreen to my app. Can you give me a > short example what to write to > the splashscreen about the part that uses the MPL licensed component ? It doesn't necessarily have to be in the splash screen. Basically, just read the MPL and do what it says. Gerv
21 Oct 2004 14:24
26 Oct 2004 23:19
R monografia monografias dissertações tcc R
Monografia Administração <Monografiaex <at> xxx.com>
2004-10-26 21:19:15 GMT
2004-10-26 21:19:15 GMT
site Monografia express auxilia estudantes e profissionais na
preparação de suas pesquisas. Temos uma equipe preparada para o
desenvolvimento de monografias e projetos de monografia para a
conclusão de cursos de graduação, pós-graduação e
especialização.
Também desenvolvemos a formatação de monografias de acordo com as normas da
ABNT (Associação Brasileira de Normas Técnicas) ou conforme as regras de sua
Faculdade/Universidade.
Os serviços são desenvolvidos por profissionais altamente capacitados, ou seja,
pessoas preparadas especialmente para este tipo de serviço e que realizam o
trabalho de acordo com as normas da ABNT e da Metodologia do Trabalho
Científico.
monografia administração direito turismo economia letras pedagogia
monografias teses tese.
Sua monografia a partir de 350,00
http://monografiaex.t35.com/index1.html
http://monografiaex.vilabol.uol.com.br
31 Oct 2004 16:19
website hosting
forall2see_2000 <at> yahoo.com <forall2see_2000 <at> yahoo.com>
2004-10-31 15:19:13 GMT
2004-10-31 15:19:13 GMT
I would like to recommend my web host http://frontpage-web-hosting.org they are an excellent web hosting company with an incredible offer.
RSS Feed