[OSM-dev] Use of svn and trac resources by CommonMap association

[Frederik Ramm]

Hi,

morb.gis at beagle.com.au wrote:
> I want to get in touch with whoever maintains the application development
> facilities for OpenStreetMap.

[...]

Your questions touch on the broader question of the nature of OSM vs. 
commonmap, or more plainly: To what degree should OSM infrastructure be 
made available to other (non OSM) projects.

My take on this is that since OSM infrastructure is nominally owned and 
operated by OSMF, and OSMF's charter talks about furthering free mapping 
in general (and not OSM specifically), the infrastructure should be open 
to a project like commonmap as long as this is not seen to put too much 
of a strain on resources needed for OSM. But I am not sure whether 
everyone else sees it that way too; you could perhaps talk to one of the 
OSMF board members and ask them to discuss this at their next meeting.

> 1. In svn, can we set up some kind of commonmap branch of the rails_port code,
> so that we can lodge the branding changes etc?

Historically anyone with an SVN account has set up any branches that he 
or she liked, so I'd just go ahead - unless you're planning to create a 
whole ton of branches and swamp our SVN with non-OSM-related things ;-). 
If you don't have an account already, you'll have to get one from TomH.

> 2. Where/to whom can I submit changes/patches to rails_port and osmosis code?

If your changes to the rails_port are bugfixes of general interest, you 
should really commit them to trunk, after perhaps a short discussion. 
(Be prepared to have them reverted if they are seen to be... *greps 
through svn log* half-baked ;-)

Osmosis changes can be committed to trunk as well (provided they are not 
commonmap specific), and prior discussion on osmosis-dev might make sense.

> 3. Can we set up some kind of category for CommonMap issues in trac?

I don't see why not, from an OSM perspective. However, since you will 
not be able to re-brand trac, and trac is more outward-facing than SVN, 
you might really want to set up your own trac so you can direct your 
users to "the commonmap trac", instead of asking them to open tickets in 
"the commonmap section of the OSM trac".

On the other hand, your users might sometimes file bugs that turn out to 
be a general rails_port bug and then the ability to seamlessly move a 
ticket could come in handy...

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"