Monday, October 27, 2008

GPL Project Watch List for Week of 10/24

The GPL v3 Watch List is intended to give you a snapshot of the GPLv3/LGPLv3 adoption for October 18th to October 24th 2008.

This Week:
  • Week Summary
  • New Projects
  • The Next Step for FOSS Adoption
  • User Contributions

This week our GPL v3 count is at 3349 GPL v3 projects, an increase of 112 GPL v3 projects. The AGPL v3 count is at 181 AGPL v3 projects. The LGPL v3 number is at 400 LGPL v3 projects, an increase of 55 LGPL v3 projects.





















New project conversions this week include:
  • Hibersap: Hibersap is a small framework that offers an abstraction layer on top of the SAP Java Connector (JCo). It maps Java classes to SAP function modules using Java Annotations and reduces the technical code to call a function in a SAP back-end system.

  • Voice Mail Viewer for Asterisk: Visual voicemail viewer for Asterisk/AsteriskNOW written in PHP. Users log in with their extension and v/m password and can download messages with the web browser.

  • jwaBlogger: jwaBlogger is social links/blogging software, that can easily be added to your website. jwaBlogger provides full HTML support, RSS and Atom feeds, a most popular blog entry history, and more. Example at: http://www.jwablogger.org.

********************************************************************************

FOSS users are becoming increasingly apathetic regarding the proactive management of software obtained for nominal cost. The recent Debian example comes to mind, where for an extended period of time, OpenSSL within it had been modified with a code checking tool. Such modification removed a programmatic element important to the generation of the key, such that the total possible key combinations were effectively reduced to a fraction of the total unbroken possibilities. This problem existed for nearly two years, with countless users depending on the code, using vendor solutions to test for the same things, and yet this went undetected.

Our government is embracing FOSS publicly, yet I have heard horror stories. They do not understand the management requirements of software delivered without a vendor, yet they have the same expectations.

http://www.gcn.com/online/vol1_no1/47320-1.html?page=1

Without a defined and active process for the ongoing and diligent public management of software, our government could be stepping into FOSS unprepared. If their motivation is cost, they will under staff the management resources that should be diligently testing all software. While I hope that they are going to staff for increased management requirements in the use of FOSS, there is no assurance either way. What makes the situation even more difficult is that there is no clear process or method for the government to implement that will offer a high degree of quality in FOSS investments.

What is lacking is not the desire to check. The responsibilities tied to the development of a FOSS project no longer ends when the project is compiled. Quality assurance and validation steps are so critical to the ongoing build process that the community needs to be part of it. Commercial vendors do not release code until it has survived a series of tests. Commercial vendors have liabilities to protect their investment, and do so through structured testing and processes, since their money is better spent in quality assurance than in remediation and legal actions afterwards.

FOSS needs a repeatable, measurable, verifiable and public checklist of testing and processes performed by the community in a "trusted" manner to safeguard the code that we all depend on. A public forum allows all of us to check an application, see which tests have been performed and which have not, allows us to contribute to the process, and qualify the contributions of others.

While the code is transparent, who has the skills and ability to look at it with the depth and creativity required these days? We need to make the management and ongoing qualification of open source software a community effort. By having the community actively involved in all pieces of quality assurance, we will have a greater understanding for the complexity in certifying code for distribution, and we will be able to verify that such work has been done.

The answer is not just to engage professional services, or use open source software that is financially backed by a large vendor. Since we lack transparency into the detailed, complex and ever changing process for testing software components, we are better to choose commercial solutions with contracts that put liability on the vendor. Additionally, mitigating the unknown risk of the use of FOSS with service contracts undermines some of the core principles of FOSS. If our only solution is to engage services, our freedoms in the use of FOSS are being undermined due to our inability to use the community to grasp, understand, constrain and manage the problem.

NIST sponsors http://cwe.mitre.org, the Common Weakness Enumeration. It is a database for identifying and describing in a common language, programmatic and architectural weaknesses within software, hardware and operating systems. It provides a reasonable starting point from which to build processes upon.

http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-0166

http://cwe.mitre.org/data/definitions/310.html

If we use a public and transparent process for the certification of FOSS, continuing in the spirit of how the code was developed, the strength of the community can actively participate in the management of unknown risk in software. We as a community can impose basic qualitative requirements on software packages. This community involvement in the validation of the code is a natural progression of the popularity and ubiquitous nature of FOSS in our computing lives.

In conclusion, the solution for software quality assurance is in the control of the user community. We need a public process to define, manage and implement validation processes, as well as a community effort to invite an ongoing process to post those results. If our professional services suppliers are worthy of their role of managing open source usage, they should be actively posting their tests, their reviews, their reports. If they do not have the requisite skills to help us manage this problem, we need a better process, and better providers, to help us manage this challenge and it is not going to get any easier soon. We owe this to ourselves, the success and health of our financially strained businesses worldwide, and our national and international security to get this right.



****************************************************************************
We appreciate all the contributions that have been made, either through our form on our web page or by email, and we also like to hear why you are changing your project's license as in the email above. It gives us more insight into which direction license trends are moving. We will continue to post up user contributions to our blog each week, and we may quote parts of your emails. If you wish the email to remain private, just mention so and we will not disclose any part of it.

Link Partners
If you are willing to copy and tranlate the content weekly, please let me know - you will receive the content as soon as it is available, and you site will be listed as a translation. I can send you a bit of tracking code so that you get credit for your contribution to the readership of this site
Post your link on the bottom of the blog page.

Send me a note at rdgroup@airius.com that you are using some or all of the content
I will make sure that we host links to your sites, and we will be able to use your content within this site as well.

************************************************************

Notable Mention

The Research Group actively takes submissions from visitors on updates on new GPL v3/LGPL 3 projects. We are amazed at the number of submissions we have gotten to date, but even more so, we are incredibly grateful to over 100 core contributors who have devoted their time and resources at helping us provide up-to-date information.

************************************************************

Subscription

For more information, go to http://gpl3.blogspot.com/.

To stop receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "unsubscribe:gpl3".

To start receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "subscribe:gpl3".

************************************************************

Our Sponsor, Palamida, Inc.

The GPL3 project, sponsored by Palamida, Inc (http://palamida.com/ ), is an effort to make reliable publicly available information regarding GPLv3 license usage and adoption in new projects.

The opinions expressed within the GPL3 Information Blog are exlusively those of Ernest Park, the subjects interviewed and the contributing authors, and are not intended to reflect the positions of Palamida, Inc and its employees.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License .

************************************************************

Palamida was launched in 2003 after its founders learned first-hand what happens when companies don't have full visibility into the code base of their software applications based on Open Source Software. Their experiences inspired them to create a solution to streamline the process of identifying, tracking and managing the mix of unknown and undocumented Open Source that comprises a growing percentage of today's software applications. Palamida is the industry's first application security solution targeting today's widespread use of Open Source Software. It uses component-level analysis to quickly identify and track undocumented code and associated security vulnerabilities as well as intellectual property and compliance issues and allows development organizations to cost-effectively manage and secure mission critical applications and products.

For more information about FOSS management solutions, go to http://palamida.com/, or send a note to sales@palamida.com.

Please mention the GPL3 site when you reach out to Palamida.


The Research Group (rdgroup@airius.com)

Ernest Park
Edwin Pahk
Antony Tran
Kevin Howard





Saturday, October 18, 2008

GPL Project Watch List for Week of 10/17

The GPL v3 Watch List is intended to give you a snapshot of the GPLv3/LGPLv3 adoption for October 13th to October 17th 2008.

This Week:
  • Week Summary
  • New Projects
  • Open Office 3: The Spread of Open Source
  • User Contributions
Consistent Conversion
The GPLv3 License continues to be popular after over a year since its release. Conversion rates have stayed consistent as projects continue to use GPLv3 to protect the freedom of their software.

This week our GPL v3 count is at 3334 GPL v3 projects, an increase of 97 GPL v3 projects. The AGPL v3 count is at 181 AGPL v3 projects. The LGPL v3 number is at 370 LGPL v3 projects, an increase of 25 LGPL v3 projects.





















New project conversions this week include:
  • DbUpdater: A customizable tool to implement the database schema version control. It can be used with any DBMS.

  • r3alm: R3alm is a third version of Realm, a simulation game where you develop a community, through characters. Each character can be assigned actions, and have statistics. In addition, your civilization has statistics such as food, population, etc.

  • rjudge: rjudge is a problem test tool for Olympiad in Informatics. We have finished the development of rctl - the coreutil of rjudge. We have put it into public and we want to receive more feedback.

********************************************************************************

Open Office 3: The Spread of Open Source

The long awaited Open Office 3 has just been released and it has caused openoffice.org's servers to be overloaded. The open source software is, for those of you who do not already know, a free alternative to Microsoft Office. This is build 9358, RC 4, of Open Office 3 and has been named the final version of the program as reported by crn.com. After its release last week, one of my coworkers went to download the program to check licensing information, but the site was too busy for him to access the download. It seems his predicament was shared by many other people who were eager to obtain a copy of the new suite. The popularity of open source is definitely growing, and in this instance it looks like demand exceeded supply (in terms of bandwidth that is). Open Office has grown to a point where it has become a formidable competitor to Microsoft Office in market share and in features.

From what I have heard and read about so far it seems that this release of Open Office has been improved greatly, making it a great time for anyone considering adopting to actually do it. Open office is capable to open Microsoft Office 2007 applications, which makes it worth it right there. There are many other free Office readers out there, but the quality of this suite will make it stand out from all the others. Other features such as an improved Spell Check in Writer have been added. The GUI has also been made more presentable, although still not as fancy as Microsoft Office, which can be a good or bad thing depending on how annoyed you are by GUI.

In an article I wrote two weeks ago, the current economic situation is making it even more beneficial to migrate to open source software. The high traffic for Open Office 3 is proof that more people are adopting open source software. Microsoft has even given kudos to Open Office, saying that it is a bigger competitor than Google Apps. As to whether that is a direct compliment to Open Office or indirect insult to Google Apps is up for interpretation, but regardless Open Office is getting more and more attention from the public and commercial companies. With recession looming, free software should be looking very appealing compared to proprietary software.

People's resistance to change is hindering open source adoption. Even though there are many benefits to open source, the majority of people are still hesitant to change their software and learn the new program. But Open Office really tries to make the shift as easy as possible. Being able to read Microsoft Office documents and emulating many of their features reduces how much a person has to learn if they want to switch over. With the ease of adoption, open source benefits, and low cost, now is really the time for Joe the Computer User to try open source, starting with Open Office.

-Antony Tran

Reference:

http://www.crn.com/software/211200503

http://www.techradar.com/news/computing/microsoft-open-office-a-bigger-rival-than-google-apps-476243

http://www.yellmalta.com/y/YellTopStories/tabid/94/selectmoduleid/527/ArticleID/495/reftab/36/Default.aspx

http://blogs.zdnet.com/open-source/?p=2997


****************************************************************************
We appreciate all the contributions that have been made, either through our form on our web page or by email, and we also like to hear why you are changing your project's license as in the email above. It gives us more insight into which direction license trends are moving. We will continue to post up user contributions to our blog each week, and we may quote parts of your emails. If you wish the email to remain private, just mention so and we will not disclose any part of it.

Link Partners
If you are willing to copy and tranlate the content weekly, please let me know - you will receive the content as soon as it is available, and you site will be listed as a translation. I can send you a bit of tracking code so that you get credit for your contribution to the readership of this site
Post your link on the bottom of the blog page.

Send me a note at rdgroup@airius.com that you are using some or all of the content
I will make sure that we host links to your sites, and we will be able to use your content within this site as well.

************************************************************

Notable Mention

The Research Group actively takes submissions from visitors on updates on new GPL v3/LGPL 3 projects. We are amazed at the number of submissions we have gotten to date, but even more so, we are incredibly grateful to over 100 core contributors who have devoted their time and resources at helping us provide up-to-date information.

************************************************************

Subscription

For more information, go to http://gpl3.blogspot.com/.

To stop receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "unsubscribe:gpl3".

To start receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "subscribe:gpl3".

************************************************************

Our Sponsor, Palamida, Inc.

The GPL3 project, sponsored by Palamida, Inc (http://palamida.com/ ), is an effort to make reliable publicly available information regarding GPLv3 license usage and adoption in new projects.

The opinions expressed within the GPL3 Information Blog are exlusively those of Ernest Park, the subjects interviewed and the contributing authors, and are not intended to reflect the positions of Palamida, Inc and its employees.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License .

************************************************************

Palamida was launched in 2003 after its founders learned first-hand what happens when companies don't have full visibility into the code base of their software applications based on Open Source Software. Their experiences inspired them to create a solution to streamline the process of identifying, tracking and managing the mix of unknown and undocumented Open Source that comprises a growing percentage of today's software applications. Palamida is the industry's first application security solution targeting today's widespread use of Open Source Software. It uses component-level analysis to quickly identify and track undocumented code and associated security vulnerabilities as well as intellectual property and compliance issues and allows development organizations to cost-effectively manage and secure mission critical applications and products.

For more information about FOSS management solutions, go to http://palamida.com/, or send a note to sales@palamida.com.

Please mention the GPL3 site when you reach out to Palamida.


The Research Group (rdgroup@airius.com)

Ernest Park
Edwin Pahk
Antony Tran
Kevin Howard





Saturday, October 11, 2008

GPL Project Watch List for Week of 10/10

The GPL v3 Watch List is intended to give you a snapshot of the GPLv3/LGPLv3 adoption for September 26th to October 3rd 2008.

This Week:
  • Week Summary
  • New Projects
  • Follow up: Jacobsen and US Copyright Law
  • User Contributions

Making Progress
If you haven't noticed already, we'd like to welcome back a member to our team, Antony Tran. After a brief hiatus, he has agreed to come back on board to help us manage the blog and GPL3 project. Welcome back.

This week our GPL v3 count is at 3237 GPL v3 projects, an increase of 22 GPL v3 projects. The AGPL v3 count is at 181 AGPL v3 projects. The LGPL v3 number is at 345 LGPL v3 projects, an increase of 51 LGPL v3 projects.

















New project conversions this week include:
  • Multigrid Contact Detection: libmgcd is a multigrid contact detection (MGCD) library

  • euFileUpload: A module to upload files. To be used in web-based applications. Written in PHP

  • luckybackup: A powerful, fast and reliable backup & sync tool.

********************************************************************************
I wrote about FOSS licenses and U.S. Copyright law back in June, prior to the case of Jacobsen v. Katzer coming out in mid-August:

http://gpl3.blogspot.com/2008/06/gpl-v3-watch-list-is-intended-to-give.html

To update that post a bit, the Jacobsen decision deserves mention. The case dealt with code licensed under the Artistic License 1.0 which was used in another project without complying with the terms of the license. See the link below on techlawjournal.com for more background. The central question of the case was whether the terms of the license were "conditions" that limited the scope of the copyright license, as opposed to "covenants" which define the terms for the use of the code. The court concluded the terms were "conditions."

While this may seem insignificant or merely a semantic non-issue, the remedies available for noncompliance with the "condition" of an open source license form the basis of the entire FOSS movement. The significance is that if a "condition" is broken or not followed, the person who broke or did not follow the particular condition is no longer entitled to use of the software under the license terms and such use is therefore copyright infringement. A remedy for copyright infringement is injunctive relief which means the violator can be prevented from further use of the software under the license or be required to follow the conditions if further use is desired.

If a "covenant" is broken or not followed, such violation is considered merely a violation of a contract term, which means the remedy is monetary and *not* injunctive. In that case the violator would still have a license to use the software and would merely have to pay contract damages.

Injunctive relief allows copyright holders who license their works under FOSS licenses to preserve the desired attribution, modification and distribution rights, which protects the openness of the code and preserves the rights of downstream users to have access to the code for research, learning or improvement. Having this decision on the books, with its clear discussion not only of the license in question, but also of the FOSS movement and its benefits, will only help the movement grow.

-Kevin Howard

References:http://www.lessig.org/blog/2008/08/huge_and_important_news_free_l.html

****************************************************************************
We appreciate all the contributions that have been made, either through our form on our web page or by email, and we also like to hear why you are changing your project's license as in the email above. It gives us more insight into which direction license trends are moving. We will continue to post up user contributions to our blog each week, and we may quote parts of your emails. If you wish the email to remain private, just mention so and we will not disclose any part of it.

Link Partners
If you are willing to copy and tranlate the content weekly, please let me know - you will receive the content as soon as it is available, and you site will be listed as a translation. I can send you a bit of tracking code so that you get credit for your contribution to the readership of this site
Post your link on the bottom of the blog page.

Send me a note at rdgroup@airius.com that you are using some or all of the content
I will make sure that we host links to your sites, and we will be able to use your content within this site as well.

************************************************************

Notable Mention

The Research Group actively takes submissions from visitors on updates on new GPL v3/LGPL 3 projects. We are amazed at the number of submissions we have gotten to date, but even more so, we are incredibly grateful to over 100 core contributors who have devoted their time and resources at helping us provide up-to-date information.

************************************************************

Subscription

For more information, go to http://gpl3.blogspot.com/.

To stop receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "unsubscribe:gpl3".

To start receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "subscribe:gpl3".

************************************************************

Our Sponsor, Palamida, Inc.

The GPL3 project, sponsored by Palamida, Inc (http://palamida.com/ ), is an effort to make reliable publicly available information regarding GPLv3 license usage and adoption in new projects.

The opinions expressed within the GPL3 Information Blog are exlusively those of Ernest Park, the subjects interviewed and the contributing authors, and are not intended to reflect the positions of Palamida, Inc and its employees.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License .

************************************************************

Palamida was launched in 2003 after its founders learned first-hand what happens when companies don't have full visibility into the code base of their software applications based on Open Source Software. Their experiences inspired them to create a solution to streamline the process of identifying, tracking and managing the mix of unknown and undocumented Open Source that comprises a growing percentage of today's software applications. Palamida is the industry's first application security solution targeting today's widespread use of Open Source Software. It uses component-level analysis to quickly identify and track undocumented code and associated security vulnerabilities as well as intellectual property and compliance issues and allows development organizations to cost-effectively manage and secure mission critical applications and products.

For more information about FOSS management solutions, go to http://palamida.com/, or send a note to sales@palamida.com.

Please mention the GPL3 site when you reach out to Palamida.


The Research Group (rdgroup@airius.com)

Ernest Park
Edwin Pahk
Antony Tran
Kevin Howard





Friday, October 3, 2008

GPL Project Watch List for Week of 10/03: Financial Crisis and Open Source

The GPL v3 Watch List is intended to give you a snapshot of the GPLv3/LGPLv3 adoption for September 26th to October 3rd 2008.

This Week:
  • Week Summary
  • New Projects
  • Financial Crisis: How will it affect Free and Open Source software?
  • User Contributions

AGPL v3 Momentum

We have noticed an increase in AGPL v3 numbers this week, which shows that the interest in the AGPL v3 is still growing. It is a relatively small license compared to the GPL v3, but is finding its niche in the market. Recently we were also contacted by a user of our site about our AGPL v3 information, who is looking to developer psychology related services using AGPL v3 software. It just goes to show that the AGPL has caught the interest of a select group of people and can be used in a wide range of fields.

This week our GPL v3 count is at 3215 GPL v3 projects, an increase of 31 GPL v3 projects. The AGPL v3 count is at 181 AGPL v3 projects, up 51 projects. The LGPL v3 number is at 294 LGPL v3 projects.
























New project conversions this week include:
  • C/C++ Libraries: Collection of C and C++ libraries, and C++ classes under the GNU Lesser General Public License. This collection includes all versions that are under the GNU LGPL, even if a newer version is available.

  • PeerSE: This is a Java based xBase engine to read write and update dbf files. Using the package's classes and methods programmers can process dBase III and IV files and some clones (e.g. Clipper/FoxPro) along with index and tag files and the individual fields.

  • Zimplit CMS: Zimplit is the easiest Content Management System (CMS) ever made. It is extremely lightweight, simple and customizable. Zimplit consists only one file. No database needed. With Zimplit you can edit any HTML/CSS page.

********************************************************************************

Financial Crisis: How will it affect Free and Open Source software?

The current financial and credit crisis on Wall Street has had a global affect on the economy that we have not seen since the Great Depression. The economic downturn has hurt nearly all sectors of the economy, the tech industry being no exception. So in these times of uncertainty, it is obvious that IT companies of all sizes will be looking for anyway to reduce costs, one of them being the implementation of open source software. Will this economic crisis be somewhat positive by accelerating the use of open source?

According to Matt Asay from CNET the answer is yes across the board. In an informal poll he performed, he asked various open source companies how the failing economy has been affecting their sales. Some might think that with the Dow Jones Industrial Average down 4000 points over the past year, these open source companies would have headed in the same direction with everyone else. However, every company that Matt Asay polled is recording record sales. It is not surprising to us or to Matt that companies are shifting from expensive proprietary software to cost efficient open source software, but it did take us back that every single company that Matt polled is doing so well. It solidifies the fact that open source companies are in a different market and a different business.

Open source has always been the underdog when competing for commercial business. There might have been too much fear or misinformation about what open source is and how it works, and before the economy began to fall, there was no reason to fix that which was not broken. But hard times call for drastic measures and for these companies to reevaluate their business models and spending. Companies can save hundreds of thousands of dollars by switching over to open source software and lose little to none functionality, perhaps even gaining in functionality. In an article entitled Five programs you can afford in a financial meltdown, Steven J. Vaughan-Nichols lists open source alternatives to popular proprietary software programs. Almost every piece of software has an open source counterpart these days and it is becoming more costly to ignore them. Perhaps one of the biggest myths about open source software is that it is a lesser product when in actuality it is just a different product built a cheaper way. The largest costs to implementing open source software, and what I suspect has held the conversion back for so long, is relearning, retraining, and readjusting the business model for the new open source software. But these costs are more time and effort than actually cash spending, and with the economy in the state that it is in, this is no time to be lazy.

The times are changing and are changing fast with what is going on in politics, the world, and the economy. The opportunity for open source to go mainstream is drawing near due to factors such as the falling economy and advancements in online technology such as Web 2.0 and cloud computing, mentioned in last weeks article. This may be a bit cynical, but it seems fitting that as capitalism is failing, open source is benefiting. Open source, which came out of the free software movement, was anti-capitalism and sought to free developers and users from the grips of proprietary software. It really is no surprise that open source is doing well during this financial crisis.

-Antony Tran
-Edwin Pahk

References:

http://www.eweek.com/c/a/Linux-and-Open-Source/Financial-Crisis-Offers-Opportunity-for-Linux-Open-Source/
http://www.thevarguy.com/2008/09/30/will-the-financial-crisis-boost-open-source/
http://news.cnet.com/8301-13505_3-10057441-16.html
http://www.computerworld.com.au/index.php/id;97976866;fp;4;fpid;1968336438


****************************************************************************
We appreciate all the contributions that have been made, either through our form on our web page or by email, and we also like to hear why you are changing your project's license as in the email above. It gives us more insight into which direction license trends are moving. We will continue to post up user contributions to our blog each week, and we may quote parts of your emails. If you wish the email to remain private, just mention so and we will not disclose any part of it.

Link Partners
If you are willing to copy and tranlate the content weekly, please let me know - you will receive the content as soon as it is available, and you site will be listed as a translation. I can send you a bit of tracking code so that you get credit for your contribution to the readership of this site
Post your link on the bottom of the blog page.

Send me a note at rdgroup@airius.com that you are using some or all of the content
I will make sure that we host links to your sites, and we will be able to use your content within this site as well.

************************************************************

Notable Mention

The Research Group actively takes submissions from visitors on updates on new GPL v3/LGPL 3 projects. We are amazed at the number of submissions we have gotten to date, but even more so, we are incredibly grateful to over 100 core contributors who have devoted their time and resources at helping us provide up-to-date information.

************************************************************

Subscription

For more information, go to http://gpl3.blogspot.com/.

To stop receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "unsubscribe:gpl3".

To start receiving these weekly mailings, please send a message to rdgroup@palamida.com with the subject "subscribe:gpl3".

************************************************************

Our Sponsor, Palamida, Inc.

The GPL3 project, sponsored by Palamida, Inc (http://palamida.com/ ), is an effort to make reliable publicly available information regarding GPLv3 license usage and adoption in new projects.

The opinions expressed within the GPL3 Information Blog are exlusively those of Ernest Park, the subjects interviewed and the contributing authors, and are not intended to reflect the positions of Palamida, Inc and its employees.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License .

************************************************************

Palamida was launched in 2003 after its founders learned first-hand what happens when companies don't have full visibility into the code base of their software applications based on Open Source Software. Their experiences inspired them to create a solution to streamline the process of identifying, tracking and managing the mix of unknown and undocumented Open Source that comprises a growing percentage of today's software applications. Palamida is the industry's first application security solution targeting today's widespread use of Open Source Software. It uses component-level analysis to quickly identify and track undocumented code and associated security vulnerabilities as well as intellectual property and compliance issues and allows development organizations to cost-effectively manage and secure mission critical applications and products.

For more information about FOSS management solutions, go to http://palamida.com/, or send a note to sales@palamida.com.

Please mention the GPL3 site when you reach out to Palamida.


The Research Group (rdgroup@airius.com)

Ernest Park
Edwin Pahk
Antony Tran
Kevin Howard