On May 1, 2015, at 1:51 AM, Sleeman, Reinoud (KNMI) <reinoud.sleeman<at>knmi.nl> wrote:
Dea WG-II members,
please find this kind offer from Chad Trabant (IRIS) to manage the FDSN StationXML schema
throug GitHub. I fully support the concept and like to thank Chad for his offer to remain the
gatekeeper for incorporating the changes in the schema. Please let us know if you have other
ideas.
__________________________________________________________________________________________________
In order to make the editing and change management of the FDSN StationXML schema a more collaborative
exercise I have created a an "organizational" account for the FDSN and then a repository for the StationXML
schema:
https://github.com/FDSN/StationXML
This allows individuals and organizations to create modifications of the schema as branches. The changes
can then be proposed to and reviewed by FDSN WG II in their final form before being accepted. In addition,
this will allow for open and transparent tracking of issues and proposed changes.
As for my IRIS-supported involvement, I do not mind continuing to act as the gatekeeper for merging changes
approved by WG II into the master branch, tagging and generating point releases as guided by the WG if this
is what the WG desires. This framework allows more than one gatekeeper if this is ever needed or desired.
Importantly, this system will allow individuals/organizations to create patches/modifications to the schema,
effectively sharing the responsibility of editing, which are then ready for review.
________________________________________________________________________________
Best regards
Reinoud
_______________________________________________
fdsn-wg2-data mailing list
fdsn-wg2-data<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data
Dea WG-II members,--
please find this kind offer from Chad Trabant (IRIS) to manage the FDSN StationXML schema
throug GitHub. I fully support the concept and like to thank Chad for his offer to remain the
gatekeeper for incorporating the changes in the schema. Please let us know if you have other
ideas.
__________________________________________________________________________________________________
In order to make the editing and change management of the FDSN StationXML schema a more collaborative
exercise I have created a an "organizational" account for the FDSN and then a repository for the StationXML
schema:
https://github.com/FDSN/StationXML
This allows individuals and organizations to create modifications of the schema as branches. The changes
can then be proposed to and reviewed by FDSN WG II in their final form before being accepted. In addition,
this will allow for open and transparent tracking of issues and proposed changes.
As for my IRIS-supported involvement, I do not mind continuing to act as the gatekeeper for merging changes
approved by WG II into the master branch, tagging and generating point releases as guided by the WG if this
is what the WG desires. This framework allows more than one gatekeeper if this is ever needed or desired.
Importantly, this system will allow individuals/organizations to create patches/modifications to the schema,
effectively sharing the responsibility of editing, which are then ready for review.
________________________________________________________________________________
Best regards
Reinoud
_______________________________________________
fdsn-wg2-data mailing list
fdsn-wg2-data<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data
On May 1, 2015, at 1:00 PM, Doug Neuhauser <doug<at>seismo.berkeley.edu> wrote:
I approve this action. Thanks!
- Doug N
On 05/01/2015 01:51 AM, Sleeman, Reinoud (KNMI) wrote:
Dea WG-II members,--
please find this kind offer from Chad Trabant (IRIS) to manage the FDSN StationXML schema
throug GitHub. I fully support the concept and like to thank Chad for his offer to remain the
gatekeeper for incorporating the changes in the schema. Please let us know if you have other
ideas.
__________________________________________________________________________________________________
In order to make the editing and change management of the FDSN StationXML schema a more collaborative
exercise I have created a an "organizational" account for the FDSN and then a repository for the StationXML
schema:
https://github.com/FDSN/StationXML
This allows individuals and organizations to create modifications of the schema as branches. The changes
can then be proposed to and reviewed by FDSN WG II in their final form before being accepted. In addition,
this will allow for open and transparent tracking of issues and proposed changes.
As for my IRIS-supported involvement, I do not mind continuing to act as the gatekeeper for merging changes
approved by WG II into the master branch, tagging and generating point releases as guided by the WG if this
is what the WG desires. This framework allows more than one gatekeeper if this is ever needed or desired.
Importantly, this system will allow individuals/organizations to create patches/modifications to the schema,
effectively sharing the responsibility of editing, which are then ready for review.
________________________________________________________________________________
Best regards
Reinoud
_______________________________________________
fdsn-wg2-data mailing list
fdsn-wg2-data<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data
------------------------------------------------------------------------
Doug Neuhauser University of California, Berkeley
doug<at>seismo.berkeley.edu Berkeley Seismological Laboratory
Office: 510-642-0931 215 McCone Hall # 4760
Fax: 510-643-5811 Berkeley, CA 94720-4760
Remote: 530-752-5615 (Wed,Fri)
_______________________________________________
fdsn-wg2-data mailing list
fdsn-wg2-data<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data
Dea WG-II members,
please find this kind offer from Chad Trabant (IRIS) to manage the FDSN
StationXML schema
throug GitHub. I fully support the concept and like to thank Chad for his
offer to remain the
gatekeeper for incorporating the changes in the schema. Please let us know
if you have other
ideas.
__________________________________________________________________________________________________
In order to make the editing and change management of the FDSN StationXML
schema a more collaborative
exercise I have created a an "organizational" account for the FDSN and
then a repository for the StationXML
schema:
https://github.com/FDSN/StationXML
This allows individuals and organizations to create modifications of the
schema as branches. The changes
can then be proposed to and reviewed by FDSN WG II in their final form
before being accepted. In addition,
this will allow for open and transparent tracking of issues and proposed
changes.
As for my IRIS-supported involvement, I do not mind continuing to act as
the gatekeeper for merging changes
approved by WG II into the master branch, tagging and generating point
releases as guided by the WG if this
is what the WG desires. This framework allows more than one gatekeeper if
this is ever needed or desired.
Importantly, this system will allow individuals/organizations to create
patches/modifications to the schema,
effectively sharing the responsibility of editing, which are then ready
for review.
________________________________________________________________________________
Best regards
Reinoud
_______________________________________________
fdsn-wg2-data mailing list
fdsn-wg2-data<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data
Dea WG-II members,
please find this kind offer from Chad Trabant (IRIS) to manage the
FDSN StationXML schema throug GitHub. I fully support the concept and
like to thank Chad for his offer to remain the gatekeeper for
incorporating the changes in the schema. Please let us know if you
have other ideas.
__________________________________________________________________________________________________
In order to make the editing and change management of the FDSN
StationXML schema a more collaborative exercise I have created a an
"organizational" account for the FDSN and then a repository for the
StationXML schema:
https://github.com/FDSN/StationXML
This allows individuals and organizations to create modifications of
the schema as branches. The changes can then be proposed to and
reviewed by FDSN WG II in their final form before being accepted. In
addition, this will allow for open and transparent tracking of issues
and proposed changes.
As for my IRIS-supported involvement, I do not mind continuing to act
as the gatekeeper for merging changes approved by WG II into the
master branch, tagging and generating point releases as guided by the
WG if this is what the WG desires. This framework allows more than
one gatekeeper if this is ever needed or desired. Importantly, this
system will allow individuals/organizations to create
patches/modifications to the schema, effectively sharing the
responsibility of editing, which are then ready for review.
________________________________________________________________________________
Best regards Reinoud
Dea WG-II members,--
please find this kind offer from Chad Trabant (IRIS) to manage the FDSN StationXML schema
throug GitHub. I fully support the concept and like to thank Chad for his offer to remain the
gatekeeper for incorporating the changes in the schema. Please let us know if you have other
ideas.
__________________________________________________________________________________________________
In order to make the editing and change management of the FDSN StationXML schema a more collaborative
exercise I have created a an "organizational" account for the FDSN and then a repository for the StationXML
schema:
https://github.com/FDSN/StationXML
This allows individuals and organizations to create modifications of the schema as branches. The changes
can then be proposed to and reviewed by FDSN WG II in their final form before being accepted. In addition,
this will allow for open and transparent tracking of issues and proposed changes.
As for my IRIS-supported involvement, I do not mind continuing to act as the gatekeeper for merging changes
approved by WG II into the master branch, tagging and generating point releases as guided by the WG if this
is what the WG desires. This framework allows more than one gatekeeper if this is ever needed or desired.
Importantly, this system will allow individuals/organizations to create patches/modifications to the schema,
effectively sharing the responsibility of editing, which are then ready for review.
________________________________________________________________________________
Best regards
Reinoud
_______________________________________________
fdsn-wg2-data mailing list
fdsn-wg2-data<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data