REUSE: Indicating licence and copyright information has never been easier
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 62 | |
| Author | ||
| License | CC Attribution 4.0 International: 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 | 10.5446/59723 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
FrOSCon 202238 / 62
4
9
12
13
17
18
20
25
28
33
34
39
40
42
44
45
48
54
55
58
60
62
00:00
Open setFreewareHypermediaLattice (order)InformationOpen sourceCodeRevision controlEmailSoftware developerProjective planeQuicksortInformationBitFreewareComputer fileCodeSharewareSoftwareSet (mathematics)Latent heatVirtual machineGame controllerDigital rights managementEmailRepository (publishing)Term (mathematics)Software developerOnline helpDeclarative programmingCodeComputer animation
06:52
InformationFreewareOpen sourceDirectory serviceEmailFlow separationFile formatComputer fileRevision controlError messageInformationComputer fileProjective planeDirectory serviceElectronic mailing listSymbol tableIdentifiabilityCodeMedical imagingBitRepository (publishing)EmailComputer-assisted translationSoftware developerBinary fileOnline helpCASE <Informatik>SharewareExterior algebraDot product2 (number)Data storage deviceComputer animation
13:38
Clique-widthGEDCOMCodeSoftwareWeb pageSource codeOpen setVideoconferencingWide area networkMassSample (statistics)World Wide Web ConsortiumRevision controlProcess (computing)Projective planeEmailDirectory serviceBinary fileInformationOpen sourceComputer fileCodeSource codeComputer animation
15:48
Keilförmige AnordnungInformationMedical imagingInformationComputer file2 (number)Projective planeMathematicsEmailSource code
17:18
VideoconferencingComputer-generated imageryInformationProjective planeComputer fileEmailComputer animationSource code
18:14
Meta elementWorld Wide Web ConsortiumComa BerenicesMassSigma-algebraEmulationVideoconferencingMessage passingExtension (kinesiology)Projective planeComputer configurationDirectory serviceMathematicsComputer fileRootInformationPublic domainRepository (publishing)Source code
20:29
Standard deviationOpen sourceFreewareSoftware developerFAQAerodynamicsRepository (publishing)Directory serviceEmailInformationDisintegrationComputing platformQueue (abstract data type)Software developerFeedbackProjective planeComputer fileExterior algebraElectronic visual displayIdentifiabilityBitLatent heatCodeInformationFreewareDirectory serviceRepository (publishing)MathematicsEmailDynamical systemSet (mathematics)Web pageComponent-based software engineeringSoftware bugImplementationMultiplication signStapeldatei1 (number)FAQProcess (computing)Thresholding (image processing)Instance (computer science)Standard deviationComputing platformRevision controlComputer animation
28:10
DisintegrationComputing platformFreewareOpen sourceExt functorInternetworkingFood energyProcess (computing)Kernel (computing)Sign (mathematics)CodeElectronic program guideProjective planeElectronic mailing listComponent-based software engineeringEmailInstance (computer science)Software frameworkTelecommunicationCore dumpLibrary (computing)MathematicsBitLatent heatElectric generatorInternetworkingSoftwareCodeGoodness of fitInformationTerm (mathematics)FAQNumberMultiplication signCollaborationismWordExpert systemFreewareFood energyContext awarenessKernel (computing)MaizeComputer animation
35:52
Electronic mailing listSoftwarePrisoner's dilemmaFinite element methodFAQBitService (economics)CodeFile formatOnline helpProjective planeUsabilityTerm (mathematics)Condition numberInformation1 (number)EmailInformation securityData miningElectronic mailing listSoftware developerWeb pageWebsiteComputer fileRootRepository (publishing)Multiplication signMereologyPresentation of a groupSoftwareRow (database)Instance (computer science)Data conversionCASE <Informatik>AuthorizationMathematicsLecture/Conference
43:34
JSONXMLUML
Transcript: English(auto-generated)
00:06
Hello everyone, it is a pleasure to be here and yes, this talk will be in English I promise I'm doing my best to practice my German. So maybe next year I will be able to host it in in German Yeah, let me first introduce myself. My name is Lina Ceballos
00:23
I am a project manager at the Free Software Foundation Europe Also known as FSFE and for those who don't know us We are a charity that empowers users to control technology and yeah, we believe that that's possible with free software
00:40
But today I came to talk about this nice initiative called REUSE so REUSE It's an initiative from the FSFE since 2017 and it's basically a set of recommendations that
01:01
Aims to make licensing and copyright Displaying easy for everybody. It makes it it aims to make it readable for humans and machines alike it's also pretty simple and very easy to verify and
01:22
Also, it seeks to Be integrated in already existing practices So I will give a brief overview of what REUSE is Then I will show you with three simple steps how you can make your project REUSE compliant. I will also do a
01:41
Demo here with a short project that I prepare to show you how the tool and these specifications look like we'll talk a little bit about some ongoing developments of the tool and Yeah, that's kind of like the overview of today But today I want to start with some questions for you. So first
02:04
Please raise your hand who has ever programmed some code Yes, I kind of knew The answer and this is also pretty straightforward and pretty simple who has ever released some of these codes as free software Yes, please Okay, I don't know if someone is already falling asleep or is the
02:26
developing proprietary software and who has who has never been confused by how to Properly declare license and copyright information in your free software project Okay, yeah, I know declaring this kind of information
02:45
It's a hassle. We know that and that's exactly what REUSE is Trying to achieve to make it simple, but also fun for everybody So let's start it first with the common issues or the common mistakes that we see
03:06
in some Free software projects or how people are displaying this kind of legal information so First of all, there is some missing information about license and copyright information of
03:22
own or third party code so sometimes we see some code and we are not sure under what license is it is or who the copyright holder is and And then this is connected to this Other mistake or issue is that reusers of the code may may overlook
03:44
These chosen licenses for all or for some individual files in your in your project and We know that the terms under your so under which your software is released are defined by the licenses so this legal information is quite important and
04:02
overlooking this information, but might become a little bit problematic and Then there is a little bit of uncertainty on how to deal with multiple licenses because You all have developed some code and then you know that a lot of free software projects are under
04:21
Many licenses and then it is a little bit unclear how to manage this information There is also Quite a lot of ambiguity with some licenses So sometimes we fight we find some text of GPL 3
04:41
But then it's a little bit hard to know if it's the GPL 3 or later or if it's only GPL so it's a little bit ambiguous if it's not very clear specified and There is also some sort of conflicting best practices because let's say again example with the licenses Some people store this text in the copying file or they're stored in the
05:07
License file or they're in the readme file so it's a little bit you always have to go and try to find what the license is and if there if there are even more licenses and
05:21
that's many of the reasons why reuse Started to help you developers But also to help users and re users of free software and how is how is reuse actually helping? So we make it easy to find this copyright and license information because we're gonna
05:44
Add this information in every single file of the repository using a header so You will see this information in every piece of code And with this we want to avoid silos because we want to store this legal information as close as possible
06:06
To the repository to every piece of code Again as I already mentioned we want to make this information readable by humans but also by machine so if you can if you go and see every file you would be able to understand and also the
06:23
the tool will be able to know and identify this information and as I already mentioned we're really trying and Yeah, putting a lot of effort of making Licensing or dealing with this legal information easy, but also fun for developers without
06:45
No matter the size of the of the project because we know that there might be a lot of big projects But reuse helps with this So how does reuse help with this
07:01
With all these issues It's really three simple steps I will go one by one and I will also show you in the demo how this works But then first you just choose and provide the license or the licenses of your repository we of course encourage people to select
07:20
Well known and recognized licenses, although we know that you can also create your own license The second is that we can add this copyright and licensing information to each file of your repository and Third we're just going to confirm that your project is reuse compliant. So let's go step by step
07:41
So the first one is to choose and provide the licenses. So let's say you select the GPL 3 or Only so you're gonna save The license text of this file in a directory that we're going to create that it's gonna be called licenses So all the licenses that you are using in your repository either for the whole project for the pictures for the documentation
08:05
It's gonna be stored in this directory. So people who go and check your project. I'm gonna know what kind of licenses you're using and Then you're gonna name this file After the SPDX license identifier because as I already mentioned
08:21
Reuse is integrating already some best practices. So we're using the SPDX license identifier So in this example, you can see that we have the directory called licenses and then our GPL 3 or later it's safe under the SPDX license identifier like the license name of
08:46
This specific license and one important thing here is that reuse Not doesn't support yet license compatibility, so if you have any questions about
09:02
Your project is licensed under certain One and then you want to use or reuse something from another license and you're a little bit unsure if they're compatible I mean first of all, I think there are a lot of quite a lot of tools to check that But we also have a licensing question mailing list in which we
09:20
Help developers with these more legal oriented issues So you have to be aware of that The tool is not gonna warn it like there's not gonna make any warning on like if there is some uncompetability regarding licenses So we already got the licenses and now we're gonna add the copyright and license information to the files
09:43
So we're gonna do it through a header who's gonna look like here in the example so for the license identifier again, we use the SPDX tag and the License name and then regarding the copyright text
10:01
We again encourage people to use the SPDX by copyright text this tag But if you already in your project have the copyright or use the symbol of the copyright It's also fine. The tool will be able to identify it but regarding the license Yeah, only the SPDX license identifier tag will be
10:23
recognized by the tool and then I know that by now you might be wondering I mean in my project there are some files that I cannot comment like images or some binary files or JSON files So for these we have two
10:40
alternatives The first one is to create a separate dot license file for this specific file so again in this example, we have the file of a cat the image of a cat and then what we're gonna do is just create a dot license that we're gonna name after the file as you can see and then in this
11:01
Separate license file. We're gonna add the legal information So we know now that the cat was taking all the copyright holder of this picture is great artist and that the cat the picture is licensed under the CCB Y4
11:21
but Now I know you might also be wondering like I have a project I'm a project has 1,000 pictures and then creating 1,000 separate files for this might be a little bit Of a hassle and also not a good idea because we Double the size of the project. So we have an alternative for this case
11:43
that There are some ongoing developments. I will talk about this Later on, but we have this depp file file that we're gonna store in a directory called dot reuse The depp file file. It's a Debian project. We're also again
12:02
integrating already existing practices And then in this case if you can see that We just select a whole directory because we are not we're sure that this information is correct Because this is the downside of this alternative is that you might overlook some
12:21
pictures that were not That the copyright holder is not this person or is under a different licenses So if you 100% sure that you know the legal information of this Then you're gonna use it and then you're gonna tell That the whole directory of images is under
12:42
This license and the copyright holder is great artist. So yeah the copyright holder and The third one is that we're gonna confirm that our project is reuse compliant and we have a tool for that A linter tool that runs pretty easy It's quite fast and then it's gonna scan your project and it's gonna identify it what licenses you're using
13:07
If there are some files that are missing Some license information or not. So in this case our project is reuse compliant. So It's all good Yeah, so these are the three steps now, I would like to show you how the tool works
13:26
So for this I have prepared this project It's pretty small so it has some code it has some images here. I Has some we can see that it has some copying files. So we have the
13:42
GPL version 3 we don't know which one it is But yeah, so let's start it. Let's say I am I am the The owner and the the copyright holder of this project. So I'm gonna do the whole process So first I'm gonna scan my project to see how it looks like
14:03
So we're gonna use our command reuse lint and Then here reuse the tool which will show us you have these files and zero of them have this legal information So we're gonna tell the tool to help us
14:22
So we're gonna use the reuse add header command to add These headers so I'm gonna start with the source with the code So I'm gonna add to the whole bin directory and to this source So let's run add header and then we're gonna start with the license
14:45
so I know that my project is under the GPL 3 or later and then we're gonna use Sorry the copyright
15:02
We're gonna specify so Jane Doe is the copyright holder and Here if you don't specify the year, then the tool is gonna add the current year So I want to specify that the year is the year of the first publication. So I start this project into
15:22
2012 so let's add the year and I'm gonna tell the tool to which directory so please add it to whole bin and also To this directory so now the tool automatically create the headers so if I go here
15:46
Maybe it's a little bit small, but then you will see that The headers are there And the tool is able to identify the syntax as well and then yeah, I just had this header to I don't know 15
16:01
files in three seconds So we would check again how their project looks like So when I recognize us that 13 of these Files have this information But we're still missing some so within those we still missing the image files
16:22
so let's ask our tool to add Again this so what you're just gonna use the same Commands, but then the pictures were taken by Dave though Yeah, the year was
16:42
2013 and Yeah in this case, I'm going to also change the license Because these pictures are under the CCB Y4. So we're just gonna Change this and
17:06
The year and then we're gonna tell the tool yes, please add this to all the image in This directory, so yeah, the tool already did this if we go again
17:21
We will see that the tool has created this individual dot license And then if we open then we will see the information is there Okay, yeah, so we are almost there let's check once again how the Project looks like we still have two more files. I'm gonna add it
17:42
The header to The make file and the readme file because the gitignore I'm gonna briefly explain it Later, so let's just add the same license and yeah Jane Doe is also the copyright holder and
18:03
the Yeah, so if you go again, then you will see it's it's there The Mac file again, it recognizes the syntax and it creates the comment header So for the gitignore, I mean gitignore is like an insignificant file. So technically is not copyrightable
18:26
but the idea of reuse is that the whole Repository every single file has this information So you can you have two options you can either license it license it under the main license of this project
18:43
so the GPL 3 or I mean no things want to stop you for doing that or you can also put it under the public domain So we can do that if we go here then Let's Just put it under the public domain. So let's use the
19:02
Yes, it is here. And then yeah, I'm just gonna change this Jane Doe let's keep the same here and then just tell the The tool please add it to the gitignore and then yeah, it would add it now
19:24
So now technically all our files have this legal information So, let's see how the tool reacts so it's still telling us that is not really is compliant and It's actually telling us here that there are some missing missing licenses. So we know that we have used
19:43
These two licenses and the text of the licenses are not still I'm not in the repository yet. You can see but the tool will also help you to do this. So with or Command reuse down download all
20:01
the tool will basically download all the licenses that you have used and Then if you go to the root of the project and you can see that the tool has created licenses directory and the three licenses are Stored there and it's pretty easy and pretty straightforward
20:21
So if you scan it once again, he will tell you Congratulations. This project is where you is compliant So, yeah, I mean this is a Very quick and simple example. I know that in reality is not that easy But it wasn't like it was meant to show you how the tool works
20:41
And you could also see that we save a lot of time. We did a lot of things. Thank you. Thanks to the tool so Let's keep talking about a little bit The reuse as a whole so the components or reuse are this set of best practices So the specifications that I have mentioned already the licenses directory adding
21:05
headers to every single file of the repository Because we are aiming to make free user standard. So the more projects Implement reuse the easier is going to become to first identify this information and then second to
21:21
Just implement that as standard practice We have the helper tool and that I just show a little bit how it works Because yeah, it aims to support developers in making their projects reuse compliant So it really helps there are a lot of commands and it's there is a lot of ongoing development to make it better
21:44
Of course and there are more features that probably you know You guys that are developers know how to use better and Then there we have also a tutorial and a FAQ Because we are trying to lower the threshold
22:03
To for people to get started with reuse. So we our tutorial is pretty much Explained pretty much what I just did And then we also have some FAQs An FAQ to answer a lot of questions regarding the tool but also
22:21
regarding some Legal questions a little bit more advanced questions. So there you can find maybe the answer to a lot of the questions that you might have and now if I'm not able to reply to answer them after My presentation. But yeah, the idea is that pretty much everybody can implement reuse and everybody
22:44
can Yeah can make a project reuse compliant just by checking the tutorial and also by having this FAQ available and Then we also have our API which You can also find through our reuse.software page and then there you can once you have done your project
23:07
You have made your project reuse compliant. You can add it there You can register your project and then you will create the API will create Dynamic budget batch that you can
23:21
Put in your project so you can add it in your readme file and then in the future People who visit your project knows that will know that your project follows the specifications of reuse So we are also now Encouraging projects to To register because then we can also know how many projects have been using these specifications
23:48
So A little bit about what special what is special about reuse So again, we have this directory Called licenses where we're going to find all the licenses that you're using
24:04
and therefore it's also easy to identify if there is some Uncompability toward like between them and it's again easier for Users and reusers to spot this information very quick
24:21
and again, every file will contain this legal information, so we'll add the spdx copyright and license identifier tags So it will become again Way easier to track to know what the license of a specific piece of code is
24:41
And we have some alternatives for uncommentable files As I already Showed so we have the dot license or the depth file and most importantly we're gonna make less ambiguous The display of this information because
25:01
We know Exactly what license has been used And then we also know for every piece of code what the legal information is so now let's talk a little bit about the ongoing developments of the of the reuse So first of all the tool that I just show
25:24
Is seeking to improve itself or Team of developers are really constantly checking the feedback and also trying to find issues or Yeah bugs that are in the tool to make it easier
25:42
For everybody as well as the api so we're changing the documentation And really actually improving improving it As much as we can that's why The feedback from the community is so important and the feedback from Developers you are the ones who are actually using the tool
26:03
And then it's important for us to also know how you feel about it. What is what could be improved? And yeah, so Again, the more projects use reuse the more The better we will get because the the more feedback feedback we will also get
26:23
And then the specifications are also Changing and improving so here I would like to mention a little bit the depth file file we are trying to Change it a little bit for a yaml file because it might be more flexible
26:44
But yeah, this is a ongoing process But the whole idea would remain so we still want to offer projects with like a big size to be able to display this information in a
27:00
more In an easier way instead of creating an individual file for every file for every of these uncommentable files And there is also an ongoing development on the on some snippet, uh support so if you have a snippet in your code, then you will be able to Declare the legal information of this specific one
27:23
Um So yeah, that's also in the pipeline and yeah, we are working on some other changes in the queue The tool has The version 1.0 has been released some weeks ago
27:42
And now we are immediately working on the version 1.1 because there is still a lot of feedback going on but Yeah, this is for yeah for the future And again, we're trying to integrate reuse to
28:01
Like in like make it better to integrate in Already existing platforms and also in other initiatives. That's why we're for instance using the spdx tags And then yeah, we're trying to make it better So it really doesn't become a burden for for you guys to make a project reuse compliant But you can you know
28:21
Make a whole use of the whole ecosystem because in the end that's what uh free software does right it can help us to improve through collaboration And then uh spreading the word which is basically what i'm doing here showing the tool um, um
28:40
I'm crying kind of impressed that uh, a lot of people don't know about the tool. Um And honestly, I feel that it's a tool that actually Helps a lot. Um, and I know that it might sound a little bit Yeah, like a burden to make a project reuse compliant even more when your project is big
29:00
But I mean, I think in the long term, uh, the the benefits in the long term that this will have All right, you know way more So yeah, we're just trying really really hard to make it easier every time for you to Uh make your project reuse compliant
29:20
um, and then yeah with this I would like to talk a little bit about our activities around reuse so for instance We are also working with the next generation initiative, uh, also known as ngi Which is a european commission
29:41
Initiative That it's trying to shape the future like the the future of the internet of the future And then we're helping a lot of these small projects to become reuse compliant. Um Yeah, some of them are not uh small at all so yeah this uh
30:00
Our work there has been a quite also Um Good we're really um Have been successful in implementing uh, reusing a lot of these projects from the ngi um, we recently last year, um released our reuse booster which uh is trying to
30:22
Change a little bit the workflow. So we're now approaching projects To help them to become reuse compliant. So we're Kind of establishing a closer communication with the projects because Again, we want to make it as easy and smooth as possible. So we're trying to
30:41
identify and understand uh their workflow and their policies and how they You know develop their project And then we are working closely with them to help them implement and reuse So for instance
31:01
Curr has become reuse compliant lately in the framework of the reuse booster And then also gnu health has decided to implement reuse, you know, it's uh components and it's also big project so it's an ongoing process, but the wheel is there and Yeah, so our team is really
31:22
trying to work closely with projects and They in the beginning reuse booster was aimed for projects to Reach us out to tell us to help but now we're trying to identify these interesting projects that we could
31:41
help with reuse And then we also have um, as I already mentioned the license questions, so we have a mailing list for that if uh You have any questions on your project regarding some legal issues We will do our best to try to help you with that because as I already mentioned the tool doesn't really support that
32:07
But in our team and also in our community we have lawyers or like legal experts that can help to solve these questions so this is kind of like a whole umbrella of
32:22
activities around Yeah, reuse So now talking a little bit about uh who has adopted reuse So in our api, we had already more than one thousand one hundred projects registered. So We like to believe there is more and some I haven't registered yet. So I mean, this is quite a big number
32:46
And that's why sometimes i'm a little bit surprised that people Don't know the reuse and we're actually working on Promoting this tool more because I think it will really benefit the whole free software ecosystem
33:04
And as I already mentioned with the next generation internet, we have more than we have held more than 100 projects there um And then yeah, we also try to make it as easy as possible for them In terms of uh community oriented so we have kde
33:23
And its frameworks and then reuse is also implementing in their licensing policy. So basically all the kde frameworks Are following the reuse specifications As I already mentioned core has uh recently become really compliant um, and yeah canoe health which is uh in process, but i'm really looking forward to see that
33:46
Um in the from the corporate side, uh, we can also see reuse implemented in the policies of siemens and huawei sap library lf energy The kernel of linux is partially And following the real specifications because of the size
34:03
But yeah, this is also quite exciting um, yeah, and then the question is if you and your projects want to implement reuse I want to follow the reuse Specifications, so how can you guys join?
34:22
For reuse we also have a mailing list where we discuss things when we Some people charge some questions or Things that are not clear so you can always sign up there To join the discussion in general Again, you can make one or two or all of the projects reuse compliant
34:43
um You will find all the information on our website reuse dot software and there Everything is connected the tutorial the faq the api And yeah, etc And you can integrate reuse into your community Again, you can also share the spread the word tell that you attend this very interesting talk in frost corn
35:06
Yeah, and yeah just make more and more people aware of Uh reuse You can also contribute with code now that you all have developed some code I mean reuse is a free software. So it's a
35:22
It's also there the code is there you can see you can always help us improve it. So Feel free because the more again the more people help us and the more people give us Feedback the better it will get and you can also help and guide others to adopt reuse
35:41
um I mean using the tool is pretty easy and it's pretty straightforward and once you understand how it works You will be able to help others and share the world and yeah, I mean, this is really it's a very easy Tool even for me that i'm not a developer. It's uh, you know, it's quite user friendly. I have to say
36:03
Um, and yeah with this I would like to thank you and also thank all our fcp supporters because They help us uh to And they enable our work. So This is an invitation if you're not to become part of it In fsf.org support slash support
36:23
All is welcome And yeah with this I will finish my presentation These are the sites and this is also the mailing list and our git repositories with the reuse and also our Yeah fsf
36:42
Repository so if you have any questions, I will be more than happy to take them Um, yeah, and otherwise, thank you so much for the attention and I hope you enjoy it Thank you
37:00
Sorry Yeah, yeah. Uh, we have also some tools for developers. Uh, so you can implement this like a
37:21
Pre-hook, so whenever you're gonna implement your code then It will identify if it's missing some Some of these specifications. So yeah in the reuse software you can find there is a specific Page for that where you can find also like how to implement it
37:40
Because yeah again, we try to make it easier and also I mean if you make your project reuse compliant Then you have to check and check every time but with this, uh, yeah, it will make Life easier. So yeah, you can find it in the in the website Sorry, should we take the yeah, I think we should we should take the questions with microphone for the recording. Sorry
38:19
on mine
38:21
When we manage security informations and also license informations in the spdx format So that they don't destroy each other when I use a reuse tool Um, yeah, I think I I yeah, I think I wouldn't I i'm not very familiar with the with the security features of spdx so
38:42
I think I cannot really answer that that question but Here's my email and on the slide Please feel free to Remind me remind it again, and then I will check with our developers that are a little bit more Close to that and then I will come back to you With that. Yeah answer
39:02
Yeah Is does anybody yeah Thank you
39:23
Maybe do you have an additional service to find out which lessons I actually need? To my files So like you you mean what kind of license you should use for your code depending on your needs for my code for my
39:45
Pictures for something in my project something like It Has some questions I answered them and Then I can see what which lessons I actually need. Yeah, okay
40:00
I mean I would say that there are some tools that do that because every time I work with that I'm surprised by the amount of tools that have been developed on that regard I personally don't know any but on our faq we have For instance these kind of questions like I have these pictures. What license should I use?
40:20
So we try to recommend to use the most common ones because it's also easier for reusers to They already know the license that they know the terms and the conditions So we tend to encourage people to use The most common ones and the most well-known licenses for
40:42
Code or for pictures so on our faq you will find some of these suggestions But if you have any specific questions regarding like Certain terms of conditions that you want to use during like for your whole project You can always ask in the licenses questions and then we'll be more than happy to help you to guide you
41:05
There to have like a more closer help from us But yeah regarding a tool. I am not very familiar with any but I would say that there might be so Yeah Thank you
41:21
I can also take it Thank you Um, do you have any hints how we should manage a project with many authors in the example? We saw a project with two authors and the typical project for example has 30 authors or more
41:41
And If author changes one file, then he's already one of the many authors and this continuously changes And the most easiest way would be to take this information automatically from git And add it to the files. Is there any API for this. Yeah, I mean from what I know, I think there are some
42:07
Ongoing common conversations with Git I mean github, let's say But in this specific case we would recommend to for instance As a copyright holder make I don't know your project. I don't know very used to
42:25
contributors and then in a In the root of your file of your project you will specify Who the contributors are so You will list them And then if someone adds something then the person would add Him or herself to this document and then you don't have to change the header
42:45
every time but it's just like a Just wrap it up by just mention contributors of the project, but then you have to make sure you specify who they are Yeah So
43:00
Does anyone else have any questions Okay then I Yeah, i'm glad everything was clear and thank you so much for the attention And if you have any questions, we also have a booth from the fc fee. You can always go there Reach me out. My email is there contact at fc fee as well Yeah, feel free to
43:20
Reach us out and if you have any Questions of need in terms of legal issues again, our mailing list is open for you. Thank you