OSGeo and LocationTech Comparison
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 | 183 | |
| Author | ||
| License | CC Attribution - NonCommercial - ShareAlike 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 and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this | |
| Identifiers | 10.5446/32102 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language | ||
| Producer | ||
| Production Year | 2015 | |
| Production Place | Seoul, South Korea |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Presentation of a groupGroup actionSoftwareUniform resource locatorFamilyXMLComputer animation
00:57
Template (C++)Slide ruleCartesian coordinate systemBitOpen sourceMixed realityGroup actionCategory of beingSoftware developerMereologyOpen setCodeNumberTerm (mathematics)Shape (magazine)Task (computing)InternetworkingDifferent (Kate Ryan album)WritingMultiplication signProjective planeExistential quantificationCollaborationismSoftwareOnline helpElectronic mailing listDatabaseRevision control1 (number)Queue (abstract data type)AdditionArchaeological field surveyRange (statistics)Position operatorProcess (computing)Game theoryShooting methodGreatest elementEvent horizonMultitier architectureElement (mathematics)Library (computing)Subject indexingData structureSpacetimePoint cloudSimilarity (geometry)Uniform resource locatorCellular automatonState of matterNormal (geometry)Internet der DingeShared memoryStaff (military)TrailLevel (video gaming)MomentumAutomatic differentiationScripting languageLine (geometry)Suite (music)MetreRight angleCurveType theoryServer (computing)Goodness of fitComputer animation
08:16
Term (mathematics)Projective planeRange (statistics)Open sourceSampling (statistics)Response time (technology)MassSeries (mathematics)MereologyElectronic mailing listArchaeological field surveyGoodness of fitProcess (computing)Decision theoryWhiteboardLocal ringSoftwareEvent horizonWikiSign (mathematics)Open setCollaborationismSoftware developerPoint (geometry)Right anglePattern recognitionBitAreaTelecommunicationOnline helpMultiplication signPeer-to-peerCodePoint cloudUniform resource locatorPersonal digital assistantSoftware bugScheduling (computing)GeometrySupersonic speedWeightInequality (mathematics)Computer-assisted translationBuildingLevel (video gaming)Figurate numberComputer animation
16:25
SoftwareGeometryOpen sourceRevision controlSource codeDigital rights managementSoftware developerMereologyEmailProjective planeSet (mathematics)WhiteboardTerm (mathematics)Uniform resource locatorCodeDecision theoryLimit (category theory)Computer fileProcess (computing)NumberDatabaseCASE <Informatik>Order (biology)Distribution (mathematics)Line (geometry)Moment (mathematics)WritingSoftware testingInternetworkingFlagLink (knot theory)Repository (publishing)ResultantBitBus (computing)PlanningSpacetimeLibrary (computing)Vector spaceMathematicsComputer configurationJava appletLogic gateSlide rulePoint cloudBeta functionComputer virusOnline helpGroup actionServer (computing)IntegerCartesian coordinate systemMultiplication signWebsiteSampling (statistics)Observational studyMedical imagingChemical equationDescriptive statisticsCryptographyStandard deviationLevel (video gaming)Conjugacy classTelecommunicationConfidence intervalOracleDevice driverEndliche ModelltheorieWordNatural numberComputer animation
24:30
CodeMultiplication signUniform resource locatorSoftwareSource codeBit rateMereologyGoodness of fitProjective planeOpen sourceSoftware developerWeb-DesignerAreaPresentation of a groupProcess (computing)Bound stateRevision controlComputer fileRepository (publishing)Online helpType theoryGeometryBitCASE <Informatik>Free variables and bound variablesFlow separationLevel (video gaming)Server (computing)Perspective (visual)Direction (geometry)Descriptive statisticsSet (mathematics)ACIDCarnot-GruppeConcentricState of matterBridging (networking)TupleShared memoryLogic synthesisInsertion lossFigurate numberHuman migrationWeightComputer animation
31:01
Computer animation
Transcript: English(auto-generated)
00:05
So that was my introduction, that was really quick. Hi again, it's been a long week. This is like the last presentation that I have to attend. I don't know about you guys. Actually, I guess there's like a keynote or something. Doesn't count, okay, well that's great.
00:22
How many people have heard of OSGO? Hooray, how many people enjoy OSGO software? Hooray, I enjoy a few of the packages, so I'll stick up more things. How many people have heard of LocationTech? Well this is way better than last year. How many people have heard of like Eclipse Foundation
00:41
or any of that kind of stuff? A few people. Okay, what I'm gonna be doing is I'm gonna be comparing two software foundations, OSGO and LocationTech, which is like the working group for the Eclipse Foundation. I'm gonna go fairly quick because it's been a long week. And here I've got two slide templates.
01:01
OSGO, LocationTech, OSGO, LocationTech. Okay, that was fun. I'm Jody, hi again. I actually work with both software foundations. On the Eclipse Foundation, I'm on the little steering committee for LocationTech. That's actually like a position you're elected into,
01:21
so it's quite an honor. Thank you for the members for accepting me in their midst. And for OSGO, I kind of heard new projects. I'm chair of the incubation committee. And what both of these things have in common is I really hate projects being embarrassing in public. Open source is a tough game to get into,
01:42
and it's really easy to like shoot off your foot. And I'm really fond of software foundations for helping developers get the job done. In terms of my employer, hi boundless. We actually work with both software foundations. Our key software product, Open GeoSuite, is actually made up primarily of OSGO projects.
02:04
OpenLayers, QGIS, GeoWebCache, GeoServer and PostGIS all fall under the OSGO banner. Now GeoWebCache is the odd one out. It's not a full project. It's kind of lurking in the OSGO lab space. And then we also have a number of projects that are taking shape under LocationTech.
02:23
GeoGig is probably our most famous one. It's like the Git workflow but with features rather than little lines of text. GeoScript and we also are starting to package up GeoMesa as part of Open GeoSuite. In terms of LocationTech, LocationTech is a working group
02:41
so the Eclipse Foundation is one of these big software foundations like Apache or the Linux Foundation. And they're starting to branch out into other industries like aerospace and so forth. And when they are branching out into our industry, it's the LocationTech working group. So just to back up a sec, this is a not-for-profit
03:03
foundation, it's member supported. And yeah, that's kind of where they're coming from. They do have a number of different working groups, aerospace, internet of things, scientists. One thing that's kind of fun here is they've got a long-term support working group. So people that are wanting to write software
03:21
that's gonna be able to run in 20 years time. They are a full-service foundation, so they offer help managing your project in terms of governance. They've got access to legal staff if you've got any IP questions. And they've also documented how you can run a project in terms of nominating committers and all that good stuff.
03:42
In terms of LocationTech, they count their members as companies or organizations. And you can see a range of companies here from Boundless and Google and IBM. Some new additions recently are Radiant Blue and Planet Labs and Ordnance Survey. And then we also have a number of groups
04:00
along the bottom that are guests. So we've got University of Calgary, we've got OSGIO. So these two foundations do work together. In terms of how membership works, they have different pricing tiers. So strategic members get a spot on the steering committee, for example. Participant members and committers and guests
04:21
has a different breakdown here. In terms of the structure of the LocationTech projects, they kind of fall into three categories here. Libraries, such as JTS, which you might have heard of. Spatial Lib Index is a new joint project that started out this year. SF Curve, and we'll also be welcoming Torc.
04:42
We're expecting their application any day now. Then we've also got a couple of applications. These are things that normal users would download and run. And we've got a number of processing. This is primarily off in the cloud space, so projects like GeoGenie and GeoMason.
05:01
LocationTech is doing a great job of public outreach, helping take spatial technologies out into the wider community. One thing that I'd like to highlight is the LocationTech tour. It's a similar size event to Phosphogy, but rather than being in one location, it takes place as a tour.
05:21
So it takes developers around to different cities. And it helps reach a different category of developers than who we have here today. So rather than preaching to the converted that have already heard about all the open source stuff we do, we actually get a lot closer to normal GIS shops. So it's a good mix.
05:41
It also has easy collaboration with other groups like OGC and OS Geo, and a lot of joint events. So just in terms of LocationTech, I'm afraid you can't see that map. The tour has gone from six cities at the start to 13 cities this year, picking up some momentum. Things that are really good about LocationTech,
06:01
the Eclipse staff, have been very helpful. This is particularly helpful for teams that are new to how open source works. And they've also been taking a lot of the thankless tasks like doing trademark checks and all this intellectual property stuff that I can't expect volunteers to do. Special thanks to Andrew, Sharon, and Mike
06:21
for helping us out. I do have a couple of cautions for people that are considering joining LocationTech. LocationTech is kind of new to the Eclipse Foundation. We don't really know how all this stuff works. So they've got like a portal. They've got some code hosting facilities, but we are all chickening out
06:41
and having our code on GitHub instead. So they've been helpful in that regard. Also, the incubation process for LocationTech is a lot of work. Even though there's an IP team to do a lot of the heavy lifting, you still have to go around and give them a copy of your code and tell them all the different bits of open source software you're using
07:01
so they can make sure it is actually open source. One thing that's really nice, it's a chance for us to introduce the Eclipse community to all the great spatial software that you guys know and love. I suppose another caution is they're not familiar with our GS industry. So we actually had to go through a lot of hassle
07:22
to get something as simple as the EPSG database approved because the EPSG database dates from like the 70s or something, and it is one of the original open data licenses, but because it's from the 70s, it wasn't on their list. The other thing is with so many new projects
07:41
all starting up at the same time, we're trying to streamline the process by getting people to depend on the same version of JTS, for example, and we've had to form the projects into a queue just because we're burying the IP team in new technologies. That said, it's taking so long that often we're like having releases of our software
08:01
and updating the versions before the previous ones are approved. So we're in a little bit of a catch-22 there. And you also should take care to plan for if something's rejected, that to replace or rewrite it. In terms of OSGEO. Hi, OSGEO.
08:20
OSGEO has a really nice mission. So it's to support the collaborative development of open source geospatial software and promote widespread use. It is nonprofit. It's vendor neutral. It's very international in flavor. I kind of don't have to say that since we're in Korea. It's also really nice that it's got an open education
08:41
and an open data outreach, and this is just really heartening to see. In terms of how it works, we've got a board of nine individuals. Any board members here? Okay, point and laugh. Charter members, we've got 280 individuals, I think.
09:00
We nominate more yearly. Who is a charter member here? Thank you for making OSGEO great. Now, it is a volunteer organization. Everyone is welcome. The only thing you have to do to take part in OSGEO is sign up to the discuss list, say hi, attend a local event.
09:21
You can put your name on a wiki if you really want to be listed somewhere. We really are driven by you rocking up and having a good time. In terms of OSGEO supporting software projects, there's a few things that we do offer as spatial projects. We are a community of your peers. We do understand what GPS codes are.
09:43
We can understand about Ivan and all commiserate about point cloud man. We also do offer some assistance to new projects in terms of marketing and outreach. There's the OSGEO live DVD which showcases a range of technologies, and we do have the incubation process to help
10:01
if you have any questions about how to run your project in an open and responsible manner. How OSGEO protects you? So we do offer limited protection. So the incubation process gives you an opportunity to review your code and assure your users that it is actually open source. And also, OSGEO also has a healthy body of prior art.
10:23
With projects like GRAS being 30 years old, if the lawyers come calling, we can probably point to prior art. This is, however, an area where we collaborate with other foundations. So we'll go and talk to the Linux Foundation if we need some help on licenses. We are not a strict IP team,
10:41
but we can help make the connections and see that you are protected and have a good time. We do have spatial expertise. So if you are a developer and you're trying to understand what all this stuff is, you can talk to other members of the community and get concepts explained in terms that make sense.
11:03
The other good thing about OSGEO is participation is free. Write board, you're not charging member fees yet. Just sign up to an email list and take part. That said, the foundation is sponsored. We'd like to thank a few of our sponsors like Ordnance Survey.
11:21
Anyone for Ordnance Survey here? GeoCat, anyone from GeoCat here? Thank you. Camp2Camp, Boundless, anyone from Boundless here? Oh wait, me. Oh no, Boundless isn't on there, it's Borealis. Hey, Boundless, why aren't you sponsoring? I'm up here being embarrassed.
11:40
Okay, excellent public outreach. Yes, so we are very, yeah, any spatial project is welcome. OSGEO Live has a range of spatial technologies. We're very easy to collaborate. We collaborate with the OGC, LocationTech and others.
12:01
We also have a massive series of worldwide events. This is just a little sample of what's been happening worldwide. Belgium to Italy to Korea to Spain to Portugal, Finland, all kinds of stuff, India. We really do have a global reach and we are wanting to take on more of the world.
12:21
The other nice thing about our outreach is Phosphor-G. Yay, okay. And just in terms of community building, OSGEO happens at the international level, like you see today, but the real heart of it is the local chapters. Kind of getting too numerous to mention. Who here is in a local chapter?
12:41
Lots of people, hooray, okay, good. One thing that's nice is OSGEO is flexible and responsive to project needs. There was no hassle when projects migrated from SBN to GitHub, for example. And also, a lot of the decision making happens in public and transparently.
13:00
That's kind of both good and bad if you follow the board list. There is one caution about the OSGEO, which is kind of an interesting double-edged sword here. OSGEO is so helpful to new projects, there's not actually much reason for projects to join OSGEO. Projects entering incubation get
13:20
a really good brand recognition boost. Right Zoo Project or PiWPS Project, but they have no incentive to finish. I don't know what to do about that. I'm on the incubation committee and these projects are like hanging out for years. The other thing is that public communication is not suitable for all occasions.
13:41
Occasionally, there's a trademark issue. We can't talk about it in public and we don't have a lot of avenues for communication out of the public eye. So when we do run into tricky questions, it can be a little bit of a hassle with the OSGEO to even figure out how to talk about them.
14:00
The other kind of trouble is OSGEO's really good for established open source projects, but we are not very good at incubating new projects and helping teach them how to do open source. This is an area where we like to collaborate with others, but we don't have any kind of great strength there ourselves. The other kind of sad thing is we've got projects
14:20
waiting literally for years to get in and the only thing that's required for a project to get into OSGEO is one of you in the audience to say, hey, I will act as a mentor. I will be the welcome wagon and hang out on their email list and say hi. So this is just an area where we really could use more volunteer participation.
14:42
So just in terms of incubation comparison, OSGEO is really straightforward. Literally you make a ticket on a bug tracker. We're interested in kind of things like the name of your project, what license it is, so we can check it's open source. Any copyright, maybe it's just done by everyone who's committed to your GitHub.
15:02
Maybe the copyright belongs to an organization. Like to know how many users. Unfortunately right now we're looking at like a one to six year response time. I do have an update. PyWPS got in this year after waiting 60 years, so that's good, yay. In terms of incubation, sorry, location tech,
15:25
the proposal process is once again straightforward. You get to write down the name of your project and the background and the scope and the license and all that kind of stuff. One thing that's kind of interesting is they'd like to know your project schedule in terms of when you plan to make a release,
15:42
and they do do a trademark check. One thing that can happen to open source projects is that a project can be released as open source, but the name can be trademarked by a company. And so if someone makes a fork at the project, they might not necessarily have permission
16:00
to use the same name. And one thing that's nice about location tech is you do get a quick response time there. In terms of OSGO incubation, any open source license will do, we're not picky. We do require that the community be active and healthy. So if it's like someone hanging out in their basement and their main user is their cat,
16:22
they're probably not gonna be successful with incubating from OSGO. We ask that the development team perform just a check of their source code to make sure all the headers are there to make sure it actually is open source. And we do ask that you list all the dependencies, all the software you use to make your project,
16:41
and copyright holders, all that kind of stuff. One thing that's interesting is we're really focused on the fact that your project should be open. It's not good if your project is, you know, run by a benevolent dictator, I think is the model, or if all the people on the project are employed by one company. We really wanna see some diversity
17:02
because we wanna protect our users from making use of a project and then having a company go under and they're left high and dry. So we do have this governance requirement that is occasionally a little bit tricky. We want decisions to be made in public. So just here's an example of the Pi CSW review.
17:22
And you can see they've gone through, they've checked their source code, and that kind of stuff. In terms of location tech, they've got a limited number of licenses they support, and that kind of jives with their commercial band, so MIT, BSD, Apache, the so-called permissive open source licenses.
17:40
They do do a trademark check. Unfortunately, they pay for that, so that's not too bad. And one thing that's nice here is you don't have to check your source code. They've got a team that will do that. The downside is they're also gonna check the source code of all the other software you use, which in the case of my projects can be an awful lot, because I'm lazy and I don't like to write things for myself.
18:02
They, trying to think of anything else fun here? They have been gradually adjusting their process in terms of using GitHub and external issue trackers. Previously, they'd been using things like CVS and Bugzilla, which all people shun for good reason. The other thing they do is they have some governance requirements,
18:20
clear line of communication, but it's standardized across projects. So while in OSG, we don't care how you run your project, just as long as it's transparent. In location tech, they have a little form that automates adding a new committer. Here's kind of like what an IP submission ticket looks like, the name, the version, the description,
18:42
a few little flags like cryptography, links to the website, the license. One thing that's important here is contributor agreements. Often open source projects get in trouble by accepting code from someone on the internet that didn't have permission to release it as open source.
19:01
And being a software group, the result is an issue tracker ticket. Okay, so just a couple examples. UDIG entered location tech incubation in 2013 and completed its creation review. And we've migrated our GitHub repository over in February 2015.
19:22
And our incubation process is ongoing. We've submitted about 60 little dependencies out of 172. I'm kind of hanging out at the back of the bus waiting for other people to do the work. We are enthusiastic about location tech. We are an Eclipse RCP project, so we better be.
19:42
We also started a little bit early before location tech had really figured out which way was up. We've gotten stuck on like three key issues. Our vector math library was not actually open source. That's been replaced in GeoTools 14, which is due out next week. We also got stuck on the EPSG database.
20:01
They didn't know what to make of it. And our last one is Java advanced imaging. It also isn't strictly open source. So we're gonna be having to look at options for replacing or asking users to install that. Another project is GeoMesa. They're kind of a cumulobased cloud data solution that plugs into GeoServer.
20:22
Yeah, so they got their initial check-in in 2014. They've submitted almost all their IP tickets, and they're kind of just waiting to clean up their code base a little bit and graduate. So they'll probably be the first project out of the gate. One of the projects at Boundless is GeoGeek. Looks like my slides are wrong for this.
20:42
I will quickly skip this. For GeoGeek, we have submitted all of our dependencies, and we've had a few rejections. So right now we're having to rework the project to not depend on Berkeley DB. And we're choosing between something called MapDB and spatial, sorry, SQLite.
21:04
So we'll see how that works out. I expect a beta release shortly. GeoGeek, we had the same few glitches. We ran into that Vecma thing. And we also had to do a name change. The trademark holder for Git asked us to change the name
21:20
since we weren't technically using the Git technology. We were using the Git workflow. So we're ready, we're feature complete, we're just kind of stuck in review. OS Geo incubation, GeoTools started in 2006. We had a couple runs at trying to incubate. The big thing for us was we found that all of our headers
21:43
had assigned copyright to the GeoTools project management committee. There's a really sad part about that. The committee didn't exist. It wasn't a legal entity. So we actually had to talk to the OS Geo board and set up assigning copyright to OS Geo. And we actually had to hunt down years and years
22:02
of committers and make sure that they were happy giving their code to OS Geo. Now we graduated with like 13 known issues, which is better than not knowing what issues are there. OS Geo doesn't ask that you fix all the IP problems, only that you know them so that any potential users
22:21
can know what they're up against. One thing that happened to us is we had accidentally included some Rcast-E jars. This caused us to pull all previous releases of GeoTools, just conflict of distribution terms. By the same token, we had to remove an Oracle JDBC driver.
22:41
And we had to work a little bit and get a special permission letter from the EPSG database guys in order to release that. Yeah. The other thing that hit us a lot is we often had test data and we had no idea where it came from. In terms of GeoServer, GeoServer entered incubation
23:02
in 2009 at the bequest of one of my customers. And the moment it entered incubation, they lost all interest in helping, getting it over the line. So I did the only thing I knew how to do as an open source leader. I drafted a code sprint in Australia.
23:21
And I had an army of like 30 volunteers, some of which were non-coders. And we all marched through GitHub header files together. And over the course of like a day and a half, we reviewed the code base. We entered in a number of issues, and all the IP issues we found were kind of fixed
23:41
two weeks later. So it was a case of a project sitting in incubation for years, does that sound familiar? And then sitting down and doing the work and having it done a couple weeks later. So yeah, initial interest was driven by marketing, but there was no money to follow up once we joined OSGO.
24:01
And it's hard to justify your participation in this kind of thing to your employer. We conscripted a work party of Phosphor G AU volunteers at a code sprint much like tomorrow. And yeah, we graduated thereafter. I'll skip over that.
24:21
Few more applications, this is out of date. So what's the plan going forward? We've got two software foundations working in this space. And here is a crew at the code sprint in Philadelphia. It was a lot colder than here. And we've got members from both OSGO and LocationTech
24:41
hacking cheerfully together, and yeah, good times. Both foundations share a similar mandate to promote open source spatial technologies. And the organizations complement each other. OSGO is really amazing with its worldwide reach. And LocationTech is really good
25:01
at helping people onboard open source. Both, and the other fun thing is projects can quite happily belong to both. There is lots of work to do. I don't really mind which foundation you join, but just please don't go it alone. There are organizations out there to help you.
25:20
If you want to contact OSGO Incubation, it's on the website, be happy to hear from you. And if you want to contact LocationTech, they would once again be happy to hear from you. Any questions? Thanks guys, this is the last talk. You can all fall asleep now. Except for that guy in the back who's already asleep.
25:49
Hey! Your mic is off. Still off? I have one question for you, Jody. How much money do we have to expense to be incubated in OSGO?
26:02
Good question, I'd have to look or talk to Andrew Ross or something. No, no, in OSGO, how many money do we have to put in to incubate? Money, you don't have to put anything. OSGO is free for participation. And what about LocationTech? I'd have to go and check, but the rates to be a member of LocationTech
26:23
depend on the size of your organization. Now the interesting part is, as a committer, you don't have to pay anything. UDIG has joined LocationTech, and I'm a individual committer on the LocationTech project, and I'm just benefiting, so.
26:42
No cost, depending on what you want to do. Oh look, we've got our placeholder guy again. We have to nominate- I'll just go away now. No, no, we have to nominate you for the most outstanding speaker, because you spoke it in every talk.
27:01
There was the most innovative developer award we have to make, something like Most Question Asker or something like this. My question is, I have an open source project. I'm basically the lead developer. I get pull requests time after time from people who help somewhat with the project,
27:21
but when I'm asked if I'm the only developer, well, that's pretty bad. That's in a spatial area. Are there any chances for me to go to OSGO incubation, or should I just skip it and do my thing alone? So there is a chance. The thing is, we've got a little staging area called OSGO Lab, and it is for smaller projects
27:44
that are just starting out, and its job is to start off small projects and help foster new open source. Okay, thanks. Now, the other thing is, you mentioned getting random GitHub pull requests. Please, please type this little file
28:02
in your GitHub repository called contributing.txt. It shows up when people go to give you a commit request, and you can have a little blurb in there and says, yeah, I'm giving you some source code. Cool. And it'll just kind of, you know, it'll save your ass a bit legally in case their employer comes after them.
28:21
So just handy user tip. Don't screw up with GitHub. Hello again. Hi, I would like to answer this question as well. Don't confuse OSGO Labs with a geo lab. Actually, geo for all movement, which have their laboratories right now
28:41
spread around the world as well. This is a little bit confusing. But as Juri said, there is this, so to say, sub incubation of OSGO called Labs, where you kind of identify yourself with OSGO organization. PyWPS was long time in Labs as well.
29:02
And I would like to invite all of you here who is interested in the topic to refine the incubation project of OSGO because now there is like one big step. This is one of the reasons why it takes so long, actually, to incubate, to pass the incubation several years for some projects, of course. And I believe if we make like five steps,
29:24
if you refine a project, it will be much easier for small projects, like for example PyWPS to join in. And what is missing right now? Incubation, one of the many things. You're not rechecking regularly whether your project,
29:40
whether, for example, geo tools or geo server still fits into the OSGO, whether there is still some community, and so on, this is missing from my perspective. Yeah, we certainly have lots of work we can do to help projects. And I'd like to thank everyone on the incubation committee for offering that help.
30:01
Why location tech support only for license? I think it just has to do with the direction they've taken as a software foundation. The licenses they support are all called permissive open source licenses. So often they operate without commercial restrictions.
30:21
People have a habit of asking questions and then walking away. It makes me sad. It's okay. I'm not on the Eclipse Foundation, so I don't know exactly why. They have chosen those specific licenses. But I do know that when we run out of the bounds of those licenses, we are able to ask
30:40
for the occasional exemption. They've also been very helpful in explaining license conflicts and so on to the member projects. Thank you for your presentation and answering the questions. It's time to close this session. It's a great honor for me to be here. Thank you.