Opened 11 years ago
Closed 10 years ago
#20885 closed Cleanup/optimization (needsinfo)
Clarify who is in copy for the various mailboxes of the foundation.
Reported by: | loic84 | Owned by: | nobody |
---|---|---|---|
Component: | *.djangoproject.com | Version: | |
Severity: | Normal | Keywords: | foundation |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Would be helpful to clarify:
- what audience receives mail from the "Contact the Django Software Foundation" contact form: https://www.djangoproject.com/contact/foundation/
- what the expected response to submitting a CLA to cla@… is. i.e. expect to receive a confirmation email with x days? I see that the profiles on djangoproject.com have a "CLA" attribute, e.g. https://www.djangoproject.com/~jacob/ but Loic and I don't have this badge and I know we've both submitted CLAs so I'm not sure it's maintained.
Change History (7)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
It's merely a suggestion, I don't imply it's "required".
I think it's important to know whom you are addressing in general; on a variety of matters I personally wouldn't write to such mailbox without knowing its audience. Am I talking to one person or twenty? Am I addressing the board, a representative of it or the whole foundation?
As for cla@, I can see a practical reason, email can get lost, especially with spam filters in mind. I never heard back from my CLA submission, not even an automatic answer, it would be good to know with whom to follow up.
comment:3 by , 11 years ago
Apologies @loic -- I wasn't implying you were demanding something unreasonable. I was trying to establish the purpose of your request.
You make a fair point. The audience for a communication channel should be clear, and it should also be clear what the "next step" or expected response will be -- an automated response, response from someone on the board within 24 hours, and so on.
And, FWIW - we *did* get your CLA; I've just responded via email to confirm.
My concern with this as a ticket (purely from a procedural perspective) is that it's not clear exactly what the action is that would close this ticket. If we need to update the website, then we need a hitlist of all the places that need to be fixed. If it's an update to process docs, then we need pointers at the appropriate sections that need improvement.
Would you be able to compile a list of specifically actionable items on this topic?
comment:4 by , 11 years ago
@russellm, no worries, I'll try to compile a list of actionable items sometime next week.
comment:5 by , 11 years ago
Triage Stage: | Unreviewed → Accepted |
---|---|
Type: | Uncategorized → Cleanup/optimization |
comment:6 by , 11 years ago
Description: | modified (diff) |
---|
comment:7 by , 10 years ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
Loic, if you want to compile the list, please open a ticket on https://github.com/django/djangoproject.com/, thanks.
Can you clarify why exactly this is required? The mailboxes are determined by function; the actual warm bodies at the other end *should* be irrelevant, AFAICT.