Evaluation and assessment of open source projects
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 |
| |
| Subtitle |
| |
| Title of Series | ||
| Number of Parts | 266 | |
| Author | ||
| License | CC Attribution 3.0 Germany: 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/66398 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Open sourceInternationalization and localizationPerformance appraisalCapability Maturity ModelPhysical systemSoftwareComputer animation
00:33
Capability Maturity ModelOpen sourceStandard deviationFeedbackCollaborationismLevel (video gaming)Term (mathematics)Information securityIndependence (probability theory)Vulnerability (computing)SoftwareSource codeVector potentialLatent heatDisintegrationSystem programmingVideo projectorDecision theoryResource allocationPlanningCompilation albumOperations researchProcess modelingCore dumpMetric systemCodeFrequencyDigital rights managementInternetworkingProjective planeOpen sourceVulnerability (computing)MereologyOperator (mathematics)Physical systemSelf-organizationVirtual machineInformationFlow separationWebsiteSoftwareObject (grammar)Reading (process)Standard deviationConfidence intervalOpticsMultiplication signSound effectMusical ensembleInformation securitySheaf (mathematics)Degree (graph theory)BitCapability Maturity ModelInformation technology consultingPerformance appraisalStudent's t-testPersonal digital assistantPosition operatorComputer animation
06:22
CollaborationismFeedbackTerm (mathematics)Capability Maturity ModelOpen sourceAdditionSoftware maintenanceSoftware developerExistenceComputer programSelf-organizationDecision theoryCodeDisintegrationTelecommunicationElectronic mailing listDesign by contractOpen sourceMereologyComputer programCollaborationismMusical ensembleSoftware developerAlgorithmPhysical systemSelf-organizationQuicksortProjective planeTerm (mathematics)Presentation of a groupOffice suiteObject (grammar)Basis <Mathematik>Multiplication signNumberFeedbackElectronic program guideInformationCategory of beingGroup actionProcess (computing)InternetworkingGoodness of fitScaling (geometry)Decision theoryComputer animation
12:11
Capability Maturity ModelOpen sourceDecision theoryDisintegrationPairwise comparisonFeedbackSoftware maintenanceCodeDataflowInternet service providerContext awarenessINTEGRALTerm (mathematics)ResultantComponent-based software engineeringComputer animation
12:59
Translation (relic)Process modelingOpen setTexture mappingLibrary (computing)Operations researchOpen sourcePhysical systemComputer programmingFormal languageComputing platformDatabaseExtension (kinesiology)Server (computing)Interactive televisionCapability Maturity ModelStandard deviationArchaeological field surveyGoodness of fitPlotterWebsiteElectronic mailing listOpen sourcePresentation of a groupSelf-organizationServer (computing)Right angleStandard deviationObject (grammar)BitConservation lawMusical ensembleImplementationSocial classComputer animation
14:53
Capability Maturity ModelOpen sourceComputer animation
Transcript: English(auto-generated)
00:09
Yes, I've worked for a long time, like choosing the whole thing for software, choosing the software is really important for us.
00:22
And that's why we have developed this system for automation. In this presentation, I'm going to talk about some of the things that we're going to talk about today.
00:50
We have some of the things that we're going to talk about today.
01:11
We have some of the things that we're going to talk about today. We have some of the things that we're going to talk about today.
01:50
We have some of the things that we're going to talk about today.
02:05
We have some of the things that we're going to talk about today. We have some of the things that we're going to talk about today.
02:45
We have some of the things that we're going to talk about today. So there are some benefits for the majority assessment and some objectives for that. So we can find out the quality and reliability for our critical operations.
03:03
We are in a situation where we are legally obliged to do some data collection that needs to be reliably available. We can learn if the value of the software is going to be good.
03:22
We can really trust the confidence in those projects when we do these assessments. We identify opportunities to contribute data, perhaps our top-level or our own. And then we can help others learn the ideas of the purpose of software.
03:44
The objectives are there to evaluate what is needed. And then, of course, the reading for all the others and so they apply it to the regular requirements.
04:01
It's more than there. There are some standards and practices that I found on the Internet. She is scared to remember what this means.
04:24
But anybody can find this information in the Internet. Most of them are for MIIT organizations that are related to adult open source software. Or for the open source project to develop themselves if they are good enough to be adopted by, for example, the
05:02
open source process. This part in our way is to address the quality and sustainability.
05:24
We need to check our quality and the documentation how they are doing it. What is the home machine difference? How is the support for the software? How is the project governed? Who is the leader?
05:40
How often do they create new software or update software? And the licensing part is actually great. And I think it's because I have a separate site for that. I don't remember why. And then, of course, we can see how the project handles certain issues and vulnerabilities.
06:07
Role of community is very important. So we need to learn how is there a working community behind the project. So it's not just the city we like. So it's very important that we should be part of our system.
06:27
If it is, then how do we convince ourselves? How is the collaboration working there? Is there a new piece coming up?
06:40
How are the users for this feedback coming back there? How do they respond to issues and requests? And how do they contribute to the long term?
07:00
And is there something working in other practices with other communities or companies? This is the license and in terms of use, it is very important and very complicated part.
07:23
Do you need to compare the licenses to our legal requirements in the country? Where is between each country so I can't give any means there? Are they protecting their intellectual property rights?
07:41
Or if we use something on top of that system, can we keep our intellectual property protected? Is there some use restrictions in the commerce world? How is one working with other local licenses?
08:00
And there is also the risk of learning from community and open source. It's really difficult to check something. It's more of a big system. And is it encouraged to continue to use open source?
08:25
There is a legal list of existing open source licenses. You probably know more about this than me. And I don't know if these are correct or not. I found this information from the internet.
08:42
But that's something that we have a special license in our house that knows the industries. And we have to know its details about the license. It's really important to check this. Especially when you are working in a national organization.
09:03
It's a controversial problem. It could be a big trouble to check something. Because of the licenses. Fourth of all is the importance of documentation and guidance in the health basis or the policy basis.
09:22
The need to prepare a comprehensive documentation where it helps. It's good that we have a nice scale of our individual guides. Maybe I won't mention an example. To support the legal and compliance of the convention is important.
09:45
Because of the license. And it's nice if they have a contribution. So I'll probably move faster as usual. Sorry.
10:00
This is a list of questions from Luke. He's here in this conference too. I asked permission for him to ask this. What questions do you need to ask when you are evaluating the resource project for yourself?
10:21
How long has it been in existence? How long has it been in existence? How long has it been in existence? Is there seating and funders? Paying other organizations to meet? Food reputation? How many data holders? Is there only one person in charge?
10:42
Is there only that information? How many data holders? How many people and public homes? Does the program receive support from the public? Who's your community leader? Is there only support from the public? How long does the program for the project remain functioning?
11:04
Is there any way to get enough data? Would there be enough time to find a replacement solution? That's an important question. Then there was this
11:27
comparison. We need to compare this to other projects. To each other. And there were very good candidates to each other. And these steps to do that decision.
11:44
The first group evaluated the user, the data creators of the software. And it was a really, really good job to come up with that. We began to
12:04
So this is the reason why we chose the program. Something like this is probably too small again to read there.
12:24
We have this criteria, this test results. What's the most activity? How active is it? No community engagement, documentation, guidance, license, terms of use, low quality testing, security, long-term sustainability,
12:40
integration, component reading, and just 4.1 to 5 for this project. It was a lot of work. Of course, hundreds of user requirements have become barriers. There was no much difference between if you want to come.
13:02
So there's probably a very good or very bad place to have this presentation because we have some good examples of success stories in the open source site presented here. We have this GIS, huge GIS,
13:22
all these children are being checked out and all these very, very successful children are being found in the open source. I guess we'll let ten of those first users buy them.
13:41
Good work, guys. Good work. I love doing such stories. Okay. So what we've talked about is the importance of open source and government organizations. This is pretty obvious.
14:00
We are committed to open source and national survey. We are using open source and we are producing open source. And I hope more governments adopt this. And we added some objectives. We have listed some standards.
14:28
We have a little drawing about what we are doing. We have some role for community. A little plot of rising considerations,
14:40
documentation, and then we have a list of goals. Thank you.