Phil,
Thanks for clarification. Your concerns are really a duplicate of
https://github.com/LMMS/lmms.io/issues/54.
Please feel free to chime in there.
In short, no one has really touched our LSP code in quite some time and
unless you know someone eager to work with our codebase, it won't happen
any time soon.
These undesired licenses should be hidden from selection and only offered
as backwards compatibility to honor historical data.
Each song, sample, preset, theme on our LSP is copyright of the submitter
and the lmms-devs can't change bad decisions without contacting each
contributor (hard to do, since user names on our LSPs don't even have
registered email addresses). The LSP is a great concept, but to be taken
as a serious collaborative platform it needs a lot of work. This issue
you've mentioned is one of many issues with the LSP, and we need help with
it. We're short on c++ developers, so the website stuff takes a back seat
to that. Sorry if that sounds grim, but we're always open to help. :)
-Tres
- [email protected]
On Sun, Feb 7, 2016 at 10:37 PM, Phil (list) <[email protected]> wrote:
> Tres,
>
> On Sun, 2016-02-07 at 21:31 -0500, Tres Finocchiaro wrote:
> > There's not much left from the original site... probably wasn't
> > handled/changed when we converted from sourceforge.
> > This conversation is best done as a dedicated lmms.io repo bug report
> > with the relevant files linked so we can investigate their history,
> > seek permission (prob from @tobydox if needed) and also discuss a
> > more permissive/permanent license.
>
> I'll file a bug as you suggest.
>
> > That said, the public should have little or no use with any of the
> > lmms.io website code... It's quite simple and specific. To make it
> > something more reusable, and to be consistent with the software
> > license, we'd be happy to do what it takes to make it better.
>
> It's not website code I'm referring to, it's the license designation
> for LMMS related files being posted to it such as: https://lmms.io/lsp/
> ?action=show&file=7972
>
> Thanks,
> Phil
>
> > -Tres
> > On Feb 7, 2016 9:15 PM, "Phil (list)" <[email protected]> wrote:
> > > I was poking around the lmms.io web site and ran across some files
> > > that
> > > were being distributed under a Common Public License. That was a
> > > new
> > > one to me so I did some poking around and now that I understand
> > > what it
> > > is (I think... as I didn't see a link to the definition or license
> > > on
> > > the site: https://en.wikipedia.org/wiki/Common_Public_License) So
> > > now
> > > I'm wondering... why was this license chosen for use on the site?
> > > Based on a quick bit of reading it's incompatible with the GPL,
> > > deprecated by it's creators, and not in the mainstream of creative
> > > licenses I've seen used. Just wondering why...
> > >
> > > Thanks,
> > > Phil
> > >
> > > -----------------------------------------------------------------
> > > -------------
> > > Site24x7 APM Insight: Get Deep Visibility into Application
> > > Performance
> > > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> > > Monitor end-to-end web transactions and take corrective actions now
> > > Troubleshoot faster and improve end-user experience. Signup Now!
> > > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> > > _______________________________________________
> > > LMMS-devel mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/lmms-devel
> > >
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
