Logo TIB AV-Portal Logo TIB AV-Portal

Welcome to the FOSS4G Community

Video in TIB AV-Portal: Welcome to the FOSS4G Community

Formal Metadata

Welcome to the FOSS4G Community
Title of Series
Part Number
Number of Parts
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Release Date

Content Metadata

Subject Area
Welcome to the Free and Open Source Software for Geospatial community. Freedom is one of the tools we use to take on the world. This presentation breaks down the principles on which our community built. This welcome presentation is a quick orientation on open source, open data, open standards and open development. Please attend this talk if you are new to the FOSS4G community, or would like some background on how all the fun toys you see on display fit together to form a larger picture. A larger picture we like to call the future.
Keywords Boundless
presentation Meeting/Interview Universal interactive sheaf bits student part
server Open Source load Development projects Open Source similar staff bits clients several words Computer animation Software Board organization Gamma
Meeting/Interview terms code time plan bits part
man unit mud Open Source Binomialkoeffizienten time nuclear share maximal Mass part events open subsets Emulation variance events Software orders law Gamma
choice point standards programming Actions mapping Open Source time mobile collaboratives ones open subsets argument part energy attributes wikis different law physics engine systems web collaboratives regional standards information mapping projects Open Source argument bits Databases several open subsets product events Computer animation Software Hardware Universal life Free
standards states time clients part geospatial technology Zeitumkehr subset wikis information formal systems man web Open Source share argument bits open subsets machine communication system geometric server mapping Open Source files mobile events MACH specific World Wide Web Consortium communication Software level encoding protocols Right web standards information Tiled projects Content Databases sets shape Computer animation Software Hardware speech protocols oracle
web pages constantly focus Computer animation Open Source time Software Open Source applications open subsets equivalence
expression Open Source distribution The list open subsets fit substitutive Software Direct interruptions classes overlay sources services distribution information views projects Open Source theoretical bits bin open subsets inclusion events Computer animation Software Contracts conditions BUS form
implementation Open Source Development distribution time administrations Integrationen sources The list open subsets component-based terms Software Rolling website implementation libraries systems choice server files projects Open Source Java bits applications open subsets Computer animation Software Universal system 5th oracle libraries
email suite Actions necessities decision sources part Arm wikis mechanisms mathematics component-based different Conversation stable icons sources collaboratives services email link decision Development point files Open Source traction The list bits part terms Computing open subsets position management processes orders organization testing procedure Results services Open Source factor files collaboratives copyright infringement Guide 3rd drivers The list Axonometrie product local clustering root Software factor message-based Context management response cone torus key copyright infringement forces projects law code directories component-based Location report Computer animation Software case lies Normierte Räume key
mathematics control processes projects student table Computing information architecture
factor feedback projects schemes bits catalog mathematics alternatives processes Meeting/Interview different structure series physics engine
Computer animation
the thank you very much yes this is
a presentation I often given to like university students and classrooms and boundless is really nice about letting us set interact with academia excellent so I always have a little bit of fun trying to figure out how to introduce this stuff because so much activity going on at the conference like phosphogen and I only get to take part in a small in in my own little section and did so
just a few words about myself my name Jody diet I work with a company called boundless and boundless is about what I would like to think of as 1 of the key players in the Foster G. community we've got developers and staff active in many of the projects will be seeing over the course of the week as as a as a volunteer I work with several open source projects the 1st project I work with his called you tools 1 that's kind of most famous is fuel server and I also work the desktop client called you which with which I quite enjoyed I also volunteer with 2 software organization that I tend to really like working with the developers and fostering the development teams with the or still Foundation I'm not sure of the incubation committee and with the Eclipse Foundation I perform a similar role as chair of the of the technology project which brings in new projects so I'd like just talk
a little bit about Foster G. everyone is here foster can just ask how many people were here at the very 1st phosphor G conference excellent welcome I'm really glad you made and you might think of philosopher
G. in primarily in terms of the party because we really do plan to have a good time this week if you took part in the code sprint or any of the activities base camp and this is really going to be a fun week and possibly
G is typically a little bit of a balanced with just a really
great event and
with all kinds of people from around the world and it's a
conference has been going on for a long time and the very
first one I believe was in 2004 and in Thailand and it's really
turned into like an annual global event that takes place in a different part of the world each year and we use it as a community in order to do outreach in order to help share are open-source culture with everyone around the world the
other thing was happening and especially in Europe is a whole bunch of regional foster G. conferences and so we can get the big international conference which are here that today and then we get a smaller conferences specific to each region but I'm not really here to talk about the conference you're you're here you're can be part of that congratulations I'm going to talk about the falsity community and it is a little bit of a lifestyle choice I kind of have a confession to make i've never personally used commercial GIS software unlike in free and open source software I'm not sure how many other people in the room and say anyone so I have always been here um have seen people like use it as a tool on occasion but I don't think I've ever like know how to learn how to do it there's actually 4 key pillars of that contribute to a community and it's not just about software time-delay explore each 1 of these in a little bit more depth I kind of wish we had done microphones is something in the crowds I could take questions as we go because I'm used to doing this talk in a university setting we'll talk a little bit about Open Data because without data RGS offer is not going to be very useful also be talking about open standards and this is the standards that allow a software to work with each other we will be talking about open source I will be talking specifically about what open source is and will also be talking about 1 of the things that I really like in this community which is open collaboration so what for Open Data as if we don't have data for our software to use it's and it's just not going to go very well for us as how I guess 1 thing it's really fun about our industry is the data that we work with is so much more valuable than the software a lot of the datasets yield use will be of collected in the 19 seventies and the programs and the programmers originally put the datasets together nowhere to be found and and we know that going in so we know that our datasets are far more valuable than our software spatial data is really important it's expensive it's time consuming to collect and this is partly why we're investing so much time and energy into things like our using standard so we can actually reuse and repurpose existing data and the datasets do tend to have very long life span 1 thing that we're particularly cheerful about in this community is the idea of open data and this is actually a very interesting and challenging idea so something to be open data we really want to be freely available to reuse and republish and this can be you know quite a challenging concept without a couple examples of like to go over OpenStreetMap is 1 of the most expensive most famous ones we also have a few other ones which were really central to our industry GeoNames is a less common ones but the EPS PSGs geodetic parameter dataset is actually like the is actually the heart of our industry and this is slightly different from free data so free data is available free of charge of many national national company sigh many countries make their datasets freely available to the public and that's not quite this is the same thing as Open Data for open data we want the public to be able to take part in the party and you contribute to the
so here's the free ones I'm talking about here GeoNames like at an opening point of interest in sense and OpenStreetMap C is a really fun project that think started in the UK and operates a little bit more like a wiki crowdsourcing collecting and feature and attribute data from around the world and the other 1 here is that he PSG dataset so this is I think it originally started as the European petroleum standards group and the petroleum industry got a little bit upset when they had maps from several different vendors use them to navigate the oil rigs and of the wool rigs ran into something and think it was expensive for so they got fed up after a while and they produced a standard database and it was 1 of the original Open Data licenses so they said this database defines the different coordinate reference systems and it allows us to line up information from 2 different data suppliers and make them work together and you can't
just trying to think what else I wanna say about that it is really important and it was a really novel idea for the time this status was made available free to use by any vendor with the restriction that they couldn't charge any additional money for the database contents
that's what I like to talk about is open standards so open standards actually allows us to share information this which the the sharing into our community without the ability to take information from 1 project to 1 community to another and everyone be operating in isolation so open standards is going to work on how we can communicate together this is the specifications of the lab anyone even our open source community here to implement and and and work together and this is the glue that allows so many of our worst your projects to deprive and got a couple of levels that would we have which are open standards come together in the most famous 1 probably in this room here is the International Organization for standard as a share so in our industry we tend to work with the TC 211 standards the other 1 which people might be more familiar with this the world Wide Web Consortium a w 3 c and this really focuses on communication on the Web it's really focuses on protocols for machine-to-machine communication and we've also been wildly successful with our industry standards and so we've got the OGC spatial consortium this is the body that defines a lot of the servers and protocols that you'll see so I work on a project called GeoServer it implements many OGC standards and that allows a desktop client like you just to accept information that's been published and I also mentioned the PSG dataset that was put together by this set ODP community committee another fun 1 and this is something that actually happens on the sparsity of and is the advent of community standards so in the event and was only in 2006 I actually took part in 1 of these birds of a feather sessions where project leads from several teams got together and defined the WMS stick our community standards so this standard exists as a wiki page in the Austria which other community standards G adjacent which describes how to encode geometry into Jason files GeoTiff and tiles there's lots of community standards the other 1 is de-facto standards so there's a lot of on with data being so valuable we do have to realize that a lot of information is locked away in in shapefile Oracle speech solar MapInfo files are open source software needs to be able to unlock and use the state so we do spend some time reverse engineering how to get data out of the system so here is a little bit
of what those look like or something
so they were kind getting to the heart of the party with open source and I really wanna focus on 1 constant refrain from open source it comes down to something very simple if you download the application you can download the source for the applications that is really all it comes down to and 1 thing that's nice about open source is often the open source licenses are far easier to understand than the commercial equivalent so BSD-licensed clocks in 1 page and the iTunes licensed gets longer every time I look at it I just wanna
focus a little bit on the BSD license this as our simplest open source license with 2 classes
and it amounts to a couple things we ask that software maintain the copyright information and we have yeah and that they maintain this disclaimer in the distribution so this is something that that say the overlayers project would make use of open
source licenses are gathered up under the relevance of the Open Source Initiative so they go around and check licenses and make sure that it it meets the fundamental ideas allowing us to share the BSD license is fairly common 1 thing that's kind of funny as you can tell a little bit about software community based on what kind of license they've selected for themselves so often think of BST is like a universal donor community that's accepted the BSD license really wants this to be used in here and near and far well so software has been released under a BSD license can be incorporated in proprietary systems and it can also be incorporated in open source solution another really popular licenses the GPL license so this is arguably the most popular open source license and this 1 is fairly strict it says that any if you do any modifications made to the original application must be provided to those that are running the application this is the 1 used by the use of project they work on and this is especially appropriate for system administrators have been going to be running GeoServer is application they want have full access to the source code so they can see what they have and what they're writing it is also the license used by Oracle and when the distributing the open JDK implementation of John and the lgpl license is a little bit more business-friendly so this allows to hold that has been written in in in lgpl projects such as steel tools to be used both in proprietary and also in strictly open source solutions and this is a really I suppose this is 1 of the reasons why do tools and went with this license is it was the most fashionable business-friendly license at the time and we really wanted this library to be used by as many people as possible the
different licenses don't necessarily work together so as I said the BSD license can be used by pretty much anyone with some of the license terms are incompatible so when you do it on your are assembling your own project using open source components you should take some care to review the licenses and making sure that you're actually in a situation where you can produce and publish and use the resulting application I can
and there are some services to help you choose a license and choose a license . com is a really nice 1 provides nice little click-through and question and answer kind
so 1 thing I'd like to keep in mind here is that the open source license only describes how the softer is published and distributed is another question entirely how the softer was obtained and that's kind of a question of government and its so they can be a little bit tricky that as chair of the open source committee this is 1 of the main things we help projects were actually tracking down where they got the source code from which brings me open collaboration so as it will in our community is not good enough for a project to strictly be open source we want to make sure that everybody in this room and can actually take part in our history projects and for the this prevents the idea of vendor lock-in and so if you are you are working with a product that is perhaps released as open source but all of the developers are owned by 1 company you're in trouble with that company decides to pivot didn't change what projects it's working on you still have a copy of the source code and you can hire new developers to work on it for you but you don't necessarily have the stability that you like it if you were able to join the project more formally and take part in the decision making process so this is all about managing risks when you're dropping a new software component is actually really well under stood risks for like procurement we're making approaches the open source software helps mitigate some ideas like the vendor lock-in but it does expose you to other risks such as the license incompatibility so managing this kind of stuff is really the responsibility of the project team project leadership but that said if you're just getting into open source you might actually end up performing in order of the projects he started to make use of and or you might look to a software foundation that can perform and not on your behalf OK so the key features were looking for here with open governance is we really want the and that some of the software development to be transparent and inclusive we really want to see the decision making process being done publicly on a wiki on a mailing list rather than beside behind closed doors or even at the pump over the years and this is 1 of the key success factors that we're looking for and so produce over the way we handle this is we have a public issue tracker so anyone can sign up and report new issues you can also review the issues that are being worked on and volunteering take part of you when you wish you can at least see what is happening we also use a public e-mail astrologer that development and conversations and then we do have a non-public Developer's Guide which shows all the procedures we followed including how to make a release indeed for GeoServer if you need an older release you can actually raise your hand on the developed Western volunteer and follow a procedure and make a new official release of Jews can so 1 of the things that happens as a result projects is going through an open source review and so this involves going through all the source code and and and just double-checking that all the all the licenses have been applied correctly this lecture be really difficult so as failure to check that the software the software can obtain correctly that can be quite devastating so yeah each open source file includes a little bit of a header that says case made this file what license it's being made available on GitHub you can often check that actions that contributed guidelines others a contributing and the file at the root of the directory and some projects are willing to accept that work from you without any sanity check other projects will actually ask you to sign something like a should license agreement before they're willing to work with you FIL you don't like something mechanical but it can be very fairly easy to mess up and yeah so this can happen where the project team is best this up the product might end up being pulled from the market so when general tools is going through incubation we actually found we accidentally included a JDBC driver or necessary driver which Interpol prior releases of our project until we could fix the problem another really common mistake is an employee of like the municipality providing a fixed to the project and the project merging it again and then it turns out hold on a 2nd that person is actually employed he made their managers permission to accept that fixed because they're not operating as an individual that there are operating as a member of the organization check the other thing I'd like to just take a brief mention of this is that the difference between a software foundations such as Austria or location text and such as force for to get up so Software Foundation's really stress vendor-neutral governance allowing different companies and organizations and volunteers to work together and they can also offer have strong legal protection for the project and its users the most kind of common law suits we protect against copyright and patent infringements and so on such as the end of 1 was mentioning earlier and a software for and the other hand like a house is really just focused on hosting source come and so they don't operate as a Software Foundation they make their money not by selling software or supporting software but by selling services to their corporate customers so we can have a i take part of the couple Software Foundation's the Open Source Geospatial Foundation and empowering everyone with open source geospatial also location text which is a working group of the Eclipse Foundation so I'd like to welcome everyone with to foster G and I hope everyone has a great week at any questions yeah
that how do we manage the
architecture the so the question was how do we manage the architecture of say for example GeoServer yeah so GeoServer structured with Project Steering Committee and we did start with an original project and my graduate student back in like 2003 but we have made a couple of very serious architectural changes and we did so using of public proposal process so it and if you ever done like change control in government or a big company we've stolen all that language to make people feel comfortable but really the idea is to get the potential idea on the table
and get everyone to agree to it before we go ahead with the architectural change and so on I think the difference between GeoServer 1 to of was a really big architectural change the factor and that was done as a proposals and by just saying hey I wanted to take the dual tools for for the use project and change from using structure to using spring and introduce a really strong catalog API and so that was done as a series of proposals linearly process but it depends on the key so that your 17 and can do a proposal very quickly and they haven't done so recently and the GeoTools scheme has a little bit of a different process so they also do proposals but they do a timebox on so if you do a proposal you have to wait 2 or 3 days of feedback and many people haven't gotten back to you you can start in on proposed 1 thing that's very both of these the project governments structure is that you can't just veto the proposal and say no net of negative 1 Vito is fine but you have to give the person an alternative idea because often they're working for a customer or a deadline and so we try to be sensitive to In the other questions thank you very much and enjoy the week