Live GIS Disc Apply - Revision history

Neteler: Dupe?

2019-07-06T13:28:31Z

Dupe?

Wiki-Sethg: update mailing list URL

2019-05-06T23:02:19Z

update mailing list URL

Wiki-Camerons at 20:32, 23 August 2015

2015-08-23T20:32:31Z

Wiki-Camerons at 22:59, 29 November 2014

2014-11-29T22:59:20Z

Wiki-Camerons at 21:31, 31 December 2012

2012-12-31T21:31:01Z

Wiki-Camerons at 20:10, 3 April 2012

2012-04-03T20:10:16Z

Wiki-Camerons at 19:24, 3 January 2012

2012-01-03T19:24:59Z

Wiki-Camerons at 23:36, 30 June 2011

2011-06-30T23:36:48Z

Wiki-Camerons at 20:36, 10 June 2011

2011-06-10T20:36:03Z

Wiki-Camerons at 20:26, 10 June 2011

2011-06-10T20:26:53Z

← Older revision		Revision as of 13:28, 6 July 2019
Line 1:		Line 1:
		+	Dupe of [[OSGeoLive Apply]]?
		+
	''Please email answers to these questions if you wish to propose including a new application on the OSGeo-Live distribution. The email should be sent to the OSGeo-Live list: https://lists.osgeo.org/mailman/listinfo/osgeolive''		''Please email answers to these questions if you wish to propose including a new application on the OSGeo-Live distribution. The email should be sent to the OSGeo-Live list: https://lists.osgeo.org/mailman/listinfo/osgeolive''

Line 41:		Line 43:

	* In past releases, we have included Windows and Mac installers for some applications. It is likely we won't have space for these in future releases. However, if there is room, would you be wishing to include Windows and/or Mac installers?		* In past releases, we have included Windows and Mac installers for some applications. It is likely we won't have space for these in future releases. However, if there is room, would you be wishing to include Windows and/or Mac installers?
		+
		+	[[Category: Software Stack]]
		+	[[Category: OSGeoLive]]

← Older revision		Revision as of 23:02, 6 May 2019
Line 1:		Line 1:
−	''Please email answers to these questions if you wish to propose including a new application on the OSGeo-Live distribution. The email should be sent to the OSGeo-Live list: ~~http~~://lists.osgeo.org/mailman/listinfo/~~live-demo~~''	+	''Please email answers to these questions if you wish to propose including a new application on the OSGeo-Live distribution. The email should be sent to the OSGeo-Live list: https://lists.osgeo.org/mailman/listinfo/osgeolive''

	* Please describe your application.		* Please describe your application.

@@ Line 4: / Line 4: @@
 ** What is its name?
 ** What is the home page URL?
-** Which OSI approved Open Source Licence is used?
+** Which [http://opensource.org/licenses OSI approved Open Source Licence] is used?
 ** What does the application do and how does it add value to the GeoSpatial stack of software?
 ** Does the application make use of OGC standards? Which versions of the standards? Client or server? You may wish to add comments about how standards are used.

@@ Line 12: / Line 12: @@
 * Stability is very important to us on OSGeo-Live. If a new user finds a bug in one application, it will tarnish the reputation of all other OSGeo-Live applications as well. (We pay most attention to the following answers):
 ** If risk adverse organisations have deployed your application into production, it would imply that these organisations have verified the stability of your software. Has the application been rolled out to production into risk (ideally risk adverse) organisations? Please mention some of these organisations?
-** [https://www.ohloh.net/ Ohloh] provides metrics to help assess the health of a project. Eg: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html Could you please ensure that your project is registered with Ohloh, and Ohloh has been updated to reference the correct code repository(s) for your project. What is the Ohloh URL for your project?
+** [https://www.openhub.net/ Open HUB] provides metrics to help assess the health of a project. Eg: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html Could you please ensure that your project is registered with Open HUB, and Open HUB has been updated to reference the correct code repository(s) for your project. What is the Open HUB URL for your project?
 ** What is the size of the user community? You can often answer this by mentioning downloads, or describing a healthy, busy email list?
 ** What is the size of your developer community?

@@ Line 12: / Line 12: @@
 * Stability is very important to us on OSGeo-Live. If a new user finds a bug in one application, it will tarnish the reputation of all other OSGeo-Live applications as well. (We pay most attention to the following answers):
 ** If risk adverse organisations have deployed your application into production, it would imply that these organisations have verified the stability of your software. Has the application been rolled out to production into risk (ideally risk adverse) organisations? Please mention some of these organisations?
 ** What is the size of the user community? You can often answer this by mentioning downloads, or describing a healthy, busy email list?
 ** What is the size of your developer community?

@@ Line 6: / Line 6: @@
 ** Which OSI approved Open Source Licence is used?
 ** What does the application do and how does it add value to the GeoSpatial stack of software?
 ** What language is it written in?
 ** Which version of the application should be included in the next OSGeo-Live release?

@@ Line 17: / Line 17: @@
 ** How long has the project has had mature code.
-* OSGeo-Live is targeted at applications that people can use rather than libraries. Does the application have a user interface (possibly a command line interface) that a user can interact with?
+* OSGeo-Live is targeted at applications that people can use rather than libraries. Does the application have a user interface (possibly a command line interface) that a user can interact with? (We do make an exception for Incubated OSGeo Libraries, and will include Project Overviews for these libraries, even if they don't have a user interface.)
 * We give preference to OSGeo Incubated Projects, or Projects which are presented at [http://foss4g.org FOSS4G] conferences. If your project is involved in OSGeo Incubation, or has been selected to be presented at FOSS4G, then please mention it.
@@ Line 35: / Line 35: @@
 * We aim to reduce disk space by having all applications make use of a common dataset. We encourage applications to make use of the example datasets already installed:
 http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets If another dataset would be more appropriate, please discuss here. Is it appropriate, to remove existing demo datasets which may already be included in the standard release.
 * In past releases, we have included Windows and Mac installers for some applications. It is likely we won't have space for these in future releases. However, if there is room, would you be wishing to include Windows and/or Mac installers?

@@ Line 10: / Line 10: @@
 * Stability is very important to us on OSGeo-Live. If a new user finds a bug in one application, it will tarnish the reputation of all other OSGeo-Live applications as well. (Way pay most attention to the following answers):
-** Has the application been rolled out to production in a number of locations? Can you mention some risk adverse organizations who use your application?
+** If risk adverse organisations have deployed your application into production, it would imply that these organisations have verified the stability of your software. Has the application been rolled out to production into risk (ideally risk adverse) organisations? Please mention some of these organisations?
-** What is the size of the user community and developer community? You can often answer this by mentioning downloads, or describing a healthy, busy email list?
+** What is the size of the user community? You can often answer this by mentioning downloads, or describing a healthy, busy email list?
 ** Do you have a bug free, stable release?
 ** Please discuss the level of testing that your project has gone through.