Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Shedding commercial attitudes towards documentation

Will secret copyright treaty restrict your digital rights?

Saving the "Best" for Last - Fedora 12 (Constantine)

LinuxCertified Announces its next Linux System and Network Administration BootCamp

The Problem With The Linux Community

Vim 101: A Beginner's Guide to Vim

Open Source Science: A Revolution From Within

openSUSE 11.2-- Incremental Updates, Plenty of Polish

Microsoft, other rivals slam Google Chrome OS

Intel Linux Graphics Shine With Fedora 12




Technical Specialist II – PC – LAN (AZ)
Next Step Systems
US-AZ-Scottsdale

Justtechjobs.com Post A Job | Post A Resume
:FSFE and GPL-Violations.org on Reporting (and Avoiding) Licensing Issues
FSFE and GPL-Violations.org on Reporting (and Avoiding) Licensing Issues
Dec 10, 2008, 22 :01 UTC (0 Talkback[s]) (2190 reads)

(Other stories by Kristin Shoemaker)

[ Thanks to sakgarg for this link. ]

"Some of the advice is common sense (suspected violations are best handled in private, reported only to the involved parties, and organizations such as GPL-Violations and the appropriate branch of the Free Software Foundation), but reminders are always useful, especially in the heat of the moment.

"The guide illustrates that reporting a possible license violation should be as specific as filing a bug report. Forwarded email threads, if necessary, should only include pertinent information. Links to the project, the parts of the code involved, as well as the license by which the code is protected should be included."

Complete Story

Related Stories:
Non-Free "Blobs" in the Linux Kernel?(Dec 02, 2008)
Proprietary Firmware and the Pursuit of a Free Kernel(Dec 01, 2008)
The Linux Licensing Labyrinth(Nov 19, 2008)
FSF Releases New Version of GNU Free Documentation License(Nov 04, 2008)
FSFE's Antitrust Victory With Samba(Oct 25, 2008)
Support the Free Software Foundation's High-Priority List Campaign(Oct 25, 2008)
Harald Welte on His New Role With VIA(Aug 12, 2008)



No talkbacks posted.
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.commediabistro.comJusttechjobs.comGraphics.com

Search:

WebMediaBrands Corporate Info

Legal Notices, Licensing, Permissions, Privacy Policy.
Advertise | Newsletters | Shopping | E-mail Offers | Freelance Jobs