On 14/10/2020 16.48, Matt Sicker wrote:
Can any of this DNS info be driven by LDAP? I'm no sysadmin, but
aren't they both distributed directory protocols essentially? I've
seen DNS-related schemas for LDAP which makes me think they can
integrate, but again, I'm no sysadmin. :)
LDAP records for projects are generally wiped when a project retires.
IF someone wanted to put some work into whimsy to maybe punt it to,
let's say ou=retired,ou=groups,dc=apache,dc=org instead, maybe we could
work with that.
But I'd be perfectly happy with the text file I have now :)
On Wed, 14 Oct 2020 at 04:13, sebb <seb...@gmail.com> wrote:
[Try again with corrected Whimsy email]
Seems to me it might be better for Whimsy to update the following file:
https://svn.apache.org/repos/private/committers/board/committee-info.yaml
Whimsy already updates this when PMCs are created.
S.
On Wed, 14 Oct 2020 at 07:49, Daniel Gruno <humbed...@apache.org> wrote:
Hi whimsy folks and secretary,
While sorting out some automated sorting of our DNS entries, I got to
working on a list of retired projects out of necessity, as it occurred
to me we don't do a very good job of keeping track of it after the board
has retired a project. The file (infra auth required) is at
https://svn.apache.org/repos/infra/infrastructure/trunk/tlpreq/retired.txt
and has a simple "project # comment" syntax.
Would it be possible for whimsy/secretary to add new entries as they
happen? This would not only help us keep track of DNS entries, but also
help infra assess which resources belong to retired projects and need
dismantling.
WDYT?
There is no rush on this, we can manually add new entries, but it would
be a nice addition if we could automate it during board meetings.
With regards,
Daniel on behalf of ASF Infra.
