[Carto] OSGeo SVN Repository for C# Map Rendering Engine?

[Landon Blake]

Tyler,

I think this is a great solution. I'll recommend we move the C# code
there as we complete the port.

Sound good George?

Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
 
 

-----Original Message-----
From: Tyler Mitchell (OSGeo) [mailto:tmitchell at osgeo.org] 
Sent: Monday, May 03, 2010 1:30 PM
To: Landon Blake
Cc: carto at lists.osgeo.org
Subject: Re: OSGeo SVN Repository for C# Map Rendering Engine?


On 05/03/2010 01:06 PM, Landon Blake wrote:
> Tyler,
>
> George and I have agreed to work together on a rendering engine
written
> in C# that can consume our preliminary MRI file. We'll start by
porting
> my existing Java code. Do you think we could get a slice of OSGeo SVN
> for our C# code?
>
> Do we need to apply for OSGeo Lab status to get that?

Other than going the labs route there is no other formal process 
required.  And if it's only going to start with a couple people, there 
is limited benefit to setting up a full instance with separate access 
control groups.  We could create a spot right now off of our main OSGeo 
SVN.  For example, I've started it here :)

http://svn.osgeo.org/community/projects/carto
and a few subfolders to help get started.

Work for you?
Any one who wants to commit will need an OSGeo user id:
http://osgeo.org/osgeo_userid

And one of us existing users will have to grant your account permissions

to commit to this repository.  Just email me with your user id.

Please note that there is a TON of other stuff in OSGeo's general SVN 
repository - so don't go downloading the root folder or even all of 
"/community/" unless you mean to :)  Likewise, commit back only in the 
carto folder explicitly, as many many other users are active in this 
other folders.

Tyler


Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.