[Geoserver-devel] Request for commit access - geopackage community module

GeoServer GeoServer Developer
1

I've been doing some work on the geopackage community module, partly to get
it ready for migration to extension.

In addition to the geopackage module (WFS output, WMS output, WPS
generator), its likely some changes will be required on the mbtiles
community module.

I do not have commit access to geoserver (I do for geotools), and request
access.

I've previously submitted my CLAs, and have a some commits already merged
via PR (79 according to github:
https://github.com/geoserver/geoserver/commits?author=bradh although a lot
of that is docs or mechanical fixes).

Brad

2

Brad,

are you sure that you do not already have commit access? You are listed as a member of the GitHub geoserver organisation.
https://github.com/geoserver

Although it is a technicality, +1 to add you as a committer.

In my view, all PSC members should have commit access so that they can perform the dirty, dirty jobs that we expect of them. :wink:

Kind regards,
Ben.

On 01/10/17 12:31, Brad Hards wrote:

I've been doing some work on the geopackage community module, partly to get
it ready for migration to extension.

In addition to the geopackage module (WFS output, WMS output, WPS
generator), its likely some changes will be required on the mbtiles
community module.

I do not have commit access to geoserver (I do for geotools), and request
access.

I've previously submitted my CLAs, and have a some commits already merged
via PR (79 according to github:
https://github.com/geoserver/geoserver/commits?author=bradh although a lot
of that is docs or mechanical fixes).

Brad

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

3

Oh, I see. You were not in the right GitHub team. I have added you.

Kind regards,
Ben.

On 01/10/17 12:41, Ben Caradoc-Davies wrote:

Brad,

are you sure that you do not already have commit access? You are listed as a member of the GitHub geoserver organisation.
https://github.com/geoserver

Although it is a technicality, +1 to add you as a committer.

In my view, all PSC members should have commit access so that they can perform the dirty, dirty jobs that we expect of them. :wink:

Kind regards,
Ben.

On 01/10/17 12:31, Brad Hards wrote:

I've been doing some work on the geopackage community module, partly to get
it ready for migration to extension.

In addition to the geopackage module (WFS output, WMS output, WPS
generator), its likely some changes will be required on the mbtiles
community module.

I do not have commit access to geoserver (I do for geotools), and request
access.

I've previously submitted my CLAs, and have a some commits already merged
via PR (79 according to github:
https://github.com/geoserver/geoserver/commits?author=bradh although a lot
of that is docs or mechanical fixes).

Brad

------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

4

On Sun, Oct 1, 2017 at 1:41 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Brad,

are you sure that you do not already have commit access? You are listed as
a member of the GitHub geoserver organisation.
https://github.com/geoserver

Although it is a technicality, +1 to add you as a committer.

Seconded of course! :slight_smile:
(and surprised he did not have already)

Cheers
Andrea

--

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.