Opened 6 years ago

Closed 5 years ago

#13948 closed task (wontfix)

Publish a gpg key for jobs@tpo

Reported by: aagbsn Owned by: Sebastian
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


A potential applicant for our PM position asked me why we don't publish a gpg key for the jobs@ or jobs-pm@ (#13940) alias.

How should we go about doing this?

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by aagbsn

This person suggests:

human: Schleuder is a gpg-enabled mailinglist with remailer-capabilities.

comment:2 Changed 6 years ago by aagbsn

weasel suggests that I simply create a key and share with the rest of the humans pointed to by jobs@tpo
This seems like the least effort approach.

Any opposition to me creating/publishing a key for jobs@tpo ? Or did we want to create a new alias for just this position? See #13940

comment:3 Changed 6 years ago by Sebastian

It creates hassle for those involved, so you shouldn't make such a promise without asking them first. Also, if you did this, the people on the list should actually make a commitment not to leak the contents of the mail by talking about it amongst themselves in unencrypted mails, which we're not well set up to handle since none of our lists are set up for encryption.

comment:4 Changed 6 years ago by arma

This is partly why I want to split it up by role. Otherwise every person who has ever volunteered to help sort or parse or respond for any job has to .. what, get a copy of each key that we make?

comment:5 Changed 6 years ago by aagbsn

Agree that just providing a key and not following through with keeping the content private is misleading. We haven't got a strategy for doing that yet, and our (my) intention is to share the set of candidates with the rest of the community. Is this problematic?

comment:6 Changed 5 years ago by Sebastian

Resolution: wontfix
Status: newclosed

I'm closing this as won't fix. Please reopen if you still want to do this, and have a plan for how. Maybe a plan can emerge from the dev meeting.

Note: See TracTickets for help on using tickets.