Re: [teampractices] Code review before writing new code

On 06/30/2015 05:34 PM, Antoine Musso wrote: Le 10/06/2015 10:41, Gilles Dubuc a écrit : Maybe that specific way of seeing things (am I in review debt?) could be supported by software. I.e. a prominent indicator of whether or not you've pushed more changesets than you've reviewed. It might be s

Re: [teampractices] Code review before writing new code

On 06/11/2015 09:40 AM, Quim Gil wrote: We had this before, but it caused two problems: * keeping https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects up to date and in sync with korma was not easy This is a solvable problem. For example, it could be added to https://www.media

Re: [teampractices] Code review before writing new code

On 06/08/2015 06:35 AM, Antoine Musso wrote: Le 08/06/2015 10:51, Quim Gil a écrit : Er, sorry, the previous email just left my mailbox too fast. The proposal below has a related Phabricator task: https://phabricator.wikimedia.org/T101686 https://office.wikimedia.org/wiki/Health_check_survey_r

Re: [teampractices] Code review

On 06/08/2015 04:23 AM, Quim Gil wrote: Thank you, very useful. I'm happy to see that our problem with code review keeps becoming more evident, if only as a step to finally doing something about it. http://korma.wmflabs.org/browser/gerrit_review_queue.html shows that our backlog of patches waiti

Re: [teampractices] Why are WMF Department/team pages on mediawiki.org?

On 05/26/2015 12:44 PM, Kevin Smith wrote: This could just be my inexperience here. To me, maps and wikidata are clearly wikimedia software, but do not seem to be mediawiki software. They are "related" to mediawiki, but I'm not sure what that should mean. It sounds like you define mediawiki as be

Re: [teampractices] Why are WMF Department/team pages on mediawiki.org?

On 05/22/2015 06:12 PM, Kevin Smith wrote: Thanks for the context! S: Yes, my first sentence was meant to be TPG-specific. I lost that in editing right before I hit "send". Restricted access on mwfoundation is a pretty good argument for not going there. Having "one" place to go sounds good in

Re: [teampractices] Why are WMF Department/team pages on mediawiki.org?

On 05/22/2015 04:36 PM, Greg Grossmeier wrote: For me, mostly due to keeping things in one[0] place. It's easier mentally to keep team pages and project pages (where project pages are more sensibly on mw.org) together since our teams are heavily technical/based on MediaWiki development. Yes, I

Re: [teampractices] ANYONE: Phab, burnup charts, and double-counting

On 04/29/2015 11:26 AM, Kevin Smith wrote: I only started thinking about this an hour ago, but so far I am perplexed as to how to work around this. For what it's worth, solutions could include technical features, or socially-enforced conventions. The latter is probably best (or at least fastest

Re: [teampractices] "Roadmap" project in Phabricator

On 02/20/2015 02:16 PM, James Forrester wrote: * As a Wikimedia user who care​s about editing tools, I no longer have somewhere to keep track of bigger planned changes to editing things, and have to pick them out of other changes to e.g. Apps or Search which I don't care about. It

Re: [teampractices] Phabricator for monthly and quarterly reports

On 02/18/2015 11:49 AM, Guillaume Paumier wrote: Hi, Le mardi 3 février 2015, 20:29:09 Quim Gil a écrit : On Tue, Feb 3, 2015 at 6:04 PM, Amir E. Aharoni < amir.ahar...@mail.huji.ac.il> wrote: Continuing the theme of my previous post about using Phabricator for roadmap planning - how can Pha

Re: [teampractices] Duplication of information in Phabricator workboards?

On 02/10/2015 03:03 PM, Arthur Richards wrote: One of the main problems I've encountered with Phabricator workboards is the duplication of information. Most workboard have the following columns- 1. Backlog 2. In Dev 3. Needs Review 4. Done If we follow the conventions that have been sug

Re: [teampractices] Phabricator for long-term planning and roadmaps

On 02/03/2015 08:50 AM, Amir E. Aharoni wrote: Is there any way to get Phabricator to auto-generate or synchronize such roadmaps? Some teams are using Epics (https://phabricator.wikimedia.org/tag/epic/), essentially large-scale tracking cards. However, I still don't think we can expect the

Re: [teampractices] Guideline for tasks assigned

On 12/15/2014 03:24 AM, Quim Gil wrote: Can we agree on this basic guideline, at least at a WMF Engineering & Product level? "You should have a task assigned to yourself only when you are prepared to work on it." https://www.mediawiki.org/wiki/Phabricator/Project_management#Assigning_tasks Ye

Re: [teampractices] Mingle -> Phabricator migration

On 12/08/2014 01:42 PM, Gilles Dubuc wrote: Here's a script I hacked together to migrate my team's mingle cards to phabricator: https://phabricator.wikimedia.org/P129 Can you add a license? It would also be nice to have it in a repo, but that can be done by anyone once there's a license. Th

Re: [teampractices] Triaging bugs and managing task backlog in Phabricator

On 12/03/2014 02:39 AM, Subramanya Sastry wrote: There are redundancies here which is a good thing. For example, tags could clearly be used for setting custom priorities (not that it is a great use case). There are already many examples of tags besides components, including https://phabricator

Re: [teampractices] Team membership, what does it mean.

On 12/02/2014 11:49 PM, Jeremy Baron wrote: On Wed, Dec 3, 2014 at 4:28 AM, Matthew Flaschen wrote: On 12/02/2014 05:32 PM, Jeremy Baron wrote: I think we should generally prohibit projects from containing tasks if those projects are used as ACLs or limit membership for any other reason

Re: [teampractices] Team membership, what does it mean.

On 12/02/2014 11:40 PM, Gabriel Wicke wrote: On Tue, Dec 2, 2014 at 8:28 PM, Matthew Flaschen mailto:mflasc...@wikimedia.org>> wrote: Does Phabricator actually have default CC? I would guess you could accomplish it through Herald, but I don't know another way. Watching a

Re: [teampractices] Triaging bugs and managing task backlog in Phabricator

On 12/02/2014 04:32 PM, S Page wrote: The default column in every workboard is "Backlog". With this approach I think it makes sense to rename that column in the team's project board to something like "Needs team triage" or "Consider for next sprint". Hmm, this is an interesting question (whethe

Re: [teampractices] Triaging bugs and managing task backlog in Phabricator

On 12/02/2014 04:49 PM, Bryan Davis wrote: We are using these columns today: * To Do * In Dev/Progress * Needs Review/Feedback * Done * Archive (hidden) Rather than create a new board for each iteration/sprint/whatever we are using the archive column as a storage area for things that have been c

Re: [teampractices] Team membership, what does it mean.

On 12/02/2014 05:32 PM, Jeremy Baron wrote: I think we should generally prohibit projects from containing tasks if those projects are used as ACLs or limit membership for any other reason. What would the ACL do if there are no tasks involved? Any brand new contributor with no special privileg

Re: [teampractices] Trellos & Minglers, what is blocking your migration to Phabricator?

On 11/13/2014 12:31 PM, Quim Gil wrote: On Thu, Nov 13, 2014 at 4:22 PM, Arthur Richards mailto:aricha...@wikimedia.org>> wrote: The lack of this feature in Phabricator may seem like just a minor inconvenience to some. But I believe it's been an integral part of teams feeling like

Re: [teampractices] Trellos & Minglers, what is blocking your migration to Phabricator?

On 10/23/2014 04:18 AM, Jared Zimmerman wrote: multi-user simultaneous editing. I don't think Trello actually allows simultaneous editing of the same field (e.g. multiple people editing the description together Etherpad style). If people are editing different fields, than Phabricator should

Re: [teampractices] mingle seats

On 10/20/2014 02:56 PM, Arthur Richards wrote: PS since the scrum of scrums dependency wall is managed in Mingle, I am hesitant to kill accounts for any active WMF engineers. We should start thinking about how we can implement this in Phabricator or on-wiki instead. Matt Flaschen __

Re: [teampractices] Burndown charts progress in Phabricatotr (was Fwd: [Wikitech-l] Phabricator update)

On 10/02/2014 01:31 PM, Greg Grossmeier wrote: I'm really excited about this, Quim, thanks to Christopher and the WMDE team for taking this on! Agreed, this should be a great project. Thanks! Matt Flaschen ___ teampractices mailing list teampractic

Re: [teampractices] teammate onboarding/offboarding tool

On 08/06/2014 12:00 PM, Sumana Harihareswara wrote: https://github.com/heroku/starboard "Starboard is a tool which creates Trello boards for tracking the various tasks necessary when onboarding, offboarding, or crossboarding employees. We use Trello extensively within Heroku, and Starboard makes

Re: [teampractices] remote pair programming tools

On 07/10/2014 09:56 AM, Sumana Harihareswara wrote: Is there a set of best practices/tools, ideally cross-platform and open source, that we could use to help Wikimedia developers remotely pair program? What are folks currently using? Some resources: http://www.pairprogramwith.me/ http://opensou

Re: [teampractices] How spotify builds products

On 06/11/2014 02:03 PM, Arthur Richards wrote: I am continually impressed with Spotify - not just as a product in and of itself, but particularly by the processes by which they build it. I stumbled upon a nice (if potentially a little old) writeup of their product process: http://blog.crisp.se/2

Re: [teampractices] Impressions about the switch from Trello to Phabricator

On 05/13/2014 08:35 PM, Steven Walling wrote: * /Task assignment:/ in Trello tasks can't actually be assigned. You can only have card members and subscribers. We work around this by talking about it, but it is nice when a task has a clear assignment, especially when we need to work

Re: [teampractices] Impressions about the switch from Trello to Phabricator

On 05/15/2014 10:14 AM, Quim Gil wrote: How are sprints organized in Trello? Do you have an automatic process or do you need to create sprints manually? Growth uses a single board (https://trello.com/b/FdtPTV2y/growth) with Backlog (everything not archived or in another column), Current Sprint

Re: [teampractices] Impressions about the switch from Trello to Phabricator

On 05/13/2014 09:07 PM, Kevin Leduc wrote: Another Phabricator weakness relative to Trello my team noticed while sprint planning is the lack of real-time collaboration. My team could not see the description I was typing into a task (ala eatherpad) and had to wait for me to save my changes. They

Re: [teampractices] Mingle

On 04/18/2014 06:05 PM, Quim Gil wrote: As Steven say, each card (task) can have different permissions, Having task-specific permissions does not really seem like a feature to me, so far. It seems like doing it by project should be sufficient. Matt Flaschen _

Re: [teampractices] Mobile web team experimenting with Trello - experiences with migration?

On 04/08/2014 01:36 PM, Arthur Richards wrote: 2) I've seen how the Mobile apps team manages their boards and a bit of how the Flow team manages theirs - but I'm not sure either approach is 100% right for us. How can we set up boards in such a way to make it easy to: a) manage an overall/project

Re: [teampractices] Apache Allura

On 04/02/2014 02:20 PM, Quim Gil wrote: On Wednesday, April 2, 2014, Toby Negrin mailto:tneg...@wikimedia.org>> wrote: https://forge-allura.apache.org/p/allura/wiki/Home/ I haven't heard this mentioned in these discussions but it seems like a viable solution. They provided a

Re: [teampractices] Apache Allura

On 04/02/2014 02:20 PM, Quim Gil wrote: On Wednesday, April 2, 2014, Toby Negrin mailto:tneg...@wikimedia.org>> wrote: https://forge-allura.apache.org/p/allura/wiki/Home/ I haven't heard this mentioned in these discussions but it seems like a viable solution. They provided a

Re: [teampractices] Bugzilla migration Re: Project management tools review: Regressions/tradeoffs; migration

On 03/26/2014 04:38 PM, Steven Walling wrote: I'd also like to suggest a somewhat radical alternative, which is not automatically importing any Bugzilla items in to Phabricator. Let me explain the steps here and what I think the advantages would be: 1. We set up Phabricator. All new issues shou

Re: [teampractices] Bugzilla migration Re: Project management tools review: Regressions/tradeoffs; migration

On 03/28/2014 05:31 PM, Luis Villa wrote: Or to try to put it another way: it is common that old bugs are actively harmful to developers by making the BTS less useful, particularly in large, old projects, where change in the code makes it hard to reproduce old bugs, or likely that they are no lon

Re: [teampractices] Bugzilla migration Re: Project management tools review: Regressions/tradeoffs; migration

On 03/26/2014 09:46 PM, Quim Gil wrote: 4. Projects with history in Bugzilla are created, old bugs are dealt in Bugzilla, new ones are dealt in the new tool. Ouch, it can get messy. 5. Other scenarios? I'm not sure if this is what you mean, so to be explicit, 4 could also be done at a global l

Re: [teampractices] Bugzilla migration Re: Project management tools review: Regressions/tradeoffs; migration

On 03/26/2014 09:58 PM, Steven Walling wrote: As for history: I'm not sure there is value in migrating all resolved bug history, since the task status of Phabricator does not exactly match Bugzilla anyway, and contains a lot of irrelevant information to strip like gerrit patch links, keywords, an

Re: [teampractices] Project management tools review: Regressions/tradeoffs; migration

On 03/25/2014 12:14 PM, Andre Klapper wrote: User/reporter experience is to further discuss if we continue to want users to be able to report issues directly into the tool. Yes, I think this is required. That's the best way to get teams aware of issues (not saying I expect all users use bugtr

Re: [teampractices] Project management tools review: Regressions/tradeoffs; migration

On 03/25/2014 06:31 PM, Quim Gil wrote: What are the options when it comes to permissions to edit tasks in Phabricator? This relates to the discussion about who decides the prioritization of a task. Yes, we should think about whether this should be limited to project team members (something li

Re: [teampractices] Project management tools review: Regressions/tradeoffs; migration

On 03/26/2014 01:36 AM, sankarshan wrote: Do you use keywords on the current instance of the Bugzilla? If so, how do you utilize keywords? Do you also have a definition of what each keywords signifies (eg. something similar to )? I think this is

Re: [teampractices] Project management tools review: Regressions/tradeoffs; migration

On 03/25/2014 06:58 PM, Shahyar Ghobadpour wrote: Phabricator supports anonymous user access. The problem is in fact that the login page becomes the "home page" when you aren't logged in. Case in point, the Fedora Project using Phabricator with a direct link to maniphest: https://phab.qadevel.clo

Re: [teampractices] Phabricator's Kanban tool

On 03/21/2014 11:40 PM, S Page wrote: * This edit window has an Upload file icon, tells you to drag and drop images... doesn't work in Firefox. Does for me. You're supposed to drag from your local file browser (E.g. Konqueror on Linux, presumably Finder on OS X and Explorer on Windows,

Re: [teampractices] Phabricator's Kanban tool

On 03/12/2014 04:37 PM, Steven Walling wrote: This looks pretty darn good indeed. :) Indeed, the proposed new interface (screenshot linked from Greg's email) looks really good, but even the one we have seems pretty solid, and has some wins above Trello (e.g. story points, and (I think) being

Re: [teampractices] Volunteer contributors (WAS: teampractices Digest, Vol 7, Issue 2)

On 03/03/2014 10:36 PM, Benjamin Sternthal wrote: Is this something contributors could be involved with in some aspect/capacity (I am interested) or do you think this would be staff only? You're certainly very welcome to participate in teampractices. Exactly how the community will work with th

Re: [teampractices] [Engineering] Feedback requested on proposal for creation of Agile Specialist Group

On 03/04/2014 09:19 PM, Whatamidoing (WMF)/Sherry Snyder wrote: They're saying, "Stop poking me with a stick twice a week". Agile proponents are saying, "Well, the only alternative is that we stab you with a big knife twice a year". They are very loudly in favor of "don't poke me at all". If

Re: [teampractices] [Engineering] Feedback requested on proposal for creation of Agile Specialist Group

On 03/03/2014 08:51 PM, Oliver Keyes wrote: > So is the answer advisors, or just hiring engineers for the teams that need them with a focus in the JDs and interview processes on people with scrum experience willing to take up being a scrum master as a primary duty? The latter (hiring a combinat

Re: [teampractices] [Engineering] Feedback requested on proposal for creation of Agile Specialist Group

Forgot to reply all. Matt Flaschen On 03/03/2014 11:00 PM, Whatamidoing (WMF)/Sherry Snyder wrote: (2) Did you all know that a significant proportion of our user community is unhappy with the way that Agile affects them? "Release early, release often" from the user's perspective means "have h

Re: [teampractices] [Engineering] Feedback requested on proposal for creation of Agile Specialist Group

On 03/03/2014 11:00 PM, Whatamidoing (WMF)/Sherry Snyder wrote: (2) Did you all know that a significant proportion of our user community is unhappy with the way that Agile affects them? "Release early, release often" from the user's perspective means "have horribly and/or newly busted stuff scr

Re: [teampractices] Hangout alternative: appear.in

On 02/19/2014 04:17 PM, Sumana Harihareswara wrote: http://appear.in/ is a WebRTC videoconferencing site hosted by Norwegian telcom Telenor. It works absolutely fine for people on Linux. Although the source code isn't openly licensed, appear.in doesn't require that the user ins

Re: [teampractices] Hangout alternative: appear.in

On 02/19/2014 04:17 PM, Sumana Harihareswara wrote: http://appear.in/ is a WebRTC videoconferencing site hosted by Norwegian telcom Telenor. It works absolutely fine for people on Linux. Although the source code isn't openly licensed, appear.in doesn't require that the user ins

Re: [teampractices] pull bugs into Mingle/Trello rather than push

On 01/22/2014 06:07 PM, S Page wrote: The Flow team set up Bingle[1] to pull all new bugs into Mingle. We've found problems with this approach: * It unbalances the sprint to continually see bugs appears in the "left" lane that we keep shunting off. For our team, the Backlog does not affect the

Re: [teampractices] How deviantART organizes its work

On 01/10/2014 05:02 PM, Steven Walling wrote: One of the things that keeps us stuck in IRC land is that it's not just an internal company tool. It's also deeply embedded in the Wikimedia community, even among a segment of "non-technical" community members. We used to actually hold IRC office hour

Re: [teampractices] How deviantART organizes its work

On 01/10/2014 04:34 PM, Shahyar Ghobadpour wrote: Things like Bugzilla and IRC were the de facto standards for open-source communities in the past. I think we're stuck in that mindset, and should be looking at more contemporary solutions. I would really like to discuss this with everyone, and see

Re: [teampractices] Project Management Tools Evaluation

On 01/11/2014 02:50 PM, Benjamin Sternthal wrote: https://blog.mozilla.org/websites/2013/06/28/kanban-web-productions-lessons-learned/ I would be happy to answer any questions you may have. Thanks, that was an interesting and helpful read. One of the issues that Mozilla and Wikimedia share ar

Re: [teampractices] Hangout alternative - chatb.org

On 12/14/2013 10:10 PM, Erik Moeller wrote: Chatb.org is a lightweight WebRTC videoconferencing service - works in an Etherpad-like fashion (share URLs to give access). Fully open source, by Jan Gerber. There's also a WebRTC Etherpad plugin, running at pad.textb.org . Code

Re: [teampractices] Hangout alternative - chatb.org

On 12/14/2013 10:10 PM, Erik Moeller wrote: Chatb.org is a lightweight WebRTC videoconferencing service - works in an Etherpad-like fashion (share URLs to give access). Fully open source, by Jan Gerber. There's also a WebRTC Etherpad plugin, running at pad.textb.org . That

Re: [teampractices] How deviantART organizes its work

On 12/05/2013 03:53 PM, Quim Gil wrote: ING DIRECT also does/did the second part (customer support time, even if hired as a software engineer), though I don't think that long. If we wanted something analogous, it could be bug triage. Customer support is done at https://www.mediawiki.org/wiki/S

Re: [teampractices] Addition to Scrum of Scrums?

On 12/03/2013 03:10 PM, Steven Walling wrote: Within that context, I still wonder if it might make sense for someone to represent strategically relevant projects being worked on in the community. I think that makes sense. For individual patch sets, the best solution is to bug someone who is a

Re: [teampractices] How deviantART organizes its work

On 11/27/2013 11:45 AM, Erik Moeller wrote: "Coming on board · When you make it past the interview stage we’ll do a project together on contract, typically lasting between 3-8 weeks, to see how we work together. When you join full-time, regardless of your position, you’ll do customer support for

Re: [teampractices] How deviantART organizes its work

On 11/27/2013 10:32 AM, Quim Gil wrote: As part of the WMF hiring and onboarding process, we could ask candidates to fix https://www.mediawiki.org/wiki/Annoying_little_bugs This could make sense for serious candidates, if the task is chosen well. But we also like to be able to send the same

Re: [teampractices] Bugzilla Etiquette draft [was: Re: Scrum-y tools based on BZ]

On 11/26/2013 11:25 AM, Andre Klapper wrote: [Resending with a clearer subject line, as I have not received any feedback yet.] On Thu, 2013-10-31 at 18:27 -0700, Erik Moeller wrote: Andre, do we have something like that already? [[mw:Bugzilla]] seems focused on just the technical details -- ma

Re: [teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

On 11/06/2013 11:22 AM, Andre Klapper wrote: I've created a stub at https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette and welcome comments on the Talk/Discussion page. Thanks for starting this. I've commented on the talk page. Matt Flaschen ___

Re: [teampractices] Experimenting with Pivotal Tracker

On 11/14/2013 03:48 PM, Steven Walling wrote: This brings up a big issue with both FOSS and proprietary tools: how do we get our data out and migrate it if necessary? Yes, with proprietary tools we're at the mercy of the vendor. This is particularly an issue with software as a service, since

Re: [teampractices] Experimenting with Pivotal Tracker

On 11/14/2013 12:28 AM, Diederik van Liere wrote: Would it be an idea to make a shortlist of serious alternatives to Trello and Mingle, both open source and proprietary tools, and compare them? For example, I would like to have a look at kanbanery.com but I am sure that ot

Re: [teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

On 11/04/2013 06:17 PM, Andre Klapper wrote: On Thu, 2013-10-31 at 18:27 -0700, Erik Moeller wrote: I agree it should be a policy, and it would be even better to have it written. Andre, do we have something like that already? [[mw:Bugzilla]] seems focused on just the technical details -- maybe

Re: [teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

On 11/01/2013 12:07 AM, Rob Lanphier wrote: It would take an awful lot of empathy for that person to understand where we are coming from. Chances are, their reaction will be "well, that will teach me to ever do that again", and then poof, they're gone. I don't think it's much of a stretch to a

Re: [teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

On 10/31/2013 03:51 PM, Erik Moeller wrote: On Thu, Oct 31, 2013 at 12:47 PM, Matthew Flaschen wrote: I don't think we should get into weird substitutions just because people are edit warring. Is there any good reason to reopen bugs, e.g. commenting functionality being lost? If not I

Re: [teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

On 10/31/2013 03:26 PM, Quim Gil wrote: The solution I found was to agree that "Lowest" is the new "No". I'm not joking. As soon as we get our hands dirty in Bugzilla tech community metrics I will make sure we remove Lowest reports fom the picture, otherwise they distort it completely. I don't

Re: [teampractices] Ron Jeffries "What is Scrum and why does it matter?"

On 10/25/2013 04:48 PM, Chris McMahon wrote: In case you want to hear about the current state of Scrum from one of the people who invented Agile[1], Mr. Jeffries posted this today: http://xprogramming.com/articles/what-is-scrum-and-why-does-it-matter/ Thanks. That was a really concise explan

Re: [teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

On 10/29/2013 01:29 PM, Greg Grossmeier wrote: Regarding the backlog management aspect, it appears that the SUMO team (support.mozilla.org) will be using this work-around: https://sumo-ernest.paas.allizom.org/project/support-mozilla-org/2013-backlog This is cool. I'm glad to see people are wor

Re: [teampractices] [Engineering] notes from this week's scrum of scrums meeting

On 10/15/2013 09:42 PM, Toby Negrin wrote: I'll defer to Arthur on this but I don't have any issues with it. I find that's it quite difficult to know what wiki to use for a particular use case. -Toby I think the general rule should be to make it public unless there's an explicit reason it mus