From strk at kbt.io  Thu May  2 09:11:12 2024
From: strk at kbt.io (Sandro Santilli)
Date: Thu, 2 May 2024 18:11:12 +0200
Subject: Motion Passed: System Admin Contract III 2024 [+ Downgrade]
Message-ID: <ZjO7IAaZfM02J5t4@c23>

I'm declaring the motion for System Admin Contract III passed
with following votes:

  +1 Vicky Vergara
  +1 Jorge Sanz
  +1 Regina Obe
  +1 Alex Mandel
  +1 Markus Neteler

Full thread: https://lists.osgeo.org/pipermail/sac/2024-January/016347.html

As a followup to budget discussion reduction I've also downgraded the
proposal to ?6400 and will submit for signature:
https://nextcloud.osgeo.org/s/BzJaotPKzg9MAfk

--strk;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20240502/786732d1/attachment.sig>

From lr at pcorp.us  Tue May  7 15:11:36 2024
From: lr at pcorp.us (Regina Obe)
Date: Tue, 7 May 2024 18:11:36 -0400
Subject: OSGeo7 is down at moment
Message-ID: <002c01daa0cb$879e3a70$96daaf50$@pcorp.us>

Looks like it's been down for about an hour.

Checking on it now.

Thanks,
Regina


From lr at pcorp.us  Tue May  7 18:36:28 2024
From: lr at pcorp.us (Regina Obe)
Date: Tue, 7 May 2024 21:36:28 -0400
Subject: OSGeo7 is down at moment
Message-ID: <000801daa0e8$26841c60$738c5520$@pcorp.us>

> Cc: 'OSGeo Discussions' <discuss at lists.osgeo.org>
> Subject: OSGeo7 is down at moment
> 
> Looks like it's been down for about an hour.
> 
> Checking on it now.
> 
> Thanks,
> Regina

[Regina Obe] 
OSGeo7 is back up and been for a couple of hours.  I still plan to move some
services over particularly ldap to osgeo9 this weekend 
since that impacts pretty much everything.






	


From strk at kbt.io  Wed May  8 08:30:36 2024
From: strk at kbt.io (Sandro Santilli)
Date: Wed, 8 May 2024 17:30:36 +0200
Subject: Gitea deployment, now Ansible based
Message-ID: <ZjuanGuZoOnoqjm7@c19>

FYI, the Gitea configuration is now controlled via ansible.


Staging deploy:

  ANSIBLE_CONFIG=ansible.osgeo.staging.cfg \
  ansible-playbook deployment/deploy-gitea.yml

Production deploy:

  ANSIBLE_CONFIG=ansible.osgeo.staging.cfg \
  ansible-playbook deployment/deploy-gitea.yml

The configuration is now a template:

  deployment/roles/gitea/templates/app.ini.j2

This allows us to use variables to tweak the configuration
for use in staging, as done by the staging inventory group
var file:

  inventory/staging/group_vars/gitea.yml

For this reason the gitea-config git repository was archived
and remotes for it were removed from the production and
the staging server.

The wiki page was updated accordingly:

  https://wiki.osgeo.org/wiki/SAC:Gitea


--strk;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20240508/b92c44f6/attachment.sig>

From trac_osgeo at osgeo.org  Sat May 11 23:56:03 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Sun, 12 May 2024 06:56:03 -0000
Subject: [OSGeo] #2599: Unable to edit wiki pages
In-Reply-To: <036.2b4d6df119f6252f07cbb6c1ef4ded53@osgeo.org>
References: <036.2b4d6df119f6252f07cbb6c1ef4ded53@osgeo.org>
Message-ID: <051.0b66467ceaaf388225a1f62d4859e5bc@osgeo.org>

#2599: Unable to edit wiki pages
---------------------------+---------------------------------------
 Reporter:  vasile         |       Owner:  sac@?
     Type:  task           |      Status:  closed
 Priority:  normal         |   Milestone:  Sysadmin Contract 2024-I
Component:  SysAdmin/Wiki  |  Resolution:  fixed
 Keywords:  wiki           |
---------------------------+---------------------------------------
Changes (by robe):

 * status:  new => closed
 * resolution:   => fixed

Comment:

 closing this out since we haven't had any complaints about this recently.
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2599#comment:61>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From trac_osgeo at osgeo.org  Sun May 12 00:02:42 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Sun, 12 May 2024 07:02:42 -0000
Subject: [OSGeo] #2905: Investigate slowness of nextcloud.osgeo.org and fix
In-Reply-To: <034.95301470d545a04f4bbe57d9b38c5791@osgeo.org>
References: <034.95301470d545a04f4bbe57d9b38c5791@osgeo.org>
Message-ID: <049.0dfb3eeafc2c875d760299baffe4f5f5@osgeo.org>

#2905: Investigate slowness of nextcloud.osgeo.org and fix
----------------------+---------------------------------------
 Reporter:  robe      |       Owner:  sac@?
     Type:  task      |      Status:  new
 Priority:  normal    |   Milestone:  Sysadmin Contract 2024-I
Component:  SysAdmin  |  Resolution:
 Keywords:            |
----------------------+---------------------------------------
Comment (by robe):

 Going to close this out as nextcloud speed seems fine at the moment.
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2905#comment:2>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From trac_osgeo at osgeo.org  Sun May 12 00:03:20 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Sun, 12 May 2024 07:03:20 -0000
Subject: [OSGeo] #2905: Investigate slowness of nextcloud.osgeo.org and fix
In-Reply-To: <034.95301470d545a04f4bbe57d9b38c5791@osgeo.org>
References: <034.95301470d545a04f4bbe57d9b38c5791@osgeo.org>
Message-ID: <049.15781f90afd1891825104aa464e406e9@osgeo.org>

#2905: Investigate slowness of nextcloud.osgeo.org and fix
----------------------+---------------------------------------
 Reporter:  robe      |       Owner:  sac@?
     Type:  task      |      Status:  closed
 Priority:  normal    |   Milestone:  Sysadmin Contract 2024-I
Component:  SysAdmin  |  Resolution:  fixed
 Keywords:            |
----------------------+---------------------------------------
Changes (by robe):

 * status:  new => closed
 * resolution:   => fixed

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2905#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From trac_osgeo at osgeo.org  Sun May 12 13:55:43 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Sun, 12 May 2024 20:55:43 -0000
Subject: [OSGeo] #2275: IP whitelisting of new plugins.qgis.org server
In-Reply-To: <043.b48d94d6d5d048037673fabe586682e8@osgeo.org>
References: <043.b48d94d6d5d048037673fabe586682e8@osgeo.org>
Message-ID: <058.cdaff9514c1c591a3e2d6a2532f0ae0e@osgeo.org>

#2275: IP whitelisting of new plugins.qgis.org server
---------------------------+---------------------
 Reporter:  rduivenvoorde  |       Owner:  sac@?
     Type:  task           |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  SysAdmin       |  Resolution:  fixed
 Keywords:                 |
---------------------------+---------------------
Comment (by jef):

 rule removed - superceeded by #3177
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2275#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From trac_osgeo at osgeo.org  Tue May 14 06:56:53 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Tue, 14 May 2024 13:56:53 -0000
Subject: [OSGeo] #3068: MX record for discourse.osgeo.org is not
 propagating properly
In-Reply-To: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
References: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
Message-ID: <049.148368fcc3aa88d6eed11419424b2a5a@osgeo.org>

#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
 Reporter:  strk          |       Owner:  sac@?
     Type:  task          |      Status:  new
 Priority:  normal        |   Milestone:  Unplanned
Component:  SysAdmin/DNS  |  Resolution:
 Keywords:  discourse     |
--------------------------+------------------------
Comment (by strk):

 My (new) server and my desktop client are still not getting the MX record
 for discourse.osgeo.org as of today. Was the zone version updated ?
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3068#comment:2>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From trac_osgeo at osgeo.org  Tue May 14 06:57:05 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Tue, 14 May 2024 13:57:05 -0000
Subject: [OSGeo] #3068: MX record for discourse.osgeo.org is not
 propagating properly
In-Reply-To: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
References: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
Message-ID: <049.22d8db2df4009b30464d9bdfece0b555@osgeo.org>

#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
 Reporter:  strk          |       Owner:  sac@?
     Type:  task          |      Status:  new
 Priority:  normal        |   Milestone:  Unplanned
Component:  SysAdmin/DNS  |  Resolution:
 Keywords:  discourse     |
--------------------------+------------------------
Comment (by strk):

 It would be nice to put the DNS zone under Ansible too...
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3068#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From trac_osgeo at osgeo.org  Tue May 14 06:58:56 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Tue, 14 May 2024 13:58:56 -0000
Subject: [OSGeo] #3068: MX record for discourse.osgeo.org is not
 propagating properly
In-Reply-To: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
References: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
Message-ID: <049.f68970443b3c924b2cdbf17f372bcc8d@osgeo.org>

#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
 Reporter:  strk          |       Owner:  sac@?
     Type:  task          |      Status:  new
 Priority:  normal        |   Milestone:  Unplanned
Component:  SysAdmin/DNS  |  Resolution:
 Keywords:  discourse     |
--------------------------+------------------------
Comment (by strk):

 Even osgeo7 resolver isn't getting the MX record at the moment:
 {{{
 tech_dev at osgeo7:~$ nslookup
 > set type=mx
 > discourse.osgeo.org
 Server:         127.0.0.53
 Address:        127.0.0.53#53

 Non-authoritative answer:
 discourse.osgeo.org     canonical name = web.osgeo9.osgeo.org.

 Authoritative answers can be found from:
 >
 }}}
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3068#comment:4>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From trac_osgeo at osgeo.org  Tue May 14 07:28:55 2024
From: trac_osgeo at osgeo.org (OSGeo)
Date: Tue, 14 May 2024 14:28:55 -0000
Subject: [OSGeo] #3068: MX record for discourse.osgeo.org is not
 propagating properly
In-Reply-To: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
References: <034.769a82bc949277bf7286a2eddd8da342@osgeo.org>
Message-ID: <049.3495001cebeb2b6d86c012beed00fccb@osgeo.org>

#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
 Reporter:  strk          |       Owner:  sac@?
     Type:  task          |      Status:  new
 Priority:  normal        |   Milestone:  Unplanned
Component:  SysAdmin/DNS  |  Resolution:
 Keywords:  discourse     |
--------------------------+------------------------
Comment (by strk):

 I see no output from these commands:
 {{{
 dig @213.186.33.99 -t mx discourse.osgeo.org| grep 'MX' | grep -v '^;'
 dig @2001:41d0:3:163::1 -t mx discourse.osgeo.org| grep 'MX' | grep -v
 '^;'
 }}}

 Both addresses are from ovh.net
 The ehinet addresses wont' respond from the outside
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3068#comment:5>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.

From maplabs at light42.com  Tue May 14 12:34:46 2024
From: maplabs at light42.com (Brian M Hamlin)
Date: Tue, 14 May 2024 12:34:46 -0700
Subject: mailing list - was v17 kickoff
In-Reply-To: <7866017b-4140-4b8f-838c-d98d3cc85e32@gmail.com>
References: <7866017b-4140-4b8f-838c-d98d3cc85e32@gmail.com>
Message-ID: <c03f1a22-2235-b4e6-aade-e2445cfb507d@light42.com>

Hello and best wishes from Berkeley, California

 ? very recently Angelos sent an email to #osgeolive email list with an 
announcement for the v17 kickoff -- great news

 ? However, immediately after that kickoff email, SPAM EMAIL returned to 
the email list.

 ? Here in Berkeley, I delete spam messages from the mailing list as 
needed. In the quiet months since the last #osgeolive, there is almost 
zero spam.? Yet the day after the kickoff email and three replies, now 
there are dozens of new SPAM EMAIL messages coming in ?!

 ? SPAM EMAIL activity appears to be directly linked to the mailing list 
activity -- no emails, no spam / new emails, new spam.

 ? The kind of SPAM EMAIL on the mailing list is exactly the low-grade 
commercial kind in English, that someone else gets paid to send. Someone 
or something, has setup a responder to the email list to add commercial 
content SPAM EMAIL to this list when there is activity. The SPAM EMAIL 
that has been coming for almost a year now, is similar in format and 
content.

 ? The #osgeolive email list is a service to the public and "civil 
society".. it is a communications method between people that are far 
away and not linked otherwise.? This spam activity inserts itself on top 
of a healthy, low cost and efficient link, like an infection.? Worse, no 
one gets paid to build world class, excellent technology on #osgeolive 
but someone or some thing invades the list for tiny amounts of money, 
distracting and annoying those that are doing works for others and the 
environmental world.

[0] https://lists.osgeo.org/mailman/listinfo/osgeolive

 ? Perhaps it is time to start a new email list, and notify the 210 
subscribers with a personal contact, to rebuild trust and put this EMAIL 
SPAM in the past. Other suggestions welcome

 ? best regards?? --Brian M Hamlin??? /? MAPLABS? /? Berkeley, California



From jody.garnett at gmail.com  Tue May 14 14:24:28 2024
From: jody.garnett at gmail.com (Jody Garnett)
Date: Tue, 14 May 2024 14:24:28 -0700
Subject: mailing list - was v17 kickoff
In-Reply-To: <c03f1a22-2235-b4e6-aade-e2445cfb507d@light42.com>
References: <7866017b-4140-4b8f-838c-d98d3cc85e32@gmail.com>
 <c03f1a22-2235-b4e6-aade-e2445cfb507d@light42.com>
Message-ID: <CAOhbgAk3sPiy2+B6rusD_8KG_NdtR845wod_nk6OcObrMuD59A@mail.gmail.com>

Consider as an opportunity to move to discourse (rather than create a new
email list?)

--
Jody Garnett


On Tue, May 14, 2024 at 1:09?PM Brian M Hamlin <maplabs at light42.com> wrote:

> Hello and best wishes from Berkeley, California
>
>    very recently Angelos sent an email to #osgeolive email list with an
> announcement for the v17 kickoff -- great news
>
>    However, immediately after that kickoff email, SPAM EMAIL returned to
> the email list.
>
>    Here in Berkeley, I delete spam messages from the mailing list as
> needed. In the quiet months since the last #osgeolive, there is almost
> zero spam.  Yet the day after the kickoff email and three replies, now
> there are dozens of new SPAM EMAIL messages coming in ?!
>
>    SPAM EMAIL activity appears to be directly linked to the mailing list
> activity -- no emails, no spam / new emails, new spam.
>
>    The kind of SPAM EMAIL on the mailing list is exactly the low-grade
> commercial kind in English, that someone else gets paid to send. Someone
> or something, has setup a responder to the email list to add commercial
> content SPAM EMAIL to this list when there is activity. The SPAM EMAIL
> that has been coming for almost a year now, is similar in format and
> content.
>
>    The #osgeolive email list is a service to the public and "civil
> society".. it is a communications method between people that are far
> away and not linked otherwise.  This spam activity inserts itself on top
> of a healthy, low cost and efficient link, like an infection.  Worse, no
> one gets paid to build world class, excellent technology on #osgeolive
> but someone or some thing invades the list for tiny amounts of money,
> distracting and annoying those that are doing works for others and the
> environmental world.
>
> [0] https://lists.osgeo.org/mailman/listinfo/osgeolive
>
>    Perhaps it is time to start a new email list, and notify the 210
> subscribers with a personal contact, to rebuild trust and put this EMAIL
> SPAM in the past. Other suggestions welcome
>
>    best regards   --Brian M Hamlin    /  MAPLABS  /  Berkeley, California
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20240514/6fb524d4/attachment.htm>

From strk at kbt.io  Wed May 15 08:15:16 2024
From: strk at kbt.io (Sandro Santilli)
Date: Wed, 15 May 2024 17:15:16 +0200
Subject: mailing list - was v17 kickoff
In-Reply-To: <c03f1a22-2235-b4e6-aade-e2445cfb507d@light42.com>
References: <7866017b-4140-4b8f-838c-d98d3cc85e32@gmail.com>
 <c03f1a22-2235-b4e6-aade-e2445cfb507d@light42.com>
Message-ID: <ZkTRhEK5PxMpOoAs@c19>

On Tue, May 14, 2024 at 12:34:46PM -0700, Brian M Hamlin wrote:

> ? Perhaps it is time to start a new email list, and notify the 210
> subscribers with a personal contact, to rebuild trust and put this EMAIL
> SPAM in the past. Other suggestions welcome

Installing spamassassin on the osgeo mail server would possibly help
a little bit. Worth a ticket.

--strk;

  Libre GIS consultant/developer
  https://strk.kbt.io/services.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20240515/8bb91877/attachment.sig>