[Board] Fwd: [OGC Portal] OGC Compliance Renewal Notification (30 Day Expiration Notice)

[Stephan Meißl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

Jeff once shared the account info with a couple of us. I think I still
have it and I'm going to send it to you Mike.

What is the preferred way to handle this for the future? If there is
need I can help with OGC related stuff but I guess we should agree on a
procedure, don't we?

cu
Stephan


On 08/08/2016 09:21 AM, Jachym Cepicky wrote:
> Well, 
> 
> I do not see any ogc password reminder response in my mailbox too
> 
> J
> 
> ne 7. 8. 2016 v 23:32 odesílatel Michael Smith
> <michael.smith.erdc at gmail.com <mailto:michael.smith.erdc at gmail.com>> n
apsal:
> 
>     Evidently I don't receive the info at osgeo.org <mailto:info at osgeo.or
g>
>     emails. I responded to the site and requested a password reminder
>     but didn't get anything. If anyone as the password for this system
,
>     I can log in and update our OGC registration for another year. 
> 
>     Michael Smith
>     OSGeo Treasurer
>     treasurer at osgeo.org <mailto:treasurer at osgeo.org>
> 
>     On Aug 7, 2016, at 2:06 PM, Jachym Cepicky <jachym.cepicky at gmail.c
om
>     <mailto:jachym.cepicky at gmail.com>> wrote:
> 
>>     Hi OSGeo Board,
>>
>>     this seems to be unknown question for our projects: how do we
>>     renew our products registration by OGC (see at the end of the
>>     thread). Anybody did this before?
>>
>>     Jachym
>>
>>     ---------- Forwarded message ---------
>>     From: Angelos Tzotsos <tzotsos at gmail.com <mailto:tzotsos at gmail.co
m>>
>>     Date: pá 5. 8. 2016 v 13:14
>>     Subject: Re: [OGC Portal] OGC Compliance Renewal Notification (30
>>     Day Expiration Notice)
>>     To: Jachym Cepicky <jachym.cepicky at gmail.com
>>     <mailto:jachym.cepicky at gmail.com>>
>>     Cc: Frank Warmerdam <warmerdam at pobox.com
>>     <mailto:warmerdam at pobox.com>>, Michael Smith
>>     <michael.smith at usace.army.mil <mailto:michael.smith at usace.army.mi
l>>
>>
>>
>>     Hi,
>>
>>     I am not sure how we proceed with this.
>>     In the past all I needed to do it to renew registration for mysel
f.
>>     How do we do that as an org?
>>
>>     On Thu, Aug 4, 2016 at 11:37 AM, Jachym Cepicky
>>     <jachym.cepicky at gmail.com <mailto:jachym.cepicky at gmail.com>> wrot
e:
>>
>>         hi,
>>
>>         I assume, that this mail arrived to propper mail boxes
>>         (Michael, Angelos and Frank), therefore, I'm not going to
>>         forward to any other mailbox
>>
>>         Jachym
>>
>>
>>         On Wed, Aug 3, 2016, 16:06 Barbara Sherman
>>         <bsherman at opengeospatial.org
>>         <mailto:bsherman at opengeospatial.org>> wrote:
>>
>>
>>               Open Source Geospatial Foundation
>>
>>             This is an automated email to inform you that your
>>             OGC-certified compliance license(s) for the following
>>             products are due to be renewed by *September 2nd, 2016*.
>>             After that date your products will no longer be listed as
>>             certified OGC compliant.
>>
>>             If you have already received an earlier notice and have
>>             started the renewal process please ignore this message.
>>
>>             We invite you to easily renew online in our implementatio
n
>>             portal:
>>             http://www.opengeospatial.org/resource/products/registrat
ion
>>
>>             As a reminder, the account used to manage your
>>             certification listings is: *osgeo (info at osgeo.org
>>             <mailto:info at osgeo.org>)*
>>
>>             Link to current public listings: Compliant Only
>>             <http://www.opengeospatial.org/resource/products/complian
t?org_match=Open+Source+Geospatial+Foundation>
>>             | Compliant or Implementing
>>             <http://www.opengeospatial.org/resource/products/?org_mat
ch=Open+Source+Geospatial+Foundation>.
>>
>>             If you have any questions please send an email to
>>             compliance at opengeospatial.org
>>             <mailto:compliance at opengeospatial.org>. The OGC complianc
e
>>             team will be more than glad to help you.
>>
>>             ---------------------------------------------------------
- ---------------
>>
>>
>>                 Current OGC-Compliant Listings
>>
>>
>>                   GDAL/OGR 1.11
>>
>>             Specification(s)	Original Certification
>>             OGC KML 2.2.0
>>             (OGC Reference Implementation)	2014-08-15
>>             OGC KML (Level 2) 2.2.0
>>             (OGC Reference Implementation)	2014-08-15
>>             OGC KML (Level 3) 2.2.0
>>             (OGC Reference Implementation)	2014-08-15
>>
>>
>>                   MapServer 6.2
>>
>>             Specification(s)	Original Certification
>>             OpenGIS Web Map Service (WMS) Implementation Specificatio
n
>>             1.3.0
>>             (OGC Reference Implementation)	2016-01-12
>>
>>
>>                   pycsw 1.10
>>
>>             Specification(s)	Original Certification
>>             OpenGIS Catalogue Service Implementation Specification 2.
0.2
>>             (OGC Reference Implementation)	2016-01-26
>>             OpenGIS Catalogue Service Implementation Specification
>>             [Catalogue Service for the Web] 2.0.2
>>             (OGC Reference Implementation)	2016-01-26

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJXqFBJAAoJEKNQXeNWi+qt8lsP/0nGSLo0R6POe3JBUCX6bGZX
Qu5gmqEKidAZN9Hkh2xumDUKt9NvZ6oyKXX7hWrjxXCodA/4+aWser2fYu+T845f
L73frLu1MURo4cGQBmrJiNY9a1u7E5TccN1JHNXbaTEJaSnmZXLSGYBFivo1HkTx
GKBAJeIRpOQG0SSPVY5RF7irbo/xv5UXgi6wqXuJDB/T93xTACjH0zKHTkOKINW2
Cl4KnrrSpa3n20tZGnKUvGFLi++NusHpMU0vaAiHpcwgWlK41i0O7Cr+8Mw3kCCY
20x2xT6ACzhDPt/zl3XIpqyXM0XoZXWi9ELwyu0oGr748w+a+vOaO8aUiBtk5FRz
sKWCYayg2VDPGlFn6KVI5Fm+4xU6PC0UKNjOgzBmjjpErE5TmEsTX6URQQ+cwIXN
bk+TdYsVxbAFoLI11Rg4jwkOSXMxAe19TXeYUdOX5dhU1SCtoyGvX/D8GLkz6f3F
Z8T7BpYYZqn+FczkRydjZiZJiJjrex+haH1j02odFFg3XOTEFU3G6FPIkngB3q3Y
VGLUQGQWH/pa+lRCY/eV/yB/KnnAm29oqysJ7FOiHFwQTiGEmBzsLZX2gVxhl0zq
WFFZL/F1ez5EemY2CIAetcJ7modlSopx+74dl7bbjT7XbUPgr9ck1erxUvfLN7oU
suaMLFvHzk72w35MadcN
=7hdb
-----END PGP SIGNATURE-----