OSGeo - User contributions [en]

Election 2025 Candidate Manifestos

2025-12-15T22:35:05Z

RajatShinde: /* What your interests are in terms of the board */

A space for the candidates for election to the Board to share some information about themselves, their aspirations for OSGeo, what they would like to change, improve or introduce and what role they would like to play on the board.

You are welcome to follow the template, and add further relevant info as you need:

== ''Name Template'' - ''Country'' ([https://www.osgeo.org/member/''name''/ OSGeo profile]) ==

=== About me ===

=== My vision ===

=== What you have done within the community in the past ===

=== What your interests are in terms of the board ===

=== Any things that you would like to change or introduce ===

=== What role you would wish to fulfill on the board (if any) ===

== ''Ariel Anthieni'' - ''Argentina'' ([https://www.osgeo.org/member/anthieni/ OSGeo profile]) ==

=== About me ===

Today is my second time writing this manifesto, to introduce you to the Board, with my two years of learning many, challenges were presented to me, such as language and opportunities to collaborate with the global and regional community.

I started, as a curiosity in 2007 when I started the SDI of the province of Santa Fe in Argentina, where I was born, where everything was new for me, in 2012 with others we founded Geoinquietos, in Buenos Aires, where it became my home, and from then on we said, thanks to the support of the OSGeo community, I organized FOSS4G in Argentina, in 2016 I chaired the FOSS4G Argentina, and participated in the organization of the 2017 and 2019 editions.
I was also part of the organization of SOTM Argentina 2017 and SOTM LATAM 2018. In 2018, I was part of the foundation of the Geolibres Association (https://geolibres.org.ar/), which supports the geospatial communities of Argentina (Geolibres Argentina, Openstreetmap Argentina, QGIS Argentina).
Our first great challenge was to organize the International FOSS4G 2021 Buenos Aires and then supporting the region and so that free software is increasingly used, accompanying the creation of the local OSGeo chapter in Brazil and the organization of the International FOSS4G 2024 Belém, coordinating the LOC along with the chairs, which marked the integration of OsGeo in other regions of the world.
Also over the last few years I had the great opportunity to participate in the International and Regional FOSS4G, as well as Code Sprint and SOTM events.

In Latin America, together with ECLAC, we were able to design, develop and implement Open source solutions for statistical institutes in more than 12 countries, for the construction of SDIs and to generate the technological solution of the SDI Americas for the entire American continent.

Apart from this, I am the CEO of ([https://kan.com.ar/ Kan Territory & IT]), where we specialize in creating open source tools for cities, companies, institutions for the integration of geospatial, statistical and alphanumeric data, enhancing their solutions.

He is also actively involved in UN, UNGGIM and the UN Open GIS Initiative.

**Representation and current positions**
* Chair of the OSGeo UN Committee
* Co-Chair UN Open GIS
* OSGeo representative in the UNGGIM network of Geospatial Societies
* President of Geolibres Argentina
* CEO of Territorio Kan & TI

**Communities in which I participate**
* IDERA – IDE of Argentina
* UN OPEN GIS
* OSM LATAM
* QGISArgentina
* OSM Argentina
* Geolibres Argentina
* UNGGIM
* OSGeo UN Committee

=== My vision ===

My vision is very simple, to be able to achieve the use of open source in every corner of the planet, integrating and growing local communities to be able to achieve greater insertion in people's lives, improving their quality of life. and that it is not a limit on language, technology or knowledge transfer. Also raise awareness for the evolution of a sustainable Foundation over time so that it can continue supporting the projects that are incubated and new projects.

=== What you have done within the community in the past ===

* OSGeo representative in the UNGGIM 2022 Geospatial Societies network - current
* President of the OSGeo 2024 UN Committee - current
* Collaborator in the State of the LATAM Map 2025
* VP LATAM of OSGeo 2024
* Member of the OSGeo Board of Directors 2023-2024
* Coordinator of FOSS4G 2024 Belém (International)
* Collaborator in FOSS4G-AR 2017 and 2019
* Chair of FOSS4G-AR 2016
* Coordinator of FOSS4G Buenos Aires 2021 (International)
* Founding Member of Ge@inquietos Argentina
* Founder and current President of Geolibres Argentina
* Responsible for the Local Chapter OSM Argentina and QGIS Argentina
* Member of the SDI of Argentina since 2012

=== What your interests are in terms of the board ===

To be able to generate greater insertion of the regions that do not currently participate with the creation of local chapters in the countries that are missing. Achieve the sustainability of the foundation, seeing the possibility of obtaining a sponsor for open source in general, and from different regions. Continue supporting integration with the governments of the UN member countries and that language is not a limitation to integration.

=== Any things that you would like to change or introduce ===

I would like to introduce more options so that open source developers from regions such as Latin America can easily access it, finish finalizing the local chapter of Colombia and strengthen links with the UN and its member countries through agreements and possible sponsorship. Then continue building with everything that has been achieved year after year to make the foundation increasingly more sustainable.

=== What role you would wish to fulfill on the board (if any) ===

I would like to be Vice President for Latin America, to be able to reach more countries and communities.

== ''Vicky Vergara'' - ''Mexico'' ([https://www.osgeo.org/member/vicky-vergara/ OSGeo profile]) ==

=== About me ===

I haven't changed much from the last times I wrote a manifesto:
* On [https://wiki.osgeo.org/wiki/Election_2023_Candidate_Manifestos#Vicky_Vergara_-_Mexico_.28OSGeo_profile.29 2023] I wrote about my hobbies and what I like to do during a FOSS4G.
* On [https://wiki.osgeo.org/wiki/Election_2021_Candidate_Manifestos#Vicky_Vergara.2C_Mexico_.28OSGeo_profile.29 2021] I wrote about what the 9 year old me thought about where I live and how it has changed.
* On [https://wiki.osgeo.org/wiki/Election_2019_Candidate_Manifestos#5._Vicky_Vergara.2C_Mexico_.28OSGeo_profile.29 2019] I wrote about that my laziness make me do and redo things until I figure out how to do them efficient and fast, so the next time I do them I can be lazy.
* On [https://wiki.osgeo.org/wiki/Election_2017_Candidate_Manifestos#Vicky_Vergara 2017] I wrote about how I arrived to OSGeo

My conclusion re-reading the ''about me'' in those manifestos: I like to talk and write.

Some day I would like share with you the autographs I have gathered during the FOSS4G, that is I made people talk and write :-), in all languages, for example, this year I have in Nepali, Bengali, Japanese

This time I will leave my autograph in Spanish here:

Deseo que todo en su vida personal y profesional sea de lo mejor para todos.
Vicky

(Translation: I hope that everything in your personal or professional life is the best for you all.)

=== My vision ===

Summary if my Vision of OSGeo:

* OSGeo Foundation is here to serve the Flora of the world.
* OSGeo Foundation is here to serve the Fauna of the world.
* OSGeo Foundation is here to serve the Climate of the world.
* OSGeo Foundation is here to serve the People of the world.
* OSGeo Foundation is here to serve the Countries of the world.
* All OSGeo community members are PSC (Propose, Suggest and Comment)

=== What you have done within the community in the past ===

Normal life in front of the computer:
* Developing any of the pgRouting software:
** pgRouting
** vrpRouting
** osm2pgrouting
** pgRouting workshop
* Work on OSGeoLive:
** Documentation
** Checking the installed software
* Member of committees:
** Code of Conduct Committee
** System Administration Committee
** Board Member
* Other tasks
** Google Summer of Code mentor
** Read and answer mails

=== What your interests are in terms of the board ===

* The right to be the best one can be.
* Promote the development and use of Open Source Software.

=== Any things that you would like to change or introduce ===

'''Think''' about why things are not happening.

* Why "[abc] is NOT [xyz] OSGeo".
* Why do some projects do not start incubation?
* Why is there no local OSGeo chapter in X country?
* Why do we have mostly sponsors from North America and Europe?
* Why we only hear (and see) those, who raise their voice and shout out loud. But we miss to reach the silent majority?
* What causes the "inactivity"?
* Are we scalable?
* Why ....

=== What role you would wish to fulfill on the board (if any) ===

Vice president of the Latin America Area

== ''Jeroen Ticheler'' - ''The Netherlands'' ([https://www.osgeo.org/member/jeroen-ticheler/ OSGeo profile]) ==

=== About me ===

I’m Jeroen Ticheler, director and owner of ([https://www.geocat.net GeoCat]), founder of ([https://www.geonetwork-opensource.org GeoNetwork]) and current member of the board of directors of OSGeo.

I’m obsessed with helping organising and publishing (geospatial) data using free and open source software in a sustainable way. I started my career at the United Nations supporting Early Warning Systems with satellite imagery and quickly moved to also support the management of geospatial data.

Now, 25 years onwards, the GeoNetwork software we develop runs at over 85% of national geoportals in Europe (find thousands of harmonized, authoritative datasets ([https://inspire-geoportal.ec.europa.eu/srv/eng/catalog.search#/datathemes here]) ) and is in use at all levels in governments around the world.

A bit more background on me can be found in ([https://www.osgeo.org/member/jeroen-ticheler/ my OSGeo profile]) and in ([https://wiki.osgeo.org/w/index.php?title=Election_2023_Candidate_Manifestos#About_me the description]) for the 2023 elections.

=== My vision ===

For the coming two years I want to focus on change in OSGeo. For this I have written ([https://docs.google.com/document/d/1KRdCKB8HvI9FctF1Ulg6UfoCImjEYKaQkgg9l1HueZs '''a vision document''']) that is currently up for comments by the community. My goal is to ''Get Things Done''. More specifically those things described in the vision document that have traction within the community.

=== What you have done within the community in the past ===

Besides my involvement as PSC chair in the GeoNetwork opensource project, I have been involved as Charter member from 2006 onwards, served on the OSGeo Marketing and Conference Committees, as well as on the OSGeo Board (2007-2009 and 2023-now).

In the last 10+ years my involvement has also been in the form of a sponsor to OSGeo and FOSS4G (both global, regional and local) and by organising a yearly Code Sprint in Bolsena 2007-2023.

In the run up to the vision document mentioned above, I have taken time to talk face to face with numerous people and the current board membership.

=== What your interests are in terms of the board ===

As a member of the board I can help to '''make OSGeo future proof'''. This requires several concrete actions and needs our community to step up to the tasks to make that happen. As a community member with a long history, I'm convinced I can bring ideas to the table and move them forward.

=== Any things that you would like to change or introduce ===

Yes, many. But the main ones would be:

# Numbered list item to '''make OSGeo financially solid''' so it can support its mission: To foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.
# make sure there are new options for '''paid/supporting membership''' and for '''sponsoring''' that are attractive for both the community, sponsors, OSGeo and FOSS4G conference organisers.
# make sure there is '''a European legal entity of OSGeo''' that can serve its European membership, Local Chapters and the global OSGeo mission.

Furthermore one of the things that absolutely has my attention is responsible entrepreneurship. OSGeo needs to be a well balanced community of people from all parts of society, including volunteers, students and scientists, public servants and businesses.

=== What role you would wish to fulfill on the board (if any) ===

The role of president or vice president.

== Marco Bernasocchi, Switzerland ([https://www.osgeo.org/member/bernasocchi/ OSGeo profile]) ==

=== About me ===
I am an open-source advocate, consultant, teacher, and developer. My background is in geography with a specialization in geographic information science. I live in Switzerland in a small Romansh speaking mountain village where I love scrambling around the mountains to enjoy the feeling of freedom it gives me. I’m a very communicative person, I fluently speak Italian, German, French English, and Spanish and love travelling.

I'm the QGIS.org Chair, serve on the OSGeo board as VP Europe and work as CEO of OPENGIS.ch which I founded in 2011. Since 2014 I share the company ownership with Matthias Kuhn. At OPENGIS.ch LLC we develop, train and consult our client on any aspect related to QGIS, QField, PostGIS and WebGIS technologies.

I first came in contact with the OSGEO world during my BSc when the University of Zurich was teaching us proprietary products and I started looking around for Open Source alternatives and started using QuantumGIS “Simon (0.6)”. In 2008, when starting my MSc, I made the definitive switch to Ubuntu and I started working more and more with QuantumGIS Metis (0.11) and ended developing some plugins and part of Globe as my Masters' thesis.

Since then my whole work has pivoted around QGIS and enabling people and companies to embrace opensource for their GIS needs.

=== My vision ===
Serving as a pragmatic community conciliator - collecting thoughts from people with differing opinions and trying to find the high road through difficult issues I want to focus my and the community's energies on being inclusive and forward-thinking.

I see FOSS as a very socially responsible way to develop software, but even more, I see the immense technological advantage that writing open-source code brings. This is why I always strive to allow both pragmatic and ideological views to respectfully coexist and enrich each other.

=== What you have done within the community in the past ===
* OSGeo Board member since 2021 (VP Europe)
* QGIS contributor since 2011
* QGIS.org Chair since 2020
* QGIS.org Vice-Chair 2018-2020
* QField (originally QGIS for android) creator
* FOSS4G Session Leader, various FOSS4G Talks and workshops
* Charter Member since 2018
* Google Summer of Code 2012: Mentor
* Google Summer of Code 2011: Student Developer

=== What your interests are in terms of the board ===

One of my main motivations to be part of the board is to help OSGeo keep its incredible growth rate by being even more attractive to new community members, sponsors and large/corporate users. To achieve this, to me the key is maintaining the right balance between sustainable processes and helping interesting and motivating grassroots projects.

=== Any things that you would like to change or introduce ===
As still fairly technical driven person, I like to understand the inner workings of things and projects before commenting on changes :)

=== What role you would wish to fulfil on the board (if any) ===
I am open to any role based on how I could best serve the board.

== Matthew Hanson - United States ([https://www.osgeo.org/member/hanson/ OSGeo profile]) ==

=== About me ===

I’m Matthew Hanson. I first attended FOSS4G in 2011 and have since participated in 10 international FOSS4G and 8 FOSS4G North America conferences. That first FOSS4G changed the course of my career, and made it clear this was the community and work I wanted to be part of.

I work in Earth observation and geospatial software, focusing on cloud‑native architectures, open standards, and open‑source tooling. I’m best known for my work on STAC and related efforts, and for talks and writing aimed at making interoperable geospatial systems more accessible. I currently work at Element 84 at the intersection of open source, commercial Earth observation, and operational systems.

=== My vision ===

I see OSGeo as a truly international foundation that brings together open‑source geospatial communities that have, over time, diverged across projects, regions, and domains. OSGeo has a unique role to play in helping these communities reconnect, share practices, and recognize their common ground.

I also believe OSGeo can help welcome people who are already using and contributing to open‑source geospatial software, but do not yet see themselves as part of the OSGeo community. By acting as a neutral, inclusive convening space, OSGeo can strengthen collaboration, elevate shared standards and values, and help the community adapt to a rapidly evolving geospatial ecosystem.

=== What you have done within the community in the past ===

My work has focused on standards, interoperability, and community education. I am a core contributor and long‑term advocate for STAC and have served on the STAC Steering Committee since its inception. I am also a member of the editorial board of the Cloud‑Native Geospatial Forum.

I regularly speak at FOSS4G (global and North America) and related events, and write about cloud‑native geospatial systems and open standards. Much of my work bridges open‑source projects, public agencies, and commercial satellite data providers to enable practical adoption and interoperability.

=== What your interests are in terms of the board ===

As a board member, I am interested in strengthening OSGeo’s international presence and supporting collaboration across the community. In particular, I want to help bring together open‑source geospatial communities that have grown apart, and help welcome practitioners who are already part of the ecosystem but may not yet identify with OSGeo.

I am also interested in how OSGeo can continue to evolve alongside emerging developer communities and modern software development practices, including the impact of cloud-native development and AI-assisted coding on how open-source projects are built, discovered, and sustained. I see OSGeo as a natural place to convene thoughtful, inclusive conversations around these changes.

Finally, I am interested in strengthening coordination between global and regional FOSS4G conferences, so that regional events and the global conference reinforce each other and contribute to a healthy, connected international community.

=== Any things that you would like to change or introduce ===

If elected, I would like to help OSGeo strengthen connections across its diverse projects and communities, including those that operate somewhat independently today. I would also like to focus on outreach to practitioners who already rely on open‑source geospatial software but are not yet engaged with OSGeo, and encourage more cross‑project dialogue to reduce fragmentation.

=== What role you would wish to fulfill on the board (if any) ===

As a first‑time board member, my focus would be on contributing, learning, and supporting the existing board and its leadership. I respect the work of current board members and am open to serving in whatever role best supports the board and the broader OSGeo community.

== Rajat Shinde - India (Currently, residing in the US) ([https://www.osgeo.org/member/shinde OSGeo profile]) ==

=== About me ===
I’m Rajat Shinde, a computer scientist and GIS practitioner from India, currently based in the United States, working with the NASA Office of Data Science and Informatics at NASA Marshall Space Flight Center (MSFC) and the University of Alabama in Huntsville. I hold a Ph.D. in Geographical Information Systems and have worked across academia and industry on geospatial data science, AI, and Earth observation applications.

I first joined the OSGeo community at FOSS4G in 2017. I was elected to the OSGeo Board in 2021 and re-elected in 2023. I focus on bridging communities through collaborations with OGC, IEEE (including IEEE GRSS), and MLCommons, and on strengthening contributor pathways via student programs. I serve as a Project Steering Committee (PSC) member for pgRouting and ZOO-Project, and I have been a long-term Google Summer of Code mentor and organization administrator.

=== My vision ===
My vision is to make OSGeo easier to join and easier to stay in, suggesting clear pathways to new members for contributing and growing into long-term community leaders.

I also want to strengthen a progressive, globally representative FOSS4G ecosystem that collaborates with other open-source communities to advance open standards and interoperability. I will continue supporting OSGeo India and GeoBharat to expand participation and sustained contributions in India along with other regional GIS initiatives.

=== What you have done within the community in the past ===
* OSGeo Board: Vice President (2023–2025); elected Board member (2021, re-elected 2023)
* FOSS4G-Asia Program Committee 2026
* Standards + collaboration: OSGeo Standards Committee representative at OGC Geo-Huntsville 2023; OSGeo–OGC–ASF joint code sprint participant
* FOSS4G: FOSS4G 2021 session leader; FOSS4G Asia workshop contributor/speaker
* Project governance: PSC member (ZOO-Project, pgRouting)
* Education + outreach: UN OSGeo Education Challenge 2021 mentor (pgRouting track); engaged with UN OpenGIS and UN GeoAI WGs
* OSGeo Initiatives: GSoC student (2017), mentor (2018–present), org admin (2020–present); Google Code-in mentor (2019)
* Community resources: Contributor to the Cloud-native Geospatial Guide
* GeoAI interoperability: Leading projects with other open source communities such as MLCommons and IEEE
* Open source quality: JOSS manuscript reviewer (geospatial/geoscience software)

=== What your interests are in terms of the board ===
* To strengthen OSGeo’s external collaborations and long-term sustainability. I want to bring in more partnerships, MoUs, and sponsorships—aligned with OSGeo values—to better support projects, events, and community programs, with a specific focus on expanding relationships across Asia (including India, Japan, Nepal, and other regional hubs).

* Finally, as GIS evolves rapidly (cloud-native, data/AI-driven, reproducibility, and open standards), I want OSGeo to continue serving as the foundation for spreading responsible and trustworthy FOSS4G practices through deeper collaboration with adjacent open-source communities and standards bodies. As OSGeo approaches its 20-year milestone in 2026, this will help in defining a roadmap towards stronger OSGeo family.

=== Any things that you would like to change or introduce ===
I would like to strengthen on two points-
* Stronger links between regional and global FOSS4G: lightweight coordination and shared practices so regional events gain visibility/support, and global activities reflect regional priorities.
* More joint work with peer communities: expand cross-community collaborations (e.g., OSGeo–OGC joint code sprints and standards-aligned activities) to strengthen interoperable, responsible FOSS4G.

=== What role you would wish to fulfill on the board (if any) ===
I am open to any role deemed fit by the board.

[[Category:Elections]]
[[Category:Election 2025]]

Election 2025 Candidate Manifestos

2025-12-15T22:34:40Z

RajatShinde: /* What you have done within the community in the past */

A space for the candidates for election to the Board to share some information about themselves, their aspirations for OSGeo, what they would like to change, improve or introduce and what role they would like to play on the board.

You are welcome to follow the template, and add further relevant info as you need:

== ''Name Template'' - ''Country'' ([https://www.osgeo.org/member/''name''/ OSGeo profile]) ==

=== About me ===

=== My vision ===

=== What you have done within the community in the past ===

=== What your interests are in terms of the board ===

=== Any things that you would like to change or introduce ===

=== What role you would wish to fulfill on the board (if any) ===

== ''Ariel Anthieni'' - ''Argentina'' ([https://www.osgeo.org/member/anthieni/ OSGeo profile]) ==

=== About me ===

Today is my second time writing this manifesto, to introduce you to the Board, with my two years of learning many, challenges were presented to me, such as language and opportunities to collaborate with the global and regional community.

I started, as a curiosity in 2007 when I started the SDI of the province of Santa Fe in Argentina, where I was born, where everything was new for me, in 2012 with others we founded Geoinquietos, in Buenos Aires, where it became my home, and from then on we said, thanks to the support of the OSGeo community, I organized FOSS4G in Argentina, in 2016 I chaired the FOSS4G Argentina, and participated in the organization of the 2017 and 2019 editions.
I was also part of the organization of SOTM Argentina 2017 and SOTM LATAM 2018. In 2018, I was part of the foundation of the Geolibres Association (https://geolibres.org.ar/), which supports the geospatial communities of Argentina (Geolibres Argentina, Openstreetmap Argentina, QGIS Argentina).
Our first great challenge was to organize the International FOSS4G 2021 Buenos Aires and then supporting the region and so that free software is increasingly used, accompanying the creation of the local OSGeo chapter in Brazil and the organization of the International FOSS4G 2024 Belém, coordinating the LOC along with the chairs, which marked the integration of OsGeo in other regions of the world.
Also over the last few years I had the great opportunity to participate in the International and Regional FOSS4G, as well as Code Sprint and SOTM events.

In Latin America, together with ECLAC, we were able to design, develop and implement Open source solutions for statistical institutes in more than 12 countries, for the construction of SDIs and to generate the technological solution of the SDI Americas for the entire American continent.

Apart from this, I am the CEO of ([https://kan.com.ar/ Kan Territory & IT]), where we specialize in creating open source tools for cities, companies, institutions for the integration of geospatial, statistical and alphanumeric data, enhancing their solutions.

He is also actively involved in UN, UNGGIM and the UN Open GIS Initiative.

**Representation and current positions**
* Chair of the OSGeo UN Committee
* Co-Chair UN Open GIS
* OSGeo representative in the UNGGIM network of Geospatial Societies
* President of Geolibres Argentina
* CEO of Territorio Kan & TI

**Communities in which I participate**
* IDERA – IDE of Argentina
* UN OPEN GIS
* OSM LATAM
* QGISArgentina
* OSM Argentina
* Geolibres Argentina
* UNGGIM
* OSGeo UN Committee

=== My vision ===

My vision is very simple, to be able to achieve the use of open source in every corner of the planet, integrating and growing local communities to be able to achieve greater insertion in people's lives, improving their quality of life. and that it is not a limit on language, technology or knowledge transfer. Also raise awareness for the evolution of a sustainable Foundation over time so that it can continue supporting the projects that are incubated and new projects.

=== What you have done within the community in the past ===

* OSGeo representative in the UNGGIM 2022 Geospatial Societies network - current
* President of the OSGeo 2024 UN Committee - current
* Collaborator in the State of the LATAM Map 2025
* VP LATAM of OSGeo 2024
* Member of the OSGeo Board of Directors 2023-2024
* Coordinator of FOSS4G 2024 Belém (International)
* Collaborator in FOSS4G-AR 2017 and 2019
* Chair of FOSS4G-AR 2016
* Coordinator of FOSS4G Buenos Aires 2021 (International)
* Founding Member of Ge@inquietos Argentina
* Founder and current President of Geolibres Argentina
* Responsible for the Local Chapter OSM Argentina and QGIS Argentina
* Member of the SDI of Argentina since 2012

=== What your interests are in terms of the board ===

To be able to generate greater insertion of the regions that do not currently participate with the creation of local chapters in the countries that are missing. Achieve the sustainability of the foundation, seeing the possibility of obtaining a sponsor for open source in general, and from different regions. Continue supporting integration with the governments of the UN member countries and that language is not a limitation to integration.

=== Any things that you would like to change or introduce ===

I would like to introduce more options so that open source developers from regions such as Latin America can easily access it, finish finalizing the local chapter of Colombia and strengthen links with the UN and its member countries through agreements and possible sponsorship. Then continue building with everything that has been achieved year after year to make the foundation increasingly more sustainable.

=== What role you would wish to fulfill on the board (if any) ===

I would like to be Vice President for Latin America, to be able to reach more countries and communities.

== ''Vicky Vergara'' - ''Mexico'' ([https://www.osgeo.org/member/vicky-vergara/ OSGeo profile]) ==

=== About me ===

I haven't changed much from the last times I wrote a manifesto:
* On [https://wiki.osgeo.org/wiki/Election_2023_Candidate_Manifestos#Vicky_Vergara_-_Mexico_.28OSGeo_profile.29 2023] I wrote about my hobbies and what I like to do during a FOSS4G.
* On [https://wiki.osgeo.org/wiki/Election_2021_Candidate_Manifestos#Vicky_Vergara.2C_Mexico_.28OSGeo_profile.29 2021] I wrote about what the 9 year old me thought about where I live and how it has changed.
* On [https://wiki.osgeo.org/wiki/Election_2019_Candidate_Manifestos#5._Vicky_Vergara.2C_Mexico_.28OSGeo_profile.29 2019] I wrote about that my laziness make me do and redo things until I figure out how to do them efficient and fast, so the next time I do them I can be lazy.
* On [https://wiki.osgeo.org/wiki/Election_2017_Candidate_Manifestos#Vicky_Vergara 2017] I wrote about how I arrived to OSGeo

My conclusion re-reading the ''about me'' in those manifestos: I like to talk and write.

Some day I would like share with you the autographs I have gathered during the FOSS4G, that is I made people talk and write :-), in all languages, for example, this year I have in Nepali, Bengali, Japanese

This time I will leave my autograph in Spanish here:

Deseo que todo en su vida personal y profesional sea de lo mejor para todos.
Vicky

(Translation: I hope that everything in your personal or professional life is the best for you all.)

=== My vision ===

Summary if my Vision of OSGeo:

* OSGeo Foundation is here to serve the Flora of the world.
* OSGeo Foundation is here to serve the Fauna of the world.
* OSGeo Foundation is here to serve the Climate of the world.
* OSGeo Foundation is here to serve the People of the world.
* OSGeo Foundation is here to serve the Countries of the world.
* All OSGeo community members are PSC (Propose, Suggest and Comment)

=== What you have done within the community in the past ===

Normal life in front of the computer:
* Developing any of the pgRouting software:
** pgRouting
** vrpRouting
** osm2pgrouting
** pgRouting workshop
* Work on OSGeoLive:
** Documentation
** Checking the installed software
* Member of committees:
** Code of Conduct Committee
** System Administration Committee
** Board Member
* Other tasks
** Google Summer of Code mentor
** Read and answer mails

=== What your interests are in terms of the board ===

* The right to be the best one can be.
* Promote the development and use of Open Source Software.

=== Any things that you would like to change or introduce ===

'''Think''' about why things are not happening.

* Why "[abc] is NOT [xyz] OSGeo".
* Why do some projects do not start incubation?
* Why is there no local OSGeo chapter in X country?
* Why do we have mostly sponsors from North America and Europe?
* Why we only hear (and see) those, who raise their voice and shout out loud. But we miss to reach the silent majority?
* What causes the "inactivity"?
* Are we scalable?
* Why ....

=== What role you would wish to fulfill on the board (if any) ===

Vice president of the Latin America Area

== ''Jeroen Ticheler'' - ''The Netherlands'' ([https://www.osgeo.org/member/jeroen-ticheler/ OSGeo profile]) ==

=== About me ===

I’m Jeroen Ticheler, director and owner of ([https://www.geocat.net GeoCat]), founder of ([https://www.geonetwork-opensource.org GeoNetwork]) and current member of the board of directors of OSGeo.

I’m obsessed with helping organising and publishing (geospatial) data using free and open source software in a sustainable way. I started my career at the United Nations supporting Early Warning Systems with satellite imagery and quickly moved to also support the management of geospatial data.

Now, 25 years onwards, the GeoNetwork software we develop runs at over 85% of national geoportals in Europe (find thousands of harmonized, authoritative datasets ([https://inspire-geoportal.ec.europa.eu/srv/eng/catalog.search#/datathemes here]) ) and is in use at all levels in governments around the world.

A bit more background on me can be found in ([https://www.osgeo.org/member/jeroen-ticheler/ my OSGeo profile]) and in ([https://wiki.osgeo.org/w/index.php?title=Election_2023_Candidate_Manifestos#About_me the description]) for the 2023 elections.

=== My vision ===

For the coming two years I want to focus on change in OSGeo. For this I have written ([https://docs.google.com/document/d/1KRdCKB8HvI9FctF1Ulg6UfoCImjEYKaQkgg9l1HueZs '''a vision document''']) that is currently up for comments by the community. My goal is to ''Get Things Done''. More specifically those things described in the vision document that have traction within the community.

=== What you have done within the community in the past ===

Besides my involvement as PSC chair in the GeoNetwork opensource project, I have been involved as Charter member from 2006 onwards, served on the OSGeo Marketing and Conference Committees, as well as on the OSGeo Board (2007-2009 and 2023-now).

In the last 10+ years my involvement has also been in the form of a sponsor to OSGeo and FOSS4G (both global, regional and local) and by organising a yearly Code Sprint in Bolsena 2007-2023.

In the run up to the vision document mentioned above, I have taken time to talk face to face with numerous people and the current board membership.

=== What your interests are in terms of the board ===

As a member of the board I can help to '''make OSGeo future proof'''. This requires several concrete actions and needs our community to step up to the tasks to make that happen. As a community member with a long history, I'm convinced I can bring ideas to the table and move them forward.

=== Any things that you would like to change or introduce ===

Yes, many. But the main ones would be:

# Numbered list item to '''make OSGeo financially solid''' so it can support its mission: To foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.
# make sure there are new options for '''paid/supporting membership''' and for '''sponsoring''' that are attractive for both the community, sponsors, OSGeo and FOSS4G conference organisers.
# make sure there is '''a European legal entity of OSGeo''' that can serve its European membership, Local Chapters and the global OSGeo mission.

Furthermore one of the things that absolutely has my attention is responsible entrepreneurship. OSGeo needs to be a well balanced community of people from all parts of society, including volunteers, students and scientists, public servants and businesses.

=== What role you would wish to fulfill on the board (if any) ===

The role of president or vice president.

== Marco Bernasocchi, Switzerland ([https://www.osgeo.org/member/bernasocchi/ OSGeo profile]) ==

=== About me ===
I am an open-source advocate, consultant, teacher, and developer. My background is in geography with a specialization in geographic information science. I live in Switzerland in a small Romansh speaking mountain village where I love scrambling around the mountains to enjoy the feeling of freedom it gives me. I’m a very communicative person, I fluently speak Italian, German, French English, and Spanish and love travelling.

I'm the QGIS.org Chair, serve on the OSGeo board as VP Europe and work as CEO of OPENGIS.ch which I founded in 2011. Since 2014 I share the company ownership with Matthias Kuhn. At OPENGIS.ch LLC we develop, train and consult our client on any aspect related to QGIS, QField, PostGIS and WebGIS technologies.

I first came in contact with the OSGEO world during my BSc when the University of Zurich was teaching us proprietary products and I started looking around for Open Source alternatives and started using QuantumGIS “Simon (0.6)”. In 2008, when starting my MSc, I made the definitive switch to Ubuntu and I started working more and more with QuantumGIS Metis (0.11) and ended developing some plugins and part of Globe as my Masters' thesis.

Since then my whole work has pivoted around QGIS and enabling people and companies to embrace opensource for their GIS needs.

=== My vision ===
Serving as a pragmatic community conciliator - collecting thoughts from people with differing opinions and trying to find the high road through difficult issues I want to focus my and the community's energies on being inclusive and forward-thinking.

I see FOSS as a very socially responsible way to develop software, but even more, I see the immense technological advantage that writing open-source code brings. This is why I always strive to allow both pragmatic and ideological views to respectfully coexist and enrich each other.

=== What you have done within the community in the past ===
* OSGeo Board member since 2021 (VP Europe)
* QGIS contributor since 2011
* QGIS.org Chair since 2020
* QGIS.org Vice-Chair 2018-2020
* QField (originally QGIS for android) creator
* FOSS4G Session Leader, various FOSS4G Talks and workshops
* Charter Member since 2018
* Google Summer of Code 2012: Mentor
* Google Summer of Code 2011: Student Developer

=== What your interests are in terms of the board ===

One of my main motivations to be part of the board is to help OSGeo keep its incredible growth rate by being even more attractive to new community members, sponsors and large/corporate users. To achieve this, to me the key is maintaining the right balance between sustainable processes and helping interesting and motivating grassroots projects.

=== Any things that you would like to change or introduce ===
As still fairly technical driven person, I like to understand the inner workings of things and projects before commenting on changes :)

=== What role you would wish to fulfil on the board (if any) ===
I am open to any role based on how I could best serve the board.

== Matthew Hanson - United States ([https://www.osgeo.org/member/hanson/ OSGeo profile]) ==

=== About me ===

I’m Matthew Hanson. I first attended FOSS4G in 2011 and have since participated in 10 international FOSS4G and 8 FOSS4G North America conferences. That first FOSS4G changed the course of my career, and made it clear this was the community and work I wanted to be part of.

I work in Earth observation and geospatial software, focusing on cloud‑native architectures, open standards, and open‑source tooling. I’m best known for my work on STAC and related efforts, and for talks and writing aimed at making interoperable geospatial systems more accessible. I currently work at Element 84 at the intersection of open source, commercial Earth observation, and operational systems.

=== My vision ===

I see OSGeo as a truly international foundation that brings together open‑source geospatial communities that have, over time, diverged across projects, regions, and domains. OSGeo has a unique role to play in helping these communities reconnect, share practices, and recognize their common ground.

I also believe OSGeo can help welcome people who are already using and contributing to open‑source geospatial software, but do not yet see themselves as part of the OSGeo community. By acting as a neutral, inclusive convening space, OSGeo can strengthen collaboration, elevate shared standards and values, and help the community adapt to a rapidly evolving geospatial ecosystem.

=== What you have done within the community in the past ===

My work has focused on standards, interoperability, and community education. I am a core contributor and long‑term advocate for STAC and have served on the STAC Steering Committee since its inception. I am also a member of the editorial board of the Cloud‑Native Geospatial Forum.

I regularly speak at FOSS4G (global and North America) and related events, and write about cloud‑native geospatial systems and open standards. Much of my work bridges open‑source projects, public agencies, and commercial satellite data providers to enable practical adoption and interoperability.

=== What your interests are in terms of the board ===

As a board member, I am interested in strengthening OSGeo’s international presence and supporting collaboration across the community. In particular, I want to help bring together open‑source geospatial communities that have grown apart, and help welcome practitioners who are already part of the ecosystem but may not yet identify with OSGeo.

I am also interested in how OSGeo can continue to evolve alongside emerging developer communities and modern software development practices, including the impact of cloud-native development and AI-assisted coding on how open-source projects are built, discovered, and sustained. I see OSGeo as a natural place to convene thoughtful, inclusive conversations around these changes.

Finally, I am interested in strengthening coordination between global and regional FOSS4G conferences, so that regional events and the global conference reinforce each other and contribute to a healthy, connected international community.

=== Any things that you would like to change or introduce ===

If elected, I would like to help OSGeo strengthen connections across its diverse projects and communities, including those that operate somewhat independently today. I would also like to focus on outreach to practitioners who already rely on open‑source geospatial software but are not yet engaged with OSGeo, and encourage more cross‑project dialogue to reduce fragmentation.

=== What role you would wish to fulfill on the board (if any) ===

As a first‑time board member, my focus would be on contributing, learning, and supporting the existing board and its leadership. I respect the work of current board members and am open to serving in whatever role best supports the board and the broader OSGeo community.

== Rajat Shinde - India (Currently, residing in the US) ([https://www.osgeo.org/member/shinde OSGeo profile]) ==

=== About me ===
I’m Rajat Shinde, a computer scientist and GIS practitioner from India, currently based in the United States, working with the NASA Office of Data Science and Informatics at NASA Marshall Space Flight Center (MSFC) and the University of Alabama in Huntsville. I hold a Ph.D. in Geographical Information Systems and have worked across academia and industry on geospatial data science, AI, and Earth observation applications.

I first joined the OSGeo community at FOSS4G in 2017. I was elected to the OSGeo Board in 2021 and re-elected in 2023. I focus on bridging communities through collaborations with OGC, IEEE (including IEEE GRSS), and MLCommons, and on strengthening contributor pathways via student programs. I serve as a Project Steering Committee (PSC) member for pgRouting and ZOO-Project, and I have been a long-term Google Summer of Code mentor and organization administrator.

=== My vision ===
My vision is to make OSGeo easier to join and easier to stay in, suggesting clear pathways to new members for contributing and growing into long-term community leaders.

I also want to strengthen a progressive, globally representative FOSS4G ecosystem that collaborates with other open-source communities to advance open standards and interoperability. I will continue supporting OSGeo India and GeoBharat to expand participation and sustained contributions in India along with other regional GIS initiatives.

=== What you have done within the community in the past ===
* OSGeo Board: Vice President (2023–2025); elected Board member (2021, re-elected 2023)
* FOSS4G-Asia Program Committee 2026
* Standards + collaboration: OSGeo Standards Committee representative at OGC Geo-Huntsville 2023; OSGeo–OGC–ASF joint code sprint participant
* FOSS4G: FOSS4G 2021 session leader; FOSS4G Asia workshop contributor/speaker
* Project governance: PSC member (ZOO-Project, pgRouting)
* Education + outreach: UN OSGeo Education Challenge 2021 mentor (pgRouting track); engaged with UN OpenGIS and UN GeoAI WGs
* OSGeo Initiatives: GSoC student (2017), mentor (2018–present), org admin (2020–present); Google Code-in mentor (2019)
* Community resources: Contributor to the Cloud-native Geospatial Guide
* GeoAI interoperability: Leading projects with other open source communities such as MLCommons and IEEE
* Open source quality: JOSS manuscript reviewer (geospatial/geoscience software)

=== What your interests are in terms of the board ===
- To strengthen OSGeo’s external collaborations and long-term sustainability. I want to bring in more partnerships, MoUs, and sponsorships—aligned with OSGeo values—to better support projects, events, and community programs, with a specific focus on expanding relationships across Asia (including India, Japan, Nepal, and other regional hubs).

- Finally, as GIS evolves rapidly (cloud-native, data/AI-driven, reproducibility, and open standards), I want OSGeo to continue serving as the foundation for spreading responsible and trustworthy FOSS4G practices through deeper collaboration with adjacent open-source communities and standards bodies. As OSGeo approaches its 20-year milestone in 2026, this will help in defining a roadmap towards stronger OSGeo family.

=== Any things that you would like to change or introduce ===
I would like to strengthen on two points-
* Stronger links between regional and global FOSS4G: lightweight coordination and shared practices so regional events gain visibility/support, and global activities reflect regional priorities.
* More joint work with peer communities: expand cross-community collaborations (e.g., OSGeo–OGC joint code sprints and standards-aligned activities) to strengthen interoperable, responsible FOSS4G.

=== What role you would wish to fulfill on the board (if any) ===
I am open to any role deemed fit by the board.

[[Category:Elections]]
[[Category:Election 2025]]

Election 2025 Candidate Manifestos

2025-12-15T22:32:45Z

RajatShinde: Rajat Shinde Manifesto update

A space for the candidates for election to the Board to share some information about themselves, their aspirations for OSGeo, what they would like to change, improve or introduce and what role they would like to play on the board.

You are welcome to follow the template, and add further relevant info as you need:

== ''Name Template'' - ''Country'' ([https://www.osgeo.org/member/''name''/ OSGeo profile]) ==

=== About me ===

=== My vision ===

=== What you have done within the community in the past ===

=== What your interests are in terms of the board ===

=== Any things that you would like to change or introduce ===

=== What role you would wish to fulfill on the board (if any) ===

== ''Ariel Anthieni'' - ''Argentina'' ([https://www.osgeo.org/member/anthieni/ OSGeo profile]) ==

=== About me ===

Today is my second time writing this manifesto, to introduce you to the Board, with my two years of learning many, challenges were presented to me, such as language and opportunities to collaborate with the global and regional community.

I started, as a curiosity in 2007 when I started the SDI of the province of Santa Fe in Argentina, where I was born, where everything was new for me, in 2012 with others we founded Geoinquietos, in Buenos Aires, where it became my home, and from then on we said, thanks to the support of the OSGeo community, I organized FOSS4G in Argentina, in 2016 I chaired the FOSS4G Argentina, and participated in the organization of the 2017 and 2019 editions.
I was also part of the organization of SOTM Argentina 2017 and SOTM LATAM 2018. In 2018, I was part of the foundation of the Geolibres Association (https://geolibres.org.ar/), which supports the geospatial communities of Argentina (Geolibres Argentina, Openstreetmap Argentina, QGIS Argentina).
Our first great challenge was to organize the International FOSS4G 2021 Buenos Aires and then supporting the region and so that free software is increasingly used, accompanying the creation of the local OSGeo chapter in Brazil and the organization of the International FOSS4G 2024 Belém, coordinating the LOC along with the chairs, which marked the integration of OsGeo in other regions of the world.
Also over the last few years I had the great opportunity to participate in the International and Regional FOSS4G, as well as Code Sprint and SOTM events.

In Latin America, together with ECLAC, we were able to design, develop and implement Open source solutions for statistical institutes in more than 12 countries, for the construction of SDIs and to generate the technological solution of the SDI Americas for the entire American continent.

Apart from this, I am the CEO of ([https://kan.com.ar/ Kan Territory & IT]), where we specialize in creating open source tools for cities, companies, institutions for the integration of geospatial, statistical and alphanumeric data, enhancing their solutions.

He is also actively involved in UN, UNGGIM and the UN Open GIS Initiative.

**Representation and current positions**
* Chair of the OSGeo UN Committee
* Co-Chair UN Open GIS
* OSGeo representative in the UNGGIM network of Geospatial Societies
* President of Geolibres Argentina
* CEO of Territorio Kan & TI

**Communities in which I participate**
* IDERA – IDE of Argentina
* UN OPEN GIS
* OSM LATAM
* QGISArgentina
* OSM Argentina
* Geolibres Argentina
* UNGGIM
* OSGeo UN Committee

=== My vision ===

My vision is very simple, to be able to achieve the use of open source in every corner of the planet, integrating and growing local communities to be able to achieve greater insertion in people's lives, improving their quality of life. and that it is not a limit on language, technology or knowledge transfer. Also raise awareness for the evolution of a sustainable Foundation over time so that it can continue supporting the projects that are incubated and new projects.

=== What you have done within the community in the past ===

* OSGeo representative in the UNGGIM 2022 Geospatial Societies network - current
* President of the OSGeo 2024 UN Committee - current
* Collaborator in the State of the LATAM Map 2025
* VP LATAM of OSGeo 2024
* Member of the OSGeo Board of Directors 2023-2024
* Coordinator of FOSS4G 2024 Belém (International)
* Collaborator in FOSS4G-AR 2017 and 2019
* Chair of FOSS4G-AR 2016
* Coordinator of FOSS4G Buenos Aires 2021 (International)
* Founding Member of Ge@inquietos Argentina
* Founder and current President of Geolibres Argentina
* Responsible for the Local Chapter OSM Argentina and QGIS Argentina
* Member of the SDI of Argentina since 2012

=== What your interests are in terms of the board ===

To be able to generate greater insertion of the regions that do not currently participate with the creation of local chapters in the countries that are missing. Achieve the sustainability of the foundation, seeing the possibility of obtaining a sponsor for open source in general, and from different regions. Continue supporting integration with the governments of the UN member countries and that language is not a limitation to integration.

=== Any things that you would like to change or introduce ===

I would like to introduce more options so that open source developers from regions such as Latin America can easily access it, finish finalizing the local chapter of Colombia and strengthen links with the UN and its member countries through agreements and possible sponsorship. Then continue building with everything that has been achieved year after year to make the foundation increasingly more sustainable.

=== What role you would wish to fulfill on the board (if any) ===

I would like to be Vice President for Latin America, to be able to reach more countries and communities.

== ''Vicky Vergara'' - ''Mexico'' ([https://www.osgeo.org/member/vicky-vergara/ OSGeo profile]) ==

=== About me ===

I haven't changed much from the last times I wrote a manifesto:
* On [https://wiki.osgeo.org/wiki/Election_2023_Candidate_Manifestos#Vicky_Vergara_-_Mexico_.28OSGeo_profile.29 2023] I wrote about my hobbies and what I like to do during a FOSS4G.
* On [https://wiki.osgeo.org/wiki/Election_2021_Candidate_Manifestos#Vicky_Vergara.2C_Mexico_.28OSGeo_profile.29 2021] I wrote about what the 9 year old me thought about where I live and how it has changed.
* On [https://wiki.osgeo.org/wiki/Election_2019_Candidate_Manifestos#5._Vicky_Vergara.2C_Mexico_.28OSGeo_profile.29 2019] I wrote about that my laziness make me do and redo things until I figure out how to do them efficient and fast, so the next time I do them I can be lazy.
* On [https://wiki.osgeo.org/wiki/Election_2017_Candidate_Manifestos#Vicky_Vergara 2017] I wrote about how I arrived to OSGeo

My conclusion re-reading the ''about me'' in those manifestos: I like to talk and write.

Some day I would like share with you the autographs I have gathered during the FOSS4G, that is I made people talk and write :-), in all languages, for example, this year I have in Nepali, Bengali, Japanese

This time I will leave my autograph in Spanish here:

Deseo que todo en su vida personal y profesional sea de lo mejor para todos.
Vicky

(Translation: I hope that everything in your personal or professional life is the best for you all.)

=== My vision ===

Summary if my Vision of OSGeo:

* OSGeo Foundation is here to serve the Flora of the world.
* OSGeo Foundation is here to serve the Fauna of the world.
* OSGeo Foundation is here to serve the Climate of the world.
* OSGeo Foundation is here to serve the People of the world.
* OSGeo Foundation is here to serve the Countries of the world.
* All OSGeo community members are PSC (Propose, Suggest and Comment)

=== What you have done within the community in the past ===

Normal life in front of the computer:
* Developing any of the pgRouting software:
** pgRouting
** vrpRouting
** osm2pgrouting
** pgRouting workshop
* Work on OSGeoLive:
** Documentation
** Checking the installed software
* Member of committees:
** Code of Conduct Committee
** System Administration Committee
** Board Member
* Other tasks
** Google Summer of Code mentor
** Read and answer mails

=== What your interests are in terms of the board ===

* The right to be the best one can be.
* Promote the development and use of Open Source Software.

=== Any things that you would like to change or introduce ===

'''Think''' about why things are not happening.

* Why "[abc] is NOT [xyz] OSGeo".
* Why do some projects do not start incubation?
* Why is there no local OSGeo chapter in X country?
* Why do we have mostly sponsors from North America and Europe?
* Why we only hear (and see) those, who raise their voice and shout out loud. But we miss to reach the silent majority?
* What causes the "inactivity"?
* Are we scalable?
* Why ....

=== What role you would wish to fulfill on the board (if any) ===

Vice president of the Latin America Area

== ''Jeroen Ticheler'' - ''The Netherlands'' ([https://www.osgeo.org/member/jeroen-ticheler/ OSGeo profile]) ==

=== About me ===

I’m Jeroen Ticheler, director and owner of ([https://www.geocat.net GeoCat]), founder of ([https://www.geonetwork-opensource.org GeoNetwork]) and current member of the board of directors of OSGeo.

I’m obsessed with helping organising and publishing (geospatial) data using free and open source software in a sustainable way. I started my career at the United Nations supporting Early Warning Systems with satellite imagery and quickly moved to also support the management of geospatial data.

Now, 25 years onwards, the GeoNetwork software we develop runs at over 85% of national geoportals in Europe (find thousands of harmonized, authoritative datasets ([https://inspire-geoportal.ec.europa.eu/srv/eng/catalog.search#/datathemes here]) ) and is in use at all levels in governments around the world.

A bit more background on me can be found in ([https://www.osgeo.org/member/jeroen-ticheler/ my OSGeo profile]) and in ([https://wiki.osgeo.org/w/index.php?title=Election_2023_Candidate_Manifestos#About_me the description]) for the 2023 elections.

=== My vision ===

For the coming two years I want to focus on change in OSGeo. For this I have written ([https://docs.google.com/document/d/1KRdCKB8HvI9FctF1Ulg6UfoCImjEYKaQkgg9l1HueZs '''a vision document''']) that is currently up for comments by the community. My goal is to ''Get Things Done''. More specifically those things described in the vision document that have traction within the community.

=== What you have done within the community in the past ===

Besides my involvement as PSC chair in the GeoNetwork opensource project, I have been involved as Charter member from 2006 onwards, served on the OSGeo Marketing and Conference Committees, as well as on the OSGeo Board (2007-2009 and 2023-now).

In the last 10+ years my involvement has also been in the form of a sponsor to OSGeo and FOSS4G (both global, regional and local) and by organising a yearly Code Sprint in Bolsena 2007-2023.

In the run up to the vision document mentioned above, I have taken time to talk face to face with numerous people and the current board membership.

=== What your interests are in terms of the board ===

As a member of the board I can help to '''make OSGeo future proof'''. This requires several concrete actions and needs our community to step up to the tasks to make that happen. As a community member with a long history, I'm convinced I can bring ideas to the table and move them forward.

=== Any things that you would like to change or introduce ===

Yes, many. But the main ones would be:

# Numbered list item to '''make OSGeo financially solid''' so it can support its mission: To foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.
# make sure there are new options for '''paid/supporting membership''' and for '''sponsoring''' that are attractive for both the community, sponsors, OSGeo and FOSS4G conference organisers.
# make sure there is '''a European legal entity of OSGeo''' that can serve its European membership, Local Chapters and the global OSGeo mission.

Furthermore one of the things that absolutely has my attention is responsible entrepreneurship. OSGeo needs to be a well balanced community of people from all parts of society, including volunteers, students and scientists, public servants and businesses.

=== What role you would wish to fulfill on the board (if any) ===

The role of president or vice president.

== Marco Bernasocchi, Switzerland ([https://www.osgeo.org/member/bernasocchi/ OSGeo profile]) ==

=== About me ===
I am an open-source advocate, consultant, teacher, and developer. My background is in geography with a specialization in geographic information science. I live in Switzerland in a small Romansh speaking mountain village where I love scrambling around the mountains to enjoy the feeling of freedom it gives me. I’m a very communicative person, I fluently speak Italian, German, French English, and Spanish and love travelling.

I'm the QGIS.org Chair, serve on the OSGeo board as VP Europe and work as CEO of OPENGIS.ch which I founded in 2011. Since 2014 I share the company ownership with Matthias Kuhn. At OPENGIS.ch LLC we develop, train and consult our client on any aspect related to QGIS, QField, PostGIS and WebGIS technologies.

I first came in contact with the OSGEO world during my BSc when the University of Zurich was teaching us proprietary products and I started looking around for Open Source alternatives and started using QuantumGIS “Simon (0.6)”. In 2008, when starting my MSc, I made the definitive switch to Ubuntu and I started working more and more with QuantumGIS Metis (0.11) and ended developing some plugins and part of Globe as my Masters' thesis.

Since then my whole work has pivoted around QGIS and enabling people and companies to embrace opensource for their GIS needs.

=== My vision ===
Serving as a pragmatic community conciliator - collecting thoughts from people with differing opinions and trying to find the high road through difficult issues I want to focus my and the community's energies on being inclusive and forward-thinking.

I see FOSS as a very socially responsible way to develop software, but even more, I see the immense technological advantage that writing open-source code brings. This is why I always strive to allow both pragmatic and ideological views to respectfully coexist and enrich each other.

=== What you have done within the community in the past ===
* OSGeo Board member since 2021 (VP Europe)
* QGIS contributor since 2011
* QGIS.org Chair since 2020
* QGIS.org Vice-Chair 2018-2020
* QField (originally QGIS for android) creator
* FOSS4G Session Leader, various FOSS4G Talks and workshops
* Charter Member since 2018
* Google Summer of Code 2012: Mentor
* Google Summer of Code 2011: Student Developer

=== What your interests are in terms of the board ===

One of my main motivations to be part of the board is to help OSGeo keep its incredible growth rate by being even more attractive to new community members, sponsors and large/corporate users. To achieve this, to me the key is maintaining the right balance between sustainable processes and helping interesting and motivating grassroots projects.

=== Any things that you would like to change or introduce ===
As still fairly technical driven person, I like to understand the inner workings of things and projects before commenting on changes :)

=== What role you would wish to fulfil on the board (if any) ===
I am open to any role based on how I could best serve the board.

== Matthew Hanson - United States ([https://www.osgeo.org/member/hanson/ OSGeo profile]) ==

=== About me ===

I’m Matthew Hanson. I first attended FOSS4G in 2011 and have since participated in 10 international FOSS4G and 8 FOSS4G North America conferences. That first FOSS4G changed the course of my career, and made it clear this was the community and work I wanted to be part of.

I work in Earth observation and geospatial software, focusing on cloud‑native architectures, open standards, and open‑source tooling. I’m best known for my work on STAC and related efforts, and for talks and writing aimed at making interoperable geospatial systems more accessible. I currently work at Element 84 at the intersection of open source, commercial Earth observation, and operational systems.

=== My vision ===

I see OSGeo as a truly international foundation that brings together open‑source geospatial communities that have, over time, diverged across projects, regions, and domains. OSGeo has a unique role to play in helping these communities reconnect, share practices, and recognize their common ground.

I also believe OSGeo can help welcome people who are already using and contributing to open‑source geospatial software, but do not yet see themselves as part of the OSGeo community. By acting as a neutral, inclusive convening space, OSGeo can strengthen collaboration, elevate shared standards and values, and help the community adapt to a rapidly evolving geospatial ecosystem.

=== What you have done within the community in the past ===

My work has focused on standards, interoperability, and community education. I am a core contributor and long‑term advocate for STAC and have served on the STAC Steering Committee since its inception. I am also a member of the editorial board of the Cloud‑Native Geospatial Forum.

I regularly speak at FOSS4G (global and North America) and related events, and write about cloud‑native geospatial systems and open standards. Much of my work bridges open‑source projects, public agencies, and commercial satellite data providers to enable practical adoption and interoperability.

=== What your interests are in terms of the board ===

As a board member, I am interested in strengthening OSGeo’s international presence and supporting collaboration across the community. In particular, I want to help bring together open‑source geospatial communities that have grown apart, and help welcome practitioners who are already part of the ecosystem but may not yet identify with OSGeo.

I am also interested in how OSGeo can continue to evolve alongside emerging developer communities and modern software development practices, including the impact of cloud-native development and AI-assisted coding on how open-source projects are built, discovered, and sustained. I see OSGeo as a natural place to convene thoughtful, inclusive conversations around these changes.

Finally, I am interested in strengthening coordination between global and regional FOSS4G conferences, so that regional events and the global conference reinforce each other and contribute to a healthy, connected international community.

=== Any things that you would like to change or introduce ===

If elected, I would like to help OSGeo strengthen connections across its diverse projects and communities, including those that operate somewhat independently today. I would also like to focus on outreach to practitioners who already rely on open‑source geospatial software but are not yet engaged with OSGeo, and encourage more cross‑project dialogue to reduce fragmentation.

=== What role you would wish to fulfill on the board (if any) ===

As a first‑time board member, my focus would be on contributing, learning, and supporting the existing board and its leadership. I respect the work of current board members and am open to serving in whatever role best supports the board and the broader OSGeo community.

== Rajat Shinde - India (Currently, residing in the US) ([https://www.osgeo.org/member/shinde OSGeo profile]) ==

=== About me ===
I’m Rajat Shinde, a computer scientist and GIS practitioner from India, currently based in the United States, working with the NASA Office of Data Science and Informatics at NASA Marshall Space Flight Center (MSFC) and the University of Alabama in Huntsville. I hold a Ph.D. in Geographical Information Systems and have worked across academia and industry on geospatial data science, AI, and Earth observation applications.

I first joined the OSGeo community at FOSS4G in 2017. I was elected to the OSGeo Board in 2021 and re-elected in 2023. I focus on bridging communities through collaborations with OGC, IEEE (including IEEE GRSS), and MLCommons, and on strengthening contributor pathways via student programs. I serve as a Project Steering Committee (PSC) member for pgRouting and ZOO-Project, and I have been a long-term Google Summer of Code mentor and organization administrator.

=== My vision ===
My vision is to make OSGeo easier to join and easier to stay in, suggesting clear pathways to new members for contributing and growing into long-term community leaders.

I also want to strengthen a progressive, globally representative FOSS4G ecosystem that collaborates with other open-source communities to advance open standards and interoperability. I will continue supporting OSGeo India and GeoBharat to expand participation and sustained contributions in India along with other regional GIS initiatives.

=== What you have done within the community in the past ===
* OSGeo Board: Vice President (2023–2025); elected Board member (2021, re-elected 2023)
* FOSS4G-Asia Program Committee 2026
* Standards + collaboration: OSGeo Standards Committee representative at OGC Geo-Huntsville 2023; OSGeo–OGC–ASF joint code sprint participant
* FOSS4G: FOSS4G 2021 session leader; FOSS4G Asia workshop contributor/speaker
* Project governance: PSC member (ZOO-Project, pgRouting)
* Education + outreach: UN OSGeo Education Challenge 2021 mentor (pgRouting track); engaged with UN OpenGIS and UN GeoAI WGs
* Contributor pipeline: GSoC student (2017), mentor (2018–present), org admin (2020–present); Google Code-in mentor (2019)
* Community resources: Contributor to the Cloud-native Geospatial Guide
* GeoAI interoperability: Leading GeoAI metadata standard work supporting OSGeo projects (e.g., ZOO-Project) and TorchGeo
* Open source quality: JOSS manuscript reviewer (geospatial/geoscience software)

=== What your interests are in terms of the board ===
- To strengthen OSGeo’s external collaborations and long-term sustainability. I want to bring in more partnerships, MoUs, and sponsorships—aligned with OSGeo values—to better support projects, events, and community programs, with a specific focus on expanding relationships across Asia (including India, Japan, Nepal, and other regional hubs).

- Finally, as GIS evolves rapidly (cloud-native, data/AI-driven, reproducibility, and open standards), I want OSGeo to continue serving as the foundation for spreading responsible and trustworthy FOSS4G practices through deeper collaboration with adjacent open-source communities and standards bodies. As OSGeo approaches its 20-year milestone in 2026, this will help in defining a roadmap towards stronger OSGeo family.

=== Any things that you would like to change or introduce ===
I would like to strengthen on two points-
* Stronger links between regional and global FOSS4G: lightweight coordination and shared practices so regional events gain visibility/support, and global activities reflect regional priorities.
* More joint work with peer communities: expand cross-community collaborations (e.g., OSGeo–OGC joint code sprints and standards-aligned activities) to strengthen interoperable, responsible FOSS4G.

=== What role you would wish to fulfill on the board (if any) ===
I am open to any role deemed fit by the board.

[[Category:Elections]]
[[Category:Election 2025]]

Google Summer of Code 2025 Ideas

2025-02-11T01:57:15Z

RajatShinde: /* OSGeo Foundation graduated project */

Board Meeting 2024-04-30

2024-04-29T23:41:29Z

RajatShinde:

This board meeting is '''scheduled Tuesday 30 April 2024''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=04&day=30&hour=18&min=0&sec=0&p1=250&p2=26&p3=49&p4=155&p5=51&p6=312 '''18:00''' UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board Loomio] and actions on the [https://git.osgeo.org/gitea/osgeo/todo/issues OSGeo todo] issue tracker.

== Agenda ==

=== Current items ===

# ''roll call''
# ''appoint meeting chair, meeting scribe/secretary''
# ''Review and approve past minutes''
#* [[Board_Meeting_2024-03-26]]
# Executive positions (continued)
# OSGeo BoF at FOSS4G Europe status - OSGeo meeting plans
# “How to Sponsor” text done, draft page on website
# FOSS4G SotM Oceania TGP Request [https://lists.osgeo.org/pipermail/board/2024-April/013520.html]
# EC funding for FOSS4G Europe 2024
# GeoStyler code sprint funding request
# MDM2024: Collaboration proposal [https://lists.osgeo.org/pipermail/board/2024-April/013519.html]
# Utilization of a new room on meet.osgeo.org for local chapters [https://lists.osgeo.org/pipermail/board/2024-April/013523.html]
# OSGeo deal with Geo Week 2025 Event
# Review pending actions
# FOSS4G 2024 Belem TGP Request
# ''Add your topic here''

== Minutes ==

* Presiding:
* Scribing:
* Attending:
* Guests:

=== Actions ===

* See https://git.osgeo.org/gitea/osgeo/todo/issues

== IRC Log ==
* no log, Jitsi meeting

== Next meeting ==
*[[Board Meeting 2024-05-28]]

[[Category:Board]]
[[Category:Board Meetings 2024]]

Board Meeting 2024-04-30

2024-04-25T14:22:52Z

RajatShinde: Adding agenda topic

This board meeting is '''scheduled Tuesday 30 April 2024''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=04&day=30&hour=18&min=0&sec=0&p1=250&p2=26&p3=49&p4=155&p5=51&p6=312 '''18:00''' UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board Loomio] and actions on the [https://git.osgeo.org/gitea/osgeo/todo/issues OSGeo todo] issue tracker.

== Agenda ==

=== Current items ===

# ''roll call''
# ''appoint meeting chair, meeting scribe/secretary''
# ''Review and approve past minutes''
#* [[Board_Meeting_2024-03-26]]
# Executive positions (continued)
# OSGeo BoF at FOSS4G Europe status
# “How to Sponsor” text progress
# Review pending actions
# Utilization of a new room on meet.osgeo.org for local chapters
# ''Add your topic here''

== Minutes ==

* Presiding:
* Scribing:
* Attending:
* Guests:

=== Actions ===

* See https://git.osgeo.org/gitea/osgeo/todo/issues

== IRC Log ==
* no log, Jitsi meeting

== Next meeting ==
*[[Board Meeting 2024-05-28]]

[[Category:Board]]
[[Category:Board Meetings 2024]]

Google Summer of Code 2024 Ideas

2024-02-05T19:10:21Z

RajatShinde: Add GRASS Ideas

Google Summer of Code 2024 Ideas

2024-02-05T01:23:38Z

RajatShinde: /* The ideas pages */

Provenance Review pgRouting

2024-01-30T02:17:22Z

RajatShinde: /* Committers */ minor changes

=pgRouting Provenance Review=

== Project History ==
pgRouting is an extension of PostGIS and PostgreSQL geospatial database and adds routing and other network analysis functionality. A predecessor of pgRouting – pgDijkstra, written by Sylvain Pasche from Camptocamp, was later extended by Orkney and renamed to pgRouting. The project is now supported and maintained by Georepublic, Paragon Corporation and a broad user community.

==Libraries==

''List or reference a table of included libraries and/or components. Include:''
* ''Library Name''
* ''License''
* ''Whether the library license is compatible with the project''
* ''Whether the library is compiled into the project's releases, or required as an external dependancy''
* ''Whether the library is included in the project's code repository''
* ''Issue? (link if issue if one exists)''
* ''Ok? (Yes/No/Black - implies not checked yet)''
* ''Comment(s)''

{| class="wikitable" border="1"
! Library !! License !! Compatible? !! Included in core? !! Issue(s)? !! Ok? !! Comments
|-
| PostgresSQL || PostgreSQL License || yes || no|| no || yes || Not shipped or included on pgRouting repository
|-
| Boost Graph || Boost Software License || yes || no || no || yes || License included in the repository
|-
| Sphinx || 2-Clause BSD || yes || no|| no || yes ||Not shipped or included on pgRouting repository
|-
| python || PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 || yes || no || no || yes ||Not shipped or included on pgRouting repository
|-
| perl || GNU General Public License v2.0 or later || yes || no || no || yes ||Not shipped or included on pgRouting repository
|-
| pgtap || Copyright (c) 2008-2023 David E. Wheeler. Some rights reserved. || yes || no|| no || yes ||Not shipped or included on pgRouting repository
|-
| PostGIS || GNU General Public License v2.0 or later || yes || no || no || yes ||Not shipped or included on pgRouting repository
|}

Note: CGAL was used on versions < 3.0.0 Those versions are no longer supported

==Source Files==

''List of source files, including code, documentation and data, including:''
* ''File name''
* ''License''
* ''Copyright Holder (if known)''
* ''License header included?''
* ''Issue? (link if issue if one exists)''
* Ok''? (Yes/No/Black implies not checked yet)''
* ''Comment(s)''

{| class="wikitable" border="1"
! File !! Licence !! Copyright Holder !! Issue(s)? !! Licenced? !! Ok? !! Comments
|-
| include/allpairs/pgr_allpairs.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/alphaShape/pgr_alphaShape.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/astar/astar.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bdAstar/bdAstar.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bdDijkstra/pgr_bdDijkstra.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bellman_ford/pgr_bellman_ford.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bellman_ford/pgr_edwardMoore.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/breadthFirstSearch/pgr_binaryBreadthFirstSearch.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/breadthFirstSearch/pgr_breadthFirstSearch.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/check_parameters.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/debug_macro.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/e_report.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/pgdata_getters.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/postgres_connection.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/time_msg.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/circuits_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/contracted_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/coordinate_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/costFlow_t.h || GPLv2 || Maoguang Wang || n/a || yes || yes ||
|-
| include/c_types/delauny_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/edge_bool_t_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/edge_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/edge_xy_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/flow_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/geom_text_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/graph_enum.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/i_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/ii_t_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/iid_t_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/info_t.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/line_graph_full_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/mst_rt.h || GPLv2 || Aditya Pratap Singh || n/a || yes || yes ||
|-
| include/c_types/path_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/pickDeliver/orders_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/pickDeliver/schedule_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/pickDeliver/vehicle_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/point_on_edge_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/restriction_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/routes_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/stoerWagner_t.h || GPLv2 || Aditya Pratap Singh || n/a || yes || yes ||
|-
| include/c_types/transitiveClosure_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/trsp/trsp.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/tsp_tour_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/chinese/pgr_chinesePostman.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/circuits/hawickcircuits.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/coloring/pgr_bipartite_driver.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/coloring/pgr_edgeColoring.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/coloring/pgr_sequentialVertexColoring.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/components/componentsResult.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/components/pgr_components.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/components/pgr_makeConnected.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/ch_graphs.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_contract.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_contractionGraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_deadEndContraction.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_linearContraction.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/Dmatrix.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/basePath_SSEC.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/basic_edge.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/basic_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/bline.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/bpoint.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/ch_edge.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/ch_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/combinations.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/compPaths.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/get_check_data.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/get_data.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/identifier.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/identifiers.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/interruption.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/line_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/linear_directed_graph.h || GPLv2 || Anthony Nicola Tasca || n/a || yes || yes ||
|-
| include/cpp_common/path_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgdata_fetchers.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_alloc.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_assert.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_base_graph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_bidirectional.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_messages.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/rule.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/signalhandler.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/xy_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dagShortestPath/pgr_dagShortestPath.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dijkstra/dijkstra.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dijkstra/drivingDist.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dijkstra/pgr_dijkstraVia.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dominator/pgr_lengauerTarjanDominatorTree_driver.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/allpairs/floydWarshall_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/allpairs/johnson_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/alpha_shape/alphaShape_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/astar/astar_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bdAstar/bdAstar_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bdDijkstra/bdDijkstra_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bellman_ford/bellman_ford_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bellman_ford/bellman_ford_neg_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bellman_ford/edwardMoore_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/breadthFirstSearch/binaryBreadthFirstSearch_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/breadthFirstSearch/breadthFirstSearch_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/chinese/chinesePostman_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/circuits/hawickcircuits_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/coloring/bipartite_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/coloring/edgeColoring_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/coloring/sequentialVertexColoring_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/articulationPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/biconnectedComponents_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/bridges_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/connectedComponents_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/makeConnected_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/strongComponents_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/contraction/contractGraph_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dagShortestPath/dagShortestPath_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dijkstra/dijkstraVia_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dijkstra/dijkstra_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dominator/lengauerTarjanDominatorTree_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/driving_distance/drivedist_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/driving_distance/withPoints_dd_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/lineGraph/lineGraphFull_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/lineGraph/lineGraph_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/edge_disjoint_paths_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/max_flow_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/maximum_cardinality_matching_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/minCostMaxFlow_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/mincut/stoerWagner_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/ordering/cuthillMckeeOrdering_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/pickDeliver/pickDeliverEuclidean_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/pickDeliver/pickDeliver_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/planar/boyerMyrvold_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/planar/isPlanar_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/kruskal_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/mst_common.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/prim_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/randomSpanningTree_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/topologicalSort/topologicalSort_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/transitiveClosure/transitiveClosure_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/traversal/depthFirstSearch_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trspVia_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trspVia_withPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trsp_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trsp_withPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/tsp/TSP_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/tsp/euclideanTSP_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/withPoints/get_new_queries.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/withPoints/withPointsVia_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/withPoints/withPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/yen/ksp_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/yen/turnRestrictedPath_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/yen/withPoints_ksp_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/lineGraph/pgr_lineGraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/lineGraph/pgr_lineGraphFull.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_costFlowGraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_flowgraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_maxflow.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_maximumcardinalitymatching.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_minCostMaxFlow.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/mincut/pgr_stoerWagner.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/ordering/cuthillMckeeOrdering.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/planar/pgr_boyerMyrvold.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/details.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_kruskal.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_mst.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_prim.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_randomSpanningTree.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/topologicalSort/pgr_topologicalSort.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/transitiveClosure/pgr_transitiveClosure.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/traversal/pgr_depthFirstSearch.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/GraphDefinition.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/edgeInfo.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/pgr_trspHandler.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/trsp_core.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/tsp/tsp.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/astar_visitors.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/dfs_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/dfs_visitor_with_root.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/dijkstra_visitors.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/edges_order_bfs_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/edges_order_dfs_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/found_goals.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/prim_dijkstra_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/book_keeping.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/dnode.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/fleet.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/initial_solution.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/initials_code.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/optimize.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/order.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/pd_orders.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/pd_problem.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/pgr_pickDeliver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/solution.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/tw_node.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/vehicle.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/vehicle_node.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/vehicle_pickDeliver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/withPoints/pgr_withPoints.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/yen/pgr_ksp.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/yen/pgr_turnRestrictedPath.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/floydWarshall.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/floydWarshall_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/johnson.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/johnson_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/alpha_shape/alphaShape.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/alpha_shape/alphaShape_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/alpha_shape/pgr_alphaShape.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/astar/astar.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/astar/astar_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdAstar/bdAstar.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdAstar/bdAstar_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdDijkstra/bdDijkstra.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdDijkstra/bdDijkstra_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford_neg.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford_neg_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/edwardMoore.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/edwardMoore_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/binaryBreadthFirstSearch.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/binaryBreadthFirstSearch_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/breadthFirstSearch.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/breadthFirstSearch_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/chinese/chinesePostman.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/chinese/chinesePostman_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/circuits/hawickCircuits.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/circuits/hawickCircuits_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/bipartite.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/bipartite_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/edgeColoring.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/edgeColoring_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/pgr_edgeColoring.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/sequentialVertexColoring.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/sequentialVertexColoring_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/basePath_SSEC.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/basic_edge.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/basic_vertex.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/ch_edge.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/ch_vertex.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/check_parameters.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/e_report.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/identifier.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/pgr_alloc.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/pgr_assert.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/postgres_connection.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/signalhandler.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/time_msg.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/xy_vertex.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/articulationPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/articulationPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/biconnectedComponents.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/biconnectedComponents_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/bridges.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/bridges_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/componentsResult.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/connectedComponents.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/connectedComponents_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/makeConnected.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/makeConnected_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/pgr_components.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/strongComponents.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/strongComponents_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/contraction/contractGraph.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/contraction/contractGraph_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/contraction/pgr_contract.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/Dmatrix.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/arrays_input.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/bpoint.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/combinations.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/compPaths.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/get_check_data.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/pgdata_fetchers.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/pgdata_getters.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/pgr_messages.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/rule.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dagShortestPath/dagShortestPath.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dagShortestPath/dagShortestPath_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstra.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstraVia.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstraVia_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstra_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dominator/lengauerTarjanDominatorTree.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dominator/lengauerTarjanDominatorTree_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/driving_distance/drivedist_driver.cpp || GPLv2 || pgRouting developers || n/a || yes ||
|-
| src/driving_distance/many_to_dist_driving_distance.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/driving_distance/many_to_dist_withPointsDD.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/driving_distance/withPoints_dd_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/ksp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/ksp_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/turnRestrictedPath.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/turnRestrictedPath_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/withPoints_ksp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/withPoints_ksp_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraph.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraphFull.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraphFull_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraph_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/edge_disjoint_paths.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/edge_disjoint_paths_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/max_flow.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/max_flow_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/maximum_cardinality_matching.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/maximum_cardinality_matching_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/minCostMaxFlow.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/minCostMaxFlow_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/pgr_flowgraph.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/pgr_maxflow.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/pgr_minCostMaxFlow.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/mincut/stoerWagner.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/mincut/stoerWagner_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ordering/cuthillMckeeOrdering.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ordering/cuthillMckeeOrdering_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/book_keeping.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/dnode.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/fleet.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/initial_solution.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/optimize.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/order.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pd_orders.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pd_problem.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pgr_pickDeliver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliver.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliverEuclidean.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliverEuclidean_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliver_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/solution.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/tw_node.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/vehicle.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/vehicle_node.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/vehicle_pickDeliver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/boyerMyrvold.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/boyerMyrvold_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/isPlanar.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/isPlanar_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/details.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/kruskal.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/kruskal_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/mst_common.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/prim.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/prim_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/randomSpanningTree.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/randomSpanningTree_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/topologicalSort/topologicalSort.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/topologicalSort/topologicalSort_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/transitiveClosure/transitiveClosure.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/transitiveClosure/transitiveClosure_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/traversal/depthFirstSearch.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/traversal/depthFirstSearch_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/GraphDefinition.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/edgeInfo.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/new_trsp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/pgr_trspHandler.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia_withPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia_withPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_core.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_withPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_withPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/TSP.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/TSP_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/euclideanTSP.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/euclideanTSP_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/tsp.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/version/version.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/get_new_queries.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/pgr_withPoints.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPointsVia.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPointsVia_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|}

==Copyright Holders==

''List or reference all copyright holders of the project's source files. These are all the people that would need to be contacted if the license of the project is to be changed. List:''

* ''Organisation or person''
* ''Contact details for Organisation or person''
* ''Issue? (link if issue if one exists)''
* ''Comments''

See
* https://github.com/pgRouting/pgrouting/issues/2527
* https://docs.pgrouting.org/3.6/en/pgRouting-introduction.html#contributors-past-present

== Committers ==
''List or reference a table of committers, including:''
* ''Committer name''
* ''Commit username in code repository''
* ''Committer's employer(s) (if applicable)''
* ''Committer (or employer) has signed contribution agreement? (yes/no)''

List of contributors and status can be found here:
* https://github.com/pgRouting/pgrouting/issues/2527
* https://github.com/orgs/pgRouting/teams/pgrouting

==Further Issues ==
''List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.''

[[Category: Incubation]]

Provenance Review pgRouting

2024-01-30T02:17:02Z

RajatShinde: /* Committers */ Remove TODO

=pgRouting Provenance Review=

== Project History ==
pgRouting is an extension of PostGIS and PostgreSQL geospatial database and adds routing and other network analysis functionality. A predecessor of pgRouting – pgDijkstra, written by Sylvain Pasche from Camptocamp, was later extended by Orkney and renamed to pgRouting. The project is now supported and maintained by Georepublic, Paragon Corporation and a broad user community.

==Libraries==

''List or reference a table of included libraries and/or components. Include:''
* ''Library Name''
* ''License''
* ''Whether the library license is compatible with the project''
* ''Whether the library is compiled into the project's releases, or required as an external dependancy''
* ''Whether the library is included in the project's code repository''
* ''Issue? (link if issue if one exists)''
* ''Ok? (Yes/No/Black - implies not checked yet)''
* ''Comment(s)''

{| class="wikitable" border="1"
! Library !! License !! Compatible? !! Included in core? !! Issue(s)? !! Ok? !! Comments
|-
| PostgresSQL || PostgreSQL License || yes || no|| no || yes || Not shipped or included on pgRouting repository
|-
| Boost Graph || Boost Software License || yes || no || no || yes || License included in the repository
|-
| Sphinx || 2-Clause BSD || yes || no|| no || yes ||Not shipped or included on pgRouting repository
|-
| python || PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 || yes || no || no || yes ||Not shipped or included on pgRouting repository
|-
| perl || GNU General Public License v2.0 or later || yes || no || no || yes ||Not shipped or included on pgRouting repository
|-
| pgtap || Copyright (c) 2008-2023 David E. Wheeler. Some rights reserved. || yes || no|| no || yes ||Not shipped or included on pgRouting repository
|-
| PostGIS || GNU General Public License v2.0 or later || yes || no || no || yes ||Not shipped or included on pgRouting repository
|}

Note: CGAL was used on versions < 3.0.0 Those versions are no longer supported

==Source Files==

''List of source files, including code, documentation and data, including:''
* ''File name''
* ''License''
* ''Copyright Holder (if known)''
* ''License header included?''
* ''Issue? (link if issue if one exists)''
* Ok''? (Yes/No/Black implies not checked yet)''
* ''Comment(s)''

{| class="wikitable" border="1"
! File !! Licence !! Copyright Holder !! Issue(s)? !! Licenced? !! Ok? !! Comments
|-
| include/allpairs/pgr_allpairs.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/alphaShape/pgr_alphaShape.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/astar/astar.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bdAstar/bdAstar.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bdDijkstra/pgr_bdDijkstra.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bellman_ford/pgr_bellman_ford.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/bellman_ford/pgr_edwardMoore.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/breadthFirstSearch/pgr_binaryBreadthFirstSearch.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/breadthFirstSearch/pgr_breadthFirstSearch.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/check_parameters.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/debug_macro.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/e_report.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/pgdata_getters.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/postgres_connection.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_common/time_msg.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/circuits_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/contracted_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/coordinate_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/costFlow_t.h || GPLv2 || Maoguang Wang || n/a || yes || yes ||
|-
| include/c_types/delauny_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/edge_bool_t_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/edge_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/edge_xy_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/flow_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/geom_text_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/graph_enum.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/i_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/ii_t_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/iid_t_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/info_t.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/line_graph_full_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/mst_rt.h || GPLv2 || Aditya Pratap Singh || n/a || yes || yes ||
|-
| include/c_types/path_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/pickDeliver/orders_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/pickDeliver/schedule_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/pickDeliver/vehicle_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/point_on_edge_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/restriction_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/routes_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/stoerWagner_t.h || GPLv2 || Aditya Pratap Singh || n/a || yes || yes ||
|-
| include/c_types/transitiveClosure_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/trsp/trsp.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/c_types/tsp_tour_rt.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/chinese/pgr_chinesePostman.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/circuits/hawickcircuits.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/coloring/pgr_bipartite_driver.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/coloring/pgr_edgeColoring.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/coloring/pgr_sequentialVertexColoring.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/components/componentsResult.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/components/pgr_components.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/components/pgr_makeConnected.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/ch_graphs.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_contract.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_contractionGraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_deadEndContraction.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/contraction/pgr_linearContraction.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/Dmatrix.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/basePath_SSEC.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/basic_edge.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/basic_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/bline.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/bpoint.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/ch_edge.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/ch_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/combinations.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/compPaths.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/get_check_data.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/get_data.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/identifier.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/identifiers.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/interruption.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/line_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/linear_directed_graph.h || GPLv2 || Anthony Nicola Tasca || n/a || yes || yes ||
|-
| include/cpp_common/path_t.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgdata_fetchers.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_alloc.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_assert.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_base_graph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_bidirectional.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/pgr_messages.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/rule.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/signalhandler.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/cpp_common/xy_vertex.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dagShortestPath/pgr_dagShortestPath.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dijkstra/dijkstra.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dijkstra/drivingDist.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dijkstra/pgr_dijkstraVia.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/dominator/pgr_lengauerTarjanDominatorTree_driver.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/allpairs/floydWarshall_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/allpairs/johnson_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/alpha_shape/alphaShape_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/astar/astar_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bdAstar/bdAstar_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bdDijkstra/bdDijkstra_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bellman_ford/bellman_ford_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bellman_ford/bellman_ford_neg_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/bellman_ford/edwardMoore_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/breadthFirstSearch/binaryBreadthFirstSearch_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/breadthFirstSearch/breadthFirstSearch_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/chinese/chinesePostman_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/circuits/hawickcircuits_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/coloring/bipartite_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/coloring/edgeColoring_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/coloring/sequentialVertexColoring_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/articulationPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/biconnectedComponents_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/bridges_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/connectedComponents_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/makeConnected_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/components/strongComponents_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/contraction/contractGraph_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dagShortestPath/dagShortestPath_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dijkstra/dijkstraVia_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dijkstra/dijkstra_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/dominator/lengauerTarjanDominatorTree_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/driving_distance/drivedist_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/driving_distance/withPoints_dd_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/lineGraph/lineGraphFull_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/lineGraph/lineGraph_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/edge_disjoint_paths_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/max_flow_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/maximum_cardinality_matching_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/max_flow/minCostMaxFlow_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/mincut/stoerWagner_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/ordering/cuthillMckeeOrdering_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/pickDeliver/pickDeliverEuclidean_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/pickDeliver/pickDeliver_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/planar/boyerMyrvold_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/planar/isPlanar_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/kruskal_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/mst_common.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/prim_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/spanningTree/randomSpanningTree_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/topologicalSort/topologicalSort_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/transitiveClosure/transitiveClosure_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/traversal/depthFirstSearch_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trspVia_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trspVia_withPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trsp_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/trsp/trsp_withPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/tsp/TSP_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/tsp/euclideanTSP_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/withPoints/get_new_queries.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/withPoints/withPointsVia_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/withPoints/withPoints_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/yen/ksp_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/yen/turnRestrictedPath_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/drivers/yen/withPoints_ksp_driver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/lineGraph/pgr_lineGraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/lineGraph/pgr_lineGraphFull.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_costFlowGraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_flowgraph.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_maxflow.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_maximumcardinalitymatching.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/max_flow/pgr_minCostMaxFlow.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/mincut/pgr_stoerWagner.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/ordering/cuthillMckeeOrdering.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/planar/pgr_boyerMyrvold.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/details.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_kruskal.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_mst.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_prim.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/spanningTree/pgr_randomSpanningTree.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/topologicalSort/pgr_topologicalSort.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/transitiveClosure/pgr_transitiveClosure.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/traversal/pgr_depthFirstSearch.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/GraphDefinition.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/edgeInfo.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/pgr_trspHandler.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/trsp/trsp_core.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/tsp/tsp.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/astar_visitors.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/dfs_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/dfs_visitor_with_root.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/dijkstra_visitors.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/edges_order_bfs_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/edges_order_dfs_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/found_goals.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/visitors/prim_dijkstra_visitor.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/book_keeping.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/dnode.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/fleet.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/initial_solution.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/initials_code.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/optimize.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/order.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/pd_orders.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/pd_problem.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/pgr_pickDeliver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/solution.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/tw_node.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/vehicle.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/vehicle_node.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/vrp/vehicle_pickDeliver.h || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/withPoints/pgr_withPoints.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/yen/pgr_ksp.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| include/yen/pgr_turnRestrictedPath.hpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/floydWarshall.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/floydWarshall_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/johnson.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/allpairs/johnson_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/alpha_shape/alphaShape.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/alpha_shape/alphaShape_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/alpha_shape/pgr_alphaShape.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/astar/astar.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/astar/astar_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdAstar/bdAstar.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdAstar/bdAstar_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdDijkstra/bdDijkstra.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bdDijkstra/bdDijkstra_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford_neg.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/bellman_ford_neg_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/edwardMoore.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/bellman_ford/edwardMoore_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/binaryBreadthFirstSearch.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/binaryBreadthFirstSearch_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/breadthFirstSearch.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/breadthFirstSearch/breadthFirstSearch_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/chinese/chinesePostman.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/chinese/chinesePostman_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/circuits/hawickCircuits.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/circuits/hawickCircuits_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/bipartite.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/bipartite_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/edgeColoring.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/edgeColoring_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/pgr_edgeColoring.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/sequentialVertexColoring.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/coloring/sequentialVertexColoring_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/basePath_SSEC.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/basic_edge.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/basic_vertex.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/ch_edge.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/ch_vertex.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/check_parameters.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/e_report.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/identifier.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/pgr_alloc.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/pgr_assert.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/postgres_connection.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/signalhandler.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/time_msg.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/common/xy_vertex.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/articulationPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/articulationPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/biconnectedComponents.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/biconnectedComponents_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/bridges.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/bridges_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/componentsResult.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/connectedComponents.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/connectedComponents_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/makeConnected.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/makeConnected_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/pgr_components.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/strongComponents.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/components/strongComponents_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/contraction/contractGraph.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/contraction/contractGraph_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/contraction/pgr_contract.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/Dmatrix.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/arrays_input.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/bpoint.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/combinations.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/compPaths.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/get_check_data.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/pgdata_fetchers.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/pgdata_getters.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/pgr_messages.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/cpp_common/rule.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dagShortestPath/dagShortestPath.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dagShortestPath/dagShortestPath_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstra.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstraVia.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstraVia_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dijkstra/dijkstra_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dominator/lengauerTarjanDominatorTree.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/dominator/lengauerTarjanDominatorTree_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/driving_distance/drivedist_driver.cpp || GPLv2 || pgRouting developers || n/a || yes ||
|-
| src/driving_distance/many_to_dist_driving_distance.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/driving_distance/many_to_dist_withPointsDD.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/driving_distance/withPoints_dd_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/ksp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/ksp_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/turnRestrictedPath.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/turnRestrictedPath_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/withPoints_ksp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ksp/withPoints_ksp_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraph.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraphFull.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraphFull_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/lineGraph/lineGraph_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/edge_disjoint_paths.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/edge_disjoint_paths_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/max_flow.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/max_flow_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/maximum_cardinality_matching.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/maximum_cardinality_matching_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/minCostMaxFlow.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/minCostMaxFlow_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/pgr_flowgraph.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/pgr_maxflow.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/max_flow/pgr_minCostMaxFlow.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/mincut/stoerWagner.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/mincut/stoerWagner_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ordering/cuthillMckeeOrdering.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/ordering/cuthillMckeeOrdering_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/book_keeping.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/dnode.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/fleet.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/initial_solution.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/optimize.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/order.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pd_orders.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pd_problem.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pgr_pickDeliver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliver.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliverEuclidean.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliverEuclidean_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/pickDeliver_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/solution.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/tw_node.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/vehicle.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/vehicle_node.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/pickDeliver/vehicle_pickDeliver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/boyerMyrvold.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/boyerMyrvold_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/isPlanar.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/planar/isPlanar_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/details.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/kruskal.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/kruskal_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/mst_common.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/prim.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/prim_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/randomSpanningTree.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/spanningTree/randomSpanningTree_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/topologicalSort/topologicalSort.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/topologicalSort/topologicalSort_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/transitiveClosure/transitiveClosure.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/transitiveClosure/transitiveClosure_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/traversal/depthFirstSearch.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/traversal/depthFirstSearch_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/GraphDefinition.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/edgeInfo.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/new_trsp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/pgr_trspHandler.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia_withPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trspVia_withPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_core.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_withPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/trsp/trsp_withPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/TSP.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/TSP_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/euclideanTSP.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/euclideanTSP_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/tsp/tsp.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/version/version.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/get_new_queries.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/pgr_withPoints.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPoints.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPointsVia.c || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPointsVia_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|-
| src/withPoints/withPoints_driver.cpp || GPLv2 || pgRouting developers || n/a || yes || yes ||
|}

==Copyright Holders==

''List or reference all copyright holders of the project's source files. These are all the people that would need to be contacted if the license of the project is to be changed. List:''

* ''Organisation or person''
* ''Contact details for Organisation or person''
* ''Issue? (link if issue if one exists)''
* ''Comments''

See
* https://github.com/pgRouting/pgrouting/issues/2527
* https://docs.pgrouting.org/3.6/en/pgRouting-introduction.html#contributors-past-present

== Committers ==
''List or reference a table of committers, including:''
* ''Committer name''
* ''Commit username in code repository''
* ''Committer's employer(s) (if applicable)''
* ''Committer (or employer) has signed contribution agreement? (yes/no)''

List of contributors and status can be found here:
- https://github.com/pgRouting/pgrouting/issues/2527
- https://github.com/orgs/pgRouting/teams/pgrouting

==Further Issues ==
''List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.''

[[Category: Incubation]]

Election 2023 Candidate Manifestos

2023-12-30T04:12:39Z

RajatShinde:

A space for the candidates for election to the Board to share some information about themselves, their aspirations for OSGeo, what they would like to change, improve or introduce and what role they would like to play on the board.

You are welcome to follow the template, and add further relevant info as you need:

== Jeroen Ticheler - The Netherlands ([https://www.osgeo.org/member/jeroen-ticheler/ OSGeo profile]) ==

=== About me ===

Wageningen (The Netherlands), Ivory Coast and Mali were the places I grew up as a child. It brought me to study Tropical Forestry with a focus on GIS and Remote Sensing. Following graduation in 1997, I started working to support the Early Warning System for Food Security and the Desert Locust Early Warning System at the UN Food and Agricultural Organization (FAO) in Rome for nine years.

With the support of the FAO, I managed to start the development of GeoNetwork opensource around the year 2001, a catalog that allowed us to organise and release large quantities of geospatial data to the public.

In 2007, GeoCat was established and I moved back to The Netherlands. Besides everything geospatial, I love traveling, carpentry, slowly build an overland truck, study Analytical Psychology, and walk, work and live outside.

=== My vision ===

My vision is that geospatial knowledge can improve the way we live on our planet. That science requires the open software we jointly develop and that sustainable Free and Open Source Software projects require healthy businesses that commit themselves to contribute back responsibly.

We, as a community, can accomplish so much through local and global collaborations. Our projects and communities provide (the best) tools and knowledge accessible for all to benefit.

=== What you have done within the community in the past ===

Besides my involvement as PSC chair in the GeoNetwork opensource project, I have been involved as Charter member from 2006 onwards, served on the OSGeo Marketing and Conference Committees, as well as on the OSGeo Board. In the last 10+ years my involvement has mainly been in the form of a sponsor to OSGeo and FOSS4G (both global, regional and local) and by organising a yearly Code Sprint in Bolsena since 2007.

=== What your interests are in terms of the board ===

My mission is to connect people by connecting communities and information. I strongly promote the use of international standards and Free and Open Source Software for geographic data and information. I'll commit myself to help OSGeo to bring people together that collaborate, innovate and give back.

=== Any things that you would like to change or introduce ===

Responsible entrepreneurship will definitely be one of the things that has my attention. OSGeo needs to be a well balanced community of people from all parts of society, including volunteers, students and scientists, public servants and businesses.

=== What role you would wish to fulfil on the board (if any) ===

No preference at this stage, I'm willing to take up any role needed.

== Marco Bernasocchi, Switzerland ([https://www.osgeo.org/member/bernasocchi/ OSGeo profile]) ==

=== About me ===
I am an open-source advocate, consultant, teacher, and developer. My background is in geography with a specialization in geographic information science. I live in Switzerland in a small Romansh speaking mountain village where I love scrambling around the mountains to enjoy the feeling of freedom it gives me. I’m a very communicative person, I fluently speak Italian, German, French English, and Spanish and love travelling. I'm the QGIS.org Chair and work as CEO of OPENGIS.ch which I founded in 2011. Since 2014 I share the company ownership with Matthias Kuhn. At OPENGIS.ch LLC we develop, train and consult our client on any aspect related to QGIS, QField, PostGIS and WebGIS technologies.

I first came in contact with the OSGEO world during my BSc when the University of Zurich was teaching us proprietary products and I started looking around for Open Source alternatives and started using QuantumGIS “Simon (0.6)”. In 2008, when starting my MSc, I made the definitive switch to Ubuntu and I started working more and more with QuantumGIS Metis (0.11) and ended developing some plugins and part of Globe as my Masters' thesis.

Since then my whole work has pivoted around QGIS and enabling people and companies to embrace opensource for their GIS needs.

=== My vision ===
Serving as a pragmatic community conciliator - collecting thoughts from people with differing opinions and trying to find the high road through difficult issues I want to focus my and the community's energies on being inclusive and forward-thinking.

I see FOSS as a very socially responsible way to develop software, but even more, I see the immense technological advantage that writing open-source code brings. This is why I always strive to allow both pragmatic and ideological views to respectfully coexist and enrich each other.

=== What you have done within the community in the past ===
* QGIS contributor since 2011
* QGIS.org Chair since 2020
* QGIS.org Vice-Chair 2018-2020
* QField (originally QGIS for android) creator
* FOSS4G Session Leader, various FOSS4G Talks and workshops
* Charter Member since 2018
* Google Summer of Code 2012: Mentor
* Google Summer of Code 2011: Student Developer

=== What your interests are in terms of the board ===

One of my main motivations to be part of the board is to help OSGeo keep its incredible growth rate by being even more attractive to new community members, sponsors and large/corporate users. To achieve this, to me the key is maintaining the right balance between sustainable processes and helping interesting and motivating grassroots projects.

=== Any things that you would like to change or introduce ===
As still fairly technical driven person, I like to understand the inner workings of things and projects before commenting on changes :)

=== What role you would wish to fulfil on the board (if any) ===
I am open to any role based on how I could best serve the board.

== Vicky Vergara - Mexico ([https://www.osgeo.org/member/vicky-vergara/ OSGeo profile]) ==

=== About me ===

When I am in front of the computer, there can be an earthquake and I won't notice. I forget to eat, sometimes when I get hungry it's already time to go to bed.

That is something I do not recommend, but things change when I go to any FOSS4G:
* I take my autographs notebook and get many nice thoughts from members of the community.
* I like to talk to people,
* I like to see presentations
and these interactions let me know that there is a person behind that computer/software that I am using.

Also never forget to do some other non OSGeo related stuff like
* Learn how to grow nepenthes
* Continue with building my HMS Victory model ship
* Learn how to do egg tempera, idea that came from going to FOSS4G Florence and see its art.

=== My vision ===

Promote the development and use of Open Source Software.

=== What you have done within the community in the past ===
This 2023 was very intense.
* OSGeo board with all the work that comes with it, that is very interesting.
* pgRouting PSC with all the work that comes with it.
* Translating OSGeoLive, pgRouting.
* Doing improvements on pgRouting.
* Taking care of OSGeoLive documentation as part of my duties of PSC on OSGeoLive
* For the nth year, been a mentor on the Google Summer of Code program
* Been more active part on the SAC committee during the second semester.
* Participating in the UN-OPENGIS meetings
* Doing some contributions on Valhalla

=== What your interests are in terms of the board ===
For this term I will use the word scalability.

I am an Economist and Computer Scientist who lacks skills for example: cooking or doing accounting.
I am a volunteer at home so I cook when I remember that we need to eat, and try to do my best, of course my sons can do things like poached eggs or omelettes, but my limit is scrambled and sunny side broken.
I hire professionals, someone cooks for me, someone does my accounting.

In OSGeo, we are a growing community of volunteers. But are we scalable?

A volunteer do contributions when they have time to do contributions.
Some might be jobless, some might be be freelancers, some might be hired by companies that support their contributions to open source, and some might have jobs that do not, and many more situations that I can not even imagine.

The worst case scenario I can think of, (in chat form):
* Person X: (My job situation is unknown to you) and I do volunteering in A, B ,C, D, and E on OSGeo
* Person Z: Great!, please also do G
* Person X: OK
Time passes
* Person Z: Hmm, have you finished?
* Person X: No, I haven't got time
Time passes
* Person X: (Found a job on another industry / got sick / had an accident / life happens), can't do any more volunteering work

Who will do A~G after X leaves?

Since I arrived I see the same names in many different committees, working groups, etc.

We do things when we can, not necessarily when they need to be done. We do them the best we can.
We have are our limits on areas that we understand and try ti help when we have a small idea on what to do, but can't do no more than that. (like my cooking I can do up to a limit, but after that we go to a restaurant)

That way of working, where the few do most of the work on their volunteer time, is not scalable in my opinion.

I do not have a solution to this problem in a volunteer environment.
But at least I would like to start a discussion about it.

=== Any things that you would like to change or introduce ===

Scalability

=== What role you would wish to fulfill on the board (if any) ===

I am fine with the role that is assigned to me. But by preference, this time I would like someone else to be the vice-president of the Latin America area.

== Besfort Guri, Kosovo ([https://www.osgeo.org/member/guri/ OSGeo profile]) ==

=== About me ===

Besfort has been a hacktivist since 2009 in Kosovo, as a member of FLOSSK (Free Libre Open Source Software Kosova – flossk.org). He has been serving as a board member since 2015, and since 2020 he has been acting as President of the Executive Board of FLOSSK.

Since 2010 a mapper at OpenStreetMap, and a member at OSM Foundation since 2018. In 2019 FLOSSK became a Local Chapter at OSM, and Besfort is leading this Local Chapter, in 2019, FLOSSK with a lead of Besfort, organized State of the Map Southeast Europe – sotmsee.org. He is serving as a member of the Advisory Board of the Board of OpenStreetMap Foundation.

Besfort has been active in OSGeo for some years now as well, he has been serving as Charter Member since 2022. FLOSSK has been the local chapter of OSGeo since 2020, and he is leading as well this local chapter. He was part of the organizing team for the canceled FOSS4G 2021 Europe, now he is Co-Chair of the Program Committee at FOSS4G 2024 Europe. He was chair of FOSS4G 2023 in Prizren.

He runs a small company called OpS-IN (Open Spatial Information Network) where he develops different GIS systems. His two biggest projects that he implemented through the company are "SPAK – Spatial Planning Application for Kosovo", and "ACLIS – Albanian Cadastral Land Information System" Both projects have the entire architecture of the system, based on OSGeo projects, like PostgreSQL / PostGIS, QGIS, GeoServer, Open Layers etc.

=== My vision ===

Promote the development and use of FLOSS Software, more specifically FLOSS GIS.

=== What you have done within the community in the past ===

* Promote FLOSS (FLOSS GIS) in Balkan Area, in different aspects
* Part of the Organizing Committee of canceled FOSS4G 2021 Europe
* Chair of FOSS4G 2023 Prizren, Kosovo
* Co-Chair of Program Committee of FOSS4G Europe 2024

=== What your interests are in terms of the board ===

Focusing on responsible entrepreneurship in OSGeo, I aim to unite diverse communities—volunteers, students, scientists, public servants, and businesses. I bring expertise in Balkan community engagement and a commitment to nurturing entrepreneurship in developing nations. This multifaceted approach cultivates an inclusive ecosystem, driving both tech advancements and societal progress within OSGeo.

=== Any things that you would like to change or introduce ===

OSGeo wants a mix of people from everywhere—volunteers, students, scientists, public servants, and businesses—to build a balanced community. It's important to include countries at different stages of development, like those with growing economies and opportunities.

=== What role you would wish to fulfill on the board (if any) ===
I don't have any specific preference at this stage, I'm willing to take up any role needed.

== Rajat Shinde, Ph.D. - India/ (Currently residing in the United States of America) ([https://www.osgeo.org/member/shinde/ OSGeo profile]) ==

=== About me ===

Hey there! My name is Rajat (meaning ''shining like Silver'' in Hindi). I hail from India and currently, I am working as a Computer Scientist with NASA IMPACT / the University of Alabama in Huntsville (UAH). I have a Ph.D. degree in Geo-informatics with a specialization in LiDAR data processing using deep learning algorithms. During my Ph.D., I was a recipient of the Prime Minister's Research Fellowship conferred by the Government of India to selected doctoral candidates. Before diving into the spatial dimension, I used to be an Electronics and Communication Engineer.

In 2023, it is my continued nomination to be a member of the OSGeo Board of Directors. In 2021, I was nominated for the first time and got elected as the youngest-ever board member and subsequently as a Vice President of the OSGeo Board.

My journey with open-source (and OSGeo) started in 2017 when I got to attend and present at the FOSS4G Asia 2017. In the same year, I had an amazing experience in contributing to the MapMint project as a Google Summer of Code Student. From 2018 onwards, I am contributing as a GSoC Admin and mentor for the ZOO-Project and MapMint. Also, I serve as a Project Steering Committee (PSC) Member for the ZOO-Project and pgRouting projects (read: star_eyes). I was one of the mentors for the United Nations OSGeo Education Challenge 2021 for the pgRouting project and represented OSGeo during the Google Summer of Code Mentor Summit 2023 held in California, US.

When I look back in 2017, from where I started, I feel elated and equally responsible to be able to contribute back to the biggest and dynamic community for Free and Open Source Software. Moreover, I feel proud of being a part of this OSGeo community; of knowing great personalities, working with them, and encouraging new members to be a part of it.

When I am away from my laptop, I love to practice flute and read books.

[https://www.linkedin.com/in/rajat-shinde/ More details]

=== My vision ===
* Introduce new and young contributors to the OSGeo community via various initiatives
* Contribute to the OSGeo India and GeoBharat activities

=== What you have done within the community in the past ===

I have a short experience participating in diverse positions while being a part of the OSGeo community. A brief description is as follows:

* Vice President, OSGeo Board of Directors 2021-23
* Representative of the OSGeo Standards Committee for the OGC Geo-Huntsville 2023
* FOSS4G 2021 Session Leader, FOSS4G Asia Workshop Contributor and Speaker
* OSGeo-OGC-ASF Joint Code Sprint Participant
* Project Steering Committee (PSC) Member for the ZOO-Project, pgRouting
* Mentor for the United Nations OSGeo Education Challenge 2021 - pgRouting Track (Attending the UN OpenGIS and UN GeoAI WG Meetings)
* Charter Member since 2017
* Google Summer of Code 2020-onwards: Organization Administrator
* Google Summer of Code 2018-onwards: Mentor
* Google Summer of Code 2017: Student Developer
* Google Code-in 2019: Mentor

I am also an academic manuscript reviewer for the Journal of Open Source Software (JOSS) and I review manuscripts in the domain of geospatial and geoscience research and software.

=== What your interests are in terms of the board ===

For this tenure, my primary interest is in propagating the experiences to the best of my capability to the new members. Additionally, my focus would be on promoting the Geo-Bharat and OSGeo India activities with the LoC.

=== Any things that you would like to change or introduce ===
One thing that I would want to work on is promptly working on accountability with roles and responsibilities. One of the nominees - Vicky touched upon Scalability and I echo these thoughts. As someone who works closely with new and young contributors in the community as a part of the GSoC initiative, I would try to encourage more individuals to be part of the different OSGeo committees so that we can enable more hands and minds to finish tasks.

=== What role you would wish to fulfill on the board (if any) ===
I am open to any role based on the requirements of the board based on my past learnings and experiences. I have a lot to learn! :)

== ''Name'' - ''Country'' ([https://www.osgeo.org/member/''name''/ OSGeo profile]) ==

=== About me ===

=== My vision ===

=== What you have done within the community in the past ===

=== What your interests are in terms of the board ===

=== Any things that you would like to change or introduce ===

=== What role you would wish to fulfill on the board (if any) ===

[[Category:Elections]]
[[Category:Election 2022]]

Election 2023 Candidate Manifestos

2023-12-30T04:11:58Z

RajatShinde: Updating menifesto for Rajat Shinde

A space for the candidates for election to the Board to share some information about themselves, their aspirations for OSGeo, what they would like to change, improve or introduce and what role they would like to play on the board.

You are welcome to follow the template, and add further relevant info as you need:

== Jeroen Ticheler - The Netherlands ([https://www.osgeo.org/member/jeroen-ticheler/ OSGeo profile]) ==

=== About me ===

Wageningen (The Netherlands), Ivory Coast and Mali were the places I grew up as a child. It brought me to study Tropical Forestry with a focus on GIS and Remote Sensing. Following graduation in 1997, I started working to support the Early Warning System for Food Security and the Desert Locust Early Warning System at the UN Food and Agricultural Organization (FAO) in Rome for nine years.

With the support of the FAO, I managed to start the development of GeoNetwork opensource around the year 2001, a catalog that allowed us to organise and release large quantities of geospatial data to the public.

In 2007, GeoCat was established and I moved back to The Netherlands. Besides everything geospatial, I love traveling, carpentry, slowly build an overland truck, study Analytical Psychology, and walk, work and live outside.

=== My vision ===

My vision is that geospatial knowledge can improve the way we live on our planet. That science requires the open software we jointly develop and that sustainable Free and Open Source Software projects require healthy businesses that commit themselves to contribute back responsibly.

We, as a community, can accomplish so much through local and global collaborations. Our projects and communities provide (the best) tools and knowledge accessible for all to benefit.

=== What you have done within the community in the past ===

Besides my involvement as PSC chair in the GeoNetwork opensource project, I have been involved as Charter member from 2006 onwards, served on the OSGeo Marketing and Conference Committees, as well as on the OSGeo Board. In the last 10+ years my involvement has mainly been in the form of a sponsor to OSGeo and FOSS4G (both global, regional and local) and by organising a yearly Code Sprint in Bolsena since 2007.

=== What your interests are in terms of the board ===

My mission is to connect people by connecting communities and information. I strongly promote the use of international standards and Free and Open Source Software for geographic data and information. I'll commit myself to help OSGeo to bring people together that collaborate, innovate and give back.

=== Any things that you would like to change or introduce ===

Responsible entrepreneurship will definitely be one of the things that has my attention. OSGeo needs to be a well balanced community of people from all parts of society, including volunteers, students and scientists, public servants and businesses.

=== What role you would wish to fulfil on the board (if any) ===

No preference at this stage, I'm willing to take up any role needed.

== Marco Bernasocchi, Switzerland ([https://www.osgeo.org/member/bernasocchi/ OSGeo profile]) ==

=== About me ===
I am an open-source advocate, consultant, teacher, and developer. My background is in geography with a specialization in geographic information science. I live in Switzerland in a small Romansh speaking mountain village where I love scrambling around the mountains to enjoy the feeling of freedom it gives me. I’m a very communicative person, I fluently speak Italian, German, French English, and Spanish and love travelling. I'm the QGIS.org Chair and work as CEO of OPENGIS.ch which I founded in 2011. Since 2014 I share the company ownership with Matthias Kuhn. At OPENGIS.ch LLC we develop, train and consult our client on any aspect related to QGIS, QField, PostGIS and WebGIS technologies.

I first came in contact with the OSGEO world during my BSc when the University of Zurich was teaching us proprietary products and I started looking around for Open Source alternatives and started using QuantumGIS “Simon (0.6)”. In 2008, when starting my MSc, I made the definitive switch to Ubuntu and I started working more and more with QuantumGIS Metis (0.11) and ended developing some plugins and part of Globe as my Masters' thesis.

Since then my whole work has pivoted around QGIS and enabling people and companies to embrace opensource for their GIS needs.

=== My vision ===
Serving as a pragmatic community conciliator - collecting thoughts from people with differing opinions and trying to find the high road through difficult issues I want to focus my and the community's energies on being inclusive and forward-thinking.

I see FOSS as a very socially responsible way to develop software, but even more, I see the immense technological advantage that writing open-source code brings. This is why I always strive to allow both pragmatic and ideological views to respectfully coexist and enrich each other.

=== What you have done within the community in the past ===
* QGIS contributor since 2011
* QGIS.org Chair since 2020
* QGIS.org Vice-Chair 2018-2020
* QField (originally QGIS for android) creator
* FOSS4G Session Leader, various FOSS4G Talks and workshops
* Charter Member since 2018
* Google Summer of Code 2012: Mentor
* Google Summer of Code 2011: Student Developer

=== What your interests are in terms of the board ===

One of my main motivations to be part of the board is to help OSGeo keep its incredible growth rate by being even more attractive to new community members, sponsors and large/corporate users. To achieve this, to me the key is maintaining the right balance between sustainable processes and helping interesting and motivating grassroots projects.

=== Any things that you would like to change or introduce ===
As still fairly technical driven person, I like to understand the inner workings of things and projects before commenting on changes :)

=== What role you would wish to fulfil on the board (if any) ===
I am open to any role based on how I could best serve the board.

== Vicky Vergara - Mexico ([https://www.osgeo.org/member/vicky-vergara/ OSGeo profile]) ==

=== About me ===

When I am in front of the computer, there can be an earthquake and I won't notice. I forget to eat, sometimes when I get hungry it's already time to go to bed.

That is something I do not recommend, but things change when I go to any FOSS4G:
* I take my autographs notebook and get many nice thoughts from members of the community.
* I like to talk to people,
* I like to see presentations
and these interactions let me know that there is a person behind that computer/software that I am using.

Also never forget to do some other non OSGeo related stuff like
* Learn how to grow nepenthes
* Continue with building my HMS Victory model ship
* Learn how to do egg tempera, idea that came from going to FOSS4G Florence and see its art.

=== My vision ===

Promote the development and use of Open Source Software.

=== What you have done within the community in the past ===
This 2023 was very intense.
* OSGeo board with all the work that comes with it, that is very interesting.
* pgRouting PSC with all the work that comes with it.
* Translating OSGeoLive, pgRouting.
* Doing improvements on pgRouting.
* Taking care of OSGeoLive documentation as part of my duties of PSC on OSGeoLive
* For the nth year, been a mentor on the Google Summer of Code program
* Been more active part on the SAC committee during the second semester.
* Participating in the UN-OPENGIS meetings
* Doing some contributions on Valhalla

=== What your interests are in terms of the board ===
For this term I will use the word scalability.

I am an Economist and Computer Scientist who lacks skills for example: cooking or doing accounting.
I am a volunteer at home so I cook when I remember that we need to eat, and try to do my best, of course my sons can do things like poached eggs or omelettes, but my limit is scrambled and sunny side broken.
I hire professionals, someone cooks for me, someone does my accounting.

In OSGeo, we are a growing community of volunteers. But are we scalable?

A volunteer do contributions when they have time to do contributions.
Some might be jobless, some might be be freelancers, some might be hired by companies that support their contributions to open source, and some might have jobs that do not, and many more situations that I can not even imagine.

The worst case scenario I can think of, (in chat form):
* Person X: (My job situation is unknown to you) and I do volunteering in A, B ,C, D, and E on OSGeo
* Person Z: Great!, please also do G
* Person X: OK
Time passes
* Person Z: Hmm, have you finished?
* Person X: No, I haven't got time
Time passes
* Person X: (Found a job on another industry / got sick / had an accident / life happens), can't do any more volunteering work

Who will do A~G after X leaves?

Since I arrived I see the same names in many different committees, working groups, etc.

We do things when we can, not necessarily when they need to be done. We do them the best we can.
We have are our limits on areas that we understand and try ti help when we have a small idea on what to do, but can't do no more than that. (like my cooking I can do up to a limit, but after that we go to a restaurant)

That way of working, where the few do most of the work on their volunteer time, is not scalable in my opinion.

I do not have a solution to this problem in a volunteer environment.
But at least I would like to start a discussion about it.

=== Any things that you would like to change or introduce ===

Scalability

=== What role you would wish to fulfill on the board (if any) ===

I am fine with the role that is assigned to me. But by preference, this time I would like someone else to be the vice-president of the Latin America area.

== Besfort Guri, Kosovo ([https://www.osgeo.org/member/guri/ OSGeo profile]) ==

=== About me ===

Besfort has been a hacktivist since 2009 in Kosovo, as a member of FLOSSK (Free Libre Open Source Software Kosova – flossk.org). He has been serving as a board member since 2015, and since 2020 he has been acting as President of the Executive Board of FLOSSK.

Since 2010 a mapper at OpenStreetMap, and a member at OSM Foundation since 2018. In 2019 FLOSSK became a Local Chapter at OSM, and Besfort is leading this Local Chapter, in 2019, FLOSSK with a lead of Besfort, organized State of the Map Southeast Europe – sotmsee.org. He is serving as a member of the Advisory Board of the Board of OpenStreetMap Foundation.

Besfort has been active in OSGeo for some years now as well, he has been serving as Charter Member since 2022. FLOSSK has been the local chapter of OSGeo since 2020, and he is leading as well this local chapter. He was part of the organizing team for the canceled FOSS4G 2021 Europe, now he is Co-Chair of the Program Committee at FOSS4G 2024 Europe. He was chair of FOSS4G 2023 in Prizren.

He runs a small company called OpS-IN (Open Spatial Information Network) where he develops different GIS systems. His two biggest projects that he implemented through the company are "SPAK – Spatial Planning Application for Kosovo", and "ACLIS – Albanian Cadastral Land Information System" Both projects have the entire architecture of the system, based on OSGeo projects, like PostgreSQL / PostGIS, QGIS, GeoServer, Open Layers etc.

=== My vision ===

Promote the development and use of FLOSS Software, more specifically FLOSS GIS.

=== What you have done within the community in the past ===

* Promote FLOSS (FLOSS GIS) in Balkan Area, in different aspects
* Part of the Organizing Committee of canceled FOSS4G 2021 Europe
* Chair of FOSS4G 2023 Prizren, Kosovo
* Co-Chair of Program Committee of FOSS4G Europe 2024

=== What your interests are in terms of the board ===

Focusing on responsible entrepreneurship in OSGeo, I aim to unite diverse communities—volunteers, students, scientists, public servants, and businesses. I bring expertise in Balkan community engagement and a commitment to nurturing entrepreneurship in developing nations. This multifaceted approach cultivates an inclusive ecosystem, driving both tech advancements and societal progress within OSGeo.

=== Any things that you would like to change or introduce ===

OSGeo wants a mix of people from everywhere—volunteers, students, scientists, public servants, and businesses—to build a balanced community. It's important to include countries at different stages of development, like those with growing economies and opportunities.

=== What role you would wish to fulfill on the board (if any) ===
I don't have any specific preference at this stage, I'm willing to take up any role needed.

== ''Rajat Shinde, Ph.D.'' - ''India/ (Currently residing in the United States of America)'' ([https://www.osgeo.org/member/shinde/ OSGeo profile]) ==

=== About me ===

Hey there! My name is Rajat (meaning ''shining like Silver'' in Hindi). I hail from India and currently, I am working as a Computer Scientist with NASA IMPACT / the University of Alabama in Huntsville (UAH). I have a Ph.D. degree in Geo-informatics with a specialization in LiDAR data processing using deep learning algorithms. During my Ph.D., I was a recipient of the Prime Minister's Research Fellowship conferred by the Government of India to selected doctoral candidates. Before diving into the spatial dimension, I used to be an Electronics and Communication Engineer.

In 2023, it is my continued nomination to be a member of the OSGeo Board of Directors. In 2021, I was nominated for the first time and got elected as the youngest-ever board member and subsequently as a Vice President of the OSGeo Board.

My journey with open-source (and OSGeo) started in 2017 when I got to attend and present at the FOSS4G Asia 2017. In the same year, I had an amazing experience in contributing to the MapMint project as a Google Summer of Code Student. From 2018 onwards, I am contributing as a GSoC Admin and mentor for the ZOO-Project and MapMint. Also, I serve as a Project Steering Committee (PSC) Member for the ZOO-Project and pgRouting projects (read: star_eyes). I was one of the mentors for the United Nations OSGeo Education Challenge 2021 for the pgRouting project and represented OSGeo during the Google Summer of Code Mentor Summit 2023 held in California, US.

When I look back in 2017, from where I started, I feel elated and equally responsible to be able to contribute back to the biggest and dynamic community for Free and Open Source Software. Moreover, I feel proud of being a part of this OSGeo community; of knowing great personalities, working with them, and encouraging new members to be a part of it.

When I am away from my laptop, I love to practice flute and read books.

[https://www.linkedin.com/in/rajat-shinde/ More details]

=== My vision ===
* Introduce new and young contributors to the OSGeo community via various initiatives
* Contribute to the OSGeo India and GeoBharat activities

=== What you have done within the community in the past ===

I have a short experience participating in diverse positions while being a part of the OSGeo community. A brief description is as follows:

* Vice President, OSGeo Board of Directors 2021-23
* Representative of the OSGeo Standards Committee for the OGC Geo-Huntsville 2023
* FOSS4G 2021 Session Leader, FOSS4G Asia Workshop Contributor and Speaker
* OSGeo-OGC-ASF Joint Code Sprint Participant
* Project Steering Committee (PSC) Member for the ZOO-Project, pgRouting
* Mentor for the United Nations OSGeo Education Challenge 2021 - pgRouting Track (Attending the UN OpenGIS and UN GeoAI WG Meetings)
* Charter Member since 2017
* Google Summer of Code 2020-onwards: Organization Administrator
* Google Summer of Code 2018-onwards: Mentor
* Google Summer of Code 2017: Student Developer
* Google Code-in 2019: Mentor

I am also an academic manuscript reviewer for the Journal of Open Source Software (JOSS) and I review manuscripts in the domain of geospatial and geoscience research and software.

=== What your interests are in terms of the board ===

For this tenure, my primary interest is in propagating the experiences to the best of my capability to the new members. Additionally, my focus would be on promoting the Geo-Bharat and OSGeo India activities with the LoC.

=== Any things that you would like to change or introduce ===
One thing that I would want to work on is promptly working on accountability with roles and responsibilities. One of the nominees - Vicky touched upon Scalability and I echo these thoughts. As someone who works closely with new and young contributors in the community as a part of the GSoC initiative, I would try to encourage more individuals to be part of the different OSGeo committees so that we can enable more hands and minds to finish tasks.

=== What role you would wish to fulfill on the board (if any) ===
I am open to any role based on the requirements of the board based on my past learnings and experiences. I have a lot to learn! :)

== ''Name'' - ''Country'' ([https://www.osgeo.org/member/''name''/ OSGeo profile]) ==

=== About me ===

=== My vision ===

=== What you have done within the community in the past ===

=== What your interests are in terms of the board ===

=== Any things that you would like to change or introduce ===

=== What role you would wish to fulfill on the board (if any) ===

[[Category:Elections]]
[[Category:Election 2022]]

OSGeo Community Sprint 2023

2023-10-10T17:00:34Z

RajatShinde: /* Participants */

Annual Code Sprint comes to Vienna (Austria) in 2023!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo_Community_Sprint_2019|Prizren]] (2023)
* [[OSGeo_Virtual_Community_Sprint_2020|Virtual Event]] (2020)
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Community_Sprint_2023#Sponsoring |Sponsoring the Event]].

; <big>Venue Sponsor</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:BIDS23.jpg|340px|Big Data from Space 2023 (BiDS)|link=https://www.bigdatafromspace2023.org/]]
 
https://www.bigdatafromspace2023.org/
|}

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/
||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Bh-logo.jpg|300px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Gaia3D.png|240px|Gaia3D||link=https://gaia3d.com/en/]]
 
[https://gaia3d.com/en/ https://gaia3d.com/en/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:Logo-EOX.png|140px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[File:Pixel8_logo_full.png|140px|link=https://www.pixel8.earth/]]
 
[https://www.pixel8.earth/ https://www.pixel8.earth/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Azavea-logo.png|160px|link=https://www.azavea.com/]]
 
[https://www.azavea.com/ https://www.azavea.com/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
||
[[File:IGN_logo.png|140px|link=https://ign.fr/]]
 
[https://ign.fr/ https://ign.fr/]
|}

== Dates and Times ==

* Date: November 6 to November 9
* Time: 9:00am to 1:30pm each day

== Other Events in Q4 2023 ==

* ''please add your event''

== Location ==

* [https://en.wikipedia.org/wiki/Vienna Vienna], Austria

=== BIDS23 ===
The OSGeo Community Sprint 2023 will be hosted by the Big Data from Space 2023 (BiDS) event.

BiDS brings together key actors from industry, academia, EU entities and government to reveal user needs, exchange ideas and showcase latest technical solutions and applications touching all aspects of space and big data technologies, providing a unique opportunity to discuss and present the most recent innovations and challenges encountered in the context of big data from space. The 2023 edition of BiDS will focus not only technologies enabling insight and foresight inferable from big data from space. Together, we want to emphasize how breakthrough space data driven technologies impact on society’s grand challenges, such as climate change and the green transition.

The event, organized by the [https://www.esa.int/ European Space Agency] (ESA) together with the [https://www.satcen.europa.eu/ European Union Satellite Center] (SatCen) and the [https://commission.europa.eu/about-european-commission/departments-and-executive-agencies/joint-research-centre_en Joint Research Center] (JRC), will take place at the [https://www.acv.at/en/ Austria Center Vienna], and counts with the support of the partners [https://www.ffg.at/en FFG], [https://austria-in-space.at/en/ Austria in Space] and the [https://www.bmk.gv.at/en.html Federal Ministry Republic of Austria].

=== Coding Venue ===
* The Austria Center Vienna will be the host of BIDS '23.
* As Austria's largest conference center, it opened in 1987 and has 19 halls, 180 meeting rooms, and 26,000 square meters of exhibition and networking space with a capacity of up to 22,800 guests.
* It is a popular destination in the international conference circuit and is located next to a UN headquarters, making it a unique location for the latest edition of Big Data from Space.
* [https://www.acv.at/en/ Austria Center Vienna], Bruno-Kreisky-Platz 1, 1220 Wien, Austria
* [https://www.openstreetmap.org/#map=16/48.2343/16.4144 OpenStreetMap]

=== Parking ===
* Austria Center Vienna provides parking space

=== Accommodation ===
Several hotels and apartments are close to the venue. You will be able to find lots of options within walking distance.
Here are a few options:

{|border=1
|-
| '''Hotel Name''' || '''Price Range (Euros)''' || '''Distance''' || '''Notes'''
|-
|}

=== How to get there ===

'''Travelling to/from Vienna international airport'''

==== Metro ====

==== Suburban Rail ====

==== Bus Services ====

==== Taxi ====

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''OSGeoLive''':
** Work towards 16.0 release

* '''Pangeo community''':
** [https://github.com/pangeo-data/bids2023_codesprint Pangeo project ideas], incl. Alexander Kmoch & DGGS

* '''STAC BoF / European Community Show of Hands''':
** We (EOX) would like to better get to know the European scene of STAC users and contributors. For this reason we'd like to organize a Birds of a Feather session, where we talk about the use and development of STAC specification, tools and resources. If there is a reasonable interest, we could expand this to a session actually dedicated towards actual work on STAC related items.

* '''GRASS GIS''':
** Review lidar binning code for large point clouds (''r.in.pdal'' tool)
** Work on topics not completed at the recent [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023#Agenda_-_What_we_plan_to_do GRASS Community Meeting Prague 2023]

* '''pycsw'''
** STAC enhancements
** OGC API - Records alignment
** metadata repository abstraction
** federation
** 3.0.0-beta1 release

* '''pygeoapi'''
** updating CI to Python 3.8
** PR/issue sweep
** OGC API - Maps updates
** data access abstraction (fs, s3, etc.) in core
** 0.16 release

* '''MapServer'''
** Creation of a new OGC API workshop
** mappyfile community project discussions

* '''QGIS'''
**

* '''PDAL'''
** geometric and topometric topics (for example: neighbors search, grid computations, and other stuff).

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="60"|Accommodation
!width="60"|Likelihood
!width="30"|Food Restrictions
!width="60"|social event
|-
| 1 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x || x || booked || Certain || No || x ||
|-
| 2 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || OSGeo || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || x || x || x || x || booked || Certain || No || x ||
|-
| 3 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc(at)gmail.com || OSGeo || pdal, mapserver, other geopython projects || x || x || x || x || || Certain || No || x ||
|-
| 4 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl(at)eox.at || EOX || MapServer, View Server/EOxServer, various || x || x || x || x || local || Certain || No || x ||
|-
| 5 ||[[User:Allixender|Alexander Kmoch]] || EE || alexander.kmoch(at)ut.ee || Univ. Tartu, Pangeo || DGGS, DGGRID, pygeoapi, xarray, various || x || x || x || x || || Certain || No || x ||
|-
| 6 ||[[User:hobu|Howard Butler]] || US || howard(at)hobu.co || Hobu, Inc. || PDAL, GDAL, point clouds || x || x || x || x || || Certain || No || x ||
|-
| 7 ||[[User:darkblueb|Brian M Hamlin]] || US || maplabs(at)light42.com || CalOpenData || OSGeoLive, Open Data Cube || x || x || x || x || || Certain || Vegetarian || x ||
|-
| 8 ||[[User:mbernasocchi|Marco Bernasocchi]] || CH || marco@opengis.ch || OSGeo, QGIS.org || QGIS || x || x || x || x || || Certain || NOne || x ||
|-
| 9 ||[[User:Sethg|Seth Girvin]] || FR || sethg@geographika.net || OSGeo || MapServer, OSGeoLive, GeoStyler, mappyfile|| x || x || x || x || booked || Certain || None || x ||
|-
| 10 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH || pka (at) sourcepole.com || Sourcepole || OGC APIs, BBOX, GeoRust, various|| x || x || x || - || || Very likely || None || x ||
|-
| 11 ||[[User:Anita_Graser|Anita Graser]] || AT || anita@qgis.orgm || AIT || QGIS, MobilityDB, MovingPandas || x || x || x || x || local || Certain || None || x ||
|-
| 12 ||[[User:chambbj|Brad Chambers]] || US || brad.chambers(at)gmail.com || Grover Consulting Services || PDAL, point clouds || x || x || x || x || || Certain || No || x ||
|-
| 13 ||[[User:jef|Jürgen Fischer]] || DE || jef(at)norbit.de || norBIT GmbH || QGIS, OSGeo4W || x || x || x || x || tbd || Likely || None || x ||
|-
| 14 ||[[User:Fschindler|Fabian Schindler]] || AT || fabian.schindler(at)eox.at || EOX || MapServer, View Server/EOxServer || x || x || x || x || local || Certain || Vegetarian || x ||
|-
| 15 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)Geolabs.fr || GeoLabs || ZOO-Project, MapServer || x || x || - || - || local || Very likely || None || x ||
|-
| 16 ||[[User:Fschindler|Léa Vauchier]] || FR || lea.vauchier(at)ign.fr|| IGN || pdal, point clouds || x || x || x || x || tbd || Very Likely || Vegetarian || x ||
|-
| 17 ||[[User:Fschindler|Antoine Lavenant]] || FR || antoine.lavenant(at)ign.fr|| IGN || pdal, point clouds || x || x || x || x || tbd || Very Likely || No || x ||
|-
| 18 ||[[User:aanthieni|Ariel Anthieni]] || AR || aanthieni(at)kan.com.ar || OSGeo, Kan Territory&IT, Geolibres Arg. || GeoNode, QGIS, Metadata || x || x || x || x || || Very Likely || None || x ||
|-
| 19 ||[[User:tinaok|Tina Odaka]] || AR || Tina.Odaka(at)ifremer.fr || IFREMER, LOPS, Pangeo || DGGS(Healpix)-Xarray || x || x || x || x ||tbd || Certain || No || x ||
|-
| 20 ||[[User:danlooo|Daniel Loos]] || DE || dloos(at)bgc-jena.mpg.de || Max Planck Biogeochemistry || DGGS || x || x || x || x ||tbd || Likely || No || x ||
|-
| 21 ||[[User:rouault|Even Rouault]] || FR || even.rouault(at)spatialys.com || Spatialys || GDAL, PROJ || x || x || x || x || booked || Certain || No || x ||
|-
| 22 ||[[User:dbaston|Dan Baston]] || US || dbaston(at)isciences.com || ISciences || GDAL, GEOS || x || x || x || x ||tbd || Certain || No || x ||
|-
| 23 ||[[User:tinaok|Jean Marc Delouis]] || FR || jmdelouis(at)ifremer.fr || CNRS, LOPS, Pangeo || DGGS(Healpix)-Xarray || x || x || x || x ||tbd || Likely || No || x ||
|-
| 24 ||[[User:tinaok|Justus Magin]] || FR || justus.magin(at)ifremer.fr || CNRS, LOPS, Pangeo || DGGS(Healpix)-Xarray || x || x || x || x ||tbd || Certain || Vegetarian || x ||
|-
| 25 ||[[User:tinaok|Benoit Bovy]] || FR || Tina.Odaka(at)ifremer.fr || Xarray || DGGS(Healpix)-Xarray || x || x || x || - ||tbd || Likely || No || x ||
|-
| 26 ||[[User:neteler|Markus Neteler]] || DE || neteler(at)mundialis.de || mundialis || GRASS GIS || x || x || x || x ||tbd || Very Likely || No || x ||
|-
| 27 ||[[User:lubojr|Lubomir Dolezal]] || AT || lubomir.dolezal(at)eox.at || EOX || View Server/EOxServer || x || x || x || x || local || Certain || No || x ||
|-
| 28 ||[[User:ungarj|Joachim Ungar]] || AT || joachim.ungar(at)eox.at || EOX || mapchete || x || x || - || x || local || Certain || No || x ||
|-
| 29 ||[[User:jankovicgd|Nikola Jankovic]] || AT || niikola.jankovic(at)eox.at || EOX || View Server/EOxServer || x || x || x || x || local || Certain || No || x ||
|-
| 30 ||Martin Dobias || SK || martin.dobias(at)lutraconsulting.co.uk || Lutra Consulting || QGIS, PDAL || - || x || x || x || tbd || Likely || No || x ||
|-
| 31 ||[[User:eynardbg|Guillaume Eynard-Bontemps]] || FR || guillaume.eynard-bontemps(at)cnes.fr || CNES, Pangeo || Xarray, Datacubes || - || x || x || x || booked || Very Likely || No || x ||
|-
| 32 ||Andreas Neumann || CH || andreas(at)qgis.org || QGIS / ETH Zurich || QGIS || - || x || x || x || booked || certain || No || x ||
|-
| 33 ||Aron Gergely || NL || aron.gergely(at)rasterra.nl || Rasterra || QGIS, xarray, pangeo || - || x || x || x || booked || Very Likely || No || x ||
|-
| 34 ||[[User:bmallinger|Bernhard Mallinger]] || AT || bernhard.mallinger(at)eox.at || EOX || pygeoapi, View Server/EOxServer, EOxHub || x || x || x || x || local || Certain || Vegetarian || x ||
|-
| 35 ||Raymond Nijssen || NL || r.nijssen(at)terglobo.nl || Terglobo || QGIS || - || x || x || x || booked || Certain || No || x ||
|-
| 36 ||Richard Duivenvoorde || NL || richard(at)zuidt.nl || Zuidt || QGIS || - || x || x || x || booked || Certain || No || x ||
|-
| 37 ||Selma Vidimlic || BA || selma@kartoza.com || QGIS / Kartoza || QGIS || x || x || x || x || tbd || Certain || No || x ||
|-
| 38 || Moritz Langer || AT || moritz.langer@ama.gv.at || equip || pygeoapi, various python projects || x || x || x || x || local || Very likely || Vegetarian || x ||
|}

Remote:
1. Vaclav (Vashek) Petras (US, wenzeslaus gmail com, NC State University, GRASS GIS, asynchronous, 6 hours behind)
2. Rajat Shinde (US, rajatshinde2303 gmail com, NASA IMPACT - UAH, ZOO-Project, Asynchronous, GMT-5)

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Gitter channel: https://gitter.im/OSGeo/Sprint

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed. See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place Nov 6-9, 2023.

We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place in Vienna and will be hosted by [https://www.bigdatafromspace2023.org/, Big Data From Space '23] and organized by members of the local OSGeo chapter.

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2023/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tzotsos@osgeo.org directly.

== Event Owner ==
* [[User:kalxas|Angelos Tzotsos]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!

[[Category:Code_Sprints]]
[[Category:C Tribe Code Sprint]]

Board Meeting 2023-08-29

2023-08-17T05:29:12Z

RajatShinde:

This board meeting is '''scheduled Tuesday 29 August 2023''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023&month=8&day=29&hour=13&min=0&sec=0&p1=250&p2=26&p3=49&p4=155&p5=51&p6=312 '''13:00''' UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board Loomio] and actions on the [https://git.osgeo.org/gitea/osgeo/todo/issues OSGeo todo] issue tracker.

== Agenda ==

=== Current items ===

# ''roll call''
# ''appoint meeting chair, meeting scribe/secretary''
# ''Review and approve past minutes''
#* [[Board_Meeting_2023-07-25]]
# EU CRA directive [https://lists.osgeo.org/pipermail/qgis-psc/2023-July/010092.html]
# opengis harmonization update
# FOSS4G 2024 Belem International [https://www.loomio.com/p/DeWlap9k/motion-to-approve-belem-to-host-foss4g-2024]
# UNGGIM
# Accept mappyfile to OSGeo Community Project status [https://lists.osgeo.org/pipermail/board/2023-August/013341.html]
# OSGeo - AGU MoU: Opportunity for renewal
# Invitation of the OSGeo president to FOSS4G-ASIA 2023 Seoul
# ''Add your topic here''

== Minutes ==

* Presiding:
* Scribing:
* Attending:
* Guests:

=== Actions ===

* See https://git.osgeo.org/gitea/osgeo/todo/issues

== IRC Log ==
* no log, Jitsi meeting

== Next meeting ==
*[[Board Meeting 2023-09-26]]

[[Category:Board]]
[[Category:Board Meetings 2023]]

Board Meeting 2023-05-30

2023-05-30T15:25:01Z

RajatShinde:

This board meeting is '''scheduled Tuesday 30 May 2023''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023&month=5&day=30&hour=18&min=0&sec=0&p1=250&p2=26&p3=49&p4=155&p5=51&p6=312 '''18:00''' UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board Loomio] and actions on the [https://git.osgeo.org/gitea/osgeo/todo/issues OSGeo todo] issue tracker.

== Agenda ==

=== Current items ===

# ''roll call''
# ''appoint meeting chair, meeting scribe/secretary''
# ''Review and approve past minutes''
#* [[Board_Meeting_2023-04-25]]
# Additional request for deegree code sprint funding [https://lists.osgeo.org/pipermail/board/2023-May/013275.html]
# BIDS 2023 Code sprint updates
# OSGeo Oceania Travel Grant Funding Request [https://lists.osgeo.org/pipermail/board/2023-May/013287.html]
# FOSS4G 2023 - Discussion with news floating around...
# ''Add your topic here''

== Minutes ==

* Presiding:
* Scribing:
* Attending:
* Guests:

=== Actions ===

* See https://git.osgeo.org/gitea/osgeo/todo/issues

== IRC Log ==
* no log, Jitsi meeting

== Next meeting ==
*[[Board Meeting 2023-06-25]]

[[Category:Board]]
[[Category:Board Meetings 2023]]

Board of Directors

2023-04-19T16:55:34Z

RajatShinde: /* OSGeo Foundation Board of Directors */

== OSGeo Foundation Board of Directors ==

The board is elected by the [https://www.osgeo.org/about/charter-members Charter Members] as outlined in the [[Board Election Procedure]].

Period: December 2022 - November 2024
* [https://www.osgeo.org/member/angelos-tzotsos Angelos Tzotsos] - Athens, Greece (Central European Time UTC +2h) [[Executive_Positions|President]]
* [https://www.osgeo.org/member/michael-smith/ Michael Smith] - Hanover, New Hampshire, USA (Eastern Time UTC -5h) [[Treasurer]]
* [https://www.osgeo.org/member/tom-kralidis Tom Kralidis] - Toronto, Ontario, Canada (Eastern Time UTC -5h)
* [https://wiki.osgeo.org/wiki/User:Aanthieni Ariel Anthieni] - Buenos Aires, Argentina (Argentina Time UTC -3h)

Period: December 2021 - November 2023

* [https://www.osgeo.org/member/steer/ Adam Steer] - Norway (Central European Time Zone UTC +1h)
* [https://www.osgeo.org/member/bernasocchi/ Marco Bernasocchi] - Switzerland (Central European Time Zone UTC +1h)
* [https://www.osgeo.org/member/codrina-maria-ilie/ Codrina Maria Ilie] - Bucharest, Romania (Central European Time Zone UTC +1h)
* [https://www.osgeo.org/member/shinde/ Rajat Shinde] - India/Huntsville, AL, USA (currently) (Central Time UTC -5h)
* [https://www.osgeo.org/member/vicky-vergara/ Vicky Vergara] - Naucalpan, Mexico (Central Standard Time UTC -6h)







More detailed information is available in the [[Board Member Profiles]].

= Board Activities and Meetings =

== Board Activities ==

=== Motions ===

The board is using Loomio to track motions and facilitate voting (see [[Board Voting Procedure]]):

* https://www.loomio.org/g/kdSmIwxu/osgeo-board

=== Actions ===

The board is an issue tracker for actions:

* https://git.osgeo.org/gitea/osgeo/todo/issues

== Board Meetings ==

In general the OSGeo board meets on [https://meet.jit.si/OsgeoBoard Jitsi] or [[IRC|IRC]] the last Monday of the month from [http://www.timeanddate.com/worldclock/meetingdetails.html?hour=15&min=0&sec=0&p1=43&p2=49&p3=1234&p4=286&p5=157&p6=671&p7=207&p8=1091&p9=259 15.00 UTC]

Upcoming board meetings:

; Video call: board will get together for a video call and work through discussions and tasks in 1 hour [https://meet.jit.si/OsgeoBoard Jitsi] meeting. May also consist of an informal "work party" of board members and officers to work on tasks and collaboration not easily handled in IRC / email.

* [[[Board_Meeting_2022-10-31]] [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022&month=10&day=31&hour=16&min=0&sec=0&p1=256&p2=286&p3=49&p4=269&p5=250&p6=37 16:00 UTC]

; IRC Meeting: [[IRC|Internet Rely Chat]] meetings are held on Libera.Chat [irc://irc.libera.chat/#osgeo OSGeo channel], please note that due to spam you are now required to register with the "NickServ" bot to verify your identity prior to posting messages on IRC. Before 2021, the board was using the FreeNode OSGeo channel that was [http://irclogs.geoapt.com/osgeo logged] providing a great record of IRC meetings.

* none scheduled

; Face to Face Meeting: board will get together in person and work through discussions and tasks that are not easily handled in a 1 hour IRC meeting or via e-mail. For face to face meetings travel costs will be covered by the foundation.

* none scheduled

; Member meeting: board meeting with OSGeo members at OSGeo events providing a chance to listen and discuss our community. May also consist of informal "party" to celebrate our community, members, and what we accomplish together

* none scheduled

=== Previous meetings ===

[[:Category:Board_Meetings_2023|2023]] -
[[:Category:Board_Meetings_2022|2022]] -
[[:Category:Board_Meetings_2021|2021]] -
[[:Category:Board_Meetings_2020|2020]] -
[[:Category:Board_Meetings_2019|2019]] -
[[:Category:Board_Meetings_2018|2018]] -
[[:Category:Board_Meetings_2017|2017]] -
[[:Category:Board_Meetings_2016|2016]] -
[[:Category:Board_Meetings_2015|2015]] -
[[:Category:Board_Meetings_2014|2014]] -
[[:Category:Board_Meetings_2013|2013]] -
[[:Category:Board_Meetings_2012|2012]] -
[[:Category:Board_Meetings_2011|2011]] -
[[:Category:Board_Meetings_2010|2010]] -
[[:Category:Board_Meetings_2009|2009]] -
[[Board Meetings 2008|2008]] -
[[Board Meetings 2007|2007]] -
[[Board Meetings 2006|2006]] -
[http://www.osgeo.org/content/foundation/meetings/board/board_meetings.html Earlier].

= Initiatives =

While the board is focused on decision making occasionally there is a call for a long term activity in support of our goals and objectives. We are especially proud of joint initiatives undertaken with other parties as a tangible result of collaboration and community building.

[https://www.osgeo.org/initiatives/ Initiatives]:

* [https://www.osgeo.org/initiatives/geo-for-all/ GeoForAll] - education and research outreach

* [https://www.osgeo.org/initiatives/foss4g/ FOSS4G (Events)] - managed by the conference committee

* [https://www.osgeo.org/initiatives/foss4g-travel-grant-program/ Travel Grant Program] - facilitate accessibility and diversity at our global and regional FOSS4G events

* [https://www.osgeo.org/initiatives/open-geoscience/ Open GeoScience] - make scientific research, data and results transparent and accessible for science and society

* [https://www.osgeo.org/initiatives/un-initiative/ UN Initiatve] - support the UN migration to Open Source Geospatial software solutions

* [https://www.osgeo.org/initiatives/gsoc/ Google Summer of Code (GSoC)] - encourage university student participation in open source software development

* [https://www.osgeo.org/initiatives/osgeo-live-initiative/ OSGeoLive Initiative]

* [[OSGeo Community Project Initiative]]: created foster innovation and collaboration resulting in a lower barrier of entry to join the OSGeo Family. Managed by the board with the assistance of the incubation committee to [https://wiki.osgeo.org/wiki/Incubation_Committee#Step_2:_Join_Community_Projects_Program review applicants].

* [[OSGeo Code Sprints Initiative]] - sponsorship program for projects and communities planning targeted software development.

* [[OSGeo Security Initiative]] - sponsorship program providing emergency funds for projects faced with an urgent security vulnerability.

* [https://www.osgeo.org/meta-crs-initiative/ Meta CRS Initiative] - gathers together interested parties from across several projections, and coordinate system related technologies

* [https://www.osgeo.org/opengis-harmonization/ OpenGIS Harmonization] - untangle the use of org.opengis java package between OSGeo GeoTools project and OGC GeoAPI Standard. This is a cross-project initiative as many projects in our Java family are affected by any change.

While the board is responsible for defining the scope and responsibilities of these activities, initiatives require participation for success. OSGeo projects and committees may have additional initiatives of interest beyond the ones listed here as overseen by the board.

Creating an initiative is a great way to setup for a recurring activity (such as GSoC) without the "overhead" of establishing a full OSGeo committee.

= Working Groups =

While the board is focused on decision making occasionally there is a call for action. The following working groups are focused on accomplishing a specific 2-3 week objective and will report back to the board list when completed. This is in contrast to long term activities handled by committees.

== 2021 Working Groups ==

* none at present

== 2015 Working Groups ==

* [[2015 Sponsorship Drive Working Group]] - contact prior sponsors, blog post inviting new sponsors
* [[GeoForAll OSGeo Relationship]]: Revised Education Committee mandate pending clarification of relationship with Geo4All advisory board (our GeoForAll representatives are Venkatesh Raghavan and Jeff McKenna)

= Planning =

== 2022 Planning ==

=== Operational Budget for 2022 ===

The board is dividing this years budget up by committee, initiative and project!

* [[OSGeo Budget 2022]]

== 2021 Planning ==

=== Operational Budget for 2021 ===

The board is dividing this years budget up by committee, initiative and project!

* [[OSGeo Budget 2021]]

== 2020 Planning ==

=== Operational Budget for 2020 ===

The board is dividing this years budget up by committee, initiative and project!

* [[OSGeo Budget 2020]]

== 2019 Planning ==

Documents:

* [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidence.pdf OSGeo Financial Guidance]

=== Operational Budget for 2019 ===

The board is dividing this years budget up by committee, initiative and project!

* [[OSGeo Budget 2019]]

== 2018 Planning ==

=== Operational Budget for 2018 ===

The board is dividing this years budget up by committee, initiative and project!

* [[OSGeo Budget 2018]]

=== Sponsorship Opportunities for 2018 ===

OSGeo maintains a sponsorship program recognizing financial contributions to our projects, initiatives and events.

* [[OSGeo Sponsorship Opportunities 2018]]

== 2017 Planning ==

=== Operational Budget for 2017 ===

The board is dividing this years budget up by committee:

* [[OSGeo Budget 2017]]

=== Sponsorship Opportunities for 2017 ===

The foundation recognizes sponsors who financially support our events, initiatives and open source projects.

* [[Sponsorship Opportunities for 2017]]

The following has been published as the following [http://www.osgeo.org/node/1755 blog post] and [http://www.osgeo.org/sponsorship how to sponsor page].

== 2016 Planning ==

=== Operational Budget for 2016 ===

Thanks to our sponsors, and a series of successful events, OSGeo does has an operational budget for 2016.

* [[OSGeo Budget 2016]]

The Board has divided the above budget up according to our priority as an organization. Please keep in mind that prior boards have taken this approach - and spent nothing due to lack of volunteers willing to lead the charge. The following is budget and does not provide a commitment to spend money on the actives listed - to do that we need your commitment as a volunteer!

=== Strategic Plan 2016 ===

''From Anne'': See the parallel Skate-Boarding of Fedora at http://fedoramagazine.org/lets-talk-about-fedora-project-objectives/ - I really like the idea of having 18 months goals, that are measurable, backed up by community agreement. Let's discuss this at the first Sprint. There are also [http://www.jonobacon.org/2014/11/14/ubuntu-governance-reboot/ some thoughts on Ubuntu governance] that can inspire us, but I haven't gone through the whole discussion yet, and there are many differences between OSGeo and Ubuntu; so I'm not sure on how much we can learn from it.

This section outlines OSGeo strategic plan for 2016 - this is a result of the [http://www.osgeo.org/about vision, mission and goals] established at the [[Board_Face_to_Face_Meeting_2016|2016 face to face meeting]].

Strategic objectives for 2016:

* S01: showcasing excellence in our communities
* S02: proactively engage with external partners
* S03: Fostering our mission, vision and goals
* S04: Empowering our communities and extending our reach

These objectives were taken to the community for concrete / measurable actions volunteers were interested in tackling over the course of 2016.

Update: We did not receive enough feedback to form a strategic plan.

== 2013 Planning ==

* [[OSGeo Board : Board Priorities 2013]] - establish OSGeo as a low capital, volunteer focused organization focused supporting communities and initiatives which support themselves

= Reference =

* Please see foundation [https://www.osgeo.org/about/bylaws/ bylaws] for official responsibilities
* Arnulf Christl's [http://arnulf.us/sevendipity/archives/49-OSGeo-Director-Retrospective.html OSGeo Director Retrospective]. Arnulf was an OSGeo Board member and President of OSGeo.
* for incoming Board members [[Board_of_Directors/OnboardingChecklist|OnboardingChecklist]]

== Documents ==
* [[https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf OSGeo Financial Guidance]]
* [[Executive Positions]] and [[Director Responsibilities]]
* [[Board Election Procedure]]
* [[Election 2022]]
* [[Election 2021]]
* [[Election 2020]]
* [[Election 2019]]
* Election 2018: [[Board_Election_2018_Results]] [[Election 2018 Candidate Manifestos]]
* Election 2017: [[Board_Election_2017_Results]] [[Election 2017 Candidate Manifestos]]
* Election 2016: [[Board_Election_2016_Results]] [[Election 2016 Candidate Manifestos]]
* Election 2015: [[Board_Election_2015_Results]] [[Election 2015 Candidate Manifestos]]
* Election 2014: [[Board Election 2014 Results]]
* Election 2013: [[Board Election 2013 Results]]
* Election 2012: [[Board Election 2012 Results]]
* Election 2011: [[Board Election 2011 Results]]
* Election 2010: [[Board Election 2010 Results]]
* Election 2009: [[Board Election 2009]], see 2009 section of [[Proposed Board Election Procedure]]
* Election 2008: [[Board Election 2008]], see 2008 section of [[Proposed Board Election Procedure]]
* Election 2007: [[Board Election 2007]], see 2007 section of [[Proposed Board Election Procedure]]
* [[Foundation Sponsorship]] (adopted), [[Project Sponsorship]] (adopted), [[Local Chapter Sponsorship]] (idea)
* [[Conflict Of Interest Policy]]
* [[Board_of_Directors/OnboardingChecklist]]

== Mailing list ==

The http://lists.osgeo.org/mailman/listinfo/board mailing list is used for most public board discussions. There is also a private board mailing list used only for matters that are considered needful to be kept private.

== History of OSGeo Foundation Boards of Directors ==
* [[Board_Election_2021_Results|Board of Directors 2022]]
* [[Board_Election_2021_Results|Board of Directors 2021]]
* [[Board_Election_2020_Results|Board of Directors 2020]]
* [[Board Election 2019 Results|Board of Directors 2019]]
* [[Board_Election_2018_Results|Board of Directors 2018]] (Nov. 2018 - Oct. 2019)
* [[Board Election 2017 Results|Board of Directors 2017]] (Nov. 2017 - Oct. 2018)
* [[Board Election 2016 Results|Board of Directors 2016]] (Aug. 2016 - Aug. 2017)
* [[Board Election 2015 Results|Board of Directors 2015]] (Aug. 2015 - Aug. 2016)
* [[Board Election 2014 Results|Board of Directors 2014]] (Aug. 2014 - Aug. 2015)
* [[Board Election 2013 Results|Board of Directors 2013]] (Aug. 2013 - Aug. 2014)
* [[Board Election 2012 Results|Board of Directors 2012]] (Aug. 2012 - Aug. 2013)
* [[Board Election 2011 Results|Board of Directors 2011]] (Aug. 2011 - Aug. 2012)
* [[Board Election 2010 Results|Board of Directors 2010]] (Aug. 2010 - Aug. 2011)
* [[Board Election 2009 Results|Board of Directors 2009]] (Sept. 2009 - Aug. 2010)
* [[Board Election 2008 Results|Board of Directors 2008]] (July 2008 - Sept. 2009)
* [[Board Election 2007 Results|Board of Directors 2007]] (Aug. 2007 - July 2008)
* [[Interim Board of Directors 2006]] (Feb. 2006 - July 2007)

An interim Board of Directors with 5 members was elected on February 4th, 2006, by the initial members of the [http://www.osgeo.org Open Source Geospatial Foundation]. On March 18th, 2006, the board has been completed to now total nine members:

[[Category:Board]]

Google Summer of Code 2023 Ideas

2023-02-08T12:28:39Z

RajatShinde: /* The ideas pages */

Google Summer of Code 2023 Ideas

2023-02-01T10:37:57Z

RajatShinde: /* The ideas pages */

Google Summer of Code 2023 Ideas

2023-01-24T09:40:56Z

RajatShinde: /* OSGeo Google Summer of Code 2023 */

Google Summer of Code Administrative

2023-01-24T09:34:56Z

RajatShinde: /* Learn more */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2023]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2023 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages

This is the central page for OSGeo administrative information in Google Summer of Code.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2023 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== New Modifications with GSoC 2022 and continuing ahead...(Must Read) ==
(citing from official GSoC 2022 announcement)

* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students, and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe to it, you are encouraged to introduce yourself and your role. We look forward to hearing from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* Admins: [[User:RajatShinde|Rajat Shinde]], [[User:Rahulworld|Rahul Chauhan]], [[User:Krashish8|Ashish Kumar]]
[[Image:File-Rajat_iitb_2_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rajatshinde|Rajat Shinde]][[Image:ProfilePhoto.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rahulworld|Rahul Chauhan]]
[[Image:Ashish_Kumar_photo.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Krashish8|Ashish Kumar]]

Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

* Previous Admins (names in alphabetical order): Anne Ghisla, Carolina Arias Muñoz, Margherita Di Leo, Florin-Daniel Cioloboc, Jeff McKenna, Helmut Kudrnovsky, Werner Macho.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read below.


== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have multiple '''backup mentors''', and they should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' The mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filled within these dates. There are '''2 evaluation periods''' where mentors are required to complete an evaluation of their student from GSoC 2022. After the first 5 weeks of coding, and then at the end during submission of the project. The evaluation forms are shorter than previous years so they should take less time to complete.

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand their capability. Think about coding tasks much earlier than the deadline, and connect the task to the idea in the ideas page, as tasks should reflect the skills required to develop a certain idea.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* A former mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
* It is key '''getting to know the students before the project starts''', in order to adapt the workload to their capabilities. In the proposal template, students are asked basic information about their background, studies and experience, but some mentors report that it can be good to get in touch via hangout or similar voip and make a sort of general interview, beside challenging them with a coding challenge.
* If the student struggles during the GSoC, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
* It is often convenient to '''split the work into smaller tasks''' / clear deliverables. This way, it is easier to track the progress, both for student and mentors.
* If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
* '''Talking in conferences''' does attract quality students to apply to GSoC
* '''GSoC activities span during all year''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc

* ...

=== Bad ideas ===

* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
* If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.
* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention '''not to break the news''' to the students before they are informed by Google.

* ...

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2022/organizations/osgeo-open-source-geospatial-foundation 2022], [https://summerofcode.withgoogle.com/archive/2021/organizations/5115040503431168/ 2021], [https://summerofcode.withgoogle.com/archive/2020/organizations/5355444958134272/ 2020],[https://summerofcode.withgoogle.com/archive/2019/organizations/6684630290268160/ 2019],[https://summerofcode.withgoogle.com/archive/2018/organizations/4890968767594496/ 2018],[https://summerofcode.withgoogle.com/archive/2017/organizations/4554340639440896/ 2017],[https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016], [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2022|2022]], [[Google Summer of Code 2021|2021]], [[Google Summer of Code 2020|2020]], [[Google Summer of Code 2019|2019]], [[Google Summer of Code 2018|2018]], [[Google Summer of Code 2017|2017]], [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]

* OSGeo Applications: [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]], [[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]], [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code Administrative

2023-01-24T09:32:09Z

RajatShinde: New common GSoC Administrative page

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2023]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2023 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages

This is the central page for OSGeo administrative information in Google Summer of Code.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2023 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== New Modifications with GSoC 2022 and continuing ahead...(Must Read) ==
(citing from official GSoC 2022 announcement)

* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students, and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe to it, you are encouraged to introduce yourself and your role. We look forward to hearing from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* Admins: [[User:RajatShinde|Rajat Shinde]], [[User:Rahulworld|Rahul Chauhan]], [[User:Krashish8|Ashish Kumar]]
[[Image:File-Rajat_iitb_2_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rajatshinde|Rajat Shinde]][[Image:ProfilePhoto.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rahulworld|Rahul Chauhan]]
[[Image:Ashish_Kumar_photo.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Krashish8|Ashish Kumar]]

Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

* Previous Admins (names in alphabetical order): Anne Ghisla, Carolina Arias Muñoz, Margherita Di Leo, Florin-Daniel Cioloboc, Jeff McKenna, Helmut Kudrnovsky, Werner Macho.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read below.


== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have multiple '''backup mentors''', and they should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' The mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filled within these dates. There are '''2 evaluation periods''' where mentors are required to complete an evaluation of their student from GSoC 2022. After the first 5 weeks of coding, and then at the end during submission of the project. The evaluation forms are shorter than previous years so they should take less time to complete.

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand their capability. Think about coding tasks much earlier than the deadline, and connect the task to the idea in the ideas page, as tasks should reflect the skills required to develop a certain idea.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* A former mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
* It is key '''getting to know the students before the project starts''', in order to adapt the workload to their capabilities. In the proposal template, students are asked basic information about their background, studies and experience, but some mentors report that it can be good to get in touch via hangout or similar voip and make a sort of general interview, beside challenging them with a coding challenge.
* If the student struggles during the GSoC, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
* It is often convenient to '''split the work into smaller tasks''' / clear deliverables. This way, it is easier to track the progress, both for student and mentors.
* If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
* '''Talking in conferences''' does attract quality students to apply to GSoC
* '''GSoC activities span during all year''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc

* ...

=== Bad ideas ===

* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
* If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.
* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention '''not to break the news''' to the students before they are informed by Google.

* ...

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2022/organizations/osgeo-open-source-geospatial-foundation 2022][https://summerofcode.withgoogle.com/archive/2021/organizations/5115040503431168/ 2021][https://summerofcode.withgoogle.com/archive/2020/organizations/5355444958134272/ 2020],[https://summerofcode.withgoogle.com/archive/2019/organizations/6684630290268160/ 2019],[https://summerofcode.withgoogle.com/archive/2018/organizations/4890968767594496/ 2018],[https://summerofcode.withgoogle.com/archive/2017/organizations/4554340639440896/ 2017],[https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016], [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2022|2022]], [[Google Summer of Code 2021|2021]], [[Google Summer of Code 2020|2020]], [[Google Summer of Code 2019|2019]], [[Google Summer of Code 2018|2018]], [[Google Summer of Code 2017|2017]], [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]

* OSGeo Applications: [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]], [[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]], [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code 2023

2023-01-24T09:28:06Z

RajatShinde:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Welcome to the OSGeo [https://developers.google.com/open-source/gsoc/ Google Summer of Code] 2023 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2023 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages
* If you are a '''mentor''' you should go to our [[Google Summer of Code Administrative]] page.


== New Modifications with GSoC 2022 and continuing ahead (Must Read) ==

* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

See also older Google Summer of Code
[[Google Summer of Code 2022|2022]],
[[Google Summer of Code 2021|2021]],
[[Google Summer of Code 2020|2020]],
[[Google Summer of Code 2019|2019]],
[[Google Summer of Code 2018|2018]],
[[Google Summer of Code 2017|2017]],
[[Google Summer of Code 2016|2016]],
[[Google Summer of Code 2015|2015]],
[[Google Summer of Code 2014|2014]],
[[Google Summer of Code 2013|2013]],
[[Google Summer of Code 2012|2012]],
[[Google Summer of Code 2011|2011]],
[[Google Summer of Code 2010|2010]],
[[Google Summer of Code 2009|2009]],
[[Google Summer of Code 2008|2008]] and
[[Google_Summer_of_Code_2007|2007]] wiki pages for previous ideas and blogs from the 180+ students we've graduated through the program already.

You can subscribe to the OSGeo Google Summer of Code Mailing List here:

: http://lists.osgeo.org/mailman/listinfo/soc

[[Category:Google Summer of Code]]

Google Summer of Code 2023

2023-01-24T09:27:33Z

RajatShinde: GSoC 2023 main page

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Welcome to the OSGeo [https://developers.google.com/open-source/gsoc/ Google Summer of Code] 2023 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2022 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages
* If you are a '''mentor''' you should go to our [[Google Summer of Code 2022 Administrative]] page.


== New Modifications with GSoC 2022 and continuing ahead (Must Read) ==

* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

See also older Google Summer of Code
[[Google Summer of Code 2022|2022]],
[[Google Summer of Code 2021|2021]],
[[Google Summer of Code 2020|2020]],
[[Google Summer of Code 2019|2019]],
[[Google Summer of Code 2018|2018]],
[[Google Summer of Code 2017|2017]],
[[Google Summer of Code 2016|2016]],
[[Google Summer of Code 2015|2015]],
[[Google Summer of Code 2014|2014]],
[[Google Summer of Code 2013|2013]],
[[Google Summer of Code 2012|2012]],
[[Google Summer of Code 2011|2011]],
[[Google Summer of Code 2010|2010]],
[[Google Summer of Code 2009|2009]],
[[Google Summer of Code 2008|2008]] and
[[Google_Summer_of_Code_2007|2007]] wiki pages for previous ideas and blogs from the 180+ students we've graduated through the program already.

You can subscribe to the OSGeo Google Summer of Code Mailing List here:

: http://lists.osgeo.org/mailman/listinfo/soc

[[Category:Google Summer of Code]]

Google Summer of Code 2023 Ideas

2023-01-24T09:23:20Z

RajatShinde: /* New Modifications with GSoC 2022 and continuing ahead(Must Read) */

Google Summer of Code 2023 Ideas

2023-01-24T09:17:03Z

RajatShinde: GSoC 2023

OSGeo Budget 2023

2023-01-20T21:46:11Z

RajatShinde:

Draft budget for 2023, see [[OSGeo Budget 2022]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.
|-
| Travel
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| EGU townhall + sprint support for open research data and standards integration
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 7,500 [7,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 8,000
| Request budget to support growing interest in incubation program. Also interested in improving documentation for the osgeo board "community project" program so that consistent links can be handed out to interested parties.
|}

Total Committees Budget for 2022: $52,550 USD

Total Committees spending for 2022: TBD

Total Committees Budget for 2023: TBD

== OSGeo Initiatives ==

OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

Proposed initiatives:

* security - proposed emergency funding for osgeo projects confronted with disruptive security issue. Application similar to code-sprint requires both a solid budget and a formal CVE report to work against.
* opengis harmonization - proposed response to [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] coordinating required activities across projects (rather than as individual budget requests listed below).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| FOSS4G
| style="text-align:right;" | 66,796
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2022.
|-
| Local Chapters
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.
|-
| Events and Code Sprints
| style="text-align:right;" | 20,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.
|-
| Community Projects
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 30 projects expected in 2022. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2022: $106,796 USD

Total Initiatives spending for 2022: TBD

Total Initiatives Budget for 2023: TBD

= Projects =

== OSGeo Projects ==

OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.

Notes:

* We have reached out (2022) to the projects mailing list.
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.
* Projects with a plan may of course ask for increased funding
* This is a budget, representing planned spending in 2022 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/deegree/deegree3/wiki/deegree-budget-2023
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 2,500 (in process)
| style="text-align:right;" | TBD [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-10-21
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GeoServer Budget 2023]]
|-
| GeoTools
| style="text-align:right;" | 500
| style="text-align:right;" | 10,500
| style="text-align:right;" | TBD
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2023 GeoTools Budget Request 2023]
|-
| GRASS GIS
| style="text-align:right;" | 4,000 [3964.49]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2023 GRASS GIS budget request 2023]
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD [5,000]
| [[GvSIG Budget 2023]]
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Need to report to the board to get a budget
|-
| OpenLayers
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| https://wiki.osgeo.org/wiki/OpenLayers_Budget_2023
|-
| OTB
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | [3,500]
| for trademark expenses
|-
| PROJ
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [2,500]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
|}

Total Projects Budget for 2022: $33,000 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2023: TBD

== Community Projects ==

Community projects act through the board as they do not have a project officer. Board approved $300 for each project (see Community Projects Initiative above)

Some guidance is offered by individual projects below.

Please note that this table records budget requests, not approved budgets.

* Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget.
* Projects that have been accepted into the incubation program can ask the Incubation Committee for assistance to work on incubation (such requests are included in the incubation committee budget not here).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget.
|-
| istSOS
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | 1000
| request to support a sprint on code renew to support other specification (STAC)
|-
| GeoWebCache
| style="text-align:right;" | 300
| style="text-align:right;" |
| style="text-align:right;" | 5000
| GeoWebCache request funding to work on Issue [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] (either directly or as part of a cross-project initaitive)
|-
| ZOO-Project
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/ZOO-Project/ZOO-Project/wiki/ZOO-Project-Budget-2023
|
|}

= Events =

== Community Events ==

We have set aside a budget for community events in 2022:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No financial request made, seed and sponsorship money exists from previous years.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| (included in project request above)
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-01-30]]
* Loomio Motion: TBD
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2023

2023-01-20T19:56:07Z

RajatShinde: /* OSGeo Projects */

Draft budget for 2023, see [[OSGeo Budget 2022]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.
|-
| Travel
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| EGU townhall + sprint support for open research data and standards integration
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 7,500 [7,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 8,000
| Request budget to support growing interest in incubation program. Also interested in improving documentation for the osgeo board "community project" program so that consistent links can be handed out to interested parties.
|}

Total Committees Budget for 2022: $52,550 USD

Total Committees spending for 2022: TBD

Total Committees Budget for 2023: TBD

== OSGeo Initiatives ==

OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

Proposed initiatives:

* security - proposed emergency funding for osgeo projects confronted with disruptive security issue. Application similar to code-sprint requires both a solid budget and a formal CVE report to work against.
* opengis harmonization - proposed response to [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] coordinating required activities across projects (rather than as individual budget requests listed below).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| FOSS4G
| style="text-align:right;" | 66,796
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2022.
|-
| Local Chapters
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.
|-
| Events and Code Sprints
| style="text-align:right;" | 20,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.
|-
| Community Projects
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 30 projects expected in 2022. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2022: $106,796 USD

Total Initiatives spending for 2022: TBD

Total Initiatives Budget for 2023: TBD

= Projects =

== OSGeo Projects ==

OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.

Notes:

* We have reached out (2022) to the projects mailing list.
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.
* Projects with a plan may of course ask for increased funding
* This is a budget, representing planned spending in 2022 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/deegree/deegree3/wiki/deegree-budget-2023
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 2,500 (in process)
| style="text-align:right;" | TBD [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-10-21
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GeoServer Budget 2023]]
|-
| GeoTools
| style="text-align:right;" | 500
| style="text-align:right;" | 10,500
| style="text-align:right;" | TBD
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2023 GeoTools Budget Request 2023]
|-
| GRASS GIS
| style="text-align:right;" | 4,000 [3964.49]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2023 GRASS GIS budget request 2023]
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD [5,000]
| [[GvSIG Budget 2023]]
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Need to report to the board to get a budget
|-
| OpenLayers
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| https://wiki.osgeo.org/wiki/OpenLayers_Budget_2023
|-
| OTB
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | [3,500]
| for trademark expenses
|-
| PROJ
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [2,500]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| ZOO-Project
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/ZOO-Project/ZOO-Project/wiki/ZOO-Project-Budget-2023
|}

Total Projects Budget for 2022: $33,000 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2023: TBD

== Community Projects ==

Community projects act through the board as they do not have a project officer. Board approved $300 for each project (see Community Projects Initiative above)

Some guidance is offered by individual projects below.

Please note that this table records budget requests, not approved budgets.

* Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget.
* Projects that have been accepted into the incubation program can ask the Incubation Committee for assistance to work on incubation (such requests are included in the incubation committee budget not here).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget.
|-
| istSOS
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | 1000
| request to support a sprint on code renew to support other specification (STAC)
|-
| GeoWebCache
| style="text-align:right;" | 300
| style="text-align:right;" |
| style="text-align:right;" | 5000
| GeoWebCache request funding to work on Issue [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] (either directly or as part of a cross-project initaitive)
|-
|}

= Events =

== Community Events ==

We have set aside a budget for community events in 2022:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No financial request made, seed and sponsorship money exists from previous years.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| (included in project request above)
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-01-30]]
* Loomio Motion: TBD
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2023

2023-01-20T19:55:37Z

RajatShinde: /* OSGeo Projects */

Draft budget for 2023, see [[OSGeo Budget 2022]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.
|-
| Travel
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| EGU townhall + sprint support for open research data and standards integration
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 7,500 [7,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 8,000
| Request budget to support growing interest in incubation program. Also interested in improving documentation for the osgeo board "community project" program so that consistent links can be handed out to interested parties.
|}

Total Committees Budget for 2022: $52,550 USD

Total Committees spending for 2022: TBD

Total Committees Budget for 2023: TBD

== OSGeo Initiatives ==

OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

Proposed initiatives:

* security - proposed emergency funding for osgeo projects confronted with disruptive security issue. Application similar to code-sprint requires both a solid budget and a formal CVE report to work against.
* opengis harmonization - proposed response to [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] coordinating required activities across projects (rather than as individual budget requests listed below).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| FOSS4G
| style="text-align:right;" | 66,796
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2022.
|-
| Local Chapters
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.
|-
| Events and Code Sprints
| style="text-align:right;" | 20,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.
|-
| Community Projects
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 30 projects expected in 2022. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2022: $106,796 USD

Total Initiatives spending for 2022: TBD

Total Initiatives Budget for 2023: TBD

= Projects =

== OSGeo Projects ==

OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.

Notes:

* We have reached out (2022) to the projects mailing list.
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.
* Projects with a plan may of course ask for increased funding
* This is a budget, representing planned spending in 2022 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/deegree/deegree3/wiki/deegree-budget-2023
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 2,500 (in process)
| style="text-align:right;" | TBD [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-10-21
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GeoServer Budget 2023]]
|-
| GeoTools
| style="text-align:right;" | 500
| style="text-align:right;" | 10,500
| style="text-align:right;" | TBD
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2023 GeoTools Budget Request 2023]
|-
| GRASS GIS
| style="text-align:right;" | 4,000 [3964.49]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2023 GRASS GIS budget request 2023]
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD [5,000]
| [[GvSIG Budget 2023]]
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Need to report to the board to get a budget
|-
| OpenLayers
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| https://wiki.osgeo.org/wiki/OpenLayers_Budget_2023
|-
| OTB
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | [3,500]
| for trademark expenses
|-
| PROJ
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [2,500]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| ZOO-Project
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4000]
| https://github.com/ZOO-Project/ZOO-Project/wiki/ZOO-Project-Budget-2023
|}

Total Projects Budget for 2022: $33,000 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2023: TBD

== Community Projects ==

Community projects act through the board as they do not have a project officer. Board approved $300 for each project (see Community Projects Initiative above)

Some guidance is offered by individual projects below.

Please note that this table records budget requests, not approved budgets.

* Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget.
* Projects that have been accepted into the incubation program can ask the Incubation Committee for assistance to work on incubation (such requests are included in the incubation committee budget not here).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget.
|-
| istSOS
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | 1000
| request to support a sprint on code renew to support other specification (STAC)
|-
| GeoWebCache
| style="text-align:right;" | 300
| style="text-align:right;" |
| style="text-align:right;" | 5000
| GeoWebCache request funding to work on Issue [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] (either directly or as part of a cross-project initaitive)
|-
|}

= Events =

== Community Events ==

We have set aside a budget for community events in 2022:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No financial request made, seed and sponsorship money exists from previous years.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| (included in project request above)
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-01-30]]
* Loomio Motion: TBD
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

Standards Committee/Meetings/Meeting-2022-12-19

2022-12-19T14:52:03Z

RajatShinde:

== Date/Time==
[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022&month=11&day=17&hour=14&min=0&sec=0&p1=250&p2=26&p3=152&p4=195 Monday 19 December 2022 12h - 13h UTC]

==Location==
https://meet.jit.si/OSGeo

==Attendees==
TBD

==Agenda==

* roll call
* terms of reference
* TC representation
* participation
* work items
** CITE
** OGC workshop and dedicated onboarding sessions? https://lists.osgeo.org/pipermail/standards/2022-November/001301.html
*** timeline Q1 2023
*** call for interest Jan 2023
** bidding for innovation initiatives (as a coordinated OSGeo)
*** how to govern funding from other organizations
*** selection of '''parts''' of a bid
*** joint sprint (locations TBC)
**** Q1 2023: Switzerland
**** Q2/Q3: US
**** Q4 2023: London, UK
** OSGeo / OGC / ASF sprint

==Notes==
TBD

==Actions==
TBD

== Next meeting==
YYYY-MM-DD

2023 plans for GeoforAll

2022-10-09T19:02:33Z

RajatShinde: Add name

We are planning a meeting to discuss the future leadership and plans of GeoforAll from 2023 and beyond.

If you are interested in participating in this meeting, please add your name and email below:
* Victoria Rautenbach, victoria.rautenbach@gmail.com
* Rajat Shinde, rajatshinde2303@gmail.com

'''Meeting agenda:'''
''To be added''

Google Summer of Code 2022

2022-09-24T05:26:48Z

RajatShinde: Update GSoC 2022 results

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Welcome to the OSGeo [https://developers.google.com/open-source/gsoc/ Google Summer of Code] 2022 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2022 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages
* If you are a '''mentor''' you should go to our [[Google Summer of Code 2022 Administrative]] page.
* Final Results: [[Google Summer of Code 2022 Results]]

== New Modifications with GSoC 2022 (Must Read) ==
(citing from official GSoC 2022 announcement)

* Starting in 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple size projects ~175 hour (medium) and 350 hour (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12 week coding time frame to a maximum of 22 weeks. This is to allow for folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

See also older Google Summer of Code
[[Google Summer of Code 2021|2021]],
[[Google Summer of Code 2020|2020]],
[[Google Summer of Code 2019|2019]],
[[Google Summer of Code 2018|2018]],
[[Google Summer of Code 2017|2017]],
[[Google Summer of Code 2016|2016]],
[[Google Summer of Code 2015|2015]],
[[Google Summer of Code 2014|2014]],
[[Google Summer of Code 2013|2013]],
[[Google Summer of Code 2012|2012]],
[[Google Summer of Code 2011|2011]],
[[Google Summer of Code 2010|2010]],
[[Google Summer of Code 2009|2009]],
[[Google Summer of Code 2008|2008]] and
[[Google_Summer_of_Code_2007|2007]] wiki pages for previous ideas and blogs from the 180+ students we've graduated through the program already.

You can subscribe to the OSGeo Google Summer of Code Mailing List here:

: http://lists.osgeo.org/mailman/listinfo/soc

[[Category:Google Summer of Code]]

Google Summer of Code 2022 Results

2022-09-24T05:24:26Z

RajatShinde: GSoC 2022 results update

Board Meeting 2022-09-26

2022-08-31T10:43:11Z

RajatShinde:

This board meeting is '''scheduled Monday 26 September 2022''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022&month=09&day=26&hour=15&min=0&sec=0&p1=250&p2=26&p3=49&p4=155&p5=217&p6=312 '''15:00''' UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.

== Agenda ==

=== Current items ===

# ''roll call''
# ''appoint meeting chair, meeting scribe/secretary''
# ''Review and approve past minutes''
#* [[Board_Meeting_2022-08-27]]
# Meet with SmartGEO Expo group
# GISTAM 2023 : Partnership proposal with The Open Source Geospatial Foundation (2nd reminder)
# ''Add your topic here''

== Minutes ==

* Presiding:
* Scribing:
* Attending:
* Guests:

=== Actions ===

* See https://git.osgeo.org/gitea/osgeo/todo/issues

== IRC Log ==
* no log, a jitsi meeting

== Next meeting ==
*[[Board Meeting 2022-10-31]]

[[Category:Board]]
[[Category:Board Meetings 2022]]

Google Summer of Code 2022 Accepted

2022-05-28T06:33:40Z