nyuuzyou/wikis huggingface dataset:
GitInfrastructureComparison

= Comparison Table =
This table is aimed at helping to decide which service to install on 
OSGeo machines to provide hosting for OSGeo projects. 
 
The priority of each parameter is not currently defined.
See a list of requirements here
Feature 	Gitea 	GitLab-CE 	Trac 	Kallithea
deployed in staging 	YES 	NO 	YES (in use) 	NO
open dev. model 	YES 	MOSTLY (2) 	 	YES
security level 	 	 	 	
login via LDAP 	YES 	YES 	YES 	YES
LDAP groups sync 	NO 	 	 	
autonomous creation of repositories 	YES 	YES 	NO 	YES
autonomous creation of organizations	YES 	 	NO 	YES
organization management 	YES 	YES 	NO 	YES
private repositories 	YES 	YES 	 	YES
external issue tracker 	YES (example) 	YES 	NO 	MIN
automatic mirroring of git repos 	YES 	NO (EE only)	 	
internal issue tracker 	YES 	YES 	YES 	NO
tool to migrate from trac 	YES 	YES 	n/a 	tbd
tool to migrate from github 	 	YES 	 	
external wiki 	YES 	 	 	tbd
internal wiki 	YES (1) 	YES (1) 	YES 	NO
comment issues via mail 	NO 	YES 	YES 	YES
PostgreSQL backend 	YES 	YES 	YES 	YES
Multilanguage 	15 languages 	 	YES 	YES
Comments on diff lines 	NO 	YES 	YES (via plugins)	YES
Pull requests 	YES 	YES 	NO (?) 	YES
Webhooks 	YES 	YES 	 	tbd
Edit GIT hooks 	YES (only for enabled users) 	 	 	YES
CI 	external (like drone) 	integrated 	YES (plugin) 	YES
tracking of forks 	YES (example) 	YES 	NO 	YES
download area 	NO (but annotated tags become downloadable packages)	YES (3) 	NO 	
static web pages 	NO 	NO 	NO 	YES
ticket reply by mail 	NO 	 	YES (via plugin) 	
* (1) : GitLab and Gitea wiki permissions match repo ones. GitLab and Gitea wikis can be accessed through a git repo.
* (2) : GitLab's development process is subject to discussion and subjective opinions. Be careful when stating a definite answer to this question. You can read here and also here and there with your trollometer on.
* (3) : GitLab allows to add release notes to git tags. Release notes are Markdown text, and you can attach files to it, resulting in a download area much like github's release area.
= Other Comparisons =
* Features comparison of Gogs, GitLab, GitHub
* Choose the git host comparison table for notabug.org
= More about existing software packages =
See GitHostingSoftware
Category:Infrastructure
GitServiceRequirement

Requirements for a Git service offered by OSGeo, useful to evaluate possible solutions (see GitInfrastructureComparison)
Please add your name to the ones that are important to you, and add more items if needed.
 
# Sign in using OSGeo Userid
## --strk (talk) 06:01, 27 April 2016 (PDT)
## --kalxas (kalxas) 12:00, 06 June 2016 (UTC)
## --mloskot 21:25, 19 March 2017
# Autonomously create and manage teams
## --strk (talk) 06:01, 27 April 2016 (PDT)
## --kalxas (kalxas) 12:00, 06 June 2016 (UTC)
# Autonomously create and manage repositories
## --strk (talk) 06:01, 27 April 2016 (PDT)
## --kalxas (kalxas) 12:00, 06 June 2016 (UTC)
## --mloskot 21:25, 19 March 2017
# Create private repositories (for software vulnerability testing, etc.)
## --strk (talk) 06:01, 27 April 2016 (PDT)
## --tomkralidis (tomkralidis) 06:01, 27 April 2016 (PDT)
## --kalxas (kalxas) 12:00, 06 June 2016 (UTC)
## --lucadelu (lucadelu) 7:00, 05 September 2016 (UTC)
## --mloskot 21:25, 19 March 2017
# Import tickets from Trac
## --strk (talk) 06:01, 27 April 2016 (PDT)
## --kalxas (kalxas) 12:00, 06 June 2016 (UTC)
## --lucadelu (lucadelu) 7:00, 05 September 2016 (UTC)
## --mloskot 21:25, 19 March 2017
# Import tickets from Redmine
# Comment tickets via email
## --strk (talk) 06:34, 27 April 2016 (PDT)
# Comment/close tickets via commit log
## --strk (talk) 06:34, 27 April 2016 (PDT)
## --lucadelu (lucadelu) 7:00, 05 September 2016 (UTC)
## --mloskot 21:25, 19 March 2017
# SVN->GIT sync - (Mirroring existing SVN repository) see:/ticket/1654
## --epifanio (talk) 04:49, 01 September 2016 (PDT)
## --lucadelu (lucadelu) 7:00, 05 September 2016 (UTC)
# Integration with CI service (hosted eg. Travis CI, AppVeyor, GitLab CI), self-hosted (eg. Buildbot, ?))
## --mloskot 21:25, 19 March 2017
## --strk (talk) 00:44, 20 March 2017 (PDT)
Add a new item if your requirement is missing
Category:Infrastructure
Glosario OSGeo

Esta página servirá de glosario para la traducción de los diferentes términos utilizados en la Fundación al Español.
This page will server as a glosary for the translation into Spanish of different terms and acronyms used by the Fundation.
English 	Acron.	Español
Board of Directors 	 	Comité de Dirección
Chair of a Committee 	 	Presidente del Comité
Discussion List 	 	Lista de conversación
Local Chapter 	LC 	Capítulo Local
Project Management Committee 	PMC 	Comité de Gestión del Proyecto
Project Steering Committee 	PSC 	Comité de Dirección del Proyecto
System Administration Committee	SAC 	Comité para la Administración de Sistemas
Category:Español
Glosario SIG

Esta lista proporciona un listado de equivalencias enter palabras en inglés y español para conceptos GIS o cualquier otra área empleada por los traductores en proyectos de OSGeo como el Live GIS Disc.
== C ==
English 	Español 	Notas
Computer	Computadora, ordenador	
== F ==
English 	Español 	Notas 	
Feature 	Feature 	La traducción directa es 'carasterística, atributo', pero en contexto se refiere a entidad geográfica vectorial. Lo dejaría sin traducir, en cursiva por ser anglicismo (con un asterisco al principio y al final de la palabra) Ver Discusión.	
Feature 	Elemento, entidad	Propuesta de traducción. Creo que es una palabra a la que sí podemos encontrarle equivalencias en castellano. 	
Filter Encoding	Filter Encoding 	 	
== H ==
English 	Español 	Notas
hardcopy maps	mapas en papel	
== L ==
English	Español	Notas
Layer 	Capa 	
== O ==
English 	Español	Notas
Overview	Resumen	
== Q ==
English 	Español 	Notas
Quick start	Guía de inicio rápido	
== R ==
English	Español 	Notas 	
Render 	Renderizar	Aunque no sea muy correcta (en la discusión de Wikipedia proponen, por ejemplo, "modelar" o "representar") creo que es ampliamente usada y se entiende mejor el significado.	
Raster 	Raster 	Aunque no sea una palabra correcta en castellano, está ampliamente extendida y su significado es de sobra conocido. 	
== T ==
English	Español 	Notas 	
Tiles 	Tiles, teselas	La traducción literal es 'azulejos', se refiere a los archivos unitarios de imágenes de mapas con los que componen los geoservers las imagenes, según zona y zoom. Lo dejaría sin traducir, en cursiva por ser anglicismo (con un asterisco al principio y al final de la palabra) *IHMO* La traducción más conveniente es tesela, así es como se ha llamado siempre a las piezas que forman un mosaico [adiez] Ver Discusión	
== W ==
English 	Español 	Notas 	
WMS Tiling Cache	WMS Tiling Cache	Lo dejaría sin traducir, en cursiva por ser anglicismo (con un asterisco al principio y al final de la palabra) Ver Discusión	
__NOTOC__
Category:Education Category:Libro SIG
Gonzalo Perez

Location: Buenos Aires, Argentina
Experience:
2008 - I joined as a contributor to OpenStreetMap project. 
2012 - I became member of Geoinquietos Argentina (formerly Geoinquietos Buenos Aires).
2013 - I was part of the FOSS4G Buenos Aires 2013 conference team and organized the first State of the Map (SotM) in Buenos Aires as a side event and local edition of the OSM international conference.
2014 - Coordinator of the State of the Map 2014 (OpenStreetMap's international conference) held in Buenos Aires.
During the organization of that conference (it took a year), I proposed to other latin american OSM's contributors to create a group with our communities to gather them and work together in common objectives, months later the OSM-LatAm group was founded. After some weeks, at 'SotM 2014' we proposed to make every year a regional conference called State of the Map Latam which started in 2015.
2015 - I started to work for the National Geographic Institute.
Accepted as Charter Member of OSGeo.
2016 - Financial responsible of FOSS4G Argentina 2016 conference
2017 - Member of the FOSS4G + SOTM Argentina 2017 conference team.
Contact:
: Email: zalitoar AT gmail DOT com
: Twitter: @zalitoar
: LinkedIn gonzalogabrielperez
Category:OSGeo Member
Category:Argentina
Google Code In 2017 Recommendations for Students

@ 
== Welcome to OSGeo! ==
We are a fun vibrant community that believes in sharing Open Source software related to making maps.
== How to ask general questions about the Code-in ==
Send an Email of questions to OSGeo
* subscribe to OSGeo's "gci-discuss" mailing list here
* ask your question, and usually within a day someone from the OSGeo Code-in team (mentors or administrators) will reply
* all OSGeo mentors for the Code-in contest follow this "gci-discuss" mailing list
Ask on the #osgeo-gci IRC chat channel
* IRC-channel: #osgeo-gci channel on freenode.net
** how to connect: choose your favorite IRC client, or go directly through your web browser with webchat
** enter a nickname and click "I am not a robot" and press "Connect"
** upon entering, ask your questions as you wish (no need to wait, just say "hello, I have a question about the Code-In, how do I..."
== Get to know the OSGeo Community ==
The OSGeo foundation ( http://osgeo.org ) was founded in the year 2006 and contains many different types of Open Source software projects to help make geographical maps.
The OSGeo foundation also holds a super-fun conference each year, all over the world, named FOSS4G ( http://foss4g.org ) for Free and Open Source Software for Geospatial.
* Follow OSGeo on Twitter: @OSGeo
* Follow FOSS4G on Twitter: @foss4g
== Why OSGeo? ==
# the global geospatial (mapping) industry is huge now (400 Billion USD revenue industry, as of September 2017, read report)
# learn skills useful to get jobs in the mapping industry (Open Source is rarely taught at school, yet it is in huge demand by employers around the world)
# OSGeo community members are fun, vibrant, and willing to help!
# we have local chapters (local groups getting together or discussing on their own mailing lists in many languages) all over the world! (see list)
== Coding Languages ==
OSGeo projects use a variety of coding languages, including:
* C
* C++
* Java
* Python
* JavaScript
== OSGeo Projects & Initiatives Involved in the Code-In ==
* FOSS4G (global conference event)
* GeoServer (web mapping)
* GeoTools (geospatial library)
* GRASS GIS (desktop)
* gvSIG (desktop & mobile)
* MapServer (web mapping)
* OpenLayers (web mapping)
* OSGeoLive (installer for projects)
* pgRouting (geospatial library)
== Searching for a Project's Mailing list Archives ==
A good trick to search an OSGeo project's mailing list for help, if you are stuck on a coding problem, is to use OSGeo's Nabble Forum: http://osgeo-org.1560.x6.nabble.com/
Category:Google Code In
Google Code In 2018 Lessons Learned

(see the 2017 lessons learned page)
= Purpose =
This is to document things that admins and mentors learned, for the benefit of future Code-In exercises.
== Spam on the IRC channel ==
In 2018, we had some issues with one or two students spamming the IRC channel. The policies of the channels might need to be reviewed. Additionally, ensure that there are moderators in covering the majority of the time zones. 
== Limit the number of design tasks == 
The number of design tasks should be limited to ensure that students do not exclusively complete design tasks. 
== Possible task to teach the students about plagiarism==
At the GSoC summit, there was a lot of discussion on students that cheat. The consensus was that do not always understand what plagiarism is. The suggestion to deal with this is to possibly develop a beginner task that introduce them to the concept. For example, this test was developed for university students. 
Category:Google Code In
Google Code In 2018 Recommendations for Students

@ 
== Welcome to OSGeo! ==
We are a fun vibrant community that believes in sharing Open Source software related to making maps.
== How to ask general questions about the Code-in ==
Send an Email of questions to OSGeo
* subscribe to OSGeo's "gci-discuss" mailing list here
* ask your question, and usually within a day someone from the OSGeo Code-in team (mentors or administrators) will reply
* all OSGeo mentors for the Code-in contest follow this "gci-discuss" mailing list
Ask on the #osgeo-gci IRC chat channel
* IRC-channel: #osgeo-gci channel on freenode.net
** how to connect: choose your favorite IRC client, or go directly through your web browser with webchat
** enter a nickname and click "I am not a robot" and press "Connect"
** upon entering, ask your questions as you wish (no need to wait, just say "hello, I have a question about the Code-In, how do I..."
== Get to know the OSGeo Community ==
The OSGeo foundation ( http://osgeo.org ) was founded in the year 2006 and contains many different types of Open Source software projects to help make geographical maps.
The OSGeo foundation also holds a super-fun conference each year, all over the world, named FOSS4G ( http://foss4g.org ) for Free and Open Source Software for Geospatial.
* Follow OSGeo on Twitter: @OSGeo
* Follow FOSS4G on Twitter: @foss4g
== Why OSGeo? ==
# the global geospatial (mapping) industry is huge now (400 Billion USD revenue industry, as of September 2017, read report)
# learn skills useful to get jobs in the mapping industry (Open Source is rarely taught at school, yet it is in huge demand by employers around the world)
# OSGeo community members are fun, vibrant, and willing to help!
# we have local chapters (local groups getting together or discussing on their own mailing lists in many languages) all over the world! (see list)
== Coding Languages ==
OSGeo projects use a variety of coding languages, including:
* C
* C++
* Java
* Python
* JavaScript
== OSGeo Projects & Initiatives Involved in the Code-In ==
* FOSS4G (global conference event)
* GeoServer (web mapping)
* GRASS GIS (desktop)
* istSOS (web mapping)
* Leaflet (web mapping)
* MapServer (web mapping)
* OSGeoLive (installer for projects)
* pgRouting (geospatial library)
== Searching for a Project's Mailing list Archives ==
A good trick to search an OSGeo project's mailing list for help, if you are stuck on a coding problem, is to use OSGeo's Nabble Forum: http://osgeo-org.1560.x6.nabble.com/
Category:Google Code In
Google Code In 2019 Foundation Tasks

A page for the 2019 Google Code-In initiative (2 December 2019 to 23 January 2020).
== Join the OSGeo community ==
* your name
** link to your user account
== Video of experience with GCI and OSGeo ==
* your name
** link to Youtube video
== Video of what FOSS4G means to you ==
* your name
** link to Youtube video
Category:Google Code In
Google Code In 2019 Recommendations for Students

@ 
== Welcome to OSGeo! ==
We are a fun vibrant community that believes in sharing Open Source software related to making maps.
== How to ask general questions about the Code-in ==
Send an Email of questions to OSGeo
* subscribe to OSGeo's "gci-discuss" mailing list here
* ask your question, and usually within a day someone from the OSGeo Code-in team (mentors or administrators) will reply
* all OSGeo mentors for the Code-in contest follow this "gci-discuss" mailing list
Ask on the #osgeo-gci IRC chat channel
* IRC-channel: #osgeo-gci channel on freenode.net
** how to connect: choose your favorite IRC client, or go directly through your web browser with webchat
** enter a nickname and click "I am not a robot" and press "Connect"
** upon entering, ask your questions as you wish (no need to wait, just say "hello, I have a question about the Code-In, how do I..."
== Get to know the OSGeo Community ==
The OSGeo foundation ( http://osgeo.org ) was founded in the year 2006 and contains many different types of Open Source software projects to help make geographical maps.
The OSGeo foundation also holds a super-fun conference each year, all over the world, named FOSS4G ( http://foss4g.org ) for Free and Open Source Software for Geospatial.
* Follow OSGeo on Twitter: @OSGeo
* Follow FOSS4G on Twitter: @foss4g
== Why OSGeo? ==
# the global geospatial (mapping) industry is huge now (400 Billion USD revenue industry, as of September 2017, read report)
# learn skills useful to get jobs in the mapping industry (Open Source is rarely taught at school, yet it is in huge demand by employers around the world)
# OSGeo community members are fun, vibrant, and willing to help!
# we have local chapters (local groups getting together or discussing on their own mailing lists in many languages) all over the world! (see list)
== Coding Languages ==
OSGeo projects use a variety of coding languages, including:
* C
* C++
* Java
* Python
* JavaScript
== OSGeo Projects & Initiatives Involved in the Code-In ==
* FOSS4G (global conference event)
* GeoServer (web mapping)
* GRASS GIS (desktop)
* istSOS (web mapping)
* Leaflet (web mapping)
* MapServer (web mapping)
* OSGeoLive (installer for projects)
* pgRouting (geospatial library)
== Searching for a Project's Mailing list Archives ==
A good trick to search an OSGeo project's mailing list for help, if you are stuck on a coding problem, is to use OSGeo's Nabble Forum: http://osgeo-org.1560.x6.nabble.com/
Category:Google Code In
Google Code In 2019 Results Press Release

@ 
=== Title: Announcing OSGeo’s 2019 Google Code-in winners ===
Google Code-in (GCI) is an annual online competition aimed at introducing pre-university students (13-17 years old) to open source projects, development and communities, through short 3-5 hour tasks [1]. As opposed to the Google Summer of Code program, in GCI students are not selected by the organizations, but freely pick up tasks from one or more mentoring organizations and complete them. Students qualify for different prizes (i.e. certificate, t-shirts, hoodies and the grand prize of visiting Google’s main headquarters in San Francisco) depending on the number of tasks they complete. During GCI, OSGeo project members have a unique opportunity to interact with pre-university students and to encourage them to become part of their respective projects.
The OSGeo team consisted of 16 community members that contributed 110 tasks from 11 projects (e.g. istSOS, GRASS GIS, GeoServer, pgRouting, PostGIS, GeoNode and OpenLayers) and also OSGeo, FOSS4G and GeoForAll.
The 2019 Google Code-in (GCI) took place 2 December 2019 - 21 January 2020 and OSGeo had 401 students that completed a task with us. These 401 students completed 976 tasks [2] which is the most amount of completed tasks to date for OSGeo! This is an improvement from last year and this can be contributed to the change in dates of the competition going back to the original dates. The completed tasks range from designing badges for the OSGeo website, to tests for GRASS GIS, or bug fixes for PostGIS. These tasks might seem simplistic in some cases, but the combined results are of great value to OSGeo.
OSGeo is pleased to announce the 2019 Google Code-in Grand Prize winners, who each receive a free trip to Google headquarters in California, along with a parent/guardian, are students (note that these are the student’s account names, due to privacy concerns):
OSGeo’s Google Code-in Winners:
•	Navya Garg
•	Pranay
OSGeo’s Google Code-in Runners Up:
•	Dhanus SL
•	Lucifer
OSGeo’s Google Code-in finalists (who receive Google hoodies) are:
•	TanvirSingh
•	anishagnihotri
See here: https://codein.withgoogle.com/winners/#winners the winners from all organisations [3].
Congratulations to the winners and finalists! But also a special congratulations to all students that received a certificate and/or t-shirt. We greatly appreciate your contribution to OSGeo!
Lastly, thank you to the OSGeo mentors for the time they spent on the tasks and mentoring the students. Without your commitment this would not have been possible.
Thank you to everyone involved, mentors and students.
Regards,
OSGeo GCI admins 2019
Links:
[1] https://codein.withgoogle.com
[2] https://codein.withgoogle.com/tasks/?sp-search=OSGeo
[3] https://codein.withgoogle.com/winners/#winners
Category:Google Code In
Google Summer of Code 2007

Central page for administering OSGeo participation in Google Summer of Code 2007.
= Background = 
* Frank Warmerdam will act as Administrative contact, with support from Landon Blake.
* Google documentation on the program is at: http://code.google.com/support/bin/topic.py?topic=10442
* Last years SoC submission from Refractions: http://code.google.com/soc/2006/refract/about.html
* Last years introduction and ideas list from Refractions (uDig, PostGIS): http://www.refractions.net/soc2006/
* Mentoring HOWTO: http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html
= Timeline =
* March 12: Mentoring organization application deadline (we should have project ideas lists ready)
* March 24: Student application deadline. 
* April 9: Project PSC ordering decisions submitted in SoC Application Rankings by Project
* April 11: Accepted student applications announced.
* May 28: Students begin work.
* August 31: final evaluation deadline.
= Project Ideas Lists = 
Please link project specific proposed projects here:
* GDAL SoC Ideas
* GeoServer SoC Ideas
* GeoTools Soc Ideas
* GRASS SoC Ideas
* MapGuide Soc Ideas
* PostGIS SoC Ideas
* User-friendly Desktop Internet GIS SoC Ideas
* OpenJUMP 2007 SOC Ideas
* MapServer_2007_SOC_Ideas
The "Student Landing Page" is 2007 SoC Merged Ideas.
= Documents =
* OSGeo 2007 Google SoC Application
* SoC Application Rankings by Project
= Project Milestones =
2007 Google SoC Project Milestones
Category:Google Summer of Code
Google Summer of Code 2008 Administrative

Central page for administering OSGeo participation in Google Summer of Code 2008.
= Background = 
* Wolf Bergenheim will act as Administrative contact, with support from Frank Warmerdam.
* Google documentation on the program is at: http://code.google.com/support/bin/topic.py?topic=10442
* There is also a Google Wiki page about the program: http://code.google.com/p/google-summer-of-code/wiki/WikiStart
* Last years GSoC submission: http://code.google.com/soc/2007/osgeo/about.html
* Last years GSoC page: Google Summer of Code 2007
* Mentoring HOWTO: http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html
* Advice for Mentors from the Google Wiki: http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors
= Timeline =
* March 3rd: Project applications will be accepted
* March 17th: OSGeo has been accepted as a Google Summer of Code 2008 Mentoring Organization!
* March 24th: Student applications
= Project Ideas Lists = 
Please link project specific proposed projects here:
* GDAL SoC Ideas
* GRASS SoC Ideas
* Mapbender SoC ideas 2008
* OpenLayers & Mapbuilder SoC Ideas
* Quantum GIS SoC Ideas
* MapServer 2008 SOC Ideas
* Laval University/CamptoCamp 2008 SoC ideas
* GeoServer SoC 2008
* GeoTools SoC 2008
* uDig SoC 2008
these need updating!
* MapGuide Soc Ideas
* PostGIS SoC Ideas
* OpenJUMP 2007 SOC Ideas
The "Student Landing Page" is Google Summer of Code Ideas.
= Documents =
* OSGeo 2008 Google SoC Application
* SoC Application Rankings by Project
== How to register as a mentor ==
# Add your name, and google account information to the mentor list in the Wiki (or get your project leader to do that for you)
# Login to your Google Account.
# Start registration by reviewing and accepting the Google program Terms of Service.
# Once you have accepted the Terms of Service, you should automatically be redirected to the mentor dashboard.
# Click on the "My Profile" link[5] in the left hand navigation menu. Please update your personal information.
# At the bottom of the profile page, there will be a list of all organizations accepted into the program. Click the checkbox next to OSGeo and submit by clicking the "Become a Mentor" button.
# Subscribe to the OSGeo SoC mailinglist
= Project Milestones =
2008 Google SoC Project Milestones
= Project Pages =
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.
Category:Google Summer of Code