Last modified: 2013-09-16 15:21:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55873, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53873 - Create 'teampractices' mailing list
Create 'teampractices' mailing list
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-06 22:55 UTC by Arthur Richards
Modified: 2013-09-16 15:21 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Arthur Richards 2013-09-06 22:55:29 UTC
I would like to create a 'process-support' mailing list to provide a place for individuals and teams to get support from one another in regards to their development processes. This is in particular aimed at 'agile' teams at the WMF to share successes/failures/difficulties and receive support, but is intended to be generic and open to anyone seeking support in improving their team's processes. This list should be open to anyone to join and post, and can serve as an archive of the evolution of the various software engineering practices used at the WMF.
Comment 1 Erik Moeller 2013-09-11 20:30:43 UTC
Since process can refer to a lot of things, how about "teampractices@lists.wikimedia.org" as a more descriptive name? Would that work for you?
Comment 2 Arthur Richards 2013-09-11 21:30:59 UTC
Works for me!
Comment 3 Erik Moeller 2013-09-12 07:19:34 UTC
Done! Arthur, I've made you owner for now; you should have received the list owner password. I've also taken the liberty to subscribe you to the list.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links