Search results
Jump to navigation
Jump to search
Page title matches
- ...2015-September/013182.html that we would like to move certain parts of our infrastructure to 3rd party service - possibly Google. The discussion with SAC showed http [[Category:Infrastructure]]2 KB (255 words) - 07:02, 13 October 2015
- == Research Infrastructure Activities == This page collects all acitvities within OSGeo, which are related to research infrastructure (RI).4 KB (484 words) - 05:43, 24 November 2017
- This is an effort of the [[Infrastructure Working Group]] to produce a definitive baseline spec for what online servi ...r-profit independent organisation within Oregon State University that runs infrastructure support and hosting for a [http://osuosl.org/hosting/clients wide range of5 KB (700 words) - 12:15, 11 April 2007
- #REDIRECT [[Project Infrastructure Migration 2007]]51 bytes (4 words) - 02:46, 9 February 2017
- This is an informal Working Group established to assess OSGeo's software infrastructure needs and provisions. * [[Infrastructure Proposal]] is a work-in-progress to outline what OSGeo needs to provide, bo3 KB (376 words) - 06:01, 6 July 2010
- ...sue tracking tool. It has several methods for tying intoother parts of the infrastructure, e.g. SVN and other features. Unclear how easy to extract from current CN t ...ools through one common set of services is an ideal end goal, providing an infrastructure that makes code easier to track, documentation easier to contribute, people11 KB (1,742 words) - 23:21, 6 May 2018
- 721 bytes (91 words) - 04:23, 2 November 2013
- ...eck out the current [[Infrastructure Transition Plan 2014]] or [[:Category:Infrastructure]]''''' ...ently (really initially) going through incubation. It attempts to address infrastructure needs, and migration strategies to OSGeo servers.6 KB (899 words) - 02:46, 9 February 2017
- ...d each have at most 4GB of RAM. By pooling some services that use the same infrastructure we could essentially balance 16GB of RAM across 4 sites, assuming that heav [[Category:Infrastructure]]13 KB (1,966 words) - 23:20, 23 May 2014
- ...can we find ways to avoid relying solely on volunteer time to support the infrastructure? How can we handle funded sysadmin time in a fair way vs volunteer contribu [[Category: Infrastructure]]7 KB (1,057 words) - 11:15, 23 April 2015
Page text matches
- == Project Infrastructure ==718 bytes (87 words) - 18:10, 19 March 2016
- : ''The theme for this conference is Spatial Data Infrastructure Convergence: Building SDI Bridges to Address Global Challenges.'' ...the worlds most pressing problems. The approaches in building spatial data infrastructure within and among nations are in many respects converging. This conference w1 KB (143 words) - 13:48, 14 July 2009
- #REDIRECT [[Project Infrastructure Migration 2007]]51 bytes (4 words) - 02:46, 9 February 2017
- * Completely migrated away from CollabNet and implemented our own infrastructure, which is hosted at Peer1. ...ldcard DNS entry for *.osgeo.org, which greatly complicates and limits our infrastructure maintenance.1,001 bytes (128 words) - 12:21, 28 January 2008
- [[Category:Infrastructure]]132 bytes (17 words) - 12:15, 24 December 2020
- == Refonte de l'infrastructure technique OSGEO-FR == ...un peu tout ça, et donner moins de travail aux mainteneurs. Reposer sur l'infrastructure OSGEO, Framasoft?1 KB (151 words) - 12:30, 14 January 2019
- == Infrastructure Transition == ''Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.''2 KB (297 words) - 00:40, 3 February 2007
- == Project Infrastructure ==1 KB (155 words) - 18:16, 19 March 2016
- :Manager – Spatial Data Infrastructure ...ee geodata. [http://www.snb.ca/geonb/ GeoNB - New Brunswick's Spatial Data Infrastructure<br>]{{#umSetParam: -66.64824|45.94034|Fredericton, NB, Canada|Berniejconnor1 KB (150 words) - 19:56, 29 June 2010
- == Project Infrastructure ==2 KB (219 words) - 18:55, 19 March 2016
- [[Category: Infrastructure]]243 bytes (28 words) - 07:36, 27 August 2007
- == Infrastructure Transition Plan == [[Category: Infrastructure]]2 KB (242 words) - 08:41, 15 January 2015
- [[Category:Infrastructure]]166 bytes (25 words) - 22:19, 27 September 2011
- == Project Infrastructure ==2 KB (225 words) - 03:57, 16 July 2016
- [[Category: Infrastructure]]232 bytes (36 words) - 01:32, 30 March 2008
- == Project Infrastructure ==2 KB (240 words) - 00:15, 16 January 2019
- * Provide a working and complete (likely overly complete) spatial data infrastructure to conference participants. ...icular, by demonstrating their products capability to interact with FOSS4G infrastructure. Presenters, workshop coordinator and lab coordinators will have a greater6 KB (900 words) - 20:21, 27 November 2008
- == Project Infrastructure ==2 KB (256 words) - 18:25, 19 March 2016
- ..., specifically CVS and Bugzilla, from the University of Minnesota to OSGeo infrastructure (SVN and Trac) in April 2007 * OSGeo incubation process was slow, primarily limited to infrastructure migration from UMN to OSGeo.2 KB (269 words) - 23:00, 6 February 2008
- == Infrastructure Transition == ''Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.''3 KB (443 words) - 09:36, 12 February 2007