doomred / hacer

  1. hacer
  2. Issues
  3. Embedded License Conflict
Open Closed
Marti Admin

You can't declare ISC and use GPL in the same source.

Please fix.

doomred Author

Re: @Marti:
It's an Issue, thank you for point out that Marti.
What I known from wikipedia page:

  • One can only link LGPL codes.

Will fix in next commit.

Marti Admin

Re: @doomred:

It's one of those curiosities with LGPL and GPL... keeping things free forever. JavaScript Modules (jsm) like usage are about the only way to use them together with some of the more unusual OSI approved licenses like ISC (which I hadn't heard of until just a short while ago especially when I ran by your script and went "What's this?" ;)

doomred Author

Re: @Marti:
hacer is actually a layout rewrite script, It will be awesome if the web master use some of codes from here. I think GPL LICENSE will be too much for the bureaucracy dumb to understand.

FYI:
I improve the license info of my derivative work of GM_config in the repo.
cuz I looks good to have multi-licenses in one repo for hacer

Marti Admin

Re: @doomred:

Not quite the solution I was thinking of putting it on a branch at https://raw.github.com/doomred/hacer/devvel/hacer.gm_config.js... this pretty much contradicts the concept of forking on GitHub... I'll have to run this by the team and see if they have any issues with it being done this way.

And our current header is this (which probably needs updating soon):

/*
Copyright 2009-2013, GM_config Contributors
All rights reserved.

GM_config Contributors:
    Mike Medley <medleymind@gmail.com>
    Joe Simmons
    Izzy Soft
    Marti Martz

GM_config is distributed under the terms of the GNU Lesser General Public License.

    GM_config is free software: you can redistribute it and/or modify
    it under the terms of the GNU Lesser General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.
*/

and your post header should be something along the lines of:

/*****************************
 * Description: Customized for hacer, just works & easy to use.
 * Edit & Optimize By:
 *             dye E. jarhoo(github.com/doomred),
 * Many Thanks To:
 *             zjworks,
\*******************************************************/
Marti Admin

Re: @doomred:

And now it's updated properly on the master... e.g. please use that header at minimum in your branch. Thanks. :)

doomred Author

Re: @Marti:

I am not going bore you, but I have no experance on copyright info about derivative works,

Is this what you mean, to the header of hacer.gm_config.js?



/*
Copyright 2009-2013, GM_config Contributors
All rights reserved.

GM_config Contributors:
    Mike Medley 
    Joe Simmons
    Izzy Soft
    Marti Martz

GM_config is distributed under the terms of the GNU Lesser General Public License.

    GM_config is free software: you can redistribute it and/or modify
    it under the terms of the GNU Lesser General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public License
    along with this program.  If not, see .
*/

/*****************************
 * Description: A derivative work of GM_config for hacer,
 *                               to be just works & easy to use.
 * Edit & Optimize By:
 *             dye E. jarhoo(github.com/doomred),
 * Many Thanks To:
 *             zjworks,
\*******************************************************/

FYI: Once I fixed out an issue in gm_config, I am going to put it on library somewhere...
Can you offer me some idea about library mirroring? I looks impossible to linking mirroredn library on different sites with only web hook set on github.(i.e I think I have to modify script by hand on every mirrored sites(for mirrored library on their site), so I think use raw github will be a nice one)

Marti Admin

Re: @doomred:

Is this what you mean...

Here is the current highlighted master license header at https://github.com/sizzlemctwizzle/GM_config/blob/master/gm_config.js#L1-L24 plus your header stating that you modified it afterwards... like you stated.

Once I fixed out an issue in gm_config

You might want to let us know upstream with a new issue ticket. I haven't been testing it since May when USO went down but it was working exactly how I was using it. :)

I looks impossible to linking mirrored library on different sites with only web hook set on github.

Fork it on GitHub and just reference your fork/branch in this user.js with the @require. There's no need to web hook it in for that usage. You can see my fork and my branches here. master branch is a mirror of upstream GM_config (GMC) and slave branch is around the last version of version 2ish. Sizzle uses commit hashes over major dot minor dot build versioning so that's why it's "2ish". You can create your own slave branch, or other name, on your own fork of GMC and modify to your hearts content.

Marti Admin

Re: @Marti:

Just remember to leave the master license header intact and add your own modification block attributing you and/or your project.

doomred Author

Re: @Marti:

Got it, committed it and Issue right on the way.
Thank you Marti for reporting this.

This Issue is going to be closed.