Difference between revisions of "Live GIS Disc Apply"

From OSGeo
Jump to navigation Jump to search
(Created page with '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:/…')
 
(Dupe?)
 
(15 intermediate revisions by 2 users not shown)
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
+
Dupe of [[OSGeoLive Apply]]?
  
−
* Please describe your application. What is its name, what is the URL to its home page, what does it do?
+
''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''
  
−
* OSGeo-Live is targeted at applications that people can use rather than libraries that are included into other applications. Does the application have a user interface (possibly command line interface) that a user can interact with?
+
* Please describe your application.
 +
** What is its name?
 +
** What is the home page URL?
 +
** 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.
 +
** What language is it written in?
 +
** Which version of the application should be included in the next OSGeo-Live release?
 +
 
 +
* 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.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?
 +
** Do you have a bug free, stable release?
 +
** Please discuss the level of testing that your project has gone through.
 +
** 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? (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.
 +
 
 +
* With around 50 applications installed on OSGeo-Live, us core packagers do not have the time to liaise with every single project email list for each OSGeo-Live release. So we require a volunteer (or two) to take responsibility for liaising between OSGeo-Live and the project's communities. This volunteer will be responsible for ensuring the install scripts and English documentation are updated by someone for each OSGeo-Live release. Also test that the installed application and Quickstart documentation works as expected on release candidate releases of OSGeo-Live. Who will act as the project's liaison person.
 +
 
 +
* OSGeo-Live is Ubuntu Linux based. Our installation preference is:
 +
*# Install from UbuntuGIS or DebianGIS
 +
*# Install .deb files from a PPA
 +
*# Write a custom install script
 +
:Can you please discuss how your application will be installed.
  
 
* OSGeo-Live is memory and disk constrained. Can the application run in 512 Meg of RAM?
 
* OSGeo-Live is memory and disk constrained. Can the application run in 512 Meg of RAM?
Line 9: Line 37:
 
* How much disk space will be required to install the application and a suitable example application?
 
* How much disk space will be required to install the application and a suitable example application?
  
−
* We aim to reduce disk space by having all applications make use of a common dataset. We encourage applications to make use of the naturalearth dataset already installed:
+
* 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.
+
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.
−
 
 
−
* Have you started incubation, or are you on the waiting list to start incubation?
 
  
−
4. Stability is very important to us on OSGeo-Live. Do you have a bug free, stable release, which has been rolled out to production in a number of locations?
+
* Each OSGeo-Live application requires a Project Overview available under a [http://creativecommons.org/licenses/by/3.0/ CC By] and a Quickstart available under a [http://creativecommons.org/licenses/by-sa/3.0/ CC By-SA] license. (You may release under a second license as well). Will you produce this?
  
−
5. I notice the CeCILL licence you use is not listed on OSI list of licences. Has license been discussed and resolved on the OSGeo-Incubation list?
+
* 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?
  
−
6. Do you have a person (maybe yourself?) prepared to volunteer to be the OSGeo-Live representative, who will take responsibility for liaising between the project and OSGeo-Live and make sure that scripts and documentation are updated for each release.
+
[[Category: Software Stack]]
 +
[[Category: OSGeoLive]]

Latest revision as of 05:28, 6 July 2019

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 describe your application.
    • What is its name?
    • What is the home page URL?
    • 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?
    • 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.
    • What language is it written in?
    • Which version of the application should be included in the next OSGeo-Live release?
  • 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?
    • 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?
    • Do you have a bug free, stable release?
    • Please discuss the level of testing that your project has gone through.
    • 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? (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 FOSS4G conferences. If your project is involved in OSGeo Incubation, or has been selected to be presented at FOSS4G, then please mention it.
  • With around 50 applications installed on OSGeo-Live, us core packagers do not have the time to liaise with every single project email list for each OSGeo-Live release. So we require a volunteer (or two) to take responsibility for liaising between OSGeo-Live and the project's communities. This volunteer will be responsible for ensuring the install scripts and English documentation are updated by someone for each OSGeo-Live release. Also test that the installed application and Quickstart documentation works as expected on release candidate releases of OSGeo-Live. Who will act as the project's liaison person.
  • OSGeo-Live is Ubuntu Linux based. Our installation preference is:
    1. Install from UbuntuGIS or DebianGIS
    2. Install .deb files from a PPA
    3. Write a custom install script
Can you please discuss how your application will be installed.
  • OSGeo-Live is memory and disk constrained. Can the application run in 512 Meg of RAM?
  • How much disk space will be required to install the application and a suitable example application?
  • 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.

  • Each OSGeo-Live application requires a Project Overview available under a CC By and a Quickstart available under a CC By-SA license. (You may release under a second license as well). Will you produce this?
  • 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?
Retrieved from "http://wiki.osgeo.org/w/index.php?title=Live_GIS_Disc_Apply&oldid=120869"