OSGeo Incubation
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 188 | |
| Autor | ||
| Lizenz | CC-Namensnennung 3.0 Deutschland: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen. | |
| Identifikatoren | 10.5446/31658 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache | ||
| Produzent | ||
| Produktionsjahr | 2014 | |
| Produktionsort | Portland, Oregon, United States of America |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
| |
| Schlagwörter |
FOSS4G 2014 Portland111 / 188
7
10
14
15
16
23
24
25
28
29
33
37
39
40
43
45
46
48
50
56
64
65
69
72
74
82
89
91
98
102
107
111
114
118
128
131
132
135
138
141
143
147
149
150
157
158
161
164
165
166
173
174
175
179
185
00:00
BitKollaboration <Informatik>ZahlenbereichSpannweite <Stochastik>Lesen <Datenverarbeitung>TermDifferenteEinflussgrößeProjektive EbeneProgrammMereologieCodeSelbst organisierendes SystemOffene MengeKonfiguration <Informatik>GrundraumCodierungExogene VariableOffice-PaketWhiteboardFokalpunktWeg <Topologie>InformationBrennen <Datenverarbeitung>SoftwaretestRechenwerkBus <Informatik>MAPOrdnung <Mathematik>RechenschieberRichtungGruppenoperationWellenpaketURLInhalt <Mathematik>Mailing-ListeElektronische PublikationDatenmissbrauchMapping <Computergraphik>HilfesystemGüte der AnpassungAttributierte GrammatikWellenlehreCASE <Informatik>StichprobenumfangQuellcodeSoftwareE-MailOpen SourceVollständiger VerbandSystemaufrufTelekommunikationRechter WinkelDienst <Informatik>Web SiteHomepageGebäude <Mathematik>EntscheidungstheoriePatch <Software>Keller <Informatik>BenutzerbeteiligungProzess <Informatik>Virtuelle MaschineMultiplikationsoperatorEinsKategorie <Mathematik>FrequenzGrenzschichtablösungComputersicherheitIntegriertes InformationssystemSystemverwaltungVersionsverwaltungChecklisteVerschlingungVerkehrsinformationDesign by ContractVirtualisierungTopologieUnrundheitTaskQuelle <Physik>Quick-SortPeer-to-Peer-NetzStabilitätstheorie <Logik>Reservierungssystem <Warteschlangentheorie>ExpertensystemStandardabweichungTeilbarkeitFlächeninhaltAusnahmebehandlungGefrierenServerSoundverarbeitungOnlinecommunityDreiARM <Computerarchitektur>GRASS <Programm>Computerunterstützte ÜbersetzungKontextbezogenes SystemPunktFreewareDatenbankTouchscreenDigital Rights ManagementPhysikalisches SystemComputerspiel
Transkript: Englisch(automatisch erzeugt)
00:00
Anyone going to wave back? OK. So I'm here to talk about OSGeo incubation. Except that's not really why anyone does OSGeo incubation. We're actually all about making a difference. So this is a little bit of who I am. I'm Jody Garnett. I work with Boundless. I also work for a number of open source foundations, OSGeo.
00:23
And also, I work a little bit with the Eclipse Foundation. This is the too long, didn't read of my talk. OSGeo incubation is kind of the welcome wagon. We're here to welcome new projects into the organization. And we just have a couple things we want to check. We actually want to check that the project is using
00:41
open source, and they know where their code came from and so forth. The other alternate talk for this is how to program in public and not embarrass yourself. So I didn't put that on the program. This is really about public safety. You've got a little bit of responsibility if you're going to program in public.
01:01
We need you to play safe, both for your own sake and for the users of your software. Just a little bit about OSGeo itself. It's an open source foundation. It was founded maybe 2006. Is that about right? Got a few people nodding there.
01:20
It's international. It's got a bit more of an educational focus. And it's got a few tracks on open development, open data as well. In terms of what we offer, if you're a developer, OSGeo is really focusing on, well, if you're lonely, we've got a community of your peers, people who understand you. We do do the occasional code sprint.
01:41
And we're a good source of experience for building community around your project. The other thing we're a little bit less good at is if you're feeling a little bit threatened in a legal context, we can help you review your code base, make sure your code is actual open source.
02:02
We also have a healthy body of prior art. Particularly with some of our projects like GRASS, they go back to the dawn of time and can be used in your defense. That said, we are not a strict intellectual property machine. We actually have serious questions. We'll tag in some of the big groups like Free Software
02:22
Foundation and ask for help. If you're confused, as a developer, all this mapping stuff is pretty darn bizarre. It's good to have contact with other developers who are wrestling with the same concepts like, why is my map sideways?
02:41
Which order do the axes go in? Are you broke? It's important to note that participation in OSGeo is free. The organization is actually funded by sponsors. You can actually just sign up to an email list and get started. Who pays?
03:01
Here's our sponsors today. Thank you guys very much. So to sum up here, if you want to get back to coding, OSGeo can help you if you're lonely, threatened, confused, and it doesn't cost you anything. And it's funded through sponsorship.
03:21
There are a few other organizations getting involved in this area. The Eclipse Foundation has the location tech working group. And the Apache Foundation's also starting to look in this direction as an Apache spatial information system. Do you have to choose? No, you don't. OSGeo is really here to help foster open source mapping.
03:43
If your project's looking at participating with another group, we are here to help. We don't mind who you're working with. So in terms of what the OSGeo brand is offering, for users, the OSGeo brand is given out to projects after
04:02
we've done a little bit of a sanity check. The brand says it's open source. It says there's some documentation. They say it's open for your involvement. The code ownership has been checked a little bit. It might not have been fixed, but it has been checked. And the project has a measure of legal protection. In terms of developers, we can help you build community.
04:22
We do have this incubation process. There's also a wide range of collaboration options with things like OSGeo Live, open data standards, education committees, and so forth. OSGeo really has a mandate to help your project grow. So do come and talk to us.
04:40
And finally, for the foundation, we're here because it's what we do. And we only ask a few things out of projects that participate. We need a project officer to volunteer and talk to the board. Sorry. How about if I point this towards myself? Does that help?
05:02
Testing. I'm just going to look at some of the checklist. So you might have heard that OSGeo incubation involves a project signing up being accepted when we found a mentor for the project. And the major bit of work we do during incubation is work through a checklist. The very first thing we check is that a project is
05:23
open and public. And by open, I mean a couple of things. We need it to have an open source license. There's another group called the Open Source Initiative that keeps track of what licenses are open. We also really focus on it having open communication channels. So email, issue trackers, and so on.
05:40
We want that to be public communication. We don't want users to sign up for a project and then later realize that, oh, it's really just a vendor funded project and all the decision making happens behind closed doors. Just as a small rant, I know we talked about forming steering committee.
06:00
You don't actually have to form one. It's just what most of the projects are doing. As long as your decision making is public and in the clear, we are actually happy. In terms of community, this is a really difficult one to meet. If your project could be really wonderful, but if no one's using it, we can't really help you there.
06:21
We want to see some good collaboration between the developers and your community of users. So often this occurs around release process. So we really like to see release candidates being issued and the community being active and involved in testing them. Community active involved on the issue tracker is also good.
06:42
Another difficult one for projects to get through is long term viability. We want to make sure your project isn't going to vanish overnight because that would leave our users kind of high and dry. So you might have a wonderful project, but if it's only you and you go out of business, yeah, the users of
07:01
that software are a little bit stuck. This is also occasionally referred to as a bus number. We want your bus number to be relatively high. Copyright and license, this one goes by pretty quick. Open source license we talked about. The documentation license is a little bit odd. We really appreciate it if projects grant readers of the
07:23
documentation the same privileges we enjoy as open source developers. The ability to remix the content for their own purposes and training material. So you might have noticed at the top, these slides are Creative Commons by Attribution. This is an example of a documentation license.
07:44
In terms of actually checking, we do ask for a sanity check. This is going through all the files in your project, maybe checking their headers. We're really trying to see who wrote this file. Did you talk to them? Do you have permission to distribute this? Or are they going to come calling later and saying,
08:02
hey, what are you doing with my software? Give it back. And another fun one is we occasionally want to check the sample data that's used. I helped the Geomus project, and they had some sample data they were using from a local municipality. And rather than negotiate to distribute it, we made up
08:20
something about unicorn farming, and that was good enough for their test cases. So we want to make sure you know what you're distributing, who gave it to you. Just as a small rant, this is only a check. You don't have to fix the problem. We are perfectly happy to graduate a project with known issues.
08:40
Because this is good advertising. Maybe some of your users care. Maybe some of your users will pay to help you fix them. We just wanted to keep this in terms of risk assessment. We want your users to know what risks are associated with using your project. In terms of contributors, it's really good.
09:00
It's polite, maybe as a Canadian, to thank the people you're working with. So we do ask that you list your contributors. It's also wise, if you have any paperwork on hand, from the contributors acknowledging that they gave you the source code. It's not strictly necessary. If you don't have a code contribution agreement, it just
09:23
means that all those people still own the copyright. And that's how a lot of projects get along. I think PostGIS works in that fashion. In terms of the process, we would really like you to have version control. I don't have too much more to say about that. OSGO used to offer SVN services.
09:42
I think they're stepping back from that. We also want an issue tracker. It's really helpful for communicating with users. OSGO does offer track, if you're interested. And in terms of management, we're really interested in that open communication. We want to make sure that your project is not closed.
10:03
We want to make sure that you're open to new contributors, new developers coming in and having a say in the running of the project. So there's several things you can do to help that, public email lists, IRC, public meetings. For the GeoServer project, we meet via Skype every two weeks.
10:21
That call is open to anyone. They just have to ask on IRC. And then we post the meeting minutes at the end. In terms of documentation, this sounds like a bit of a tough ask. We really don't ask for it very much. We ask for a very simple quick start, showing how a new user can use your software.
10:41
I believe most projects would have that on hand. In terms of developer documentation, this is open-source. We'd like to make sure that new developers can come and download your software and build it. So a small rant, like if I'm looking at developer
11:01
documentation, I really want to know, how do I submit a patch or a fix? How do I contribute a new feature? In terms of release instructions, do you just build it locally and put it up for everyone else to download? That's fine. That's kind of testing using your user list.
11:21
It's really nice if you write down how you make a release. It might just be doing a quick tag in GitHub. It might be more formal with a code freeze. We're just trying to figure out how your project gets the job done. And in terms of testing instructions, it's all over the map.
11:41
Some projects have automated builds and units tests. Some make a release candidate and ask their users to test. And some people do very little testing, like a smoke test and passing it out to the user list. We don't really mind what you're doing. We just want you to write it down and tell us. So can a volunteer follow your instructions
12:01
and make a release? Are you sure? Would you be comfortable with uploading that release to the project site? I'm pretty good for GeoServer. I'm not sure I would have a good process for UDIG. It's a difficult ask for this one. In terms of community and collaboration, once you've joined OSGEO, there's a little bit of information we
12:21
need for you to get along with everyone. The OSGEO board would like a project officer. This is a volunteer contact point. And you can change that officer at any time. They just want to know one person to talk to. The marketing committee is a bit more demanding. They would like to know the name of your project, the details.
12:41
They'd really love a screen snapshot. If they can't describe or show your project to others, it's very hard for them to promote you. In light of the last talk, we also recommend projects take part in OSGEO live, but it's by no means a requirement.
13:00
Finally, there's the sysadmin committee. They would like to make sure you've got a link on the project home page. They also are responsible for lots of our infrastructure, like track, mailing lists, and so forth. Those services are available to you if you need it. There are some other OSGEO projects around.
13:21
We would really like to see some communication and collaboration between projects. So as an example, PostGIS checks that it works with MapServer and GeoServer as part of their release process. And we've got a few other examples like that. We are not quite a software stack with all our projects in OSGEO, but we really like to make sure that the
13:43
projects do work together. Any other stuff? OSGEO does do other activities. These groups here haven't asked for any direct involvement from projects, but you're totally welcome to take on any initiatives with public data or education
14:03
and join conferences such as this one. So in terms of the incubation committee, so this is the group that helps new projects. We have very little news to report. We've got Marble Virtual Globe, which has graduated in the last year or so. We have a number of projects that are close.
14:22
Actually, apparently only one. RasterMan is lurking on the user list. They're really waiting for a time period where both the developers and their mentor are ready, but I believe they've done all their checks. And we've got a number of projects that are rather busy. So these are projects that have joined OSGEO and are incubating, but they're not quite done all their checks.
14:43
GV-SIG is really close. They've done all their code checks, and I think we're trying to find a new mentor for them. We've got a few other projects, MetaCRS and Zoo Project and so forth. All of these projects are kind of in-flight, so they've expressed interest in being part of OSGEO, but we haven't
15:02
finished working with them to check things over yet. And finally, we've got one no-show. So the team engine is an OGC project. They've joined OSGEO, like they've joined incubation, but then they haven't done anything at all. So I'm not quite sure what's happening with that one.
15:24
Any questions? This is a fairly quick talk. Stunned silence.
15:42
I would like to know if you check the software for any espionage codes. I mean, I could imagine universities in certain countries being interested in bringing into your databases,
16:01
putting into the software. So the OSGEO foundation doesn't really care at that point. The code is open source. People are welcome to review it. For many of our popular open source projects, they are getting external security audits several times a year. So we get about three security audits on
16:20
GeoServer a year. Sometimes those groups run away frightened. Sometimes they report a bug, and we can explain the difference between CQL and SQL to them. So it just really varies. So does that kind of answer your question? The code is open source. Organizations can pay for a security audit.
16:41
The OSGEO foundation doesn't pay for a security audit. But it is a good idea. We can ask the board. I'm just wondering if you said the code is open, but maybe the executable code is not exactly the same. Oh, I see what you're saying.
17:00
Some foundations, like the Apache Foundation, have very strict building guidelines. So each development team has to hand over their code, hit a tag, and the Apache Foundation, somewhere in a back room, will do a really clean build from source code on that. The OSGEO Foundation just isn't playing in that area.
17:23
So each project, it's up to them to make their releases and put it up on the website. And if someone accidentally sneaks something in, we don't know. How about post? How about the GeoServer? So GeoServer, we do have a build. Right now, our releases are run on the boundless
17:42
infrastructure. But you are correct that that is happening behind closed doors. Although we do have the full build log up there on the web server, for whatever that's worth. But yeah, that is a concern. But it's one that's not often addressed in the open
18:04
source foundations. I think Apache is the only one that does it. Any other questions? Well, I have a question for you. I would really like anyone in this room to join the Incubation Committee as a member.
18:21
We do have lots of interesting projects that could really use a helping hand. I know we talked a little bit about the consequences, but often this is good fun. You get to meet a new development team. You get to help introduce them to all the wonderful projects and people we've got in our community here. We would really appreciate your participation.
18:42
Thank you.
Empfehlungen
Serie mit 12 Medien