Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-29 Thread Gabriel Roldan 
Thanks everyone for the discussion and consideration for this proposal.

Since all the PSC members casted their vote, I've transitioned the proposal
to in-progress,
and created this JIRA ticket to track progress:
https://osgeo-org.atlassian.net/browse/GEOS-10913

It contains subtasks for the identified steps to completion.

Cheers,
Gabe
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldan*
Geospatial Developer



On Tue, Mar 28, 2023 at 1:52 PM Torben Barsballe 
wrote:

> After catching up on the background of 216 along with this proposal, the
> approach makes sense to me.
> One piece I didn't see covered is build/release infrastructure for the new
> project - since it is now independent from geofence I assume it will be its
> own group on jenkins, but we can deal with that when we get there.
>
> +1
>
> Cheers,
> Torben
>
> On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan <
> gabriel.rol...@camptocamp.com> wrote:
>
>> Hi all,
>>
>> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created
>> a new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
>> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
>> /geoserver Github organization.
>>
>> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
>> details, comment back and vote.
>>
>> Best regards,
>> Gabriel.
>> *camptocamp*
>> INNOVATIVE SOLUTIONS
>> BY OPEN SOURCE EXPERTS
>>
>> *Gabriel Roldan*
>> Geospatial Developer
>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-28 Thread Torben Barsballe 
After catching up on the background of 216 along with this proposal, the
approach makes sense to me.
One piece I didn't see covered is build/release infrastructure for the new
project - since it is now independent from geofence I assume it will be its
own group on jenkins, but we can deal with that when we get there.

+1

Cheers,
Torben

On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan <
gabriel.rol...@camptocamp.com> wrote:

> Hi all,
>
> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created a
> new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
> /geoserver Github organization.
>
> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
> details, comment back and vote.
>
> Best regards,
> Gabriel.
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-28 Thread Kevin Smith 

+0

On 2023-03-28 01:57, Simone Giannecchini wrote:

apologies, I thought I did vote already-

+0

Regards,
Simone Giannecchini
==
Online training classes for GeoNode, GeoServer and MapStore from the 
experts!
Visit https://www.geosolutionsgroup.com/professional-training/ for 
more information.

==
Ing. Simone Giannecchini
@simogeo
Founder/Director GeoSolutions Italy
President GeoSolutions USA

phone: +39 0584 962313
fax:     +39 0584 1660272
mob:   +39  333 8128928
US: +1 (845) 547-7905

http://www.geosolutionsgroup.com
http://twitter.com/geosolutions_it

---
This email is intended only for the person or entity to which it is 
addressed and may contain information that is privileged, confidential 
or otherwise protected from disclosure. We remind that - as provided 
by European Regulation 2016/679 “GDPR” - copying, dissemination or use 
of this e-mail or the information herein by anyone other than the 
intended recipient is prohibited. If you have received this email by 
mistake, please notify us immediately by telephone or e-mail.



On Mon, Mar 27, 2023 at 5:55 PM Jody Garnett  
wrote:


Gabe:

GeoTools had a policy where you could start after a few days (as
long as you were happy with the risk). But itdoes not look like
geoserver offers

anything similar.
Try messaging any remaining PSC members directly if you are in a
hurry.
--
Jody Garnett


On Mon, Mar 27, 2023 at 4:54 AM Gabriel Roldan
 wrote:

Thank you all.

Question, shall we wait for the 10 days grace period for all
members to vote or is it time to move it from "under
discussion" to "in progress"?

TIA,
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldan*
Geospatial Developer*
*



On Mon, Mar 27, 2023 at 5:37 AM Alessio Fabiani
 wrote:

+0

On Fri, Mar 24, 2023 at 11:16 AM Nuno Oliveira
 wrote:

+1

On Thu, Mar 23, 2023 at 6:59 PM Ian Turton
 wrote:

+1

On Tue, 21 Mar 2023, 13:23 Gabriel Roldan,
 wrote:

Hi all,

as discussed in the "GSIP-216 GeoFence 4.0.x"
email thread, I've created a new GSIP to
request hosting the GeoFence fork, called
GeoServer ACL, as a sibling project to
GeoServer, GeoFence, and GeoServer Cloud,
under the /geoserver Github organization.

Please see
https://github.com/geoserver/geoserver/wiki/GSIP-217
for details, comment back and vote.

Best regards,
Gabriel.
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldan*
Geospatial Developer*
*

___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geoserver-devel

___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel



-- 


Regards,

Nuno Oliveira

==GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us
for more
information.==Nuno Miguel Carvalho
Oliveira@nmcoliveiraTechnical Lead / Project Manager

GeoSolutions Groupphone: +39 0584 962313fax:      +39
0584 1660272https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

---

Con riferimento alla normativa sul trattamento dei
dati personali (Reg. UE 2016/679 - Regolamento
generale sulla protezione dei dati “GDPR”), si precisa
che ogni circostanza inerente alla presente email (il
suo contenuto, gli eventuali allegati, etc.) è un dato
la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-28 Thread Simone Giannecchini 
apologies, I thought I did vote already-

+0

Regards,
Simone Giannecchini
==
Online training classes for GeoNode, GeoServer and MapStore from the
experts!
Visit https://www.geosolutionsgroup.com/professional-training/ for more
information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director GeoSolutions Italy
President GeoSolutions USA

phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39  333 8128928
US: +1 (845) 547-7905

http://www.geosolutionsgroup.com
http://twitter.com/geosolutions_it

---
This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.


On Mon, Mar 27, 2023 at 5:55 PM Jody Garnett  wrote:

> Gabe:
>
> GeoTools had a policy where you could start after a few days (as long as
> you were happy with the risk). But it does not look like geoserver offers
> 
> anything similar.
> Try messaging any remaining PSC members directly if you are in a hurry.
> --
> Jody Garnett
>
>
> On Mon, Mar 27, 2023 at 4:54 AM Gabriel Roldan <
> gabriel.rol...@camptocamp.com> wrote:
>
>> Thank you all.
>>
>> Question, shall we wait for the 10 days grace period for all members to
>> vote or is it time to move it from "under discussion" to "in progress"?
>>
>> TIA,
>> *camptocamp*
>> INNOVATIVE SOLUTIONS
>> BY OPEN SOURCE EXPERTS
>>
>> *Gabriel Roldan*
>> Geospatial Developer
>>
>>
>>
>> On Mon, Mar 27, 2023 at 5:37 AM Alessio Fabiani <
>> alessio.fabi...@geosolutionsgroup.com> wrote:
>>
>>> +0
>>>
>>> On Fri, Mar 24, 2023 at 11:16 AM Nuno Oliveira <
>>> nuno.olive...@geosolutionsgroup.com> wrote:
>>>
 +1

 On Thu, Mar 23, 2023 at 6:59 PM Ian Turton  wrote:

> +1
>
> On Tue, 21 Mar 2023, 13:23 Gabriel Roldan, <
> gabriel.rol...@camptocamp.com> wrote:
>
>> Hi all,
>>
>> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've
>> created a new GSIP to request hosting the GeoFence fork, called GeoServer
>> ACL, as a sibling project to GeoServer, GeoFence, and GeoServer Cloud,
>> under the /geoserver Github organization.
>>
>> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
>> details, comment back and vote.
>>
>> Best regards,
>> Gabriel.
>> *camptocamp*
>> INNOVATIVE SOLUTIONS
>> BY OPEN SOURCE EXPERTS
>>
>> *Gabriel Roldan*
>> Geospatial Developer
>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


 --

 Regards,

 Nuno Oliveira

 ==
 GeoServer Professional Services from the experts!

 Visit http://bit.ly/gs-services-us for more information.
 ==

 Nuno Miguel Carvalho Oliveira
 @nmcoliveira
 Technical Lead / Project Manager


 GeoSolutions Group
 phone: +39 0584 962313
 fax:  +39 0584 1660272

 https://www.geosolutionsgroup.com/
 http://twitter.com/geosolutions_it
 ---


 Con riferimento alla normativa sul trattamento dei dati personali (Reg.
 UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
 precisa che ogni circostanza inerente alla presente email (il suo
 contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
 riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
 messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
 operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

 This email is intended only for the person or entity to which it is
 addressed and may contain information that is privileged, confidential or
 otherwise protected from disclosure. We remind that - as provided by
 European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
 e-mail or the information herein by anyone other than the intended
 recipient is prohibited. If you have received this email by mistake, please
 notify us immediately by telephone or e-mail.
 ___
 Geoserver-devel mailing list
 Geoserver-devel@lists.sourcefo

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-27 Thread Jody Garnett 
Gabe:

GeoTools had a policy where you could start after a few days (as long as
you were happy with the risk). But it does not look like geoserver offers
 anything
similar.
Try messaging any remaining PSC members directly if you are in a hurry.
--
Jody Garnett


On Mon, Mar 27, 2023 at 4:54 AM Gabriel Roldan <
gabriel.rol...@camptocamp.com> wrote:

> Thank you all.
>
> Question, shall we wait for the 10 days grace period for all members to
> vote or is it time to move it from "under discussion" to "in progress"?
>
> TIA,
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
>
>
> On Mon, Mar 27, 2023 at 5:37 AM Alessio Fabiani <
> alessio.fabi...@geosolutionsgroup.com> wrote:
>
>> +0
>>
>> On Fri, Mar 24, 2023 at 11:16 AM Nuno Oliveira <
>> nuno.olive...@geosolutionsgroup.com> wrote:
>>
>>> +1
>>>
>>> On Thu, Mar 23, 2023 at 6:59 PM Ian Turton  wrote:
>>>
 +1

 On Tue, 21 Mar 2023, 13:23 Gabriel Roldan, <
 gabriel.rol...@camptocamp.com> wrote:

> Hi all,
>
> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've
> created a new GSIP to request hosting the GeoFence fork, called GeoServer
> ACL, as a sibling project to GeoServer, GeoFence, and GeoServer Cloud,
> under the /geoserver Github organization.
>
> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
> details, comment back and vote.
>
> Best regards,
> Gabriel.
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
 ___
 Geoserver-devel mailing list
 Geoserver-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-devel

>>>
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Nuno Oliveira
>>>
>>> ==
>>> GeoServer Professional Services from the experts!
>>>
>>> Visit http://bit.ly/gs-services-us for more information.
>>> ==
>>>
>>> Nuno Miguel Carvalho Oliveira
>>> @nmcoliveira
>>> Technical Lead / Project Manager
>>>
>>>
>>> GeoSolutions Group
>>> phone: +39 0584 962313
>>> fax:  +39 0584 1660272
>>>
>>> https://www.geosolutionsgroup.com/
>>> http://twitter.com/geosolutions_it
>>> ---
>>>
>>>
>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail.
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards,
>>
>> Alessio Fabiani
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Alessio Fabiani
>>
>> @alfa7691
>> Founder/Technical Lead
>>
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> mob:   +39  331 6233686
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-27 Thread Gabriel Roldan 
Thank you all.

Question, shall we wait for the 10 days grace period for all members to
vote or is it time to move it from "under discussion" to "in progress"?

TIA,
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldan*
Geospatial Developer



On Mon, Mar 27, 2023 at 5:37 AM Alessio Fabiani <
alessio.fabi...@geosolutionsgroup.com> wrote:

> +0
>
> On Fri, Mar 24, 2023 at 11:16 AM Nuno Oliveira <
> nuno.olive...@geosolutionsgroup.com> wrote:
>
>> +1
>>
>> On Thu, Mar 23, 2023 at 6:59 PM Ian Turton  wrote:
>>
>>> +1
>>>
>>> On Tue, 21 Mar 2023, 13:23 Gabriel Roldan, <
>>> gabriel.rol...@camptocamp.com> wrote:
>>>
 Hi all,

 as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've
 created a new GSIP to request hosting the GeoFence fork, called GeoServer
 ACL, as a sibling project to GeoServer, GeoFence, and GeoServer Cloud,
 under the /geoserver Github organization.

 Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
 details, comment back and vote.

 Best regards,
 Gabriel.
 *camptocamp*
 INNOVATIVE SOLUTIONS
 BY OPEN SOURCE EXPERTS

 *Gabriel Roldan*
 Geospatial Developer

 ___
 Geoserver-devel mailing list
 Geoserver-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-devel

>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards,
>>
>> Nuno Oliveira
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Nuno Miguel Carvalho Oliveira
>> @nmcoliveira
>> Technical Lead / Project Manager
>>
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>> fax:  +39 0584 1660272
>>
>> https://www.geosolutionsgroup.com/
>> http://twitter.com/geosolutions_it
>> ---
>>
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail.
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
>
> Regards,
>
> Alessio Fabiani
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Alessio Fabiani
>
> @alfa7691
> Founder/Technical Lead
>
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  331 6233686
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
__

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-27 Thread Alessio Fabiani 
+0

On Fri, Mar 24, 2023 at 11:16 AM Nuno Oliveira <
nuno.olive...@geosolutionsgroup.com> wrote:

> +1
>
> On Thu, Mar 23, 2023 at 6:59 PM Ian Turton  wrote:
>
>> +1
>>
>> On Tue, 21 Mar 2023, 13:23 Gabriel Roldan, 
>> wrote:
>>
>>> Hi all,
>>>
>>> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created
>>> a new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
>>> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
>>> /geoserver Github organization.
>>>
>>> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
>>> details, comment back and vote.
>>>
>>> Best regards,
>>> Gabriel.
>>> *camptocamp*
>>> INNOVATIVE SOLUTIONS
>>> BY OPEN SOURCE EXPERTS
>>>
>>> *Gabriel Roldan*
>>> Geospatial Developer
>>>
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
>
> Regards,
>
> Nuno Oliveira
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Nuno Miguel Carvalho Oliveira
> @nmcoliveira
> Technical Lead / Project Manager
>
>
> GeoSolutions Group
> phone: +39 0584 962313
> fax:  +39 0584 1660272
>
> https://www.geosolutionsgroup.com/
> http://twitter.com/geosolutions_it
> ---
>
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 

Regards,

Alessio Fabiani

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead


GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob:   +39  331 6233686

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

---

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-24 Thread Nuno Oliveira 
+1

On Thu, Mar 23, 2023 at 6:59 PM Ian Turton  wrote:

> +1
>
> On Tue, 21 Mar 2023, 13:23 Gabriel Roldan, 
> wrote:
>
>> Hi all,
>>
>> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created
>> a new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
>> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
>> /geoserver Github organization.
>>
>> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
>> details, comment back and vote.
>>
>> Best regards,
>> Gabriel.
>> *camptocamp*
>> INNOVATIVE SOLUTIONS
>> BY OPEN SOURCE EXPERTS
>>
>> *Gabriel Roldan*
>> Geospatial Developer
>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 

Regards,

Nuno Oliveira

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Technical Lead / Project Manager


GeoSolutions Group
phone: +39 0584 962313
fax:  +39 0584 1660272

https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
---


Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-23 Thread Ian Turton 
+1

On Tue, 21 Mar 2023, 13:23 Gabriel Roldan, 
wrote:

> Hi all,
>
> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created a
> new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
> /geoserver Github organization.
>
> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
> details, comment back and vote.
>
> Best regards,
> Gabriel.
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-23 Thread Rahkonen Jukka 
+1

-Jukka Rahkonen-

Lähettäjä: Andrea Aime 
Lähetetty: torstai 23. maaliskuuta 2023 20.12
Vastaanottaja: Gabriel Roldan 
Kopio: Geoserver-devel 
Aihe: Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL 
project

+1 here

Cheers
Andrea

On Thu, Mar 23, 2023 at 4:17 PM Gabriel Roldan 
mailto:gabriel.rol...@camptocamp.com>> wrote:
The proposal is updated specifying the versioning approach.
Is there anything else to discuss or can we proceed to voting?

TIA,

camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS
Gabriel Roldan
Geospatial Developer



On Wed, Mar 22, 2023 at 5:55 AM Andrea Aime 
mailto:andrea.a...@geosolutionsgroup.com>> 
wrote:
Hi Gabriel,
seeing the GeoFence experience, I agree with you, the two code bases will 
likely evolve at different speeds
and trying to bind them together on the same release cycle is likely going to 
be a lot of overhead for little or no gain.

Cheers
Andrea

On Tue, Mar 21, 2023 at 7:35 PM Gabriel Roldan 
mailto:gabriel.rol...@camptocamp.com>> wrote:
Hi Jody,

On Tue, Mar 21, 2023 at 1:06 PM Jody Garnett 
mailto:jody.garn...@gmail.com>> wrote:
Your proposal is straightforward and to the point, some feedback for discussion:

- I would title the proposal "GeoServer ACL project" (as the important part is 
a new project; rather than the repository where it is located).
Done. Good advice.

- One thing I would like addressed in the proposal is indicating how to keep 
the project in sync with the geoserver update cycle? I do not wish to be in the 
situation where an "official" geoserver project is running against an 
unsupported version of geoserver.
 I've been thinking deeply about this, follow up below.

- The proposal covers publishing maven artifacts which would be done from 
build.geoserver.org<https://eur06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuild.geoserver.org%2F&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7Ca72e28852d3a4fd027cf08db2bca37bc%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C638151919754017116%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cUISLa9aBvmRj9wuEjlJODEBYU5cBfzh9URLryFNFGI%3D&reserved=0>
 (as I do not wish to see credentials scattered across systems).
Sounds good to me.

Suggest that "GeoServer ACL" main branch track GeoServer main branch in order 
to stay in sync and releasable? Taking the geoserver acl client community 
module to an extension would also meet this goal.

My concern goes beyond version matching.
For the plugin, as a community module, and at least until it becomes an 
extension, the chances
to get a good test coverage from the CI builds are very few.
Besides compatibility with the server part API, concerns are limited to the 
stability of GeoServer's ResourceAccessManager interface and the Wicket 
libraries.

For the server part, the important thing is the REST API version/compatibility 
with the plugin, may it evolve over time.

Making GeoServer ACL's version follow GeoServer's main branch version doesn't 
make a lot of sense, as we'd either be forced to release new versions that have 
no changes, or be unable to, or forced to do additional work, if a new 
GeoServer ACL version is released and it needs to be backported to stable 
geoserver versions.

If both the plugin and the server stay on the same git repository, it's easier 
to ensure they stay compatible, as the CI build can run the necessary 
integration tests, and avoid situations like GeoFence's plugin (not embedded) 
where integration tests are never run, and I couldn't make them pass by setting 
up a standalone instance as indicated in the tests comments.

So, being a separate product, having its own life cycle make the most sense, 
and moreover, the CI builds could run plugin integration tests against several 
geoserver versions for a single GeoServer ACL version. e.g.
mvn verify -Dgs.version=2.24-SNAPSHOT
mvn verify -Dgs.version=2.23.0
mvn verify -Dgs.version=2.22.2

Then the GeoServer plugin's community module itself could be a practically 
empty jar with pure dependencies, on a specific gs-acl version.

To exemplify, gs-acl 1.0 is released, the geoserver community module depends on 
gs-acl-plugin:1.0 for the main branch, and all the stable branches.

When gs-acl 1.1 is released, we change the dependency of geoserver's main 
branch community module to gs-acl-plugin:1.1.

 Gabe

--
Jody Garnett


On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan 
mailto:gabriel.rol...@camptocamp.com>> wrote:
Hi all,

as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created a new 
GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a sibling 
project to GeoServer, GeoFence, and GeoServer Cloud, under the /geoserver 
Github organization.

Please see 
https://github.com/geoserver/geoserver/wiki/GSIP-217&

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-23 Thread Andrea Aime 
+1 here

Cheers
Andrea

On Thu, Mar 23, 2023 at 4:17 PM Gabriel Roldan <
gabriel.rol...@camptocamp.com> wrote:

> The proposal is updated specifying the versioning approach.
> Is there anything else to discuss or can we proceed to voting?
>
> TIA,
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
>
>
> On Wed, Mar 22, 2023 at 5:55 AM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi Gabriel,
>> seeing the GeoFence experience, I agree with you, the two code bases will
>> likely evolve at different speeds
>> and trying to bind them together on the same release cycle is likely
>> going to be a lot of overhead for little or no gain.
>>
>> Cheers
>> Andrea
>>
>> On Tue, Mar 21, 2023 at 7:35 PM Gabriel Roldan <
>> gabriel.rol...@camptocamp.com> wrote:
>>
>>> Hi Jody,
>>>
>>> On Tue, Mar 21, 2023 at 1:06 PM Jody Garnett 
>>> wrote:
>>>
 Your proposal is straightforward and to the point, some feedback for
 discussion:

 - I would title the proposal "GeoServer ACL project" (as the important
 part is a new project; rather than the repository where it is located).

>>> Done. Good advice.
>>>
>>>
 - One thing I would like addressed in the proposal is indicating how to
 keep the project in sync with the geoserver update cycle? I do not wish to
 be in the situation where an "official" geoserver project is running
 against an unsupported version of geoserver.

>>>  I've been thinking deeply about this, follow up below.
>>>
>>> - The proposal covers publishing maven artifacts which would be done
 from build.geoserver.org (as I do not wish to see credentials
 scattered across systems).

>>> Sounds good to me.
>>>
>>>
 Suggest that "GeoServer ACL" main branch track GeoServer main branch in
 order to stay in sync and releasable? Taking the geoserver acl client
 community module to an extension would also meet this goal.

>>>
>>> My concern goes beyond version matching.
>>> For the plugin, as a community module, and at least until it becomes an
>>> extension, the chances
>>> to get a good test coverage from the CI builds are very few.
>>> Besides compatibility with the server part API, concerns are limited to
>>> the stability of GeoServer's ResourceAccessManager interface and the Wicket
>>> libraries.
>>>
>>> For the server part, the important thing is the REST API
>>> version/compatibility with the plugin, may it evolve over time.
>>>
>>> Making GeoServer ACL's version follow GeoServer's main branch version
>>> doesn't make a lot of sense, as we'd either be forced to release new
>>> versions that have no changes, or be unable to, or forced to do additional
>>> work, if a new GeoServer ACL version is released and it needs to be
>>> backported to stable geoserver versions.
>>>
>>> If both the plugin and the server stay on the same git repository, it's
>>> easier to ensure they stay compatible, as the CI build can run the
>>> necessary integration tests, and avoid situations like GeoFence's plugin
>>> (not embedded) where integration tests are never run, and I couldn't make
>>> them pass by setting up a standalone instance as indicated in the tests
>>> comments.
>>>
>>> So, being a separate product, having its own life cycle make the most
>>> sense, and moreover, the CI builds could run plugin integration tests
>>> against several geoserver versions for a single GeoServer ACL version. e.g.
>>> mvn verify -Dgs.version=2.24-SNAPSHOT
>>> mvn verify -Dgs.version=2.23.0
>>> mvn verify -Dgs.version=2.22.2
>>>
>>> Then the GeoServer plugin's community module itself could be a
>>> practically empty jar with pure dependencies, on a specific gs-acl version.
>>>
>>> To exemplify, gs-acl 1.0 is released, the geoserver community module
>>> depends on gs-acl-plugin:1.0 for the main branch, and all the stable
>>> branches.
>>>
>>> When gs-acl 1.1 is released, we change the dependency of geoserver's
>>> main branch community module to gs-acl-plugin:1.1.
>>>
>>>  Gabe
>>>

 --
 Jody Garnett


 On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan <
 gabriel.rol...@camptocamp.com> wrote:

> Hi all,
>
> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've
> created a new GSIP to request hosting the GeoFence fork, called GeoServer
> ACL, as a sibling project to GeoServer, GeoFence, and GeoServer Cloud,
> under the /geoserver Github organization.
>
> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
> details, comment back and vote.
>
> Best regards,
> Gabriel.
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>>

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-23 Thread Gabriel Roldan 
The proposal is updated specifying the versioning approach.
Is there anything else to discuss or can we proceed to voting?

TIA,

*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldan*
Geospatial Developer



On Wed, Mar 22, 2023 at 5:55 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi Gabriel,
> seeing the GeoFence experience, I agree with you, the two code bases will
> likely evolve at different speeds
> and trying to bind them together on the same release cycle is likely going
> to be a lot of overhead for little or no gain.
>
> Cheers
> Andrea
>
> On Tue, Mar 21, 2023 at 7:35 PM Gabriel Roldan <
> gabriel.rol...@camptocamp.com> wrote:
>
>> Hi Jody,
>>
>> On Tue, Mar 21, 2023 at 1:06 PM Jody Garnett 
>> wrote:
>>
>>> Your proposal is straightforward and to the point, some feedback for
>>> discussion:
>>>
>>> - I would title the proposal "GeoServer ACL project" (as the important
>>> part is a new project; rather than the repository where it is located).
>>>
>> Done. Good advice.
>>
>>
>>> - One thing I would like addressed in the proposal is indicating how to
>>> keep the project in sync with the geoserver update cycle? I do not wish to
>>> be in the situation where an "official" geoserver project is running
>>> against an unsupported version of geoserver.
>>>
>>  I've been thinking deeply about this, follow up below.
>>
>> - The proposal covers publishing maven artifacts which would be done from
>>> build.geoserver.org (as I do not wish to see credentials scattered
>>> across systems).
>>>
>> Sounds good to me.
>>
>>
>>> Suggest that "GeoServer ACL" main branch track GeoServer main branch in
>>> order to stay in sync and releasable? Taking the geoserver acl client
>>> community module to an extension would also meet this goal.
>>>
>>
>> My concern goes beyond version matching.
>> For the plugin, as a community module, and at least until it becomes an
>> extension, the chances
>> to get a good test coverage from the CI builds are very few.
>> Besides compatibility with the server part API, concerns are limited to
>> the stability of GeoServer's ResourceAccessManager interface and the Wicket
>> libraries.
>>
>> For the server part, the important thing is the REST API
>> version/compatibility with the plugin, may it evolve over time.
>>
>> Making GeoServer ACL's version follow GeoServer's main branch version
>> doesn't make a lot of sense, as we'd either be forced to release new
>> versions that have no changes, or be unable to, or forced to do additional
>> work, if a new GeoServer ACL version is released and it needs to be
>> backported to stable geoserver versions.
>>
>> If both the plugin and the server stay on the same git repository, it's
>> easier to ensure they stay compatible, as the CI build can run the
>> necessary integration tests, and avoid situations like GeoFence's plugin
>> (not embedded) where integration tests are never run, and I couldn't make
>> them pass by setting up a standalone instance as indicated in the tests
>> comments.
>>
>> So, being a separate product, having its own life cycle make the most
>> sense, and moreover, the CI builds could run plugin integration tests
>> against several geoserver versions for a single GeoServer ACL version. e.g.
>> mvn verify -Dgs.version=2.24-SNAPSHOT
>> mvn verify -Dgs.version=2.23.0
>> mvn verify -Dgs.version=2.22.2
>>
>> Then the GeoServer plugin's community module itself could be a
>> practically empty jar with pure dependencies, on a specific gs-acl version.
>>
>> To exemplify, gs-acl 1.0 is released, the geoserver community module
>> depends on gs-acl-plugin:1.0 for the main branch, and all the stable
>> branches.
>>
>> When gs-acl 1.1 is released, we change the dependency of geoserver's main
>> branch community module to gs-acl-plugin:1.1.
>>
>>  Gabe
>>
>>>
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan <
>>> gabriel.rol...@camptocamp.com> wrote:
>>>
 Hi all,

 as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've
 created a new GSIP to request hosting the GeoFence fork, called GeoServer
 ACL, as a sibling project to GeoServer, GeoFence, and GeoServer Cloud,
 under the /geoserver Github organization.

 Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
 details, comment back and vote.

 Best regards,
 Gabriel.
 *camptocamp*
 INNOVATIVE SOLUTIONS
 BY OPEN SOURCE EXPERTS

 *Gabriel Roldan*
 Geospatial Developer

 ___
 Geoserver-devel mailing list
 Geoserver-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-devel

>>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-22 Thread Andrea Aime 
Hi Gabriel,
seeing the GeoFence experience, I agree with you, the two code bases will
likely evolve at different speeds
and trying to bind them together on the same release cycle is likely going
to be a lot of overhead for little or no gain.

Cheers
Andrea

On Tue, Mar 21, 2023 at 7:35 PM Gabriel Roldan <
gabriel.rol...@camptocamp.com> wrote:

> Hi Jody,
>
> On Tue, Mar 21, 2023 at 1:06 PM Jody Garnett 
> wrote:
>
>> Your proposal is straightforward and to the point, some feedback for
>> discussion:
>>
>> - I would title the proposal "GeoServer ACL project" (as the important
>> part is a new project; rather than the repository where it is located).
>>
> Done. Good advice.
>
>
>> - One thing I would like addressed in the proposal is indicating how to
>> keep the project in sync with the geoserver update cycle? I do not wish to
>> be in the situation where an "official" geoserver project is running
>> against an unsupported version of geoserver.
>>
>  I've been thinking deeply about this, follow up below.
>
> - The proposal covers publishing maven artifacts which would be done from
>> build.geoserver.org (as I do not wish to see credentials scattered
>> across systems).
>>
> Sounds good to me.
>
>
>> Suggest that "GeoServer ACL" main branch track GeoServer main branch in
>> order to stay in sync and releasable? Taking the geoserver acl client
>> community module to an extension would also meet this goal.
>>
>
> My concern goes beyond version matching.
> For the plugin, as a community module, and at least until it becomes an
> extension, the chances
> to get a good test coverage from the CI builds are very few.
> Besides compatibility with the server part API, concerns are limited to
> the stability of GeoServer's ResourceAccessManager interface and the Wicket
> libraries.
>
> For the server part, the important thing is the REST API
> version/compatibility with the plugin, may it evolve over time.
>
> Making GeoServer ACL's version follow GeoServer's main branch version
> doesn't make a lot of sense, as we'd either be forced to release new
> versions that have no changes, or be unable to, or forced to do additional
> work, if a new GeoServer ACL version is released and it needs to be
> backported to stable geoserver versions.
>
> If both the plugin and the server stay on the same git repository, it's
> easier to ensure they stay compatible, as the CI build can run the
> necessary integration tests, and avoid situations like GeoFence's plugin
> (not embedded) where integration tests are never run, and I couldn't make
> them pass by setting up a standalone instance as indicated in the tests
> comments.
>
> So, being a separate product, having its own life cycle make the most
> sense, and moreover, the CI builds could run plugin integration tests
> against several geoserver versions for a single GeoServer ACL version. e.g.
> mvn verify -Dgs.version=2.24-SNAPSHOT
> mvn verify -Dgs.version=2.23.0
> mvn verify -Dgs.version=2.22.2
>
> Then the GeoServer plugin's community module itself could be a practically
> empty jar with pure dependencies, on a specific gs-acl version.
>
> To exemplify, gs-acl 1.0 is released, the geoserver community module
> depends on gs-acl-plugin:1.0 for the main branch, and all the stable
> branches.
>
> When gs-acl 1.1 is released, we change the dependency of geoserver's main
> branch community module to gs-acl-plugin:1.1.
>
>  Gabe
>
>>
>> --
>> Jody Garnett
>>
>>
>> On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan <
>> gabriel.rol...@camptocamp.com> wrote:
>>
>>> Hi all,
>>>
>>> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created
>>> a new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
>>> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
>>> /geoserver Github organization.
>>>
>>> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
>>> details, comment back and vote.
>>>
>>> Best regards,
>>> Gabriel.
>>> *camptocamp*
>>> INNOVATIVE SOLUTIONS
>>> BY OPEN SOURCE EXPERTS
>>>
>>> *Gabriel Roldan*
>>> Geospatial Developer
>>>
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

---

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sul

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-21 Thread Gabriel Roldan 
Hi Jody,

On Tue, Mar 21, 2023 at 1:06 PM Jody Garnett  wrote:

> Your proposal is straightforward and to the point, some feedback for
> discussion:
>
> - I would title the proposal "GeoServer ACL project" (as the important
> part is a new project; rather than the repository where it is located).
>
Done. Good advice.


> - One thing I would like addressed in the proposal is indicating how to
> keep the project in sync with the geoserver update cycle? I do not wish to
> be in the situation where an "official" geoserver project is running
> against an unsupported version of geoserver.
>
 I've been thinking deeply about this, follow up below.

- The proposal covers publishing maven artifacts which would be done from
> build.geoserver.org (as I do not wish to see credentials scattered across
> systems).
>
Sounds good to me.


> Suggest that "GeoServer ACL" main branch track GeoServer main branch in
> order to stay in sync and releasable? Taking the geoserver acl client
> community module to an extension would also meet this goal.
>

My concern goes beyond version matching.
For the plugin, as a community module, and at least until it becomes an
extension, the chances
to get a good test coverage from the CI builds are very few.
Besides compatibility with the server part API, concerns are limited to the
stability of GeoServer's ResourceAccessManager interface and the Wicket
libraries.

For the server part, the important thing is the REST API
version/compatibility with the plugin, may it evolve over time.

Making GeoServer ACL's version follow GeoServer's main branch version
doesn't make a lot of sense, as we'd either be forced to release new
versions that have no changes, or be unable to, or forced to do additional
work, if a new GeoServer ACL version is released and it needs to be
backported to stable geoserver versions.

If both the plugin and the server stay on the same git repository, it's
easier to ensure they stay compatible, as the CI build can run the
necessary integration tests, and avoid situations like GeoFence's plugin
(not embedded) where integration tests are never run, and I couldn't make
them pass by setting up a standalone instance as indicated in the tests
comments.

So, being a separate product, having its own life cycle make the most
sense, and moreover, the CI builds could run plugin integration tests
against several geoserver versions for a single GeoServer ACL version. e.g.
mvn verify -Dgs.version=2.24-SNAPSHOT
mvn verify -Dgs.version=2.23.0
mvn verify -Dgs.version=2.22.2

Then the GeoServer plugin's community module itself could be a practically
empty jar with pure dependencies, on a specific gs-acl version.

To exemplify, gs-acl 1.0 is released, the geoserver community module
depends on gs-acl-plugin:1.0 for the main branch, and all the stable
branches.

When gs-acl 1.1 is released, we change the dependency of geoserver's main
branch community module to gs-acl-plugin:1.1.

 Gabe

>
> --
> Jody Garnett
>
>
> On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan <
> gabriel.rol...@camptocamp.com> wrote:
>
>> Hi all,
>>
>> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created
>> a new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
>> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
>> /geoserver Github organization.
>>
>> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
>> details, comment back and vote.
>>
>> Best regards,
>> Gabriel.
>> *camptocamp*
>> INNOVATIVE SOLUTIONS
>> BY OPEN SOURCE EXPERTS
>>
>> *Gabriel Roldan*
>> Geospatial Developer
>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-21 Thread Jody Garnett 
Your proposal is straightforward and to the point, some feedback for
discussion:

- I would title the proposal "GeoServer ACL project" (as the important part
is a new project; rather than the repository where it is located).
- One thing I would like addressed in the proposal is indicating how to
keep the project in sync with the geoserver update cycle? I do not wish to
be in the situation where an "official" geoserver project is running
against an unsupported version of geoserver.
- The proposal covers publishing maven artifacts which would be done from
build.geoserver.org (as I do not wish to see credentials scattered across
systems). Suggest that "GeoServer ACL" main branch track GeoServer main
branch in order to stay in sync and releasable? Taking the geoserver acl
client community module to an extension would also meet this goal.

--
Jody Garnett


On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan <
gabriel.rol...@camptocamp.com> wrote:

> Hi all,
>
> as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created a
> new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
> sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
> /geoserver Github organization.
>
> Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
> details, comment back and vote.
>
> Best regards,
> Gabriel.
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldan*
> Geospatial Developer
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] GSIP-217 Sibling repository for GeoServer ACL project

2023-03-21 Thread Gabriel Roldan 
Hi all,

as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created a
new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a
sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the
/geoserver Github organization.

Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for
details, comment back and vote.

Best regards,
Gabriel.
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldan*
Geospatial Developer
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel