Difference between revisions of "Official OSGeo Event Policy"
Wiki-JoWalsh (talk | contribs) m (→Policy) |
(separating guidelines for 3rd party events) |
||
Line 12: | Line 12: | ||
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy | * [[OSGeo_Conference_Policy | Board notes]] regarding event policy | ||
− | == | + | == OSGeo Event Guidelines == |
− | + | The following guidelines apply to all events that use the OSGeo name, which include: 1) the annual FOSS4G event, 2) an event hosted by an OSGeo local chapter, and 3) a 3rd party event that uses the OSGeo name. | |
− | |||
− | |||
'''A. Mission''' -- any event using the OSGeo name must contribute positively to the [[OSGeo Mission]], which is essentially to support the development of open source Geospatial Software, and promote its widespread use. | '''A. Mission''' -- any event using the OSGeo name must contribute positively to the [[OSGeo Mission]], which is essentially to support the development of open source Geospatial Software, and promote its widespread use. | ||
Line 25: | Line 23: | ||
'''D. Infrastructure''' -- any event using the OSGeo name must have a high-quality infrastructure (materials, presentation, facilities, and instructors) as to not reflect negatively on OSGeo. | '''D. Infrastructure''' -- any event using the OSGeo name must have a high-quality infrastructure (materials, presentation, facilities, and instructors) as to not reflect negatively on OSGeo. | ||
+ | |||
+ | == OSGeo 3rd Party Event Guidelines == | ||
+ | |||
+ | Third parties using the OSGeo or FOSS4G name must abide by the above guidelines, as well as: | ||
'''E. Acceptance''' -- third party events using the OSGeo name must be approved by OSGeo's [[Board of Directors]]. The exact process is as follows: | '''E. Acceptance''' -- third party events using the OSGeo name must be approved by OSGeo's [[Board of Directors]]. The exact process is as follows: |
Revision as of 07:50, 22 July 2008
Description
The purpose of this document is to outline rules that must be followed for an OSGeo event (meaning any event using the OSGeo name).
NOTE: despite the document name, this policy is not yet official, and is in discussion and consideration for approval.
Additional Resources
The following are of interest to the event policy:
- Conference committee homepage
- Board notes regarding event policy
OSGeo Event Guidelines
The following guidelines apply to all events that use the OSGeo name, which include: 1) the annual FOSS4G event, 2) an event hosted by an OSGeo local chapter, and 3) a 3rd party event that uses the OSGeo name.
A. Mission -- any event using the OSGeo name must contribute positively to the OSGeo Mission, which is essentially to support the development of open source Geospatial Software, and promote its widespread use.
B. Program -- any event using the OSGeo name must have program content that is predominantly related to Open Source geospatial software.
C. Value -- any event using the OSGeo name must offer "value for money" to paid participants, so as to not reflect poorly on OSGeo.
D. Infrastructure -- any event using the OSGeo name must have a high-quality infrastructure (materials, presentation, facilities, and instructors) as to not reflect negatively on OSGeo.
OSGeo 3rd Party Event Guidelines
Third parties using the OSGeo or FOSS4G name must abide by the above guidelines, as well as:
E. Acceptance -- third party events using the OSGeo name must be approved by OSGeo's Board of Directors. The exact process is as follows:
- event organizer must distribute a formal plan to the general public osgeo-discuss list for community discussion, and to the Conference Committee through the conference_dev list
- Conference Committee must vote on the acceptance of the event (abiding by OSGeo's conflict of interest policy)
- if accepted, the Conference Committee recommends the event to OSGeo's Board of Directors, through an email to the board list
- Board of Directors must vote on the recommended event (abiding by OSGeo's conflict of interest policy)
- A decision will be made by OSGeo within 1 month of the event organizer distributing the formal plan, described in E.1. above