1
edit
Changes
m
no edit summary
==Open Source and Copyright Policy==
This talk was done by David Fewer. He is legal counsel for the Canadian Internet Policy and Public Interest Clinicand the Canadian Software Innovation Alliance. He also conducts a technology law clinic at the University of Ottawa. He was speaking about how open source development is affected by copyright law, specifically, the Canadian Software Innovation Alliance. This is an organization that encourages government to continue to support the open software industry which has enabled Canadian developers to have a competitive advantage compared to developers of more restricted countries like the USA. A point that was stressed was that copyright law is about balancing the rights of consumers and the compensation of the author. Licensing and copyright laws need to have limits and exceptions to ensure that consumers are protected. Three essential exceptions and limits are the ability to enforce a license, ability reverse engineering and the ability to interoperate with other technologies.
These new anti-circumvention laws would severely hinder competition in the market place. Currently, Canada has a very hands-off attitude towards consumer protection where it is believed that if consumers feel that they are not being treated fairly they will not purchase the product and that the market will protect itself. This is a flawed ideal in the context of the proposed legal framework as the market will no longer be open to competitors and will stifle innovation at every point possible. It is suggested that Canada need to have a much stronger consumer protection voice in government. I believe that part of this problem is that for people to be able to make decisions as to which products to support, they must have an understanding of the product at a conceptual level. This is fairly easy with tangible goods like a car but very difficult with intangibles like software. This is especially true in an ecosystem where proprietary, closed solutions are considered to be not only the norm, but the ideal.
==Fedora: The Future, First==
This talk was done by Paul Frields who is the Project Leader of Fedora. He is employed by Red Hat software in this position. Previous to his involvement in the Fedora project he was a public servant working many jobs including being a forensic scientist. He started using Red Hat Linux 11 years ago in his work because he was able to show the entire source code of the software he used which allowed him to provide further transparency regarding his evidence. Five years ago he starting teaching Linux use to other people in his field and a year later he learned about source code management and got involved in software packaging. Two years ago he became involved in Fedora governance and six months later was part of the release team.
Paul's main point seemed to be that when creating and managing an open software development community, it is best if the community is not treated as a second class member. He described how once Red Hat decided to stop distributing Red Hat Linux to the consumer market space that the company expanded the existing Fedora project to replace the offering represented by Red Hat Linux. When this was done Red Hat started developing and supporting Red Hat Enterprise Linux for the business world. They also marketed a corporate desktop version of their operating system, but like the enterprise server, this was only for paying customers. Early in the process there were a lot of impediments to the success of Fedora like the lack of a single repository for their packages. This caused Fedora to lose almost its entire community. During the first two Fedora releases Red Hat had no way to get people in the community involved in development. This makes it very difficult to have a sustainable community.
During the Fedora Core 3-6 time period, Red Hat was only interested in not breaking anything. At this time there was also a division between the Fedora Core where Red Hat engineers worked and Fedora Extras where the community worked. This highlighted that Red Hat was still considering contributions of community members to be inferior to their own engineers work. What ended up happening is that the community developed its own packaging guidelines and build systems. These systems and guidelines were superior to the internal Red Hat policies and systems and as a result Red Hat decided that for the Fedora 7 release there would be no distinction between Core and Extras. For the first time Fedora was not fragmented. This meant that there was no longer any special membership requirements.
It was clear to me that the key message of this presentation is that Open Source and Free software principles and processes must be adopted fully in order to maximize results. A company like Red Hat which has been built on free and open source software can still make the mistake of acting like a cathedral instead of a bazaar. This is a problem in many mature open source projects, especially those which are closed source software conversions. Like the Gnu Compiler Collection before it, Fedora stagnated when it shut its doors to the community and was eventually replaced by what the community ([http://en.wikipedia.org/wiki/GNU_Compiler_Collection#EGCS egcs]) created.
I believe that Paul's view on open source is that it is key to never bend principles for a short term improvement and to value a strong community. This is highlighted by some of the Fedora Project's recent decisions. They have adopted unreleased versions of some upstream packages (X Server 1.5) in their final releases and in their upcoming release they are using a new boot splash screen program that makes use of driver features which are only supported in a very small subset of supported hardware (Plymouth). This helps free and open source software in two main ways. It drives innovation and makes it nearly impossible for closed source applications to keep working with the latest software. This could cause a company to open their product in order to get their share of the Linux user base.
==Comparison==
I feel that both speakers value open source ideals, however, I feel that David is more interested in the letter of the license than the spirit. This is to be expected as he is legal counsel to a software alliance. Paul seemed to think of the copyright laws as an enabler of free and open development. I learned quite a bit about copyright, especially the differences between US copyright law and Canadian law. It was also really interesting to learn how much is allowed under the current copyright law in Canada. Both presenters stressed how important free and open development is to software, but looked at it from different viewpoints. The similarities are demonstrated in the example of proprietary drivers. David's organisation is against blocking reverse engineering as it limits competition and Paul's takes advantage of the opportunity by performing the reverse engineering.
=ignore below===Summaries of two talksConclusions=====What was each talk I learned a lot from both presenters and found both presentations to be very interesting. I believe that my views on Open Source and Free software are very similar to both presenters. Where I feel I learned the most is in the history and context. Through David I learned a lot about======What how Open Source and Free software works in copyright and patent law while I learned a lot of the history of community relations between Fedora and Red hat from Paul. I used Red Hat Linux from version 5.2 to version 9. I found that these operating systems were overly complex and noticed that there was a lot of work to be done on them. After the speakerFedora Core was started, I found that my needs weren's main t being met as well as they could be. It was at this point======What was when I switched to using the speaker's background and Ubuntu distribution. At this point of view=====Analysis of each speaker's views on ''open source'I didn't understand why this distribution was meeting my needs. He/she may not mention I later figured out that it explicitlyis solely because Ubuntu is developed in a community. You must listen and try This allows people who care about a specific area of the project to understand based work on what they want. This makes sure that there is enough labour to produce the end result as well as ensuring that motivated people are saying, working on the system. The next realisation I came to regarding Open Source and Free software was that some projects make tremendous use of other peoples work and perhaps not sayingprovide their enhancements but do it in a way that it is of little help to the originators.====Comparison This leads to situations where software distributors have so many bits of divergent code that aren't ever assimilated into their upstream project's code that the points made by distribution becomes a barnacle. This is a situation where the presenters=====What project makes so many advancements that you can you say 't forget about open source them, but they aren't really helping because they are causing so much turbulence to adopt in the light of the points upstream project to use. This is not to say that these distributors have their place, only that they made===need to re-evaluate their goals. ===Do It was great to hear from many of the speakers have similar presenters that my views of open source Open Source and Free software aren't unique to me. This means that I am not totally insane. This conference has solidified in my mind that Open Source and Free software represent more than the letter of the licenses which they use. For a Free or do they disagree======How so=====Conclusion about your views Open Source project to be successful, it has to take on ''open source''====Does the picture full philosophy of the Open and Free approach. It has to develop and maintain a community of developers, testers, documentation writers and graphic designers to ensure that there is enough muscle to do the work. It has to be an open source you've seen presented in these talks challenge or confirm your own views about what open source is and how classless community where all contributors are valued on their merits instead of their employer. Finally it functions==has to give back in a useful manner to the people who have built the infrastructure that make the project possible.