[00:34:39] 6Team-Practices, 6Community-Advocacy, 6Developer-Relations, 3DevRel-September-2015: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#1640034 (10Ironholds) >>! In T90908#1639480, @Qgil wrote: > What about recycling this task... [06:05:08] 6Team-Practices, 6Community-Advocacy, 6Developer-Relations, 3DevRel-September-2015: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#1640421 (10Qgil) Sure, in that case the session at the Summit would be a live discussion b... [15:49:14] 6Team-Practices, 6Developer-Relations, 3DevRel-September-2015: What to do with old open patches for unmaintained/inactive repositories when not even the uploader responds - https://phabricator.wikimedia.org/T102920#1641798 (10Aklapper) If I get the last comment right, that would mean for this task's summary:... [16:58:50] 6Team-Practices, 6RelEng-Admin: Do 90 day review of post-offsite actions in early August '15 - https://phabricator.wikimedia.org/T103917#1642050 (10demon) 5Open>3Resolved In May 2015, the Release Engineering team had our offsite in Annecy, France, just prior to the Lyon hackathon. The four days were spent... [17:01:51] 6Team-Practices, 6RelEng-Admin: Do 90 day review of post-offsite actions in early August '15 - https://phabricator.wikimedia.org/T103917#1642058 (10hashar) @demon summary above has been discussed the #together private mailing list. [17:08:48] 6Team-Practices, 6RelEng-Admin: Do 90 day review of post-offsite actions in early August '15 - https://phabricator.wikimedia.org/T103917#1642075 (10demon) >>! In T103917#1642050, @demon wrote: > Re-check with the outside stakeholders of Release Engineering in one year. The problems identified from the outside... [18:25:17] ggellerman: jaufrecht meeple27 dstrine any of you wanna grab a salad together, ahead of our strategy marathon? [18:25:25] 6Team-Practices, 6Developer-Relations, 3DevRel-September-2015: Goal: Organize a Gerrit Cleanup Day on September 23, 2015 - https://phabricator.wikimedia.org/T88531#1642503 (10Aklapper) [18:25:40] mbinder: That does sound appealing [18:25:57] before the lunch rush? [18:26:30] sure [18:26:32] where? [18:26:44] I'm at home today [18:26:54] okay, let's meet at david's kitchen and see what's in his fridge [18:27:17] sounds good [18:27:32] not much lol [18:27:32] I'm sitting near Kevin, who is at his desk. somebody come and provide motive energy, please [18:27:47] I have a lot of dusty packaged food [18:28:08] dust can have good protein [18:28:16] (I"m sure I read that somewhere...probably wp) [18:31:42] https://www.irccloud.com/pastebin/0lXW16To [19:35:55] meeple27: reminder for article link [19:55:54] 6Team-Practices, 6Developer-Relations, 3DevRel-September-2015: What to do with old open patches for unmaintained/inactive repositories when not even the uploader responds - https://phabricator.wikimedia.org/T102920#1642837 (10Nemo_bis) It's impossible to assess that without a definition of INACTIVE. [21:00:38] 6Team-Practices, 10Phabricator-Upstream: Phabricator should allow multiple assignees - https://phabricator.wikimedia.org/T112679#1643038 (10Qgil) You can add as many people as you want as subscribers, or in the description of the task. Still, having one and only one owner of the task at a time makes sense, and... [21:19:13] 6Team-Practices, 6Developer-Relations, 3DevRel-September-2015: What to do with old open patches for unmaintained/inactive repositories when not even the uploader responds - https://phabricator.wikimedia.org/T102920#1643105 (10hashar) >>! In T102920#1641798, @Aklapper wrote: > If I get the last comment right,... [21:21:14] 6Team-Practices, 6Developer-Relations, 3DevRel-September-2015: What to do with old open patches for unmaintained/inactive repositories when not even the uploader responds - https://phabricator.wikimedia.org/T102920#1643113 (10hashar) >>! In T102920#1642837, @Nemo_bis wrote: > It's impossible to assess that w...