OSGeo - User contributions [en]

2007 Google SoC Application

2007-03-09T19:39:41Z

Wiki-Brucedechant:

'''1. Describe your organization.'''

OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general, and 12 projects in particular.

'''2. Why is your organization applying to participate in GSoC 2007? What do you hope to gain by participating?'''

We hope to get more students involved in open source geospatial development to grow the development community, and to advance particular projects.

'''3. Did your organization participate in GSoC 2005 or 2006? If so, please summarize your involvement and the successes and failures of your student projects.'''

OSGeo was formed in early 2006 and hasn't participated in GSoC in previous years. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which will be participating through OSGeo. The previously participating mentors and administrator from 2006 are supporting the OSGeo 2007 effort.

'''4. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?'''

Refractions Research participated in 2006, and sent 2 delegates to the mentor conference.

'''5. Who will your organization administrator be? Please include Google Account information.'''

Frank Warmerdam, OSGeo President - account: fwarmerdam

'''6. What license does your project use?'''

Different projects operate under a variety of OSI approved licenses, mainly GPL, LGPL, and MIT/X.

'''7. What is the URL for your ideas page?'''

''fill in - transfer from http://wiki.osgeo.org/index.php/Google_Summer_of_Code#Project_Ideas_Lists ''

'''8. What is the main development mailing list for your organization?'''

discuss@lists.osgeo.org - see http://lists.osgeo.org/mailman/listinfo/discuss

''add discussion lists for active projects''

* GeoServer - geoserver-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geoserver-devel details] )
* GeoTools - geotools-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geotools-devel details] )
* uDig - udig-devel@lists.refractions.net ( [http://lists.refractions.net/mailman/listinfo/udig-devel details] )
* MapGuide
** mapguide-users@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapguide-users details] )
** mapguide-internals@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapguide-internals details] )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel details] )

'''9. What is the main IRC channel for your organization?'''

#osgeo on irc.freenode.net

''list irc channels for active projects''

* irc://freenode/#geoserver
* irc://freenode/#geotools
* irc://freenode/#udig
* irc://freenode/#mapguide

'''10. Does your organization have an application template you would like to see students use? If so, please provide it now.'''

''consider''

'''11. Who will be your backup organization administrator? Please include Google Account information.'''

Landon Blake - sunburned.surveyor [] gmail.com

'''12. Who will your mentors be? Please include Google Account Information.'''

''to fill in''

* jody.garnett [] gmail.com (Jody Garnett) - available for uDig, GeoTools, GeoServer
* hobuisu [] gmail.com (Howard Butler) - available for GDAL
* jason.birch [] gmail.com (Jason Birch) - MapGuide
* pagameba [] gmail.com (Paul Spencer) - MapGuide
* trevor.wekel [] autodesk.com (Trevor Wekel) - MapGuide
* rbraygle@gmail.com / robert.bray@autodesk.com (Bob Bray) - MapGuide
* sunburned.surveyor [] gmail.com (Landon Blake) - OpenJUMP
* erwan.bocher [] gmail.com (Erwan Bocher) - OpenJUMP Alternate Mentor
* bruce.dechant [] autodesk.com (Bruce Dechant) - MapGuide

'''13. What criteria did you use to select these individuals as mentors? Please be as specific as possible.'''

Mentors are selected by project steering committees based on their reputation as skilled developers, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process.

'''14. What is your plan for dealing with disappearing students?'''

Plan A:

In order to minimize the likelyhood of disappearing students we will ensure that we have full contact information (email, home phone, etc) so that we can keep in touch with them.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require weekly blog-based progress reports, and participation on public IRC channels and mailing lists will all ensure ongoing commitment to the work.

On our side, we will ensure that our mentors are providing the student with enough guidance by requiring that all communications are held in public channels, reducing the risk of students giving up because they are not receiving enough direction.

Plan B:

Leveraging Open Source software from the OSGeo stack, coupled with high-accuracy data sources, volunteers from the open source community will process the data, including student metadata, and the results will be used for the targeting instructions for high-powered space-based lasers. Results of this will be displayed on a large video wall, which will prove that the student really has disappeared, and should act as a deterrent to future student disappearances.

http://www.jasonbirch.com/files/space_lasers.jpg
([http://ossim.telascience.org/ossimdata/nhv/DSCF0129.JPG resized from] )

'''15. What is your plan for dealing with disappearing mentors?'''

This will be a public process, and the entire community will be aware of the students' process. This will allow for strong internal awareness, and project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We considered a strategy similar to disappearing students "Plan B", but we really can't afford to lose some of these mentors.

'''16. What steps will you take to encourage students to interact with your project's community before, during and after the program?'''

''to fill in''

The steps taken depend on the individual projects, as example last year GeoTools project has asked for weekly attendence at IRC meetings or status email.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the appropriate OSGeo or project-specific mailing list when they have reached a milestone, giving a brief description of the work completed to that date.

'''17. What will you do to ensure that your accepted students stick with the project after GSoC concludes?'''

''to fill in''

The steps taken depend on the individual projects, as example last year GeoTools project asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in.

Other possibilities include:

# Asking the students to identify their greatest challenges in working on the project, and asking them to identify ways to overcome those challenges.
# Asking the students to provide input and advice on the next Summer of Code project, and possibly serving as a mentor if their experience merits that.

MapGuide RFC 1 - Commandline Parameter Changes

2006-11-17T17:45:44Z

Wiki-Brucedechant: /* Status */

This page contains an change request (RFC) for MapGuide Open Source.
More MapGuide RFCs can be found on the [[MapGuide RFCs]] page.

=Status=
{|style="text-align:left" border="1"
!RFC Template Version
|(1.0)
|-
!Submission Date
|October 31, 2006
|-
!Last Modified
|[[User:Brucedechant|Brucedechant]] 18:32, 17 November 2006 (CET)
|-
!Author
|Bruce Dechant
|-
!RFC Status
|adopted
|-
!Implementation Status
|Implemented
|-
!Proposed Release Target
|1.2
|-
!Assigned PSC guide(s)
|(when determined)
|-
| colspan=2 |
{| style="text-align:left" border="1" width="100%"
|+ align="left" |'''Voting History'''
! width="20%" | Date
! width="20%" |+1
! width="20%" |+0
! width="20%" |-0
! width="20%" |-1
|-
|November 15, 2006
|Bruce, Tom, Haris, Paul, Andy, Bob
|Jason
|
| style="color: red;" |
|}
|}

===Overview===

Make the following MapGuide server commandline parameter changes:
# Remove the need for the "/" character before the parameter name, but retain support for the "/" for backwards compatibility.
# Change the "testmode" parameter to "test", but retain support for the "testmode" for backwards compatibility.
# Remove the "/t" parameter from the renamed "testmode" parameter.
# Change the "interactive" parameter to "run", but retain support for "interactive" for backwards compatibility.
# Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter name which is not really needed

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affected:
*Resources.cpp
*Resources.h
*main.cpp
*Server.cpp
*UnitTesting.cpp

===Implications===

The commandline help will show the updated parameter names without the "/" character. However, the old parameter names with the "/" character will still work in order to maintain backwards compatibility.

===Test Plan===

*Test that the existing and renamed commandline parameters work as expected.
*Test both the correct and incorrect spellings of commandline parameters.
*Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-11-17T17:32:47Z

Wiki-Brucedechant: /* Status */

This page contains an change request (RFC) for MapGuide Open Source.
More MapGuide RFCs can be found on the [[MapGuide RFCs]] page.

=Status=
{|style="text-align:left" border="1"
!RFC Template Version
|(1.0)
|-
!Submission Date
|October 31, 2006
|-
!Last Modified
|[[User:Brucedechant|Brucedechant]] 18:32, 17 November 2006 (CET)
|-
!Author
|Bruce Dechant
|-
!RFC Status
|adopted
|-
!Implementation Status
|under development
|-
!Proposed Release Target
|1.2
|-
!Assigned PSC guide(s)
|(when determined)
|-
| colspan=2 |
{| style="text-align:left" border="1" width="100%"
|+ align="left" |'''Voting History'''
! width="20%" | Date
! width="20%" |+1
! width="20%" |+0
! width="20%" |-0
! width="20%" |-1
|-
|November 15, 2006
|Bruce, Tom, Haris, Paul, Andy, Bob
|Jason
|
| style="color: red;" |
|}
|}

===Overview===

Make the following MapGuide server commandline parameter changes:
# Remove the need for the "/" character before the parameter name, but retain support for the "/" for backwards compatibility.
# Change the "testmode" parameter to "test", but retain support for the "testmode" for backwards compatibility.
# Remove the "/t" parameter from the renamed "testmode" parameter.
# Change the "interactive" parameter to "run", but retain support for "interactive" for backwards compatibility.
# Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter name which is not really needed

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affected:
*Resources.cpp
*Resources.h
*main.cpp
*Server.cpp
*UnitTesting.cpp

===Implications===

The commandline help will show the updated parameter names without the "/" character. However, the old parameter names with the "/" character will still work in order to maintain backwards compatibility.

===Test Plan===

*Test that the existing and renamed commandline parameters work as expected.
*Test both the correct and incorrect spellings of commandline parameters.
*Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-11-15T17:41:20Z

Wiki-Brucedechant: /* Implications */

This page contains an change request (RFC) for MapGuide Open Source.
More MapGuide RFCs can be found on the [[MapGuide RFCs]] page.

===Status===
*Proposal Date: 19:18, 31 October 2006 (CET)
*Last Modified Date: 21:50, 1 November 2006 (CET)
*Author: Bruce Dechant [[User:Brucedechant|Brucedechant]]
*Status: Pending vote
*Implementation Status: Pending
*Voting History:
*Assigned PSC guide(s):

===Overview===

Make the following MapGuide server commandline parameter changes:
# Remove the need for the "/" character before the parameter name, but retain support for the "/" for backwards compatibility.
# Change the "testmode" parameter to "test", but retain support for the "testmode" for backwards compatibility.
# Remove the "/t" parameter from the renamed "testmode" parameter.
# Change the "interactive" parameter to "run", but retain support for "interactive" for backwards compatibility.
# Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter name which is not really needed

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affected:
*Resources.cpp
*Resources.h
*main.cpp
*Server.cpp
*UnitTesting.cpp

===Implications===

The commandline help will show the updated parameter names without the "/" character. However, the old parameter names with the "/" character will still work in order to maintain backwards compatibility.

===Test Plan===

*Test that the existing and renamed commandline parameters work as expected.
*Test both the correct and incorrect spellings of commandline parameters.
*Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-11-15T17:39:41Z

Wiki-Brucedechant: /* Overview */

This page contains an change request (RFC) for MapGuide Open Source.
More MapGuide RFCs can be found on the [[MapGuide RFCs]] page.

===Status===
*Proposal Date: 19:18, 31 October 2006 (CET)
*Last Modified Date: 21:50, 1 November 2006 (CET)
*Author: Bruce Dechant [[User:Brucedechant|Brucedechant]]
*Status: Pending vote
*Implementation Status: Pending
*Voting History:
*Assigned PSC guide(s):

===Overview===

Make the following MapGuide server commandline parameter changes:
# Remove the need for the "/" character before the parameter name, but retain support for the "/" for backwards compatibility.
# Change the "testmode" parameter to "test", but retain support for the "testmode" for backwards compatibility.
# Remove the "/t" parameter from the renamed "testmode" parameter.
# Change the "interactive" parameter to "run", but retain support for "interactive" for backwards compatibility.
# Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter name which is not really needed

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affected:
*Resources.cpp
*Resources.h
*main.cpp
*Server.cpp
*UnitTesting.cpp

===Implications===

The commandline help will show the updated parameter names without the "/" character. However, the old parameter names with the "/" character will still work.

===Test Plan===

*Test that the existing and renamed commandline parameters work as expected.
*Test both the correct and incorrect spellings of commandline parameters.
*Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-11-01T20:50:28Z

Wiki-Brucedechant:

===Status===
*Proposal Date: 19:18, 31 October 2006 (CET)
*Last Modified Date: 21:50, 1 November 2006 (CET)
*Author: Bruce Dechant [[User:Brucedechant|Brucedechant]]
*Status: Pending vote
*Implementation Status: Pending
*Voting History:

===Overview===

Make the following MapGuide server commandline parameter changes:
# Remove the need for the "/" character before the parameter name, but retain support for the "/" for backwards compatibility.
# Change the "testmode" parameter to "test"
# Remove the "/t" parameter from the renamed "testmode" parameter.
# Change the "interactive" parameter to "run", but retain support for "interactive" for backwards compatibility.
# Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter name which is not really needed

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affected:
*Resources.cpp
*Resources.h
*main.cpp
*Server.cpp
*UnitTesting.cpp

===Implications===

The commandline help will show the updated parameter names without the "/" character. However, the old parameter names with the "/" character will still work.

===Test Plan===

*Test that the existing and renamed commandline parameters work as expected.
*Test both the correct and incorrect spellings of commandline parameters.
*Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T21:51:40Z

Wiki-Brucedechant:

===Status===
*Proposal Date: 19:18, 31 October 2006 (CET)
*Last Modified Date: 21:24, 31 October 2006 (CET)
*Author: Bruce Dechant [[User:Brucedechant|Brucedechant]]
*Status: Pending vote
*Implementation Status: Pending
*Voting History:

===Overview===

Make the following MapGuide server commandline parameter changes:
# Change the "/" character before the parameter to a "-", but retain support for the "/" for backwards compatibility.
# Change the "testmode" parameter to "test"
# Remove the "/t" parameter from the renamed "testmode" parameter.
# Change the "interactive" parameter to "run", but retain support for "interactive" for backwards compatibility.
# Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter. This is more Windows centric and is actually the same as the Linux path separator character.

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affected:
*Resources.cpp
*Resources.h
*main.cpp
*Server.cpp
*UnitTesting.cpp

===Implications===

Users will need to be aware that the existing commandline parameters have changed, especially the "/interactive" commandline parameter change to "-run".

===Test Plan===

*Test that the existing and renamed commandline parameters work as expected.
*Test both the correct and incorrect spellings of commandline parameters.
*Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T20:24:16Z

Wiki-Brucedechant:

===Status===
*Proposal Date: 19:18, 31 October 2006 (CET)
*Last Modified Date: 21:24, 31 October 2006 (CET)
*Author: Bruce Dechant [[User:Brucedechant|Brucedechant]]
*Status: Pending vote
*Implementation Status: Pending
*Voting History:

===Overview===

Make the following MapGuide server commandline parameter changes:
# Change the "/" character before the parameter to a "-".
# Change the "testmode" parameter to "test"
# Remove the "/t" parameter from the renamed "testmode" parameter.
# Change the "interactive" parameter to "run".
# Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter. This is more Windows centric and is actually the same as the Linux path separator character.

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affected:
*Resources.cpp
*Resources.h
*main.cpp
*Server.cpp
*UnitTesting.cpp

===Implications===

Users will need to be aware that the existing commandline parameters have changed, especially the "/interactive" commandline parameter change to "-run".

===Test Plan===

*Test that the existing and renamed commandline parameters work as expected.
*Test both the correct and incorrect spellings of commandline parameters.
*Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T18:18:29Z

Wiki-Brucedechant:

===Overview===

Make the following MapGuide server commandline parameter changes:

1) Change the "/" character before the parameter to a "-".

2) Change the "testmode" parameter to "test"

3) Remove the "/t" parameter from the renamed "testmode" parameter.

4) Change the "interactive" parameter to "run".

5) Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter. This is more Windows centric and is actually the same as the Linux path separator character.

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affects:
Resources.cpp
Resources.h
main.cpp
Server.cpp
UnitTesting.cpp

===Implications===

Users will need to be aware that the existing commandline parameters have changed, especially the "/interactive" commandline parameter change to "-run".

===Test Plan===

Test that the existing and renamed commandline parameters work as expected.

Test both the correct and incorrect spellings of commandline parameters.

Test both valid and invalid specific unit test names to verify the removal of the "/t" parameter works.

--[[User:Brucedechant|Brucedechant]] 19:18, 31 October 2006 (CET)

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T18:18:00Z

Wiki-Brucedechant:

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T18:16:43Z

Wiki-Brucedechant:

===Overview===

Make the following MapGuide server commandline parameter changes:

1) Change the "/" character before the parameter to a "-".

2) Change the "testmode" parameter to "test"

3) Remove the "/t" parameter from the renamed "testmode" parameter.

4) Change the "interactive" parameter to "run".

5) Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter. This is more Windows centric and is actually the same as the Linux path separator character.

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific unit test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affects:
Resources.cpp
Resources.h
main.cpp
Server.cpp
UnitTesting.cpp

===Implications===

Users will need to be aware that the existing commandline parameters have changed, especially the "/interactive" commandline parameter change to "-run".

===Test Plan===

Test that the existing and renamed commandline parameters work as expected.

Test both the correct and incorrect spellings of commandline parameters.

Test both valid and invalid specific tests to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T18:15:06Z

Wiki-Brucedechant:

===Overview===

Make the following MapGuide server commandline parameter changes:

1) Change the "/" character before the parameter to a "-".

2) Change the "testmode" parameter to "test"

3) Remove the "/t" parameter from the renamed "testmode" parameter.

4) Change the "interactive" parameter to "run".

5) Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter. This is more Windows centric and is actually the same as the Linux path separator character.

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modified to work with the proposed changes.

====Technical====

The following files will be affects:
Resources.cpp
Resources.h
main.cpp
Server.cpp
UnitTesting.cpp

===Implications===

Users will need to be aware that the existing commandline parameters have changed, especially the "/interactive" commandline parameter change to "-run".

===Test Plan===

Test that the existing and renamed commandline parameters work as expected.

Test both the correct and incorrect spellings of commandline parameters.

Test both valid and invalid specific tests to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T18:13:18Z

Wiki-Brucedechant:

===Overview===

Make the following MapGuide server commandline parameter changes:

1) Change the "/" character before the parameter to a "-".

2) Change the "testmode" parameter to "test"

3) Remove the "/t" parameter from the renamed "testmode" parameter.

4) Change the "interactive" parameter to "run".

5) Remove the need for adding the "Test" word in front of all specific unit test names. ie: CoordinateSystem instead of TestCoordinateSystem

===Motivation===

The current commandline parameters for the MapGuide server require the "/" character before the parameter. This is more Windows centric and is actually the same as the Linux path seperator character.

The "testmode" and "interactive" parameter name changes and removal of the "Test" word for specific unit test names are really just changes for shortening the name for easier entry by the user.

The removal of the "/t" extra parameter for the renamed "testmode" ("test") parameter is recommended because it is really not needed. The user can simply specify what specific test they want to run without needing the "/t".

===Funding/Resources===

Bruce Dechant will be the resource to implement the changes outlined in this RFC.

===Proposed Changes===

The code and string resouces related to the commandline parameters of the server will be modifed to work with the proposed changes.

====Technical====

The following files will be affects:
Resources.cpp
Resources.h
main.cpp
Server.cpp
UnitTesting.cpp

===Implications===

Users will need to be aware that the existing commandline parameters have changed, especially the "/interactive" commandline parameter change to "-run".

===Test Plan===

Test that the existing and renamed commandline parameters work as expected.

Test both the correct and incorrect spellings of commandline parameters.

Test both valid and invalid specific tests to verify the removal of the "/t" parameter works.

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T18:04:36Z

Wiki-Brucedechant:

RFC - Commandline parameter changes

2006-10-31T17:56:38Z

Wiki-Brucedechant:

MapGuide RFC 1 - Commandline Parameter Changes

2006-10-31T17:54:16Z

Wiki-Brucedechant:

RFC - Commandline parameter changes

2006-10-31T17:52:45Z

Wiki-Brucedechant:

MapGuide Open Source

2006-10-31T17:37:20Z

Wiki-Brucedechant:

[[MapGuide PSC]] - MapGuide Open Source Project Steering Committee

[[MapGuide Wishes]] - Forum for wishes

[[Developer News and User Spotlight]]

[[MapGuide Open User Technical FAQ's]]

[[Other Languages - Spanish -]]

[[MapGuide Provenance Review]]

[[MapGuide RFCs]]