It takes a Village
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 | 39 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 3.0 Unported: 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/67219 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSS Backstage 202226 / 39
2
9
11
15
26
30
36
37
00:00
Open sourceOpen setBitComputer animationLecture/ConferenceMeeting/Interview
00:26
TwitterOnline chatOpen setTerm (mathematics)Product (business)TelecommunicationOpen setOpen sourceNatural numberWhiteboardObservational studyBitTelecommunicationDifferent (Kate Ryan album)Flow separationProduct (business)Computer animation
01:20
Open setFocus (optics)Multiplication signFocus (optics)Open sourceDifferent (Kate Ryan album)Rule of inferenceNormal (geometry)Natural numberExpected valuePublic key certificateDegree (graph theory)Inclusion mapProcess (computing)Identity managementType theoryComputer animation
03:17
Open sourceNatural numberExpert systemDifferent (Kate Ryan album)Group actionPerspective (visual)1 (number)UsabilityField (computer science)Medical imagingComputer animation
04:53
Open sourceError messageOpen setMetric systemOpen sourceComputing platformEvent horizonNatural numberRight angleView (database)Software developerMetric systemProjective planeSource codeComputer animation
06:04
Thermodynamischer ProzessOpen sourceGroup actionComputing platformStandard deviationMeasurement
06:38
Pattern recognitionPeer-to-peerTraffic reportingType theorySubgroupBitPerformance appraisalHypermediaComputing platformStudent's t-testUser interfaceTwitterProjective planePresentation of a groupFeedbackComputer animationTable
07:31
Chaos (cosmogony)Open sourceGoogolChaos (cosmogony)Goodness of fitDigitizingComputer animation
08:00
BitLevel (video gaming)Meta elementProjective planeHypermediaGroup actionOpen sourceComputing platformCollaborationismDifferent (Kate Ryan album)Expert systemChaos (cosmogony)Meeting/Interview
08:44
Information retrievalBitRule of inferenceSelf-organizationDifferent (Kate Ryan album)Form (programming)
09:27
Local GroupSubgroupArchitecturePerformance appraisalGroup actionOpen sourceWhiteboardComputer architectureSubgroupBitMetric systemOperator (mathematics)HypermediaAttribute grammarEvent horizonRule of inferenceComputing platformComputer animation
10:24
Software maintenanceLocal GroupSoftware developerSoftware testingContent (media)Thermodynamischer ProzessOpen sourceService (economics)WebsiteGroup actionInclusion mapOpen setProduct (business)Event horizonMetric systemSocial softwareCollaborationismSpacetimeInformationData managementChecklistPerformance appraisalCapability Maturity ModelProcess (computing)Computing platformArchitectureCodeDifferent (Kate Ryan album)Group actionEvent horizonLogic gate1 (number)Natural numberProjective planeProof theoryWhiteboardComputer architectureOpen sourceProduct (business)Thermodynamischer ProzessComputing platformProcess (computing)Functional (mathematics)ChecklistData managementInformation securityHypermediaEvoluteMeta elementSoftware development kitSimilarity (geometry)Software bugLogistic distributionOpen setAreaComputer animation
13:45
Local GroupComputing platformProcess (computing)Open setGroup actionInformation securitySubgroupTask (computing)Thermodynamischer ProzessPerformance appraisalTemplate (C++)Open sourceSoftware frameworkInclusion mapEntire functionAreaThermodynamischer ProzessComputing platformPerformance appraisalFeedbackGroup actionINTEGRALComputer animation
14:09
Product (business)Direction (geometry)Open sourceComputing platformSet (mathematics)Open sourceComputing platformRevision controlDirection (geometry)INTEGRALComputing platformNatural numberStreaming mediaCoalitionComputer animation
14:55
1 (number)Different (Kate Ryan album)Open sourceXML
15:34
ScalabilityComputing platformOpen sourceCodeLevel (video gaming)CuboidOpen sourceSystem callStandard deviationUniverse (mathematics)Service (economics)Computing platformGroup actionStudent's t-testRight angleComputer animation
16:28
Open sourceLocal GroupObservational studyThermodynamischer ProzessPerspective (visual)Standard deviationEntire functionGroup actionObservational study
17:27
Open setComputing platformScalabilityBitOpen sourceCodeComputing platformOpen setComputer animation
17:50
Group actionData structureData managementWhiteboardThermodynamischer ProzessProcess (computing)WhiteboardData structureData managementDifferent (Kate Ryan album)Computer animation
18:11
Open sourceThermal expansionComputing platformImplementationOpen sourceSoftware developerGroup actionOpen setThermal expansionComputing platformOnline helpThermodynamischer ProzessNatural numberInformation security
19:06
Metric systemThermal expansionComputer hardwareComputing platformOpen setRight angleComputer hardwareOpen sourceNumberOpen setSoftwareComputing platformThermal expansionMetric systemComputer animationEngineering drawing
19:39
Computing platformCoding theoryLattice (order)FeedbackOpen sourceComputing platformOpen setVideoconferencingTemplate (C++)Slide ruleTwitterLink (knot theory)CASE <Informatik>Lattice (order)BitDifferent (Kate Ryan album)Procedural programmingProjective planeLine (geometry)1 (number)Open setCollaborationismGroup actionPoint cloudOpen sourcePhysical systemGoogolSubgroupParameter (computer programming)Standard deviationCore dumpMeasurementComputer clusterComputer animationMeeting/Interview
23:33
Open setOpen sourceComputer animation
Transcript: English(auto-generated)
00:04
I think I should rename this to It Takes a Village 2.0 because I've been giving this talk successively over two years now and it keeps expanding so I may go a little bit fast in the beginning and then slow down a little bit more at the end in regards to you know what's the newer pieces that have come into
00:21
play. So first of all who am I? I'm Solana Bonvold. I'm the Executive Director of IEEE SA Open and here's all the different ways that you can contact me. What I wanted to first talk about was the benefits of diversity and I might be preaching a little bit to the crowd here in regards to that but
00:47
but there's several different studies that the Harvard Business Review did showing all of the different things that happen when you have diversity in your company and your crew and your executive boards and things of that nature. You get better quality products, you get more innovation, you get
01:02
increased productivity, you have less biases, clearer communication, less tribal knowledge because you can't be as assumptive which means you also get better long-term documentation and larger communities. All of these things are things I can believe that open source can greatly benefit from.
01:21
So and I also want to ask you know this question for a lot of times. If you're not diverse are you really open? So why role diversity? Why did I focus on that one particular flavor of diversity? Well one because going after that actually counters a lot of common problems that happen in diversity and
01:46
what I mean in regards to that is a lot of times diversity does not equal inclusion and so by going through and doing something like role diversity you're actually going through what's called a functional diversity which means you automatically give roles and things of that nature which I know
02:01
sometimes it's antithetical to the open source way of meritocracy and things of that nature. It actually helps other people that are coming in that are new to the community where you can do things in regards to manage your expectations. If I come in and I'm new to open source and I'm like hey I do marketing or you know I'm a director of marketing or I do these kind of things you automatically set expectations tell people who you're
02:24
there and what you're there for and it actually lends to a easier going community in many different ways for that. Also it's more about the expertise aspects so that people can bring in their expertise and you can go through and focus on those things that we talked about earlier in
02:40
regards to things like production quality and it makes it easier to recruit volunteers. One hard thing that comes in when you're recruiting is they're always like what am I going to do I don't know what I would be able to give you you know why would it be useful at all for me to come in here. If you have those roles it makes it easy they're like oh yeah no I know
03:02
this I can come in I can help you with this and in a weird way it makes it less political in regards to the normal other types of diversity identity politics. Instead it's your job it's what you got a degree in it's what you got a certification in it's things of that nature. So basic rules go where they are you're not going to get anything different if you're
03:23
fishing in a goldfish goldfish bowl you're only going to get goldfish so you're going to have to get out there and see all the different ones in there. Also remember in regards to that you need to get you need to respect their differences as well. It's really hard to make a bunch of marketing people work in GitLab. They're not used to pull requests. Guess
03:44
what the tools in GitLab for them suck right they can't do any of their enriching stuff they can't do a lot of different things like that. Same thing for bringing in nonprofits and governmental entities. Once again our tools are not made for them we're going to have to evolve and go to them. The other thing to remember is the value of newbies. I think most of
04:05
y'all are already familiar with this since working in open source but the big thing on there is the same things that you're already used to. Most of these people aren't actually newbies they're experts in their own field they've been doing these different things they're just new to open source
04:22
they're new to how we do things and so for that we have to sit there and work with them on that and so we can get rid of a lot of the tribal knowledge that's happened because we got a lot of tribal knowledge we can affix assumptions and we can make it easier to be able to ask questions without fear because sometimes those questions may blow your mind because
04:43
you hadn't even considered that perspective especially with designers and special interest groups and things of that nature and so that way you can go through and have better quality and usability. So what are we doing at IEEE SA Open? Well we're evolving the open source platform. We needed our
05:02
tools to be 100% open source so we're only using open source tools. We're focusing a lot in regards to metrics because one of the things that I view is that I think one reason we became so developer centric is because the successful open source projects were developer to developer. You know that was Apache, that was Linux, that was Kubernetes, all these different things
05:23
were good because it was one to the other and we got lazy. We use convenient data for how we measure things off of GitHub. We talk about commits and pull requests and things of that nature. None of that is friendly to any of these other people that are in your community that are already probably actually doing things like throwing events like these for you or
05:43
doing the marketing for events like these or things of that nature. There's this disastrous convenient data out there where those volunteers never get really rewarded within that community. So we wanted to be transparent, findable, granular, traceable, all these things that you're probably already used to
06:01
and of course the big one respectful of rights because we are IEEE and we're global. So one of the things that we've been working on for the platform is this community process which kind of first starts off with documentation. So we have the different groups that create documents and then they'll try to templatize it and then we'll automate, measure it, make sure it's working and then go through the standardization process. The
06:23
standardization process at IEEE is not fast. Okay maybe I should rephrase that. IEEE thinks that two years is fast which isn't normally the way that open source use it, correct? So we have to work with that. We also have to
06:40
work on creating rewards. We have a badging subgroup that's specifically focused on that. We're looking for those types of things in regards to healthy, accurate, and kind. We are a little bit Daniel Pink biased in regards to that. And then of course giving credit and so we're looking at that in regards to the platform too as to how do we give credit to these diverse roles that are coming in because we can't do the pull requests, we can't
07:03
do any of those different models and they're all queuing in and saying the different ways that they do want to be measured. I gave a presentation on behalf of your project. I should get some kind of thing for that. Or I went and I tweeted a whole bunch of stuff about social media and got this many retweets. Or I went in and I did an evaluation with all of my students
07:22
of your platform and came back with this feedback on your user interface. All of those things we can go in and start to give recognition for. There's a whole bunch of other initiatives right now that are working on role diversity as well. We work a lot with chaos at the Linux Foundation.
07:41
Amanda Kasari is doing a lot in regards to ocean. There's also an academic one which is Kasari but Kasari and credit I think just split a few months ago. And of course earlier we heard from Heath in regards to digital principles and digital impact which are the digital public goods and their work too. So one of the things we're doing is we're eating our own
08:03
cooking. So we're very meta right now and we have been pretty meta for a while which makes it a little bit hard to recruit. So what we're doing on that I'll talk about what the meta levels are and so we're doing a lot of different collaborations. As you noticed we're participating with
08:22
a lot of other groups like chaos, like the open source way 2.0, like all of these other different projects that are out there. And so we've been basically trying to gather together a bunch of social media experts. We're also working on a standard too in regards to open source governance but that isn't the platform. That's something that's actually completely separate but I'll
08:44
talk about that in a little bit. We're community driven. IEEE is a 501 C 3 which in America means something very significant. 501 C 3s are actually tax deductions which means the IRS cares a lot about what you do and
09:02
how you do it in the forms you have to file. It's different than a lot of the other organizations that are C6s which are business consortia. So we have a lot of extra rules which means sometimes things take longer but it also means that volunteers decide my budget. Volunteers decide where the different things go. It's not a corporate entity. In fact they do a lot of stuff to
09:24
prevent corporate dominance for exactly that reason. Right now in our community architecture we have OSCOM which is the open source committee that reports directly to the Board of Governors which again are volunteers. And then we underneath them we have our different advisory groups. We have a
09:40
community one and a marketing one and a technical one and then they all have subgroups. So the community one this is kind of a little bit older because there's more subgroups underneath each of them but we have things like badging, DEI, education and then for the marketing AGs we've got the events, social media toolkits, metrics and a lot going on with OSINT as you can
10:04
probably imagine that we were already doing it and it exploded with the whole situation in Ukraine. And then we have the technical AGs which are doing where we're drinking our own wine in regards to the platform. And then with OSCOM we're doing a lot of the governance of the platform too with operations manual, the governance, the naming, all those different rules. And you
10:26
can sit there and see all these different ones. We are in GitLab. Everything goes into the GitLab which can sometimes be like I said a little bit difficult but you know the community is helping evolve that. So the
10:40
community advisory group is I think of as the heart of what we're trying to do. It's all of the users and the special interest groups and the nonprofits. IEEE has a very big nonprofit academia leaning and so this is where that all really comes into play and so they do a lot of the leadership in regards to that. Not all of these people are technical people okay but
11:04
they're leaders and they know what needs to be done and how it needs to be done and they're very strategic thinkers. The next one we have is the marketing advisory group who I feel is so often the unsung heroes of open source which is basically not just marketing but evangelism, social media,
11:21
events, designers, artists, that whole group. And so they've been working on a bunch of different things including like marketing toolkits so any new project that comes in it's like oh here's a little toolkit here's how you can go and do your stuff. And then lastly the technical advisory group which you probably think you know what it is but it isn't. It's
11:46
you're probably used to an open source. Instead it's a group that helps create all the different things to help on the technical processes. They also drink their own wine too in regards to the evolution of those processes. So for
12:02
example they've been doing things like creating what is the checklist and the process for new tool and feature creation on this platform. So they're opening that and then also sending giving that to the other project saying this is how we're doing it we would love it if you would come and do that too. They also talk a lot about the prioritization and
12:23
logistics and then they're doing things like they have the security stuff and things of that nature and they have like the production readiness checklist and they're bringing in more of the product and project management and the architectural aspects that often is kind of missing in open source projects. You know they don't typically always have a role
12:41
for that and they're bringing that in. So for example this is one of the things that the TAG created and so it's like community suggests a tool. They have a community checklist where they go through and go what does this open source project actually look like if we're gonna adopt it? Is it viable? Is it actually open source? You know how is their community doing? Are they bug
13:01
fixing? Where is all that at? How does it look in regards to other open source tools that have similar functionality? Things of that nature. Then they have a community notification and then we do a proof of concept install because as we know all open source projects are completely accurate about the features that they have and how well they're working. And so the community then goes and like throws stones at it and hits it
13:23
with sticks and then comes back and says whether or not they approve it. And then we go through an open approval process and we do an architectural review and pricing and then we submit it to IEEE where it then goes through a bunch of IEEE processes as well involving the board of governors too.
13:40
And as well legal and things of that nature so we go through and like make sure everything's copacetic. And so that's the area where you go in and do that. And then we do a lot of integrations back and forth and so for example the education group got together did an evaluation of the platform and then went to the TAG and said hey we did an evaluation this was
14:01
good this wasn't this is what we would like to have dah dah dah dah dah and then also gave feedback on their evaluation process too. So one of the things that we talk about is going 100 percent open source and what that means is you know three different directions. So not only are we using open source tools like GitLab CE and
14:22
Mattermost and BigBlueButton and things of that nature but we're also open sourcing the platform itself for the containerization and on all of those other different integrations together. And then we're also allowing other entities to use our platform as well. We've actually already done one version of that now where we've set that up for
14:44
another nonprofit sorry another coalition and then across streams. So if they want new features we can go back and forth across the different platforms so that the platforms can stay integrated as well. So right now we're just doing Mattermost GitLab and BigBlueButton.
15:02
Some of the tools that we're evaluating we actually have already done plate UML. And so we're looking at the other different ones and that's what the community's looking at. And it's really important because we have to support that community and as I was saying earlier with role diversity the whole reason we're 100
15:21
percent open source is so that we can do role diversity. We can change those tools. We can make them better. We can integrate in the ones that they want. We can go through and do all of that. And that way the community can also change themselves. So we want it to be you know this is the dream. IEEE is known for doing this certain level of quality and
15:44
it might take us a while but this is where we're going. So what are we doing right now? Well one we've got the standard that I was talking about which where they're talking about best practices on open source governance. And so they're going through each of those different pieces. Some of y'all have actually been on that call that are in the room.
16:03
We're also working this year on a code-a-thon in a box. We already have workshop in a box. But we're taking that out to student services at IEEE so that any university group who wants to come in and start doing code-a-thons on our platform can do so and be supported. We're evolving the platform for and by the volunteers so
16:20
that just keeps progressing. As you saw we have the different tools coming through. And then also doing technical support for some of those different diverse roles. So best practices. This is where you'll want to go in regards to the standard that's happening. It's first right now where there's a whole process for doing standards, okay? First you have a study group and you create a par and
16:40
then you submit the par and then you go through the entire par approval process. And that's how you actually get to a standard. One of the things that's interesting about IEEE is we are doing what's called an individual based standard, not an entity. Which means you bring yourself not a corporate perspective
17:01
in regards to it so that we don't have corporate dominance. And one of the things that we look for on a lot of this is making sure that it's not just one company coming in and dominating it saying this is what it's going to be. Instead, if you look at who all has been attending these, it's all over the place. It's a lot of foundations, it's a lot of non-profits, it's a lot of academics and academic institutions.
17:22
And then we've got a bunch of public sector that's also been showing up too. And then we're open sourcing it. And so the two new tools that we do, we have a thing called Open Up, which is where we're slowly putting all the open source code to open up the platform itself. It's been a little bit slow going on the infrastructure's code because that's
17:42
not always easy to make clean, but that's one of the things that we're working on. And then also we've done a scalable containerized big blue button so that you can do a lot of different pieces. We have a lot of stuff that's happening in regards to the roles, where we're implementing a lot of processes to integrate better in regards to the IEEE's governance structures for
18:03
each of our advisory boards where they report into the Strategic Management and Delivery Committee as well as the Board of Governors. And we've also got the IEEE Foundation Fund that's called SA Open. And that is where we're looking at for platform development and expansion.
18:23
I said that we had one entity that already did an implementation of our open source platform that was funded through the fund. We had a foundation donate into the fund, and then we took out of it and created that for them. And so the cool thing about that is it was painful, but all the paperwork is ready now.
18:41
So now we actually have a better process for how we're going to be bringing in the money for doing those kind of things. And sending it back out again. We're also looking at doing that for additional resources too. So say you have a group that comes forward and they need a security audit. Or they need help with marketing. Or they need help with things of that nature.
19:00
We're figuring out what the governance process for that is going to be for giving them money out of the foundation. So where do we go next? Well, more platform expansion. We're just barely scraping the top right there. Of course, there's a big thing at IEEE in regards to open hardware, because that's what we're more known for than open source software, obviously.
19:23
So doing some different adaptions for that. Because I think we already know that GitHub's not going to do that for us. So we need to get in there and do that. Same for open data. And then also doing some best practices in open data metrics. So that we can get to those numbers that we were talking about.
19:40
And so if you want to join us, here's all the links. I'll be sharing the slides on Twitter. And thank you. Questions? So are there any questions from the audience? Critiques?
20:01
Neither. Things you see missing? Things you think are impossible and want to know if it's really going to happen? It doesn't seem to be the case. I was trying to let them be controversial. No. Yeah, yeah, okay.
20:24
So you spoke about how creating pull requests is not easy for a few folks who are contributing in some different way. And I had that in my previous work where I was struggling to, I did a workshop with them to explain, hey, this is how you do a pull request.
20:41
And they're contributing to documentation. Are you, like in any of your projects, are you at, or I think this is something people are working on. Maybe I just don't know about it. But are people working on easier ways people could submit these pull requests without doing the whole procedure?
21:02
Are there ways to help non-technical folks, if I may put it that way, to help contribute to this? So one of the things that we're looking at is a bunch of different tools. And so that's what the education group went in and did, that subgroup. They went in and they sat there, and they're the reason we're evaluating Next Cloud and Collabora.
21:21
Is because they're like, we can't stand doing our documentation in GitLab. And I don't blame them one bit, cuz I can't stand it either. And of course, we don't want to be using Google Docs for obvious reasons. So they're one of the groups that submitted that and asked for that. We're having some problems with the licensing issues,
21:40
because if it's open core, it's much easier for us. But they are not open core, so we have to figure out what that arrangement is going to be, because IEEE has 420,000 members worldwide. So we have to figure out what that is, but there is some things going on like that. Also, the marketing group has had us looking at, is it Pinpot?
22:04
Because they wanted some additional tools to help with the collaboration of graphics. And so there's a bunch of different open source tools that are out there. And so people are kind of asking for those right now. We did kind of spoil them a little bit with BigBlueButton, because BigBlueButton has that shared notes that's so awesome.
22:21
And so they got really used to collaborating in that, and they're just like, we want this, but for bigger and longer, and not just at the meeting. And so that's why we're looking at some of those other different ones. But no, I haven't found anything great for that in regards to GitLab and making it easier for them. We had that same problem working with Carsten Wade on the Open Source Way 2.0,
22:45
because that was all being done within GitHub, though, right? And it was very painful. It was very painful for our writers, because they were like, I can do documentation, but this is just, aah! And I think that we need to have something more along those lines for
23:04
things like open standards in the future. Because you often have these arguments that occur over and over again about some particular topic. And if you don't have a good way of saving that discussion in a versioning system, you're gonna have those same arguments every year.
23:22
And we would like to circumvent a little bit of that. And it's not always apparent in GitLab when you have those. Plus balloting measures would be nice too.