We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

How to teach OSS licenses and compliances at a university

00:00

Formal Metadata

Title
How to teach OSS licenses and compliances at a university
Subtitle
how to teach to the students with some of the use cases
Title of Series
Number of Parts
287
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
I have started to teach OSS licences and compliances at a Japanese university since last year. it was difficult to teach OSS licences and compliances because I should have shown many of use cases so that the students could learn what the licences and compliance are and more, they even didn't know how to deal with ordinal software licenses. So, I had to talk many of the background knowledges to the students as an 'introduction' so that students could understand the OSS licences with compliances with ease. Fortunately, there were good feedbacks from the students, though, I need to improve my lecture more gathering more use cases etc. I will give a talk my experiences there at the university and discuss how to improve my lecture to teach such 'licences and compliances' to students. I will give a talk: The opportunities to teach OSS licenses and compliances: - increase the incidents of OSS licenses violation - keep compliances not to violate OSS licenses - respect the authors and keep the licenses rules. - reinventing of the wheel with compliances the Difficulties to teach several OSS licenses: - the difficulties for students to read several OSS license descriptions directly, really complex for them, especially GPL licenses. - need to gather many of the incidents of OSS licenses violation. - need to prepare good quiz(exam) so that students could understand with ease. the lecture last year: - why the University needs the lecture - the trial and error for the students - the advice from the staff at the university - the feedbacks from the students the lecture coming next year: - gather more incidents to check - looking into the incidents more - deep-diving for the practice. - looking into new OSS licenses for DX - any ideas...welcome!
World Wide Web ConsortiumOpen sourceUniverse (mathematics)Open setData compressionProjective planeAreaSinc functionGame theoryComputer clusterDiagramSource codeComputer animation
Multiplication signOpen sourceFeedbackComputer animation
Computer scienceUniverse (mathematics)Open sourceStaff (military)Observational studyMultiplication signStudent's t-testSystem callFocus (optics)Bus (computing)Data compression
Game theoryVideoconferencingInternetworkingIntegrated development environmentEmulatorOnline helpOperating systemOpen setBit rateMultiplication signStudent's t-testNoise (electronics)ResultantIncidence algebraStaff (military)Open source
FreewareSocial softwareIncidence algebraOpen sourceComputer animation
BlogPrice indexRevision controlComputer networkThomas KuhnSocial softwareMathematicsSoftwareHypermediaWeb browserSheaf (mathematics)Similarity (geometry)Source codeMathematical analysisSurface of revolutionFacebookAverageTwitterInternetworkingRational numberComputerComputer animation
WordTwitterLink (knot theory)Incidence algebraTwitterSource codeTouchscreenPrisoner's dilemmaComputer animation
Open setRight angleCore dumpDrop (liquid)Open sourceSoftwareHorizonEnterprise architectureAuthorization
SoftwareCausalityCASE <Informatik>NP-hardDistribution (mathematics)Projective planeOpen sourceElement (mathematics)Pulse (signal processing)Computer hardwareGraph coloringIncidence algebraComputer animation
GeometryStreaming mediaStudent's t-testMoistureSoftwareOpen sourceVideo gameElement (mathematics)Water vaporMachine visionArmWeightIntegrated development environmentSuite (music)Roundness (object)Basis <Mathematik>System callEvent horizonDistribution (mathematics)Multiplication signGame theoryRight angleView (database)Data compressionQuicksortPhysical systemRule of inferenceDigital rights managementProduct (business)WordRaw image formatFigurate numberCoefficient of determinationIncidence algebraOpen setFlow separationPresentation of a groupUtility softwareKey (cryptography)Direction (geometry)Zoom lensDistributed computingAutomationDescriptive statisticsHorizonSimilarity (geometry)Different (Kate Ryan album)Computer animation
FeedbackMultiplication signCASE <Informatik>Theory of relativityStudent's t-testFeedbackOpen sourceMathematical morphologyWordProjective planeFigurate numberElement (mathematics)Game theoryHand fanStaff (military)InformationSoftwareMathematical analysisEnterprise architectureSoftware developerSource codeError messagePhysical lawInternetworkingIncidence algebraWave packetShooting methodSpeech synthesisState of matterPrisoner's dilemmaLink (knot theory)Rule of inferenceGenderCodeOpen setUsabilityDecision theoryOffice suiteMereologyComputer animation
Online chatMultiplication signEmailComputer animation
Computer animation
Transcript: English(auto-generated)
Hello, my name is Masahumi Ota. I would like to talk about my experience how to teach Open Source licenses and compliances at a Japanese university. This is me.
I have started teaching Open Source licenses and compliances at a Japanese major university since last year and used to contribute many more Open Source projects over decades. Now, I have been contributing a Raspberry Pi project
with Raspberry Pi Foundation and Raspberry Pi Trading in Asian area. This is agenda. It was first time to teach Open Source license last year.
Your feedback is very welcome to improve my lecture this year after my session. The opportunity to teach Open Source licenses and compliances. Why I have a chance to teach Open Source licenses and compliances
at the university? It was students' request. I have returned to this university as a student three years ago. It was really great time to study computer science.
I have a chance to talk to some staff who used to help me studying also. After graduation, I had a chance to talk to some staff at the university.
Two years ago, they are looking for the lecturers who teach Open Source licenses and compliances. At the same time, I was annoyed with many questions about Open Source licenses on Raspberry Pi OS
because Raspberry Pi on business now getting increased. I had to have many time to discuss the licenses on its operating system.
I have also discussed with Raspberry Pi trading guys and investigated many things by myself. As a result, I have some more knowledge to cope with some of the incidents. So, I could teach students how to deal with it.
I have applied lecture via the staff. Lately, there are many violations incidents of Open Source licenses are now getting increased.
Especially, we can see the license violations about Mastodon which has AGPL licenses. Some of you know it is familiar truth by Trump. If violated, AGPL licenses.
Software Freedom Convention blocked its violation. In Japan, there are similar incidents violated Mastodon AGPL.
Here, three knew how to disclose their source code of modified Mastodon around Twitter's features because of the SNS demand.
Appliance is really important for our business. We must not hold for violation trap in Open Source licenses. Many enterprise companies actually train their employees how to deal with an OFS license in the business and getting nervous dealing with it.
I really thought some people lacked the respect to the Open Source software authors and creators
because they worked very hard to keep the Open Source project. Lately, there are colors and vehicles incidents in Node.js but it is only erratic behaviors.
Perhaps, he wants someone to understand his hard work and respect him.
I saw a similar case in the Open Source project. He contributes and his hardware is spending much more money. He asked to donate to many more people but he can't gather much more money.
So, he closed his open-source based distribution and he has been claimed by many more open-source users. It is the same issue.
We expect it is a very important element to keep Open Source licenses.
There are similar distribution software like operating system based on the same intelligent software. It is almost reinventing of wheel.
That may hold the software violation traps. If you realize your product is as reinvent of a wheel, please check carefully not to meet the violation.
The difficulties to teach several OFS licenses. First of all, I felt difficulties to teach several open-source licenses because I have read a license description directly.
I am sure that students feel the difficulty to understand the licenses. They felt complex to them, especially in GPL.
So, I need to use approaches to teach with incidents of life with violation and use many quizzes with tentative incidents.
The principle of automated copyright and basic elements. Students may judge whether they violate any software license or not.
I should teach them what they are in detail about open-source software licenses
because it needs those elements to judge with the licenses.
The lecture last year, it was the first time to teach. His overview held at 29 May last year.
90 minutes lecture, 90 minutes workshop was in Iran. I felt 100 minutes might be long for me at first though. It was actually a short time to cover open-source licenses and compliance.
And it was annoying. Sorry, I was annoyed that almost people were online under the COVID-19 situation. I taught at the classroom teach though.
The lecture streams via Zoom were flagged to communicate. I felt the difficulties to teach under the hybrid environment because I checked the face to the student to find my presentation and lecture going.
But I can't see the student's face via Zoom. So, I feel some difficulty for that.
Sorry, not difficulties and the dogs. It was written only in Japanese, sorry. This is a lecture-side agenda last year.
I needed to introduce what software licenses are, how to approach with RAW. Students should learn the software licenses, principle of private autonomy, low priority and copyright before looking into open software licenses and compliance.
Those are really important elements to understand whole view of software licenses. I also taught software license management by builders that we need to check several rules in the license to learn the software license deeply
because on the proprietary software on the license-based software
and has a special rule in the licenses. So, students should learn the license and set by authors with free,
not something like a description and rules for that.
Comparing licenses and other proprietary licenses are also important to check its difference
and the OSS utilization is really important dealing with open-source licenses, especially at GPL when you deliver OSS-based software.
The word is utilization and a really important key when using an open-source software because almost open-source based software is modified by users.
For example, you know in OpenStack and Rancher, some cloud-based software is modified by users.
And RAN, Modify, and Rancher in their software delivery CACD system. And OpenStack is based on Modify.
So, the utilization is very much important to understand and manage open-source software. I have tried a quiz and mini-workshop to understand the kind of open source and with gamification.
But LGPL and AGPL were difficult to understand students immediately, so I set them an appendix and show some figures to understand.
I wanted them to read after my lectures and waiting for a question via Slack. Actually, there are many more issues in the LGPL-AGPL lately,
but it is very complex and the incident now for students cannot understand immediately. So, I use more figures and explain words to understand afterwards my question.
This is a workshop-side agenda. I have three tentative cases so that students understand open-source licenses.
I introduced how to work with others. Legal department, open-source goals, open-source authors, and analysis too in the past.
Second and third cases, I did not give some hint to students to solve them. I wanted them to solve by themselves the second and third issue.
It has happened and you know even some are emailed to ask you to open your source code according to open-source licenses.
So, I wanted to solve at least case two by themselves. It was also trial and error.
My lecture was on the trial and error. I have read some books and train talks by Japanese companies about open-source licenses and compliances. I realized it was really important to use the violation incident approaches
and use the license check too to understand how to deal with open-source licenses and compliances. I checked many more enterprise company docs and they train especially on the development department
so that they understand how to deal with it.
Because they have to modify open-source software in their daily business.
For example, they made software with open-source software so they should know how to deal with software licenses in their software.
Actually, I have joined some open-source projects. Some people don't understand how to deal with open-source licenses in their project.
I have discussed how to teach the students before my lectures with the staff. They kindly gave me some advices through their experience.
Gaming can show a really important element to teach the students. It makes interest learn more and more. These also fade and only lectures may be bored by students
because it rhymes complex words and more. So, they say gamification like quiz and like workshop is really important to understand how to deal with.
Fortunately, students gave me a good feedback to me. Thank you very much for the feedback to the students. So, they say good approaches to the internet and use of internet.
But, sorry for them, I couldn't have time to explain morphology and play morphology so that they understand how it works.
But, people get feedback. So, they understand the relation between the license and the law and the copyright.
So, some of them ask me if the license issue is related to IP. It is, yes. So, IP is really important lately.
So, it is very much binding with licenses. So, we should check and when IP, when they are looking into the IP.
So, also binding the licenses. A lecture coming this year, just thinking of next year.
Sorry, just thinking of this year. The lecture last year, it was the first time to teach. I think it was succeeded.
Coming this year, I have been discussing in the staff how to improve my lectures. I am now gathering more and more information and discussing the staff.
More workshops, I am planning to make. So, as you have more and more time to consider the infinite workshop,
it is a game of kitchen for the students to understand how to deal with. So, I think I have more time to plan this year's lecture.
So, if you have any ideas, I am very welcome to improve my lecture this year.
Thank you very much. And a special thanks to Veda Fan of the Linux Foundation giving some advice on how to teach Open Source license with his book.
Imada Fan of Stockholm University, give me a chance to learn some advice for the whole students. Thank you very much to all you people who helped me. And give some advice.
Thank you. Thank you for attending my session. If you have any questions, please chat to me afterwards. And if you have any opinion and give your advice to me,
please feel free to email, tweet and chat with me afterwards. Thank you very much for your time. Any questions afterwards, thank you.