[wp-meta] [Making WordPress.org] #49: Setup #wordpress-meta

Making WordPress.org noreply at wordpress.org
Wed Jul 31 00:40:09 UTC 2013

#49: Setup #wordpress-meta
  Reporter:  iandunn  |      Owner:
      Type:  task     |     Status:  new
  Priority:  normal   |  Component:  General
Resolution:           |   Keywords:

Comment (by iandunn):

 Replying to [comment:2 samuelsidler]:
 > The fewer IRC channels we have to follow, the better off we are.

 It actually seems simpler to me to have a separate channel, because it
 avoids having a lot of unrelated noise. It's much easier to monitor things
 if they're not mixed together. Especially if the existing channel we'd use
 is #wordpress-dev, which is already pretty active. I think it'd be hard to
 keep the Meta stuff straight from the  Core stuff, unless I read every
 single message or am pinged directly.

 That could just be a preference based on my personal workflow, though, so
 I'm open to using an existing channel if others prefer it.

 Replying to [comment:3 nacin]:
 > In practice, I'm not sure there is a significant amount (outside of P2
 and meta.trac) to discuss.

 I can see new volunteers having a lot of questions about workflow,
 philosophy, history, etc that aren't directly related to a specific
 ticket, but I could be wrong. We can always wait and see if there's a
 compelling need before putting in the work to setup the bot, etc; and then
 use #wordpress-dev in the meantime for anything that doesn't fit on Trac
 and the p2.

Ticket URL: <http://meta.trac.wordpress.org/ticket/49#comment:4>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software

More information about the wp-meta mailing list