labs project assigning copyright

[Tim Schaub]

Hello-

GeoExt is project for building ExtJS based applications with OpenLayers
functionality.  I read through the OSGeo Labs information and added the
project to the list [1].

The GeoExt project steering committee would like to assign copyright for
the GeoExt code base to OSGeo.  The Labs page suggests that this could
be done by "Asking the incubation committee and doing it".

If that is an acceptable way getting approval for assigning copyright,
please consider this an official request: can we please assign copyright
for the GeoExt code base to OSGeo?

I have put together a Contributor Agreement [2] and will collect
signatures from our contributors if this is acceptable.  The agreement
is based on the GeoTools template.  Our code will be distributed with a
BSD license.

Thank you for any answers you can provide.  For previous discussion on
the subject, see the OSGeo-Discuss list [3].  Also, if anybody has any
other suggestions on how this should be done, please let me know.  We're
hoping to do an initial release in the next week and would like to have
this issue settled.

Thanks,
Tim

[1] http://wiki.osgeo.org/wiki/OSGeo_Labs
[2] http://www.geoext.org/trac/geoext/wiki/ContributorAgreement
[3] http://lists.osgeo.org/pipermail/discuss/2009-April/005221.html

--
Tim Schaub
OpenGeo - http://opengeo.org
Expert service straight from the developers.
_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Cameron Shorter-2]

Tim,
I think Frank will need to put a motion forward to get this passed. Is
that right Frank? I'll have a positive response when that happens.

Tim, one suggestion that I think that OSGeo projects should follow is
that they should store all contributor agreements electronically, in svn
or a wiki or similar. If you start this practice from the project
beginning, there should be next to no overhead, and it will make future
auditing much easier.

Tim Schaub wrote:

> Hello-
>
> GeoExt is project for building ExtJS based applications with
> OpenLayers functionality.  I read through the OSGeo Labs information
> and added the project to the list [1].
>
> The GeoExt project steering committee would like to assign copyright
> for the GeoExt code base to OSGeo.  The Labs page suggests that this
> could be done by "Asking the incubation committee and doing it".
>
> If that is an acceptable way getting approval for assigning copyright,
> please consider this an official request: can we please assign
> copyright for the GeoExt code base to OSGeo?
>
> I have put together a Contributor Agreement [2] and will collect
> signatures from our contributors if this is acceptable.  The agreement
> is based on the GeoTools template.  Our code will be distributed with
> a BSD license.
>
> Thank you for any answers you can provide.  For previous discussion on
> the subject, see the OSGeo-Discuss list [3].  Also, if anybody has any
> other suggestions on how this should be done, please let me know.  
> We're hoping to do an initial release in the next week and would like
> to have this issue settled.
>
> Thanks,
> Tim
>
> [1] http://wiki.osgeo.org/wiki/OSGeo_Labs
> [2] http://www.geoext.org/trac/geoext/wiki/ContributorAgreement
> [3] http://lists.osgeo.org/pipermail/discuss/2009-April/005221.html
>

--
Cameron Shorter
Geospatial Systems Architect
Tel: [phone]
Mob: [phone]

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Frank Warmerdam]

Tim Schaub wrote:

> Hello-
>
> GeoExt is project for building ExtJS based applications with OpenLayers
> functionality.  I read through the OSGeo Labs information and added the
> project to the list [1].
>
> The GeoExt project steering committee would like to assign copyright for
> the GeoExt code base to OSGeo.  The Labs page suggests that this could
> be done by "Asking the incubation committee and doing it".
>
> If that is an acceptable way getting approval for assigning copyright,
> please consider this an official request: can we please assign copyright
> for the GeoExt code base to OSGeo?
>
> I have put together a Contributor Agreement [2] and will collect
> signatures from our contributors if this is acceptable.  The agreement
> is based on the GeoTools template.  Our code will be distributed with a
> BSD license.
>
> Thank you for any answers you can provide.  For previous discussion on
> the subject, see the OSGeo-Discuss list [3].  Also, if anybody has any
> other suggestions on how this should be done, please let me know.  We're
> hoping to do an initial release in the next week and would like to have
> this issue settled.

Tim (and Tyler),

It has been my opinion that assignment to OSGeo can be done as long as Tyler
is willing to collect the assignment documents and store them as
secretary.  I do not particularly think the incubation committee needs to
approve it unless Tyler prefers that.

Cameron brings up an interesting point with regard to keeping the documents
in SVN as scanned documents.  On the one hand, in some venues it is necessary
to have a physically signed document, but we actually take these submissions
by fax which is digital so presumably a digital scan of a physical document
is sufficient.  In this case it might be a good practice for us to keep the
documents in the OSGeo SVN.  This would mean we could dispense with Tyler
having to take any action and it would give much improved transparency.

In light of this, I would like to suggest the following procedure:

  o Projects wishing to assign copyright to the foundation should seek the
    agreement of the current OSGeo Secretary (currently Tyler), who if they
    are doubtful could seek input from the board.  For project in incubation
    or full OSGeo projects it should be automatic.

  o Agreements should all be stored in scanned format in the OSGeo SVN.
    We can give out SVN commit access to one or two representatives of each
    project so they can actually add the agreements themselves after some
    vetting.

  o Tyler should collect existing agreements he has on file, and put them
    into SVN for safekeeping and transparency.

Tyler - any thoughts?

Pending feedback, I'd be interested in the incubator recommending this
procedure to the board for approval and would be willing to prepare such
a motion.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Tim Schaub]

Hey-

Cameron Shorter wrote:

> Tim,
> I think Frank will need to put a motion forward to get this passed. Is
> that right Frank? I'll have a positive response when that happens.
>
> Tim, one suggestion that I think that OSGeo projects should follow is
> that they should store all contributor agreements electronically, in svn
> or a wiki or similar. If you start this practice from the project
> beginning, there should be next to no overhead, and it will make future
> auditing much easier.
>

I agree.  I kept the mailing address on the Contributor Agreement, but
if OSGeo would prefer *not* to get a paper copy, I can remove that.

I added instructions on sending a scanned copy to the GeoExt PSC and was
planning on having those archived online.

Thanks for the response.  I look forward to hearing a decision.

Tim

> Tim Schaub wrote:
>> Hello-
>>
>> GeoExt is project for building ExtJS based applications with
>> OpenLayers functionality.  I read through the OSGeo Labs information
>> and added the project to the list [1].
>>
>> The GeoExt project steering committee would like to assign copyright
>> for the GeoExt code base to OSGeo.  The Labs page suggests that this
>> could be done by "Asking the incubation committee and doing it".
>>
>> If that is an acceptable way getting approval for assigning copyright,
>> please consider this an official request: can we please assign
>> copyright for the GeoExt code base to OSGeo?
>>
>> I have put together a Contributor Agreement [2] and will collect
>> signatures from our contributors if this is acceptable.  The agreement
>> is based on the GeoTools template.  Our code will be distributed with
>> a BSD license.
>>
>> Thank you for any answers you can provide.  For previous discussion on
>> the subject, see the OSGeo-Discuss list [3].  Also, if anybody has any
>> other suggestions on how this should be done, please let me know.  
>> We're hoping to do an initial release in the next week and would like
>> to have this issue settled.
>>
>> Thanks,
>> Tim
>>
>> [1] http://wiki.osgeo.org/wiki/OSGeo_Labs
>> [2] http://www.geoext.org/trac/geoext/wiki/ContributorAgreement
>> [3] http://lists.osgeo.org/pipermail/discuss/2009-April/005221.html
>>
>
>

--
Tim Schaub
OpenGeo - http://opengeo.org
Expert service straight from the developers.
_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Peter Baumann-4]

Some javascript/style in this post has been disabled (why?)

Hi all (+ Bruce, as our incubation mentor),

an issue of interest to us (rasdaman) as well.
Following some google sessions, we have established an approach as follows:
- patches are accepted only via the official website and the resp. form

- and, to allow for submission, the Submitter Agreement must be accepted
- which then is bundled with the patch into a tarball stored in our patch repository, and will never be deleted.

My understanding (but not my invention) is that this way we can prove that any code submitted has agreed to the license model.

Q: is this procedure considered adequate by OSGeo?

-Peter




Frank Warmerdam wrote:

Tim Schaub wrote:
  

Hello-

GeoExt is project for building ExtJS based applications with OpenLayers 
functionality.  I read through the OSGeo Labs information and added the 
project to the list [1].

The GeoExt project steering committee would like to assign copyright for 
the GeoExt code base to OSGeo.  The Labs page suggests that this could 
be done by "Asking the incubation committee and doing it".

If that is an acceptable way getting approval for assigning copyright, 
please consider this an official request: can we please assign copyright 
for the GeoExt code base to OSGeo?

I have put together a Contributor Agreement [2] and will collect 
signatures from our contributors if this is acceptable.  The agreement 
is based on the GeoTools template.  Our code will be distributed with a 
BSD license.

Thank you for any answers you can provide.  For previous discussion on 
the subject, see the OSGeo-Discuss list [3].  Also, if anybody has any 
other suggestions on how this should be done, please let me know.  We're 
hoping to do an initial release in the next week and would like to have 
this issue settled.
    

Tim (and Tyler),

It has been my opinion that assignment to OSGeo can be done as long as Tyler
is willing to collect the assignment documents and store them as
secretary.  I do not particularly think the incubation committee needs to
approve it unless Tyler prefers that.

Cameron brings up an interesting point with regard to keeping the documents
in SVN as scanned documents.  On the one hand, in some venues it is necessary
to have a physically signed document, but we actually take these submissions
by fax which is digital so presumably a digital scan of a physical document
is sufficient.  In this case it might be a good practice for us to keep the
documents in the OSGeo SVN.  This would mean we could dispense with Tyler
having to take any action and it would give much improved transparency.

In light of this, I would like to suggest the following procedure:

  o Projects wishing to assign copyright to the foundation should seek the
    agreement of the current OSGeo Secretary (currently Tyler), who if they
    are doubtful could seek input from the board.  For project in incubation
    or full OSGeo projects it should be automatic.

  o Agreements should all be stored in scanned format in the OSGeo SVN.
    We can give out SVN commit access to one or two representatives of each
    project so they can actually add the agreements themselves after some
    vetting.

  o Tyler should collect existing agreements he has on file, and put them
    into SVN for safekeeping and transparency.

Tyler - any thoughts?

Pending feedback, I'd be interested in the incubator recommending this
procedure to the board for approval and would be willing to prepare such
a motion.

Best regards,
  

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Frank Warmerdam]

Peter Baumann wrote:

> Hi all (+ Bruce, as our incubation mentor),
>
> an issue of interest to us (rasdaman) as well.
> Following some google sessions, we have established an approach as follows:
> - patches are accepted only via the official website and the resp. form
>
> - and, to allow for submission, the Submitter Agreement must be accepted
> - which then is bundled with the patch into a tarball stored in our
> patch repository, and will never be deleted.
>
> My understanding (but not my invention) is that this way we can prove
> that any code submitted has agreed to the license model.
>
> Q: is this procedure considered adequate by OSGeo?

Peter,

Is agreement to the submitter agreement done via a web click through?
Could you provide a reference to the submitter agreement?

On the face of it, this sounds like a thorough solution.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Peter Baumann-4]

Some javascript/style in this post has been disabled (why?)

Frank-

Frank Warmerdam wrote:

Peter Baumann wrote:
  

Hi all (+ Bruce, as our incubation mentor),

an issue of interest to us (rasdaman) as well.
Following some google sessions, we have established an approach as follows:
- patches are accepted only via the official website and the resp. form

- and, to allow for submission, the Submitter Agreement must be accepted
- which then is bundled with the patch into a tarball stored in our 
patch repository, and will never be deleted.

My understanding (but not my invention) is that this way we can prove 
that any code submitted has agreed to the license model.

Q: is this procedure considered adequate by OSGeo?
    

Peter,

Is agreement to the submitter agreement done via a web click through?
  

the form is built such that you only can submit it once the agreement is agreed to.
See http://kahlua.eecs.jacobs-university.de:8000/trac/rasdaman/patchmanager

Could you provide a reference to the submitter agreement?
  

...is accessible from said page.

-Peter

On the face of it, this sounds like a thorough solution.

Best regards,
  

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Frank Warmerdam]

Peter Baumann wrote:
>> Peter,
>>
>> Is agreement to the submitter agreement done via a web click through?
>>  
> the form is built such that you only can submit it once the agreement is
> agreed to.
> See http://kahlua.eecs.jacobs-university.de:8000/trac/rasdaman/patchmanager

Peter,

The agreement seems reasonable comprehensive.  I would note it will
presumably not stand up as a copyright assignment in the USA since
in the US copyright can only be assigned with a signed document.

However, the language seems to cover this via the licensing language.

I have no objection to this mechanism.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Cameron Shorter-2]

Frank Warmerdam wrote:

<snip> ...

> In light of this, I would like to suggest the following procedure:
>
>  o Projects wishing to assign copyright to the foundation should seek the
>    agreement of the current OSGeo Secretary (currently Tyler), who if
> they
>    are doubtful could seek input from the board.  For project in
> incubation
>    or full OSGeo projects it should be automatic.
I think we need to include some guidelines on what projects OSGeo will
accept. Basically, projects can assign copyright to OSGeo if they plan
to eventually become OSGeo projects and conforming to the OSGeo
guidelines set out under OSGeo Labs.

I think that OSGeo labs should come under the responsibility of the
Incubation Committee, but am happy to bend on that point.
>
>  o Agreements should all be stored in scanned format in the OSGeo SVN.
>    We can give out SVN commit access to one or two representatives of
> each
>    project so they can actually add the agreements themselves after some
>    vetting.
I don't think we need to be prescriptive about where agreements are
stored, so long as they are stored somewhere. It may be on OSGeo svn, or
the project svn, or a wiki or similar.
>
>  o Tyler should collect existing agreements he has on file, and put them
>    into SVN for safekeeping and transparency.
This would be desirable if not too much effort.
>
> Tyler - any thoughts?
>
> Pending feedback, I'd be interested in the incubator recommending this
> procedure to the board for approval and would be willing to prepare such
> a motion.
>
> Best regards,


--
Cameron Shorter
Geospatial Systems Architect
Tel: [phone]
Mob: [phone]

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Frank Warmerdam]

Cameron Shorter wrote:
>>  o Projects wishing to assign copyright to the foundation should seek the
>>    agreement of the current OSGeo Secretary (currently Tyler), who if
>> they
>>    are doubtful could seek input from the board.  For project in
>> incubation
>>    or full OSGeo projects it should be automatic.
 >
> I think we need to include some guidelines on what projects OSGeo will
> accept. Basically, projects can assign copyright to OSGeo if they plan
> to eventually become OSGeo projects and conforming to the OSGeo
> guidelines set out under OSGeo Labs.

Cameron,

Why do you think such guidelines are needed?  Who would interprete them?
It seems like the "cost" of collecting contribution agreements is very
small and there is relatively little downside to accepting them on
behalf of a project in which the foundation might have little interest.

If I were to propose guidelines it would be that this only be done
for projects with a geospatial connection and under an open source
license.

> I think that OSGeo labs should come under the responsibility of the
> Incubation Committee, but am happy to bend on that point.

I'm agreeable, but not so certain that accepting contribution
agreements or copyright assignment needs to be related to OSGeo Labs.

>>  o Agreements should all be stored in scanned format in the OSGeo SVN.
>>    We can give out SVN commit access to one or two representatives of
>> each
>>    project so they can actually add the agreements themselves after some
>>    vetting.
> I don't think we need to be prescriptive about where agreements are
> stored, so long as they are stored somewhere. It may be on OSGeo svn, or
> the project svn, or a wiki or similar.

As legal documents of the foundation, the Secretary is responsible for
keeping them available and under his/her administration.  I am suggesting
we control their location in part to ensure that the Secretary will be
aware of their storage, and so there are relatively few places that we
need to be sure of capturing to have the foundations legal documents.

In fact, I hope to also encourage scanning and storing in this fashion of
other foundation documents that are not confidential.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Cameron Shorter-2]

Frank Warmerdam wrote:

> Cameron Shorter wrote:
>  
>>>  o Projects wishing to assign copyright to the foundation should seek the
>>>    agreement of the current OSGeo Secretary (currently Tyler), who if
>>> they
>>>    are doubtful could seek input from the board.  For project in
>>> incubation
>>>    or full OSGeo projects it should be automatic.
>>>      
>  >
>  
>> I think we need to include some guidelines on what projects OSGeo will
>> accept. Basically, projects can assign copyright to OSGeo if they plan
>> to eventually become OSGeo projects and conforming to the OSGeo
>> guidelines set out under OSGeo Labs.
>>    
>
> Cameron,
>
> Why do you think such guidelines are needed?  Who would interprete them?
> It seems like the "cost" of collecting contribution agreements is very
> small and there is relatively little downside to accepting them on
> behalf of a project in which the foundation might have little interest.
>
> If I were to propose guidelines it would be that this only be done
> for projects with a geospatial connection and under an open source
> license.
>  

The above sentence may be sufficient guidelines. Ie, Open Source +
Geospatial.
I was thinking + working on becoming an OSGeo project (ie listing in
OSGeo labs) would be slightly better, but I don't feel strongly about it.

>  
>> I think that OSGeo labs should come under the responsibility of the
>> Incubation Committee, but am happy to bend on that point.
>>    
>
> I'm agreeable, but not so certain that accepting contribution
> agreements or copyright assignment needs to be related to OSGeo Labs.
>
>  
>>>  o Agreements should all be stored in scanned format in the OSGeo SVN.
>>>    We can give out SVN commit access to one or two representatives of
>>> each
>>>    project so they can actually add the agreements themselves after some
>>>    vetting.
>>>      
>> I don't think we need to be prescriptive about where agreements are
>> stored, so long as they are stored somewhere. It may be on OSGeo svn, or
>> the project svn, or a wiki or similar.
>>    
>
> As legal documents of the foundation, the Secretary is responsible for
> keeping them available and under his/her administration.  I am suggesting
> we control their location in part to ensure that the Secretary will be
> aware of their storage, and so there are relatively few places that we
> need to be sure of capturing to have the foundations legal documents.
>
> In fact, I hope to also encourage scanning and storing in this fashion of
> other foundation documents that are not confidential.
>
> Best regards,
>  

--
Cameron Shorter
Geospatial Systems Architect
Tel: [phone]
Mob: [phone]

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Bruce Bannerman-2]

IMO:

>
> Hi all (+ Bruce, as our incubation mentor),
>

Peter,

Sorry, but to my knowledge, I have not been accepted as a mentor for Rasdaman.


Bruce_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Peter Baumann-4]

Some javascript/style in this post has been disabled (why?)

Bruce-

oops, sorry - I seem to have misinterpreted signals, obviously my not-yet-sufficient knowledge about OSGeo procedures.
We'll wait patiently then :)

-Peter


Bruce Bannerman wrote:

IMO:

  

Hi all (+ Bruce, as our incubation mentor),

    

Peter,

Sorry, but to my knowledge, I have not been accepted as a mentor for Rasdaman.


Bruce

_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator

[Tim Schaub]

Hey-

Thanks for the responses.  A summary of my understanding:

Area of Agreement
-----------------

A project with a geospatial focus and an open source license may assign
copyright to OSGeo by collecting copyright assignment agreements from
all contributors.  These signed agreements must be delivered to the
OSGeo Secretary.

Details Left to be Determined
-----------------------------

The incubation committee might be involved in determining if a project
meets OSGeo criteria (geospatial + open source).  The signed agreement
documents might be stored in a digital repository.


Unless I'm mistaken, it looks like GeoExt can assign copyright to OSGeo.
  I have collected signed agreements from all contributors to the code
base.  We are starting the process for an initial release this week, and
I'll change the copyright statements in the code based on the assumption
that the assignment is acceptable to OSGeo.

Tyler, I'll be happy to provide the agreements in whatever form works
for you.  If there is anything else we should do before making the
copyright change (or if this is not acceptable), please let me know.

Thanks,
Tim

Cameron Shorter wrote:

> Frank Warmerdam wrote:
>> Cameron Shorter wrote:
>>  
>>>>  o Projects wishing to assign copyright to the foundation should
>>>> seek the
>>>>    agreement of the current OSGeo Secretary (currently Tyler), who
>>>> if they
>>>>    are doubtful could seek input from the board.  For project in
>>>> incubation
>>>>    or full OSGeo projects it should be automatic.
>>>>      
>>  >
>>  
>>> I think we need to include some guidelines on what projects OSGeo
>>> will accept. Basically, projects can assign copyright to OSGeo if
>>> they plan to eventually become OSGeo projects and conforming to the
>>> OSGeo guidelines set out under OSGeo Labs.
>>>    
>>
>> Cameron,
>>
>> Why do you think such guidelines are needed?  Who would interprete them?
>> It seems like the "cost" of collecting contribution agreements is very
>> small and there is relatively little downside to accepting them on
>> behalf of a project in which the foundation might have little interest.
>>
>> If I were to propose guidelines it would be that this only be done
>> for projects with a geospatial connection and under an open source
>> license.
>>  
> The above sentence may be sufficient guidelines. Ie, Open Source +
> Geospatial.
> I was thinking + working on becoming an OSGeo project (ie listing in
> OSGeo labs) would be slightly better, but I don't feel strongly about it.
>>  
>>> I think that OSGeo labs should come under the responsibility of the
>>> Incubation Committee, but am happy to bend on that point.
>>>    
>>
>> I'm agreeable, but not so certain that accepting contribution
>> agreements or copyright assignment needs to be related to OSGeo Labs.
>>
>>  
>>>>  o Agreements should all be stored in scanned format in the OSGeo SVN.
>>>>    We can give out SVN commit access to one or two representatives
>>>> of each
>>>>    project so they can actually add the agreements themselves after
>>>> some
>>>>    vetting.
>>>>      
>>> I don't think we need to be prescriptive about where agreements are
>>> stored, so long as they are stored somewhere. It may be on OSGeo svn,
>>> or the project svn, or a wiki or similar.
>>>    
>>
>> As legal documents of the foundation, the Secretary is responsible for
>> keeping them available and under his/her administration.  I am suggesting
>> we control their location in part to ensure that the Secretary will be
>> aware of their storage, and so there are relatively few places that we
>> need to be sure of capturing to have the foundations legal documents.
>>
>> In fact, I hope to also encourage scanning and storing in this fashion of
>> other foundation documents that are not confidential.
>>
>> Best regards,
>>  
>
>

--
Tim Schaub
OpenGeo - http://opengeo.org
Expert service straight from the developers.
_______________________________________________
Incubator mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/incubator