Getting Started - Revision history

Wiki-Leo: revert spam from Slavelink

2013-12-29T10:12:22Z

revert spam from Slavelink

Wiki-Slavelink at 02:37, 24 December 2013

2013-12-24T02:37:55Z

Wiki-Slavelink: /* Wiki Syntax Converter */

2013-12-24T02:37:26Z

Wiki Syntax Converter

Wiki-Slavelink at 02:36, 24 December 2013

2013-12-24T02:36:19Z

Wiki-Slavelink at 02:35, 24 December 2013

2013-12-24T02:35:00Z

Wiki-Leo: Typo fixes

2011-11-17T09:10:57Z

Typo fixes

Wiki-Sbrumb: Fixed capitalization and some typos

2010-06-07T14:23:33Z

Fixed capitalization and some typos

Neteler: link http://www.osgeo.org/content/faq/getting_started.html

2009-05-03T22:00:40Z

link http://www.osgeo.org/content/faq/getting_started.html

Neteler: +Copy & Paste Excel/Openoffice to Wiki Converter

2009-05-03T21:59:30Z

+Copy & Paste Excel/Openoffice to Wiki Converter

Neteler: + how to add a new Wiki page

2008-10-16T04:46:37Z

+ how to add a new Wiki page

@@ Line 37: / Line 37: @@
 and voilà the empty page appears. Then click on the "edit this page" link. Please put
 <tt><nowiki>[[Category:FAQ]]</nowiki></tt> at bottom of the new page. (Really, we mean that! Wiki pages without a category are easily getting "lost" in the wealth of this Wiki...)
 === Wiki Syntax Converter ===

@@ Line 37: / Line 37: @@
 and voilà the empty page appears. Then click on the "edit this page" link. Please put
 <tt><nowiki>[[Category:FAQ]]</nowiki></tt> at bottom of the new page. (Really, we mean that! Wiki pages without a category are easily getting "lost" in the wealth of this Wiki...)
 === Wiki Syntax Converter ===

@@ Line 41: / Line 41: @@
 * Table nightmare? Just use the [http://people.fas.harvard.edu/~sdouglas/table.cgi Copy & Paste Excel/Openoffice to Wiki syntax Converter]...
 * http://diberri.dyndns.org/wikipedia/html2wiki/ converts HTML files to Wiki syntax.
 * Workaround for other formats: Most text processing software can save documents in HTML syntax. Copy and paste the content to this tool. The visual result is surprisingly good, but the 'source code' is somewhat overloaded with format tags (&lt;font&gt;, etc.).

@@ Line 41: / Line 41: @@
 * Table nightmare? Just use the [http://people.fas.harvard.edu/~sdouglas/table.cgi Copy & Paste Excel/Openoffice to Wiki syntax Converter]...
-[[Logo-metaspatial.png|150px |link=http://www.entrecoquins.com |alt=échangisme|échangisme]]
+[[Image:Logo-metaspatial.png|150px |link=http://www.entrecoquins.com |alt=échangisme|échangisme]]
 * http://diberri.dyndns.org/wikipedia/html2wiki/ converts HTML files to Wiki syntax.
 * Workaround for other formats: Most text processing software can save documents in HTML syntax. Copy and paste the content to this tool. The visual result is surprisingly good, but the 'source code' is somewhat overloaded with format tags (&lt;font&gt;, etc.).

@@ Line 41: / Line 41: @@
 * Table nightmare? Just use the [http://people.fas.harvard.edu/~sdouglas/table.cgi Copy & Paste Excel/Openoffice to Wiki syntax Converter]...
 * http://diberri.dyndns.org/wikipedia/html2wiki/ converts HTML files to Wiki syntax.
 * Workaround for other formats: Most text processing software can save documents in HTML syntax. Copy and paste the content to this tool. The visual result is surprisingly good, but the 'source code' is somewhat overloaded with format tags (&lt;font&gt;, etc.).

@@ Line 1: / Line 1: @@
 === Introduction ===
-So you've read the [http://www.osgeo.org/faq FAQ], joined the [http://www.osgeo.org/mailinglists mailing lists], and found your way to this wiki (where the action is), all ready to help the foundation goals, but you're wondering, so what do I do now?
+So you've read the [http://www.osgeo.org/faq FAQ], joined the [http://www.osgeo.org/mailinglists mailing lists], and found your way to this Wiki (where the action is), all ready to help the foundation goals, but you're wondering, so what do I do now?
-=== Add yourself to the Member list ===
+=== Add Yourself to the Member List ===
 Well, the first thing you can do is introduce yourself and let people know what you're about, and what you're interested in.  The best way to do this is to create an account in this Wiki (top right of this page) and add some information about yourself.  Since you've read the FAQ and the [http://www.osgeo.org/content/faq/getting_started.html Member Area], you know that everyone participating is a member, so adding yourself to this Wiki is the first thing to do.  To add information about yourself simply log in with your new account and edit your Wiki user page (click on your user name that appears at the top once you are logged in).  Please observe that you must add an email address when creating your account so that OSGeo can send you the confirmation string that is needed before you can edit. For more general information about using a Wiki, see [[Help:Contents]].
-=== Join the OSGeo Main site ===
+=== Join the OSGeo Main Site ===
 Joining the main site is primarily useful if you want to use authenticated services like Trac (for submitting bug reports against OSGeo projects) or Subversion.  To get an "OSGeo Userid" for the main site and these services, follow the instructions on the  [http://www.osgeo.org/osgeo_userid OSGeo Userid] page.
-=== Find a project to work on ===
+=== Find a Project to Work on ===
 The easiest place to start is the [[Volunteers Needed]] page, as projects will put up their requests of what they're looking for.  You also can email the discuss list directly to let people know what you're interested in, and where you could slot in.  You can also go to the [[https://www.osgeo.org OSGeo website]] which links to projects and committees that are fully started.  After you click on a project you'll be taken to their main page, where you can learn more about how to become involved.  You can also subscribe to various OSGeo [http://lists.osgeo.org/mailman/listinfo mailing lists] or browse their archives.
-=== Join a mailing list ===
+=== Join a Mailing List ===
-On many projects there are 5 or so mailing lists.  The best email list is often named the same as the project (like incubator@incubator.osgeo.org), or sometimes discuss.  Some lists can be avoided at first, like commits, cvs, and issues (which are automatic email lists from the source repositories and project trackers).  The announce will generally be low traffic.  The dev and users list may have good traffic if they are programming projects, in which case the users list is probably the place to start.  Jump on a list for a project and introduce yourself, ask where you can help out.
+On many projects there are 5 or so mailing lists.  The best email list is often named the same as the project (like incubator@incubator.osgeo.org), or sometimes discuss.  Some lists can be avoided at first, like commits, cvs, and issues (which are automatic email lists from the source repositories and project trackers).  The announce list will generally be low traffic.  The dev and users lists may have good traffic if they are programming projects, in which case the users list is probably the place to start.  Jump on a list for a project and introduce yourself, ask where you can help out.
 === Jump on IRC ===
-Many of us hang out on irc, at irc://irc.freenode.net#osgeo.  Or in more verbose terms, on the osgeo channel of irc.freenode.net.  There are a variety of IRC clients,
+Many of us hang out on IRC at irc://irc.freenode.net#osgeo.  Or in more verbose terms, on the osgeo channel of irc.freenode.net.  There are a variety of IRC clients:
 * Use the OSGeo [http://irc.telascience.org/ Web interface to IRC] (no installation needed)
 * If you're running firefox [https://addons.mozilla.org/extensions/moreinfo.php?id=16 ChatZilla] is very straightforward.
@@ Line 22: / Line 23: @@
 * There are many others as well (could people add links to their favorite clients?): [http://gaim.sourceforge.net/ Gaim].
-With IRC you can informally get to know people, what they're working on, and how to help out. Many of the projects in the open source geospatial community also have channels where people discuss development and offer social support; there are (at least) #mapserver , #gdal , #geotools , #qgis , #openlayers , #zco , #publicgeodata channels on irc.freenode.net. Read an [http://grass.gdf-hannover.de/wiki/How_to_participate_in_IRC_communication introduction to IRC].
+With IRC you can informally get to know people, what they're working on, and how to help out. Many of the projects in the open source geospatial community also have channels where people discuss development and offer social support; there are (at least) #mapserver , #gdal , #geotools , #qgis , #openlayers , #zco , and #publicgeodata channels on irc.freenode.net. Read an [http://grass.gdf-hannover.de/wiki/How_to_participate_in_IRC_communication introduction to IRC].
 IRC is one of the media used for committee and other meetings. If you missed a meeting on IRC or just want to read up on what happened you can go to the archives at http://logs.qgis.org/osgeo/. There is also an [http://frot.org/osgeo/irc experimental IRC blog] which publishes URLs posted on IRC.
-=== Hack on the wiki ===
+=== Hack on the Wiki ===
-This wiki is where a lot of action takes place.  Collaboration is much easier here, so we'll start up new documents here, and transition them over to the osgeo site when we're happy with how they look and what they say.  Documents on osgeo.org reflect OSGeo's positions, while on the wiki we work out what those positions are.  You can find out where the action has been on the wiki by clicking on [[Special:Recentchanges]].  Feel free to add new pages, propose new projects and ideas.
+This Wiki is where a lot of action takes place.  Collaboration is much easier here, so we'll start up new documents here, and transition them over to the osgeo site when we're happy with how they look and what they say.  Documents on osgeo.org reflect OSGeo's positions, while on the Wiki we work out what those positions are.  You can find out where the action has been on the Wiki by clicking on [[Special:Recentchanges]].  Feel free to add new pages, propose new projects and ideas.
 To add a new Wiki page, just take the standard URL http://wiki.osgeo.org/wiki/ and add a page name behind it (even spaces are possible in the URL):
@@ Line 35: / Line 36: @@
 and voila` the empty page appears. Then click on the "edit this page." link. Please put
-<tt><nowiki>[[Category:FAQ]]</nowiki></tt> at bottom of the new page (really, we mean that! Wiki pages without category are are easily getting "lost" in the wealth of this wiki...).
+<tt><nowiki>[[Category:FAQ]]</nowiki></tt> at bottom of the new page. (Really, we mean that! Wiki pages without a category are easily getting "lost" in the wealth of this Wiki...)
-=== Wiki Syntaxt Converter ===
+=== Wiki Syntax Converter ===
 * Table nightmare? Just use the [http://people.fas.harvard.edu/~sdouglas/table.cgi Copy & Paste Excel/Openoffice to Wiki syntax Converter]...
-* http://diberri.dyndns.org/wikipedia/html2wiki/ converts HTML files to Wiki syntax. Workaround for other formats: Most text processing software can save documents in HTML syntax. Copy and paste the content to this tool. The visual result is surprisingly good, but the 'source code' is somewhat overloaded with format tags (<font>, etc.).
+* http://diberri.dyndns.org/wikipedia/html2wiki/ converts HTML files to Wiki syntax.

← Older revision		Revision as of 21:59, 3 May 2009
Line 38:		Line 38:

	=== Wiki Syntaxt Converter ===		=== Wiki Syntaxt Converter ===
−	* http://diberri.dyndns.org/wikipedia/html2wiki/ converts HTML files to Wiki syntax. Workaround for other formats: Most text ~~procesing~~ software can save documents in HTML syntax. Copy and paste the content to this tool. The visual result is surprisingly good, but the 'source code' is somewhat overloaded with format tags (<font>, etc.).	+
		+	* Table nightmare? Just use the [http://people.fas.harvard.edu/~sdouglas/table.cgi Copy & Paste Excel/Openoffice to Wiki syntax Converter]...
		+	* http://diberri.dyndns.org/wikipedia/html2wiki/ converts HTML files to Wiki syntax. Workaround for other formats: Most text processing software can save documents in HTML syntax. Copy and paste the content to this tool. The visual result is surprisingly good, but the 'source code' is somewhat overloaded with format tags (<font>, etc.).