[wp-meta] [Making WordPress.org] #6909: Internal Messaging Between Users (and how to gate it)

[Making WordPress.org]

#6909: Internal Messaging Between Users (and how to gate it)
-----------------------------+---------------------
 Reporter:  mrfoxtalbot      |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Profiles         |  Resolution:
 Keywords:                   |
-----------------------------+---------------------

Comment (by dd32):

 > There are several scenarios were a (well vetted) internal messaging
 system would facilitate communication among contributors but I want to
 focus on security reports to illustrate why I think we should explore
 this.

 While I get the underlying intention here, I don't think a generalised
 "message someone on WordPress.org" is the appropriate solution for that
 use-case, where a far more targeted "Report an issue in this plugin" form
 with appropriate information gathering and escalation would be more
 valuable.

 This proposal obviously has far more uses than that though, which is
 explored further on, but all comes back to the notion of using email as
 the transport method, something that I'm not entirely a fan of. WordPress
 moved away from using email lists (https://lists.wordpress.org/) quite
 some time ago for good reason, and reimplementing them in this manner
 doesn't seem like something that is worth our time.

 Ultimately, I think the question needs to be asked of `what problem are
 you trying to solve?`, because the answer to that will greatly affect
 implementation.
 If it's "Contact people who have pledged time to a team via 5ftf" then you
 can ask things like "Should they be auto-subscribed to get Make/$team
 posts?" or "Should the Make P2s have a feature to send out a notification
 to everyone who has pledged time?"

 The WordPress plugin team already uses an implementation of this, both
 direct 1:1 through HelpScout and bulk emails to all committers (such as
 the "New version of WordPress is here, here's what you need to know"
 emails). Not all teams have a HelpScout inbox obviously, and the needs are
 very different to other teams.

 If we're considering anti-spam and opt-out, then the solution is probably
 either a) too much or b) poorly thought out, as 1) we can't allow
 anything-spam to be sent from w.org in the first place and 2) we already
 have a LOT of moderation happening via the support forums and we don't
 need to add another location/layer to it.


 tl;dr: What's the actual problem being solved here? What's right for one
 thing might not be for another, we already have communication platforms
 that should probably be used instead - what's actually preventing those
 being used?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6909#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org