[OSGeo-Discuss] on Google Code and export restrictions

[Chris Puttick]

----- "Frank Warmerdam" <warmerdam at pobox.com> wrote:
> Dave Patton wrote:
> > Frank Warmerdam wrote:
> > 
> >> I agree that we ought to consider developing a similar policy to
> >> Apache's.  I'll add an agenda item for the next board meeting to
> >> start digging into this.
> > 
> > One item for discussion would be what takes place
> > when a project enters incubation. Do they "opt in"
> > to the OSGeo policy? If they don't, are they then
> > excluded from being an OSGeo project? Can they
> > "opt in", and yet maintain their own project
> > infrastructure (website, svn, download links, etc.)
> > on servers in another country, and have access
> > to that infrastructure be subject to policies that
> > may conflict with the OSGeo policy?
> 
> Dave,
> 
> Projects going through incubation are allowed to maintain their own
> distinct infrastructure, wherever they want for the most part.  But
> they are still board as a project to follow OSGeo policy and obey
> applicable US laws even if their download server (for instance) is
> not in the US.
> 
> Best regards,
> -- 
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | President OSGeo,
> http://osgeo.org
> 
> _______________________________________________
> Discuss mailing list
> Discuss at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/discuss

Then I respectfully suggest, insofar as some recent US laws are at a level of paranoia that might prevent some open source software from actually being open. that OSGeo should consider reconstituting itself in a country that is less totalitarian in its attitudes.

Regards

Chris




------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.