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

Open Source as A Model for Global Collaboration

00:00

Formal Metadata

Title
Open Source as A Model for Global Collaboration
Title of Series
Number of Parts
275
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
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
We need open source now, more than ever. The world is in crisis: Corona pandemic, recent flooding disaster in South Asia, climate change, political threats, inequality. Open source could be a solution to many problems of our time because only by working together we can make bigger strides in solving some of the most critical global issues. People from around the world work together on open source projects. They show every day how a fruitful and successful collaboration on a global scale is possible despite different views, personal and historical backgrounds and experiences. In this session, Hong Phuc Dang will share successful examples from communities to governments, at the same time outline challenges and how each and everyone of us can play a role in sustaining the open source ecosystem and the world.
Keywords
CollaborationismOpen sourceLevel (video gaming)Online helpOpen sourceDiagramComputer animation
Open sourceCollaborationismLocal ringProduct (business)Social classProjective planeShared memoryWorkstation <Musikinstrument>Software testingBitLevel (video gaming)Set (mathematics)Mereology
Self-organizationOpen sourceWhiteboardComputer networkBuildingSoftwareSound effectNegative numberGroup actionOpen setOpen sourceComputer hardwareWhiteboardSoftwareBuildingSelf-organizationSystem callProjective planeSound effectBitGroup actionTwitterCollaborationismOpen setMixed realityShared memoryWave packetCore dumpSoftware developerWorkstation <Musikinstrument>Arithmetic meanDivisorElectronic mailing listNetwork topologyPrice indexComputer animation
Open sourceSoftwareEvent horizonComputer programComputer hardwareProduct (business)Coding theoryInformation technology consultingCollaborationismSoftwareShared memoryForm (programming)Projective planeVirtual realitySelf-organizationOpen sourceComputer hardwareSoftware developerOperator (mathematics)Event horizonMathematicsOrder (biology)Service (economics)Information technology consultingHypermediaFocus (optics)CurveVideo gameDifferent (Kate Ryan album)Computer animation
Repository (publishing)Software developerComputer programAverageSocial softwareElectronic mailing listEvent horizonSoftware developerEvent horizonLattice (order)VirtualizationSpacetimeEmailElectronic mailing listStudent's t-testWave packetComputer programmingDigital photographyBlock (periodic table)WhiteboardComputer animation
Server (computing)Query languageData managementPhysical systemVideoconferencingOpen sourceEvent horizonSoftwareComputer hardwareProjective planeOpen sourceForcing (mathematics)Observational studyPhysical systemEvent horizonSampling (statistics)Data managementExterior algebraSelf-organizationBridging (networking)VideoconferencingMUDOrder (biology)Network topologyBit ratePoint (geometry)CASE <Informatik>System callVideo gameScheduling (computing)Computer animation
Data managementPhysical systemVideoconferencingOpen sourceEvent horizonProjective planePhysical systemEvent horizonMereologySoftware developerSelf-organizationDigital photographySampling (statistics)Computer animation
Computer hardwareHorizonProjective planeProduct (business)FeedbackOpen sourceLevel (video gaming)CollaborationismForm (programming)BitStudent's t-testComputer animation
CodeIntegrated development environmentOpen sourceVapor barrierLevel (video gaming)Sign (mathematics)Pattern recognitionProcess (computing)Software developerVapor barrierIntegrated development environmentProjective planeSoftware developerBitUniverse (mathematics)Server (computing)Open sourceMultiplication signValidity (statistics)Event horizonOrder (biology)Virtual machineCuboidCore dumpCausalityMathematicsWhiteboardSystem callLocal ringLie groupForceInstallable File SystemState of matterTrailCodeLecture/Conference
Maxima and minimaTask (computing)Software developerSoftware testingControl flowSystem programmingCoding theorySoftware developerTask (computing)Projective planeDependent and independent variablesMultiplication signOpen sourceLie groupVideo gameSoftware testingPeer-to-peerSymbol tableMathematicsLevel (video gaming)Single-precision floating-point formatMaxima and minimaPoint (geometry)Set (mathematics)Content (media)Social classTorusChainObservational studyArithmetic meanPresentation of a groupCellular automatonCodeData conversionRight angleRepository (publishing)Online chatMultiplicationCore dumpDifferent (Kate Ryan album)BackupCodeWhiteboardComputer animation
Software testingControl flowSystem programmingCoding theoryOpen sourceSoftwareCollaborationismProjective planeSoftware developerCollaborationismProof theoryKernel (computing)Level (video gaming)Open sourceShape (magazine)Multiplication signComputer animation
Digital signalProduct (business)Computer programToken ringOpen sourceDifferent (Kate Ryan album)Sampling (statistics)Multiplication signOcean currentCartesian coordinate systemSoftware developerLie groupState of matterProcess (computing)PlanningSimilarity (geometry)Theory of everythingBit rateDigitizingCollaborationismMobile appComputer animation
CollaborationismOpen sourceSound effectNegative numberBuildingGroup actionDigital signalContext awarenessInclusion mapCharacteristic polynomialOpen sourceInclusion mapMultiplication signSound effectDifferent (Kate Ryan album)BitCollaborationismTwitterData conversionMereology1 (number)NumberVideo gameSystem callInformationPerspective (visual)Profil (magazine)Ring (mathematics)DigitizingInternetworkingAddress spaceSoftware developerMathematicsProcess (computing)Electric generatorVulnerability (computing)Lattice (order)Characteristic polynomialGroup actionNormal (geometry)Integrated development environmentPosition operatorNetwork topologySampling (statistics)Lie groupTerm (mathematics)Decision theoryPoint (geometry)Office suiteTrailException handlingState of matterSocial classEvolutePRINCE2CoprocessorOpen setComputer animation
Sound effectOpen sourceNegative numberInclusion mapCharacteristic polynomialGroup actionSoftwareSelf-organizationGroup actionMessage passingSoftware developerPoint cloudRule of inferenceVideo gameOpen sourceLevel (video gaming)Computer configurationInclusion mapEvent horizonSpeech synthesisSoftwareFlow separationSelf-organizationFamilyProduct (business)Enterprise architectureView (database)MultiplicationMereologyProjective planeCodeDifferent (Kate Ryan album)MathematicsStrategy gameOpen setCollaborationismSound effectPower (physics)Point (geometry)MeasurementCellular automatonDispersion (chemistry)Computer chessWorkstation <Musikinstrument>Formal languageGoogolTouch typingMotion captureOffice suiteUniverse (mathematics)Lie groupSampling (statistics)NumberComputer programmingHand fanMetropolitan area network
Open sourceDifferent (Kate Ryan album)EmailOpen sourceOcean currentOvalInformationMatching (graph theory)Normal (geometry)Event horizonProjective planeComputer animation
Open sourceMoment (mathematics)Projective planeFormal languagePlanningRight angleSoftwareMereologyOrder (biology)Level (video gaming)Flow separationNumbering schemeCASE <Informatik>Wave packetPoint cloudIncidence algebraOffice suiteGroup actionFreewareCollaborationismInformationTerm (mathematics)HierarchySoftware developerCircleProcess (computing)Inclusion mapVapor barrierSelf-organizationSingle-precision floating-point formatEmailUniverse (mathematics)Social classMultiplication signTranslation (relic)Cartesian coordinate systemComputer programmingRepository (publishing)Shared memoryQuicksortBit rateChainFerry CorstenGoodness of fitEvent horizonPattern languageThomas BayesAreaVideo gameForcing (mathematics)Sinc functionShape (magazine)Observational studyOpen setLie groupDifferent (Kate Ryan album)Data storage deviceHand fanStaff (military)Associative propertyComputer animation
Row (database)Cartesian closed categoryComputer animation
Transcript: English(auto-generated)
Welcome back to the third day of Congress here at the HUG stage with a very interesting sounding talk,
Open Source as a Model for Global Collaboration, where Hong, Fook, Dong, Deng will share successful examples on how open source can be a helpful tool or solution to global problems.
And I think with that, out of the way, I can already give over to our speaker. Thank you, Lenny, for the introduction. I'm very happy to be here. My first Congress was 31C3. At that time, I also gave a talk on stage about local production in fashion in the textile industry.
I still remember how I was so impressed with the whole thing, overwhelmed with the ambient setting projects and the people at the CCC back then.
And of course, like many people, I came back every year. I still can't believe that this year there is no face to face Congress, but I'm still very glad that we have this virtual experience. And I'm happy to to be part of this a little bit about myself.
I was born and raised in Vietnam. What is my relationship with open source? I am a founder of Force Asia. This is an Asia based organization that develops open source software and hardware.
We promote open source activities and try to grow the communities in the region. Because of my work and engagement in the open source community and over like
10 years, I got elected to be the vice president of the Open Source Initiative. This is a US nonprofit that safeguards the open source definition and maintains the open source license list. Recently, I also joined the Open Source Business Alliance as a board member.
This is a German nonprofit that operates Europe's biggest network of companies developing, building and using open source software. What is different between now and the 31st C3?
Not so much. I'm pretty glad to say that I'm still doing the same thing. I forget for open source development, open source activities and build a community. And, yeah, so this is what I do today.
I'm going to cover three topics at first. I want to talk a little bit about the lesson learned and example how we build open source projects and community.
And how open source is a model that can enable global collaboration. And then I want to touch briefly on two trends that bring negative effects to the open source ecosystem that I have seen the past few years.
And finally, a small call to action lesson learned. And it all started back in 2009 when my partner and I.
Found it for Asia Organization back in Vietnam. At that time, we realized the opportunities that open source and open technologies can bring to the people in the developing nation and country. The opportunity to learn, to share and to develop your own solution.
We see this opportunity and we want to bring this opportunity to spread the idea to more people, build a community so that people can make their own decision and build their own solution for themselves.
For Asia, basically a network of people who share the same idea, the same belief in sharing and collaboration. Even though our name is Asia, we have members, contributors from outside of Asia as well, from Europe, from Australia, US and many countries around the world.
What we are doing, we develop software and hardware projects like many other open source organizations out there. We run events to bring people together.
Before it was face to face, even now it's on the virtual spaces. Another focus of ours is on education. So we teach people how to write, how to write code, how to contribute to different open source projects, because we believe that in order to change something, in order to increase the adoption,
everything needs to start with education. So it's also our big focus. Since 2009, we managed to sustain the operation and this is actually not so easy as we started with two people as a grassroots organization.
We bootstrap most of our activities ourselves, do not have any backing by a corporation or by government or American like funding organization, something that is to stack everything on ourselves.
So it's always a big question for us how we can sustain the operation. The question about how to continue to grow and develop further. We constantly think of a model, how open source can generate an income financially that's able to
continue to build and work on the projects of our interests and that we are passionate about. So there are different ways to sustain. For instance, we offer services around the software that we develop. We sell hardware and we also do consultancy.
The scale of the organization, we have about 35,000 subscribers to our mailing list and media, social media, about 4,000 developers registered on GitHub. Through our changing education program, we onboard 2,000 young developers and students every year through coding programs.
We organize a lot of face-to-face meetings. Like previous year now, we do a lot of virtual events and also hackathons. We maintain a technical blog, so basically this is a space for people to share technical knowledge.
These are some of the software and hardware projects that we develop in the ForceAsia community. Today, I would just emphasize, I want to introduce two projects as an example
how open source works in a low-source scale starting from somewhere in Asia. First of all, Event Ye. Event Ye is a project that started in 2015.
This is an open source event management system. We organized events since 2009 and it's always challenging for us to see what kind of tooling to use for papers, what to use for scheduling, for a particular thing.
We always have to use multiple tools. In the very beginning, we used Google Forms just to collect submissions. We also want to, at one point, realize that there should be an open source solution that helps organizers to run events. It's really important to do events just like the Congress where people can get together, can share the idea.
That was the original goal to have an open source event management system. So we started to build this Event Ye and now it becomes fully functional. It's converted to call for papers, scheduling, ticketing.
We also recently integrated video conferencing, the solution entirely open source. We also work with other open source projects. For instance, we integrated GCP Blue Button and, of course, there are also bridges to other video solutions.
This is something that we've seen as an alternative to proprietary software like Eventbrite. Another project that I... It's one thing that I forget to mention. We have about 100 contributors since 2015 contributed to Event Ye.
They are not only coming from Vietnam, India, the part where we are in, but we also got developers from Europe and the system being used by organizations in the US as well.
And now we can continue to collaborate with more projects to develop further Event Ye. Pocket Science Lab. This is another example. We previously, I think the past few years, we have our assembly at the CCC and we also run workshop on the Pocket Science Lab.
This is the open source hardware device for education that built as a teacher-student project starting from India. But now it has become a consumer product.
We distribute it in many different continents, including Europe, the US, and the collaboration here. We came to the CCC some years ago and we got feedback from the community how to change the design, the blueprint of the hardware.
And we also collaborated with a European level project, the Horizon 2020 on Pocket Science Lab, worked together with Frau Hoff for institutes here in Germany on the production of the hardware.
So I want to talk a little bit about something that we learned over the years of developing projects and also building the community.
I often get a question from people. So how the whole thing gets started? How do you get people to contribute? How do you come up with which project to work with? So back in 2009, Force Asia started out as a place, as a conference, an event where people meet and exchange ideas.
And when people come together, they start to develop projects, they start to work together. But it's really important in the beginning of building a community. We need to understand the landscape. So people around you, what kind of technology they are familiar with.
When you introduce something, you need to be sure that the people in the community are excited about the ideas of the project. And as you see on the picture, the people around us at that time are very young people. So they're just getting out from university and also did not export a lot to the whole global open-source movement.
So we tried to promote a contribution apart from coding. So there are a lot of things that people can contribute. For instance, doing design, writing articles, promoting projects or organizing events, doing fundraising and many more.
And we realized that to promote contribution apart from technical can help to widen, to attract new joiners.
And one thing is still valid. It's valid until today, which is try to keep the entry barrier low. If you contribute to various projects, open-source projects, you can see in order to set it up on your local server. So somebody before they start to contribute, they need somehow to install it on their local machine.
And it's always different experience for different projects, not something out of the box that can easily be done by a beginner. So for us, the question is how to keep the entry barrier very low, how to get people setting up inside it before they can actually contribute.
Another lesson that we learned is to understand the motivation of developers. So if you want to attract people who write code, which is like the core thing of the project. So you need to be aware of their motivation.
So a lot of people from Asia community are motivated by opportunities to get higher in the future opportunity to travel outside of the country, which is very difficult for many citizens in that particular region.
And of course, they are motivated to work on tooling that they are familiar with. So we understand this, understand the motivation and what we try to offer to our contributors is something that's much and that can satisfy their wish.
Since 2012, we try to reach out to more international communities and invite developers, speakers from the West to come and connect with our people to share the knowledge. And at the same time, we look for opportunities to bring the contributors like overseas where they can get exposed to more global environment.
Another thing that we learned over the year, there are so many open source projects out there, right? It's not as one day you develop something to put it online and then they will attract attention from the community.
It's really difficult these days to get to onboard new developers or to get people actually engaged and contribute to your projects. And we learned that as a developer, as a co-writer, people like to improve their skill.
So we organize something like coding contests that have been going on for the past four years already. So we do this throughout the year, try to help people at first to learn how to code and then as they get better, they also win the prize for contributing to our projects.
And we find it really useful not only to attract new contributors, but at the same time, you need to widen the pool of contributors. It is the first step to guide people, to show people how to contribute to not only our project, but also open source in general.
Developer retention. So I don't want to have a side. There are a lot of things that happened in the last 10 years.
I'm not able to share every detail, but I hope that to summarize a few highlights in this presentation. Retention is a big question for many projects, not only ourselves. When you build an open source project, you need to understand that at one point, people will move on.
So people need to go on with their life. They find something more interesting. It's difficult to keep people continually engaged over the years. So therefore, it's important to always reach out to more people in the community, try to engage and change newcomers.
At the same time, you should not put the knowledge into one core person. It's always important to make sure that you have a backup on whatever you are doing.
Introduce peer review to ensure that more people can review the course. And of course, minimum two maintenance so that you don't have to rely on one person over the time. Delegate tasks, this is something that we find very useful. When people join the project, people like to have more responsibilities.
It also motivated them. This is quite interesting finding. So people are not only motivated by financial benefit or by traveling, but some people too motivated by the responsibilities that they have.
So we introduce mental roles where people can have the younger developers or newcomer to get involved. And this is something that can motivate and keep people engaged in the project.
And we also introduce development board practices. This is something that is not new to many projects out there. The question is, how can these practices being enforced and implemented in your development?
And this is the question. So a few things that we got out from our development practices, which is always one issue to one pull request. These are very simple, but a lot of people don't do it. Big issue into multiple small issues.
It's also easier for people to review this and have required so much effort from the reviewer. Test before making a pull request. So, of course, this is a standard way, but a lot of people still to make a PR without testing before they make a PR. We can make things more difficult if you merge and then something goes wrong, you have to reverse the change.
Only change is that you stay on the PR. You stay on the PR on one thing, but actually there are a lot of different code change into one PR, which is not welcome or encouraged. Help each other review each other pull request. This is like a peer review practice that we always encourage.
Document-wide coding. So document is not a favorite thing to do for developers. But we always encourage our contributors to document why they are coding so the next person can understand and follow up with the progress.
Earned right access. So basically after contribute to the project for some time, you'll be able to earn the right access to the repository. And one thing that's very important is to avoid private conversation and only collaborate with the community with the on the project level chat.
So we do get to for our chat and every single project have their own project channel. So instead of two developers talking like on private about how to fix an issue, we encourage people to do to have their conversation on on the on the public channel.
Yeah. And yeah. And how can you make sure that people really follow the practices? So it's about encourage people to remind each other is a practice that the developers continuously
helping each other and being a praise for being appreciate for for for follow the practice.
So again, so open source is a decentralized software development model that encourage open collaboration has proven how collaboration could work successfully on the global scale. Of course, the project that we develop is on a very small scales compared to Wikipedia or compared to the Linux kernel.
But you could imagine starting from a project somewhere in Asia is now being used by many other countries at the same time, happy contributors from everywhere.
So if we can achieve a local collaboration with this project, imagine how much impact it could have if open source be done on the national level, on government level. So, yeah, so I just want to give one quick example here. The current
coronavirus pandemic rates a lot of digital solution have been developed everywhere around the world. This is an example of the digital contact tracing application developed in Southeast Asia. As you can see here, we only have 10 countries in Asia and in Southeast Asia region.
And these six countries, they all develop their own solution. Yeah. And it's all a similar problem. They all say that they all want to have a digital contact tracing app. But different countries status their own application, even though it could be possible to share and call it back in some way.
But it did not happen. So I don't know how much it costs for for this country to develop the solution. But I read somewhere online the Corona fund app developed in Germany does cost over 20, 20 million euros. So you imagine if each country spend as much money to develop similar solution, why there is no
collaboration across nations so that we can save the resources at the same time, speed up the whole process. Corona pandemic is only one of the challenges that we are facing these days.
Climate change, political war, so many issues. Open source collaboration could be a solution to many problems, but we need more examples. We need a successful example to accelerate the whole open model in all industry.
Open source should not be only about software. It could be the open model could apply for for hardware, for pharmaceutical formula, could apply for processes. And it should be open source, open center or should be a default for for all different industries and encourage more collaboration across borders.
Moving on, I want to talk a little bit on the trends that bring negative effects to open source ecosystem that I have observed in the past year.
First of all, I want to talk about digital shaming. So digital shaming is being electronically attacked online.
It can literally destroy people's lives financially and emotionally. And sadly, there is an increasing number of open source contributors or anyone could be victims of this digital shaming.
Have you ever participated in a digital shaming act? For example, if you unconsciously lie or treat or retrieve something that you read online. So I don't know if anyone remembers a tweet that happened in Python some years ago where some people
would talk about a conversation, a private conversation of two male developers in a sexual way, considered a sexual way. And then these people got fired for their act. And this is just one example.
If you see something that is happening online and you see so many people lie to treat and you think that you should also support this activity by lying or retreat. So think about it before you do something. If you are not if you do not know the person, do not and do not have the understanding the whole situation.
Do not be part of digital shaming. One thing I think that is important to understand is the self-serving bias. Self-serving bias is an action done only for one's own benefit, sometimes at the expense of others.
It happens every day in our life. For example, a few days ago, I forgot to call a doctor to change my doctor appointment. And then when I was asked by my partner if I've done this because I don't want myself
to look bad, I just say that, oh, I called the doctor office, but nobody answered the call. So we tend to be always biased on our side, on our side. So whatever information that you see people claim online, you need to see that people often talk on their own perspective.
And of course, I can be a very fair person, but I will always try to protect myself. So and a lot of activities like this happen on the Internet. And many I see that I see many older generation of contributors are leaving the community because of this digital shaming,
because something that that they might have misspoken in the public and then being criticized so much by the public and then force them to leave the community. And this really creates an unhealthy environment for people who contribute and involve in open source community.
And there's also something that we should be aware of. There are a lot of people out there use vulnerable act for public interest because they think that if you if you spread yourself as a victim,
you you could get the attention and the support from the public. And it's also good to to build up your profile and interest. So this is like unreasonable, unreasonable. But it's still a practice that happened on online, on the Internet.
So important for us to be aware and do not be part of this whole thing. If we do not support the support initiative, if you do not know the people who involve or do not have a clear understanding of the real story.
Another thing that I another change that I also wanted to highlight here, diversity and inclusive inclusion. I'm really glad that there's so many so many initiatives and so many efforts in our society to push diversity and inclusion these days.
By definition, diversity refers to the traits and the characteristics that make people unique, why inclusion refers to the behaviors and social norms that ensure people feel welcome. Yeah. And as you can see, there's so many corporations, big companies now embrace
diversity and inclusion by saying that they want to get more women into leadership positions. They want to develop a more inclusive recruitment process where discrimination in recruitment could be limited.
And there's also many more. Yeah. So you can see there's more agency now being informed to advise on diversity inclusion. There's more jobs created for people who research and who want to develop further in that field.
So I'm also very happy because myself as a minority, I have a diverse background. I'm a woman at the same time coming from Asia. So this whole be it's like for many years during my my career life, I also experienced discrimination.
And this is a really great thing for for for people like myself and also a great thing to us, a more equal society.
However, there there are some side effects that I want to emphasize here on this. There's different initiatives that we should support, but there are also something that create more confusion for for for people, especially people coming from a non English native speakers.
Yeah. Have you ever experienced that you come to a meeting room with with your colleagues, the people you work with and you afraid of. Ringing up, afraid of saying something because you're not sure, afraid of address the person
because you're not sure what kind of pronoun you should use to address that person. Yeah. And there's a lot of rules about the way how you speak in public. Yeah, of course. If I am the advantages of for being a non native speaker, I can always say that I'm not aware
of all the implication in the languages, but it's really difficult for people like for white people who consider as a native speaker. So they now started to to be worried about what is the right thing. They allowed us to say or not. It would be like offend somebody in public.
And I heard it's a lot in in the communities these days. So I just want us to see that diversity inclusion is a good thing. We definitely need to support it, but we also need to be aware that white people, white men is also part of the community, part of the diversity and inclusion.
It should be about everyone. So we should not exclude or make people feel uncomfortable about coming up with new initiative that only applicable for people in particular countries. Yeah. And again, so I'm worried about.
Is it the whole diversity and inclusion, the side effect is our freedom of speech being limited because of too many rules of life these days? And do people really like can freely give their feedback?
And criticism actually is not always bad. So it's had people to improve and become better. I want to give another example that has happened to me recently. I was as an open source event where there was a group of people talking, presenting about policy on a European level.
So this is a group that advised the commission on policy and they're using a closed source software like Powerpoint to present. And there was a message in the community saying that, OK, so if we we advise
the commission on using open source, we don't wish, don't we should we use open source ourselves? And this person gave the comment being attached so much by on the just saying that, OK, so this is an act of excluding the people.
So even though he just likes to say the truth, that if you work on open source, don't you assume you use open source yourself? And he's being called out by many people saying that this is a bad act because you should not re-decide people, should allow people to participate. So for me, I do not think it's a big thing, but I see that people have
different opinions and then that person did not want to come back anymore just by saying a fact. And then hit like stating the fact being re-decide as not support inclusion practice in the community.
So this is something that we we should be all be aware and we should all be aware and think about, support the right initiative and be more open. Put yourself into other people's shoes, right? Not everyone has the same understanding.
And when people say the fact, it doesn't mean that they try to to re-decide the other person. Call to action. Each and every one of us can offer support with we are capable of. There's so many things that we can do to to become a good a good citizen.
First of all, use open source software. As I mentioned that example earlier. Yeah. So my grandmother, my my mother. Yeah. So they have never spoke to open software before. I could understand it's difficult to get these people.
But if you are working as an organization that advise government on open source level, please use open source. If you got funding from the government to develop open source projects, use open source products yourself. There's so many alternatives. So instead of Zoom, you choose the big blue button instead of Eventbrite.
You event. Yeah. Instead of Google Cloud, you Next Cloud. There's so many options out there that you that you can that you can use just by using open source software. You'd like have a have put a support on on the ecosystem. Contribute open source projects. There are so many ways.
So if writing code contribute to documentation, globalized, globalization, including localization. So change less project into different languages, organize virtual events and try to bring people together.
There are also a lot of like design works and and also make donation to open source projects. Talk about different open source projects. There's something that anyone can do. If you are a developer, release your work open source. An example earlier about the tracing app, right? So imagine how much money we could save just by sharing, develop, play together.
If you have one problem. Yes. So why why do we play develop 10, 20 different solutions to tackle one problem there? So we can also work together and advocate for open source model in your organization.
So open source is not only about software. It's about open collaboration. It's about sharing the knowledge. You bring the knowledge to to more people advocate for this model inside your organization, in company and in your government.
There's so much that you can do here if you live in Europe. So in Asia, it's so difficult. And we never have a opportunity to talk directly with our politician. But you have the chance here. So do that and make sure that there's a support for open source development. I know that there is a new open source strategy that being introduced by the Commission for 20 and 23.
So you can check out that as well. Support open source, small and medium enterprise. Yeah. So if you could give a contract, I could hire someone to work.
So why not work with small and medium companies? So we don't want open source is a few of it, a better view for cooperation, multi national companies anymore. We want more companies to come in and also be in part of the ecosystem and finally bring open source in education.
So there's several way that you can do that. You can make education possible. For instance, I teach my mom how to use Ubuntu on the office. So education could suck in your in your home. And then it could be like in school.
Work together with teacher, university, do education, coding program. Like, like what we well, like what we do at the false Asia. But there's so many small thing that you that you could do, like connect with people around you, educate people around you, your friend, your family members.
And finally, take an active role. Everyone, anyone can make a difference. We just need to to do it. Um, yeah, I would like to take the chance to invite you as well to our summit in
in March between 13 to 21st, 2000, March 2021 to connect and collaborate with open source community in Asia. This is going to be a virtual event as well. And below is my email.
I'm happy to stay in touch. And if you have any questions about our projects or about his presentation, please feel free to to contact me. Thank you. All right. So I have four questions as of current standing.
I think I'm just going to go with the first one. Do you know of solutions to avoid information hierarchies? In essence, single people knowing crucial information.
So I don't know a solution like to avoid hierarchy. But I could say that the open source development model. So when the circles and the process open, openly available to to everyone. So this is a way to avoid information in terms of hierarchy.
Yes. So if you do open source, like in the open way, so you documented your work, how the infrastructure develops. So everything is openly documented so everyone can have access. So it's the same with with many open source projects out there. If you look up on GitHub, there's no secret on our repository.
Right. The way we develop and how the infrastructure set up. What is the blueprint for our hardware? Everything is publicly available to everyone. So I would say that the open source model is a way to limit hierarchy to information.
OK, thank you. We have a question about inclusion. How is it or is there an easy way to break the language barrier in an international community? Many people want to contribute, but not everyone does speak English well enough to discuss technical or other issues deeply.
Yes. So the language barriers, it has been a topic like for so, so many years. So what do you think that could be a suitable solution for this? So there's like translation application out there. But of course, this is a barrier that is always there, the language barrier.
Right. However, on the good side, more and more people getting like being trained on English. So, so, so you can see this there even like in developing countries like Vietnam, Cambodia, Laos, more and more people started to learn and speak English very, very good and fluently.
So it's about like we need time for people to get into to learn the language and at the same time to contribute. There is not an easy solution to break the language barrier. There's always like some projects they do, they translate to make sure that they translate the contributor guidelines.
So to show people how to contribute in different languages. But at the same time, you know, it's not a ultimate solution because in order to write a code,
most of the things taken in the end of all that written in English, people need to do to understand and also have a certain level. But the good thing is that people are getting better and better.
So there's so many ways that people can can have to learn the language. So I think that in the next few years, hopefully there won't be a language barrier anymore. Everyone could be able to speak and write in English. And do you have plans on expanding outside of Asia or with Asia, maybe to Africa or other continents?
Yes. So for Asia, right. As I mentioned, we based out Asia, but the projects that we do, it actually not only focus on Asia. So we have a partner here in Europe. So we work together with the European Union.
We work together with Sproulhofer Institute and we are part of the OpenNext program. So there is already existing collaboration. So we're not focused only on the Asian market because open source is a gross border.
So anyone can do anyone can contribute. Africa is also a very good question here. So we connected with Africa for also is again. So it's not honor any. There's no nothing Congress that I could share at the moment.
But there's also initiative and user group that active in Africa. And we also connect with them at Congress. I don't know if anyone from Africa is here at the Congress, but at the open source initiative, a false Asia summit. We do have people coming and it changed and connect with us.
OK, very cool. And the last question for today would be how much of Asia's interest or activities promote contributing to existing popular software projects? Could you repeat the question, please?
How much of Asia's interest is into promoting contribution to existing open source free software projects? Yes, actually, we promote not only our object, but we actually do promote a lot of other open source projects. As I mentioned, we we you see from the stack.
Yeah. So it's the entire pandemic. We we try to use open source solution. Most possible. We set up our own next cloud incident in the project. We use liberal office for for several years and we use scheme in case. So we promote also in our training at university and the school that we work with.
We offer training on open source solution to to people. So not only we do not only promote our own false Asia project, but we actively promote other projects. And I believe that there's also like some project that I know in the community getting contributor from the false Asia community.
So which is something that we are very class in order to survive in order to grow the ecosystem. It's not only about your organization, it's about the collaboration. You need to work with other organizations and you need to foster collaboration in order to grow and foster the entire network.
So we are very open to work with other projects as well. As I said, we integrated GC already in a vignette and also big blue button. Yeah. And yeah. So there are many more. I think that really nicely concludes this great talk.
You left your details in the slide. So if anyone still has questions, as she said, write her an email. And I think from our side, this talk is finished. And if you have anything more to say, say so. And apart from that. Yes. So I just want to say thank you very much again for having me.
Thank you, Lenny and Marcus for setting up the whole thing. Really appreciate it. Ciao.