Changes between Version 1 and Version 2 of WikiStart

Jan 3, 2010, 3:38:20 PM (11 years ago)



  • WikiStart

    v1 v2  
    1 = Welcome to Trac =
    3 Trac is a '''minimalistic''' approach to '''web-based''' management of
    4 '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.
    6 All aspects of Trac have been designed with the single goal to
    7 '''help developers write great software''' while '''staying out of the way'''
    8 and imposing as little as possible on a team's established process and
    9 culture.
    11 As all Wiki pages, this page is editable, this means that you can
    12 modify the contents of this page simply by using your
    13 web-browser. Simply click on the "Edit this page" link at the bottom
    14 of the page. WikiFormatting will give you a detailed description of
    15 available Wiki formatting commands.
    17 "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
    18 a new Trac environment, containing a default set of wiki pages and some sample
    19 data. This newly created environment also contains
    20 [wiki:TracGuide documentation] to help you get started with your project.
    22 You can use [wiki:TracAdmin trac-admin] to configure
    23 [ Trac] to better fit your project, especially in
    24 regard to ''components'', ''versions'' and ''milestones''.
    27 TracGuide is a good place to start.
    29 Enjoy! [[BR]]
    30 ''The Trac Team''
    32 == Starting Points ==
    34  * TracGuide --  Built-in Documentation
    35  * [ The Trac project] -- Trac Open Source Project
    36  * [ Trac FAQ] -- Frequently Asked Questions
    37  * TracSupport --  Trac Support
    39 For a complete list of local wiki pages, see TitleIndex.
     1== Background == 
     3MetaCRS is a project encompassing several projections, and coordinate system related technologies.  Our plan is to treat a variety of coordinate system activities as one Project from an OSGeo point of view.  This helps provide enough "project mass" to justify the full OSGeo project treatment.  But more importantly it would give us a forum to cooperate.  Sharing things like coordinate system dictionaries, test suites and mathematical formulations.
     5== Project Steering Committee ==
     7The project steering committee consists of the following individuals and operates according to the [wiki:PSCGuidelines MetaCRS PSC] procedures.
     9 * Frank Warmerdam (chair)
     10 * Hugues Wisniewski
     11 * Norm Olson
     12 * Mike Adair
     13 * Howard Butler
     14 * Martin Davis
     16== Sub-projects ==
     18The following are sub-projects of MetaCRS:
     20 * [ PROJ.4] - lead - Frank Warmerdam
     21 * [ Proj4js] - lead - Mike Adair
     22 * [ CS-Map] - lead - Hugues Wisiewski
     23 * [ GeoTIFF/libgeotiff] - lead - Frank Warmerdam
     24 * [] - lead - Howard? Chris?
     25 * [ Proj4J] - lead - Martin Davis
     27== Commiters ==
     29Commiters are technically able to commit on any part of MetaCRS but traditionally they have sub-projects on which they focus, and they will avoid commits on other sub-projects without discussion with the project lead.  New commiters may be [ added] after a vote of the PSC.
     31 * Howard Butler (hobu): libgeotiff,
     32 * Hugues Wisiewski (hugueswski): CS-Map
     33 * Mike Adair (madair): Proj4js
     34 * Norm Olsen (normolsen): CS-Map
     35 * Paul Ramsey (pramsey): libgeotiff
     36 * Frank Warmerdam (warmerdam): PROJ.4, libgeotiff
     37 * Chris Schmidt (crschmidt):
     38 * Richard Didier (drichard): PROJ.4
     39 * Martin Davis (mdavis): Proj4J
     40 * Landon Blake (surveyor): Proj4J, testsuite
     41 * Martin Desruisseaux (desruisseaux): testsuite
     43== Mailing list ==
     45In order to facilitate further discussion I have created a mailing list.  Please join if you have an interest.
     49== Practical Questions ==
     51Answers are not authoritative - they are one opinion on possible answers.
     53=== Are we trying to merge the source into one super-library? ===
     55No, though there may be opportunities that arise for consolidation over time. 
     57=== Is my library/component going to be subject to the whim of other contributors? ===
     59I imagine we will want to use the ''lieutenant model'' of development where particular components are essentially maintained by a chief maintainer.  The project steering committee would establish broad policy (such as contributor rules) and facilitation for shared components (perhaps some dictionaries) while leaving technical direction of some components to their primary maintainer (ie. Norm for CS-Map). 
     61=== So will all these packages live in a single subversion repository with a single Trac instance? ===
     63The current plan is to use a single SVN repository for MetaCRS projects ( with distinct subtrees for each project.  But each project has the option of it's own distinct Trac instance - for example and
     65=== What are Java developers doing on the mailing list? ===
     67The Java developers come from a range of projects; and are very interested in geeking out about correctness and accuracy issues. There are also a couple opportunities for collaboration (shared testing scripts and the like).   
     69We will seek close cooperation with a variety individuals and organizations interested in interchange of spatial reference system descriptions, and related standards including other open source projects, organizations like OGC, national mapping agencies, and proprietary software developers.
     71== Non-Programming Collaboration ==
     72What opportunities are there for collaboration with projection libraries in languges that are not directly compatable with C programming language or C++ programming language libraries? (For example: GeoTools includes functional code for spatial reference systems in Java based on the ESPG database.)
     75 * Common Spatial Reference System or Coordinate Reference System Names and Descriptions
     76 * Coordinate System (and CRS related object) dictionaries.  Stuff like the EPSG dictionary.
     77 * Datum shift lists (towgs84), and datum grid shift files (NTv1, etc). 
     78 * Transformations, calculations, and algorithms written in pseudocode that can be edited in different languages.
     79 * Descriptions of spatial reference systems that can be used by developers in different programming languages.
     80 * Notes on transformation from different representations of a CRS (WKT, PROJ.4, GCTP, GML,...). 
     81 * Test suites with test points in a variety of coordinate systems and their lat/long and WGS84 equivelents).
     82 * Articles on spatial reference systems and translations useful for programmers interested in spatial reference system implementations. For example:
     83 ** Understanding The Difference Between National Vertical Datum of 1929 and the North American Datum of 1988
     85== Standard MetaCRS Test Data Files ==
     87Work has begun on a set of standard test data files that can be used to verify the coordinate transformations/conversions performed by the various OSGeo projects that fall under the MetaCRS umbrella. You can learn more on the [wiki:TestSuite Standard MetaCRS Test Data Files] wiki page.