On Wed, Feb 16, 2011 at 5:05 PM, Andreas Kotes <[email protected]>wrote:
> Hello,
>
> * Marc-André Moreau <[email protected]> [20110216 22:58]:
> > On Wed, Feb 16, 2011 at 3:53 PM, Otavio Salvador <
> [email protected]>wrote:
> > > On Wed, Feb 16, 2011 at 19:30, Jay Sorg <[email protected]> wrote:
> > > > I would like to state that I support with this change.
> > > > In my experience, the GPL has only created more problems than
> solutions.
> > > > It seem like we get all the bad(companies pass us over) and none of
> > > > the good(changes are not put back upstream).
> > >
> > > I disagree. We (O.S. Systems) has been pushing hard to make everything
> > > on upstream and has been doing good up to now.
> > >
> > > > Usual we don't want or can't use the changes anyway so we are just
> > > > left with the bad.
> > >
> > > In this case you're violating GPL (if you put those into products).
> >
> > That's the whole point. There are companies who will either find ways
> around
> > the GPL virality or will simply violate the GPL without care. Unless you
> > have the time and energy to pressure those companies into contributing
> their
> > code,
>
> I have good ties to the very experienced guys of
> http://www.gpl-violations.org/ and am more than happy to establish
> contact and ensure involvement should such a case come to our collective
> attention.
>
> I have reported some violations myself in the past. For instance, I once
noticed my Lexmark printer was running an embedded Linux system for which no
source code was available. It was a time-consuming task that only got me to
some unmentioned FTP server somewhere with some source code in it. In any
case, it was pretty much useless, since the important part was a proprietary
server running on top of the Linux distribution, for which the source code
was not available.
Yeah, we could go on and on about this, I just think it is a very time
consuming task that drains your energy. We might as well just focus on
coding instead with people who want to collaborate.
> > I don't see much use in having such a viral license. Also, even if you
> > manage to pressure people into releasing their source code to comply with
> > the GPL, you probably would not want the code anyway, since it's probably
> > hackish and specific to certain needs (not ready for contribution or
> > external use).
>
> my FUD alert just went wild ...
>
Nah, I actually did get some code myself by repeatedly sending emails
regarding GPL violations. I did not get the code half the time, and when I
got it, it was some source archive with no version control, no
documentation, and not that much interesting after all.
There are some interesting cases like Linksys, but the true fun part came
when people really started modifying the original code a lot to build
distributions that don't look much like the original code.
>
> > I think we should focus on working with the people that are
> > willing to collaborate than working with people who aren't willing to
> > collaborate. By switching to permissive licensing, we will get
> contributions
> > from people that are actually willing to contribute in the first place.
>
> ... and not get code from people who don't want to see their code in
> commercial-only products anymore. QED.
>
> Well, from what I've seen you haven't really contributed much code, if any.
How would this apply to you?
> Andreas
>
> --
> Andreas Kotes, CISSP, CCNA - flatline IT services - ISP & IT Consulting
> "Love many things, for therein lies the true strength, and whosoever
> loves much performs much, and can accomplish much, and what is done
> in love is done well." -- Vincent van Gogh
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Freerdp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
