nyuuzyou/wikis huggingface dataset:
Comité Científico FOSS4G Buenos Aires

== Función ==
La función de este comité es orientar y facilitar a los expositores en la presentación de sus trabajos y charlas.
En este sentido se sugiere al final un modelo de preguntas orientativas para realizar el resumen.
== Objetivos == 
Revisar los trabajos, 
ordenarlos por temática y
proponer modificaciones que garanticen calidad, respeto ético y etiqueta.
==Presentaciones para FOSS4G en Buenos Aires==
El objetivo de las presentaciones es compartir experiencias realizadas con software libre relacionadas con geomática.
Las mismas podrán ser en la modalidad oral o poster. En todos los casos se deberá enviar un resumen expandido en español, y si es posible acompañada de su versión en ingles, utilizando el siguiente formulario.
===Modelo de Resumen===
Para facilitar la organización del resumen se recomienda explicar:
* Qué se hizo
* Por qué 
* Para qué
* Con qué 
* Cómo
* Cuáles fueron los resultados
* Qué se gana con ello.
Por ejemplo:
* Que se hizo
"Se hizo un nuevo algoritmo para el despliegue de MDT, bla bla bla..."
* Por qué
"La cartografia necesita distiguir las cosas con mejor detalle y ...."
* Para qué
"Porque lo que se ve en pantalla no es suficiente para tal cosa y necesitamos mejorar la calidad de despliegue...."
* Con qué
"Con numpy y ...."
* Como
"Se generó este nuevo algoritmo bla bla bla,  y se lo programó con Python...."
*  Los resultados son
"Hay un despliegue de mayor cantidad de grises y colores ...."
* Y que se gana con ello
"Mejoramos la visualizacion ...."
== Recomendaciones ==
Se sugiere que el resumen contenga los siguientes elementos: 
* una pequeña introducción al tema aclarando porqué es importante la presentación; 
* definir en pocas palabras la metodología y software utilizado; 
* si hay código, dónde se puede consultar; 
* si hay novedades de programación, cuáles son; 
* dar una descripción de la arquitectura utilizada (si es que tiene que ver con el tema); 
* si se trata de experiencias o aplicaciones describir las metodologías y configuraciones de hardware y software; 
* si hay propuestas para mejorar el software, arquitectura o metodologías; y
* por último un párrafo con las conclusiones y referencias. 
En el caso de que se adjunten gráficos será necesario que los diagramas o dibujos sean claros, y en lo posible utilicen formatos abiertos como jpg, png y svg.
Se debe indicar la fuente y los autores de la parte presentada que haya sido desarrollado en otro contexto u otras licencias de uso.
Con respecto a la etiqueta, se exige el respeto de los demás trabajos y opiniones. 
Por ejemplo, no debe decirse 
"mi software es el mejor" sino "no tengo conocimiento que mi software haya participado en un certamen con algún otro" o 
"lo tuyo o lo de los otros no sirve" sino "estuve tan concentrado desarrollando mi sorfware, que no alcancé a probar lo que hacían los demás".
La etiqueta es importante en cuanto ayuda a la gente a entenderse y a mantener el espíritu colaborativo que nos une. Aquí hay que sumar. 
No venimos a vender un producto, sino a intercambiar ideas y experiencias.
Category:Geoinquietos Argentina
Commercial Services

The Open Source Geospatial Foundation is a non profit organization and does not provide commercial services.
= Commercial use of OSGeo Software =
There are excellent preconditions to use Free and Open Source Software packages in Business contexts. To make most effective use of software (regardless of licensing style) it can be helpful to hire commercial service providers. They can deliver solutions, support and service in time and through regular contracts. In larger environments and complex infrastructures it is normal to hire specialists to look after the network infrastructure, perform database tuning, customize software or consult on the architecture. This applies to both proprietary and Free and Open Source Software.
OSGeo does not provide these services itself but has set up a Service Provider Directory to make this information available to businesses and organizations in need of professional services and with a budget to afford them.
= FOSS Business Models =
FOSS Business Models models are identical to those of any other IT enterprise. The only element which is missing is selling license usage rights through the proprietary licensing model. Professional Support and services provided by companies around the world comprise:
* Training, Workshops, Know-how dissemination
* Installation, Maintenance
* Consultation
* Customization of interfaces and features
* Implementation of new features
* Support and Hotline at all availability levels
* Research and Development
* add your source of income
Depending on the focus of the enterprise the business model can combine any of the above types.
= Business Ready Software =
Ready-to-use software is sometimes called COTS (Commercial Off The Shelf) software. There are several packages within OSGeo and the Free and Open Source community at large that can be used right off the shelf (but does not ship in shrink-wrap packages). Others like libraries, services or other infrastructure components need to be installed and configured individually, sometimes in large and highly complex or productive environments. Some such structures need to be maintained on a daily basis, for example if security requirements (Confidentiality, Availability, Integrity) are exceptionally high. Free and Open Source Geospatial software is used in allof these contexts and is just as diverse as are the needs.
Graduated OSGeo Software has gone through the Incubation Process and thus proven to follow the guidelines that have been set up to ensure several soft factors that a software project cannot always provide out of itself. These include legally clean code licenses and use of external libraries, a functioning community and truly open governance and decision structure. Additionally some technical requirements have been defined as being minimal to a healthy project like the use of a code repository, bug tracking environment and support mechanism, most often through mailing lists. 
Category:Advocacy
Community Sprints History

This page collects a list of past Community/Code Sprint events organised by OSGeo projects.
==== Template ====
* Event title, in the header
* Type of event (code sprint, focused on developers - user meeting - community sprint - ...)
* Date of event, City, Country
* link to event website/wiki page
* Number of attendees
* Total cost of the event (a public link to event budget is appreciated)
* Amount of OSGeo funding, if any
* Contact person
== 2013 ==
=== OSGeo project name ===
==== Event title 1 ====
== 2012 ==
TBD
Como-unirse-a-geo-for-all

1. Criterios de Admisión para los Laboratorios GeoForAll.
En septiembre de 2011, la Open Source Geospatial Foundation (OSGeo) y la Asociación Cartográfica Internacional (ICA) firmaron un memorando de entendimiento (MoU) con el objetivo de desarrollar oportunidades globales de colaboración en las áreas de datos abiertos y sistemas de información geográfica de código abierto integrando organizaciones académicas, gubernamentales y la industria, propiciando oportunidades de educación abierta para todos.
El MoU tiene como objetivo proporcionar experiencia y apoyo para el establecimiento de laboratorios geoespaciales de código abierto en todo el mundo, apoyando el desarrollo de software geoespacial de código abierto, los datos abiertos y la capacitación en estándares abiertos. La organización ISPRS se unió a esta iniciativa en 2014.
El lema de la iniciativa es "Geo For All". La idea fuerza de "Geo For All" es la creencia de que el conocimiento es un bien público y los Principios Abiertos en Educación brindarán grandes oportunidades para todos.
Los requisitos para unirse a la iniciativa "Geo for All" son:
(A) La organización debe estar comprometida en contribuir a la visión descrita en el ICA-MoU OSGeo para desarrollar oportunidades de colaboración en organizaciones académicas, industriales y gubernamentales en las áreas de Sistemas de Información Geográfica libres o de código abierto (FOSS), los datos abiertos, el acceso abierto (publicaciones) y la educación abierta. La organización debe concebir a la educación, la investigación y el servicio como ejes importantes para el crecimiento humano y como principio rector clave. La organización debe contribuir a la visión de la Agenda 2030 para el Desarrollo Sostenible de las Naciones Unidas para la construcción de un mundo mejor.
(B) Al menos una persona en su institución u organización debe tener un gran conocimiento en ciencia de la información geoespacial y visión para dirigir esta actividad y para construir un equipo local de personas. Esta persona debe actuar como un oficial de enlace con la iniciativa.
(C) Deberá existir un sitio web establecido para el laboratorio geoespacial de código abierto que enumere información actual de los procesos de investigación, la personas pertenecientes al grupo e información acerca de las labores de capacitación. La presencia web permitirá a otros nodos de la red y al público en general comprender y promover los esfuerzos locales del laboratorio en torno a la investigación y la enseñanza de tecnologías y enfoques geoespaciales de código abierto. El sitio web debe establecerse dentro del primer año del anuncio del laboratorio y debe actualizarse al menos una vez al año.
Conclusiones de las reuniones de Girona

Category:Libro_SIG Category:Free_GIS_Book Category:Education Category:Español
* Cualquier colaboración será bienvenida, la idea es leer unas pocas páginas y aportar erratas y soluciones.
* Se implementará un tracker en OSOR para facilitar el acceso a bugs y soluciones.
* Hay que montar una estructura del libro en el wiki para que la gente se pueda apuntar para colaborar.
* Se revitalizará la Lista de correo como medio de comunicación.
* Es necesario revisar un poco el artwork y los gráficos en general.
* Sería interesante tener una versión "estática" en HTML del libro que además facilitaría la conversión en epub.
* Hay que compilar una versión en pdf periódicamente para que la gente vea los progresos.
* Sería interesante tener "colaboradores" con permiso de Commit para ayudar a implementar los cambios.
* Debería ponerse una fecha límite porque si no el trabajo se diluye.
Conference-Europe

FOSS4G for Europe (formerly FOSS4G for Central and Eastern Europe).
== Goals ==
* Spread OSGeo and FOSS4G ideas in the region
* Bring people (researchers, educators, developers and users) together
* INSPIRE issues, regarding FOSS4G
* Discuss region-specific issues
* Education, focus on students
Please, refer the FOSS4G-Europe Manifesto for further details.
== Committee ==
=== Current members ===
* Vasile Craciunescu
* Jachym Cepicky
* Peter Baumann
* Gérald Fenoy
* Codrina Ilie
* Marco Minghini
* Nicolas Bozon
* Arnulf Christl
* Florin Iosub
* Dimitris Kotzinos
* Jeff McKenna
* Ivan Marchesini
* Massimiliano Cannata
* Milena Nowotarska
* Peter Mooney
* Dirk Frigne
* Robert Szczepanek
* Astrid Emde
* Luca Delucchi
* Oliver May
* Jeroen Ticheler
* Tõnis Kärdi
* Besfort Guri
=== Past members ===
* Martin Landa
* Maria Brovelli
* Stephan Meißl
* Zoltan Siki
* Till Adams
* Johan Van de Wauw
== Mailing list ==
http://lists.osgeo.org/mailman/listinfo/conference-europe
== Past Events ==
* FOSS4G Central and Eastern Europe 2012-Prague, Czechia
* FOSS4G Central and Eastern Europe 2013-Bucharest, Romania
* FOSS4G Europe 2014-Bremen, Germany
* FOSS4G Europe 2015-Como, Italy
* FOSS4G 2016-Bonn, Germany (Global)
* FOSS4G Europe 2017-Paris,France (call for venue Conference-Europe-2017)
* FOSS4G Europe 2018-Guimarães, Portugal (call for venue Conference-Europe-2018)
* FOSS4G 2019-Bucharest, Romania (Global)
* FOSS4G 2022-Firenze, Italy (Global)
* FOSS4G 2023-Prizren, Kosovo (Global)
* FOSS4G Europe 2024-Tartu, Estonia (call for venue Conference-Europe-2024)
== In preparation events ==
* FOSS4G-Europe-2025
== Never happened events ==
* FOSS4G Europe 2020-Valmiera, Latvia (call for venue Conference-Europe-2020)
== Communication channels ==
* @foss4ge@fosstodon
* Linkedin
* Telegram group 
* Facebook page 
* @foss4ge Twitter is in hiatus
* info-europe@foss4g.org
Category: FOSS4G
Category: FOSS4G-Europe
Conference-Europe 2015-Como

== Date ==
July 14-17 2015
== Place == 
Como, Politecnico di Milano in Como
== Links ==
http://europe.foss4g.org/2015/
== Committee ==
* http://europe.foss4g.org/2015/Organizing Committee
== Code sprint ==
* FOSS4G-Europe 2015 Code Sprint
Category: Past Events
Category: FOSS4G
Category: FOSS4G-Europe
Conference-Europe 2017

See 
* Conference-Europe-2017
* https://europe.foss4g.org/2017/
== Date ==
From July 18 to 21 2017
== Place == 
Marne-la-Vallée
== Links ==
FOSS4G-Europe 2017
== Committee ==
* TBD
== Code sprint ==
* FOSS4G-Europe 2017 Code Sprint
== BoF sessions ==
* FOSS4G-Europe 2017 BoF sessions
== Proposals ==
* France: Proposal Letter of intent
Category: Events
Category: FOSS4G
Category: FOSS4G-Europe
Category: 2017
ConferenceCookbook

Welcome to Conference Cookbook. This wikipage should give guideline for future conference organization committees of big events such as global FOSS4G conference as well as smaller events such as code sprints.
Feel free to add your ideas and lessons learned to make life of future organization committees easier. 
* Before you start
* Common topics
* Specific topics
** FOSS4G - The Global Conference
** FOSS4G-Local - Local conferences
** Other OSGeo-related events
Conference Committee 2010 Voting Process

The OSGeo Conference Committee will use the following process to vote on the FOSS4G2010 hosting proposals:
== Ranking the Submissions ==
OSGeo conference committee members must rank the 4 candidates in order of preference (from 1 to 4, 
where 1 is the most preferred).
== Submitting your Vote ==
OSGeo conference committee members must email their rankings in a private email to Jeff McKenna by Friday December 19th (exact time)
== Aggregating the Rankings ==
The committee members' individual rankings will be combined by using a form of the preferential ballot system, called Instant-runoff Voting. Here is the process:
# All ballots are counted as one vote for the top choice given.
#If a candidate holds a majority (more than half) of the active ballots, a winner is found. (No further elimination can change the top candidate.)
#Otherwise a candidate in last place is eliminated. If there is an exact tie for last place in numbers of votes, the candidate from among those tied with fewest first choices is eliminated.
#After elimination, the votes are recounted as one vote for the highest-ranked choice on the ballot which has not been eliminated. (If a ballot has all its ranked candidates eliminated, it is called exhausted and it can no longer be counted towards any candidate. Note that this cannot occur where all candidates are numbered.)
#The runoff process above is repeated (back to 2) until a winner is found.
== Announcing the Committee Results ==
The winner of the committee's voting process will be announced on the conference-dev mailing list on December 19th.
== Board Approval ==
The OSGeo Board of Directors must approve the committee's decision before it can become official. Board members will be informed of the committee's decision on December 19th, and they will then discuss the approval of the decision through the board mailing list.
===== References =====
* Proposal Documents
* Bid questions and answers
* Bid questions and answers IRC meeting with all 4 candidates: log
Category:Conference Committee
Conference Committee 2016 Priorities

This page sets out the topics which the Conference Committee will seek to address during 2016. It is an evolving list of topics which should be updated by all members of the conference committee. As decisions or policy discussions evolve a summary should be included in each topic. 
The initial list is copied from mails (Steven and Cameron) on the Conference mailing list
# Formalize how the committee operates. Perhaps Committee_Guidelines modified by our RFP secret vote and tie breaker method so we don't have to keep rehashing these. 
# We may want to consider whether we need separate criteria for committee membership and eligibility for voting for the selection of global FOSS4Gs
# We may want to consider whether there should be a formal policy or process to manage potential competing events under the FOSS4G or OSGeo banners
# We will start the RfP process for FOSS4G 2018 immediately after 2016 closes, it will probably be a good idea to review the RfP documentation and requirements before issuing again as there have been several suggestions for improvements.
# Fleshing out our handbook and aligning with FOSS4G bid documentation
#Addressing our loss of collective knowledge between FOSS4G events, with each new event starting with a new team. Ideas have floated in the past about having a single person dedicated to FOSS4G events. This might be a paid position
# Resolving our current issue of having more detailed review of conference proposals than we have volunteer time
# Considering our relationship between OSGeo and LocationTech, both of which host Open Source Geospatial events, both of which bring unique but slightly different value propositions. 3 cities bid for FOSS4G from North America for 2017, two teamed with LocationTech. Debate about which city to select was dominated by whether OSGeo should work with LocationTech, which resulted in these cities potentially being disadvantaged. This is something the board and/or conference committee should resolve before calling for bids.
# Understanding and formalising our position related to FOSS4G regional and local events and working out how we can support and help them better
# Housekeeping. I'd like a real motion for Sanghee to join the committee. I don't consider the non-motion to add him valid. Also formalize any other items like this.
Category:Conference Committee
Conference Committee Budget 2017

= This page is to collaboratively work on a draft budget =
* Add suggestions and revisions
* If it gets complicated, we can add comments and names in different colors
* Once the Committee decides on a budget, we can send this to the Board and request approval. 
= Budget =
Item 	Amount 	Notes
MailChimp (or similar)	$0, $120, or $2400/year	Based on 10k users cost would be $900/yr
Vimeo (or similar) 	$0, $60, $204, or $600 	
Spaceholder1 	$blank_amount1 	note field1
Spaceholder2 	$blank_amount2 	note field2
Spaceholder3 	$blank_amount3 	note field3
Spaceholder4 	$blank_amount4 	note field4
== References ==
# MailChimp pricing
# Vimeo pricing
= Discussion or comments =
* This is a rough start by Eli
* This is a draft and has not been approved
Category:Committees
Category:Conference Committee
Category:Budget
Conference Committee Meetings

The Conference Committee is the official committee of OSGeo responsible for operating the annual FOSS4G conferences.
This page keeps track of past and future meetings of the committee.
== Next Committee Meeting ==
* date: 2008-12-15
* time: http://www.timeanddate.com/worldclock/fixedtime.html?year=2008&month=12&day=15&hour=16&min=0&sec=0
* venue: in IRC in the #foss4g channel (on irc.freenode.net) 
* agenda: Review bid committee's responses to the 2010 Bid Questions
* to attend: Bid representatives and conference committee members
==== Agenda ====
* Introductions (who is in attendance)
* Review answers from each bid, in the following order:
*# Barcelona
*# Beijing
*# Denver
*# Utrecht
== Previous Committee Meetings ==
=== 2008-12-08 ===
* IRC log
* Agenda: 
** Welcome new committee members: Dave Patton, Gavin Fleming, and Rafael Sperb
** Develop questions for each bid: see the 2010 Bid Questions page
=== 2008-09-03 ===
* IRC log
* Agenda:
** discuss the RFP for the hosting of the FOSS4G 2010 conference
Category:FOSS4G
Category:Conference Committee
Conference Setup Guide

The OSGeo Foundation supports local communities to promote OSGeo by encouraging exhibits at conferences an other suitable venues.
This page provides some guidance on how to organize and deploy a successful public outreach event.
This page is in DRAFT
TODO:
* Make a page template
* Add more details
=Identify the event and relevant information=
* Booth registration and cost
* Possible Sponsors
* Volunteers
=Proposal=
Put together a proposal on the wiki following the template:
Include a proposed budget with necessary materials.
If you know of possible sponsors list those to.
Examples:
* CGS 2008
* AAG 2009
Make sure to tag your page as Category:Proposed Event
=Approval=
Communicate your intentions to the Marketing Committee and attend the next marketing committee to secure approval of your plan.
Do not expect OSGeo to fund the whole event, you will need to approach sponsors and indicate how much you plan to get from sponsors in your budget.
Marketing will help you obtain an Exhibition Pack.
Once approved you can change the event page to Category:Event
=Exhibit=
Obtain an Exhibition Pack:
# Try to borrow one from the nearest local chapter.
# If they don't have one yet contact Marketing about obtaining one for use in your region.
=Other Arrangements=
* Getting demo machines
* Finalizing Sponsors
* Scheduling Volunteers
=The Event=
=Post Event Accountability=
* Make sure the budget and materials were all accounted for.
* If you borrowed materials, return them.
* Write up a summary, post some photos and other information about how the event went.
* Change the category tag to Category:Past Event and start thinking about next year.
Category:Marketing
Category: Best practice
Conference System

---DRAFT--- for discussion and information only
The OSGeo Conference Committee and FOSS4G Local Planning Committee has been exploring using the PKP Open Conference System (OCS) for managing its workflow and online presence. The FOSS4G 2008 committee plans to use it as a platform for building the conference website. It is envisioned that future events will also use it.
----
Current instance: http://osgeo.org/ocs - this is a newly created, live version that is going into operational mode. The content is just beginning to be added.
----
= Workflow =
The workflow for accepting paper presentations, reviewing them and accepting them can be streamlined with this system. The system can also be used for presenting the timelines of the event and publishing and indexing the final papers. There are metadata indexing portions of the system that will help people search, find and cite our articles more effectively. Also, it opens up the process to be, optionally, peer reviewed. By using this common system, OSGeo events can be benefit from a built on body of knowledge around on set of tools instead of re-inventing a new web site for each conference.
= Terms & Roles =
Some terms used in the system may sound confusing if they are new to you. Here are the basics you need to know as an editor:
* Conference Manager - i.e. Full administrative access to all the conference instances
* Director - Reviews paper submissions
* Track Direcctor - Responsible for specific conference tracks/categories
* Author - Submits presentation proposals, i.e. a draft PDF
* Reader - Someone who, after the event, will come to read abstracts or full conference presentations/papers
Within the system, each user is given one or more roles. Roles define the functions that a user has available to use and what they are responsible to manage. Here are typical workflows for various scenarios. A comprehensive workflow diagram follows.
== Authors ==
* Upload files and metadata
* Watches review process
* Receive notice of acceptance or rejection
== Track Directors ==
* Automatically receive papers for the section you are responsible for 
* Interact with reviewers & authors
* Finalise submissions
== Reviewers / Proofreaders / Copyeditors ==
* Receive notices of papers to review
* Submit review comments
== Summary Workflow ==
Here is a comprehensive workflow diagram, taken from higher quality PDF called [pkp.sfu.ca/files/OCSinanHour.pdf OCS in an hour]:
= References =
* Online documentation, support forum and web site for the OCS project.
* Install notes for OCS are under the SAC:Setup OCS item.
* Closely related to the Open Journal System that the OSGeo Journal is starting to use.
Category:Infrastructure
Category:FOSS4G