you look under the "Share and more" menu on a card,
it shows the card number and short URL, along with other data.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.or
;t show up in the feeds but is still their for documentation.
>
> —prtksxna
>
That seems like a lot of excess work, considering that each time you make a
project you have to manage membership from scratch etc.
--
Steven Walling,
Product Man
r me to save my changes. They also had to refresh their browser tab
> to see changes on the task or workboard
Yeah this is definitely not awesome.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing lis
7;re
immediately editing it. One simple solution might be "double click to edit"
or similar in Phabricator.
- *Attachments*: Trello shows the attached mockups or other materials as
cover images, and overall is slicker. Phabricator does have annotations
thoug
d not be posted
> publicly, or posted with redactions, I honor that.
>
Based on the fact that most teams which are keeping retrospective notes
seem to be publishing them publicly, we've done the same for Growth at
https://www.mediawiki.org/wiki/Growth/Retrospectives
--
Steven Wall
at your take is.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
nd mockups/design assets connected to the patches that
implement them. This is fundamentally how GitHub issues works, and it's so
much more efficient.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing li
On Tue, Apr 15, 2014 at 9:19 AM, Dan Andreescu wrote:
> I had volunteered my team to try it out for one of our projects, but I've
> been hesitating until we have a blessed version.
+1 for Growth.
--
Steven Walling,
Product Manager
https://wikimediafou
l that's
not very well-supported by us or upstream.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
what
I was proposing.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
ead-mode, simply crosslinking to the original bug report
seems fine to me.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
s sounds like an Assume Good Faith interpretation.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
On Wed, Mar 26, 2014 at 2:36 PM, Federico Leva (Nemo) wrote:
> Steven Walling, 26/03/2014 21:38:
>
> as a group we import tickets from Bugzilla they actually think are
>> relevant.
>>
>
> No.
>
Nemo, it is not particularly constructive to reply this way. Since we w
we have teams responsible for importing the bugs from their
backlog, the size of the backlog will be proportional to the size of the
team. We can supplement this with voluntary signup lists to help out on
certain components from Bugzilla.
--
Steven Walling,
s documentation and I
> have no idea how feasible this is now.)
>
The status right now is that the creator of a task sets the editability and
visibility levels of that task. These two settings are quite fine-grained
and somewhat separate: I can create a task that is visible but not edit
I added some to
http://fab.wmflabs.org/M1
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
be that painful
even if in another six-twelve months you might want to switch again.
Let me know if I can help Analytics set up Trello (I am an admin on our WMF
account there). The tool is much more flexible to configure than Mingle,
and I could walk you through some of the
On Fri, Mar 21, 2014 at 2:28 PM, Greg Grossmeier wrote:
> Now they're dogfooding it:
> https://secure.phabricator.com/project/board/773/
>
> (Using the board view to track work to make the board view :) )
>
I filed an issue. :)
--
Steven Walling,
P
dered options (which it is). Most of the other tools listed focus more
on issues/project management, but Phabricator also potentially replaces the
code review and repository viewing portions of our toolkit.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
__
so: https://secure.phabricator.com/T3820
>>
>> (What I was pointed to when I asked about that one on IRC)
>>
>>
>> --
>> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
>> | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
>>
>
bout how to make tasks and projects hidden/restricted,
by consistently using the "Visible To" and "Editable By" fields for
tasks/issues. This will make Ops happy I think? Also should create a doc
with rules of thumb for what kind of tasks should be public/private etc.
--
Ste
t; with the board too much :)
>
> Definitely excited about the potential of Phabricator as a potential
> unified solution to migrate to.
>
This looks pretty darn good indeed. :)
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
On Mon, Mar 3, 2014 at 4:22 PM, Katie Horn wrote:
> Does this mean you're offering to stand up a roving band of nomadic
> scrummasters, if that's what the teams decide they want? If so, please sign
> me up at the very top of that signup list.
>
What Katie and Dan said
op&v1=&format=table&action=wrap
It doesn't give you updated since $date, but I find it more useful than the
standard list format returned by a search. Thanks again to Andre for
showing me this. I'm pretty sure there's
nd there is Phabricator's own instance you can sign up for at
https://secure.phabricator.com
This may be a good time set up a test or talk more seriously about
Phabricator since we're kicking off a review of project management tools we
use... https://www.mediawiki.org/wiki/Project_management_too
we can
> reevaluate Phabricator for our needs this year. I think we could be
> working a lot more efficiently by switching to it.
>
Having played with their test version, I'd definitely be happy moving to
Phabricator as a replacement for Bugzilla, IRC, and maybe even
Trello/Mingle.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
ult in people joining the same room.
WebRTC apps seem to be missing screensharing, but otherwise I'd really love
to ditch Hangouts. It doesn't really work great with Linux, like Matt said.
--
Steven Walling,
Product Manager
https://
i/Mobile_web/Team
>>
>> --
>> Arthur Richards
>> Software Engineer, Mobile
>> [[User:Awjrichards]]
>> IRC: awjr
>> +1-415-839-6885 x6687
>>
>> ___
>> teampractices mailing list
>> teampractices@list
ed to ask Arthur, Tomasz, Katie and
others about them.
My first question is *when *should I schedule our retrospectives? For
context, Growth is in the tail end of our fifth sprint, and sprint
planning/kickoff meetings happen on Wednesdays for us.
--
Steven Walling,
Product Manager
designers go make
Wikipedia edits. I think the point is to learn about and empathize with
your users, so for this it works well.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
ere are a
> lot of volunteer patchsets languishing, I do not think SoS is the
> appropriate forum to deal with this.
>
Gotcha. I think that's fair.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices
On Tue, Dec 3, 2013 at 11:41 AM, Toby Negrin wrote:
> Feels like Engineering Community should represent these stakeholders.
Seems wise to me.
Quim?
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing l
and more.
I would volunteer myself, but I'm stretched thin already with meetings.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/ma
ommunity Department.
1. http://www.sequoiacap.com/grove/posts/akzj/trial-week-our-hiring-secret
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
loyees because sometimes you need
to get talented people. But that doesn't make it the best working
situation. There are huge benefits to having people co-located, and we
should be striving for co-located teams where ever possible.
--
Steven Walling,
Product Manager
https://wiki
tors to that component should be messing around with bug
resolution like WONTFIX. Does that seem okay?
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://list
On Thursday, November 14, 2013, Luis Villa wrote:
>
> On Wed, Nov 13, 2013 at 7:01 PM, Steven Walling
>
> > wrote:
>
>> A logistical point: Pivotal is proprietary. It's a small company based in
>> SF and owned by VMWare. However, they officially give free
p for
> you guys :p
>
No worries. The team has not switched to Pivotal Tracker yet, I just
duplicated the core of our engineering stories from the current sprint as
a test.
>
> On Thu, Nov 14, 2013 at 2:13 PM, Arthur Richards
> 'aricha...@wikimedia.org');>
> > wr
it if necessary?
Trello exports a board in JSON, and Pivotal will import/export CSV. Does
Mingle have data export functions?
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia
willing to give this one a shot, if someone wants to put it on
Labs.
Thanks for the move and refactor of
https://www.mediawiki.org/wiki/Project_management_tools Matt.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices
toolset for supporting teams.
>
Does this mean we get to hire an internal tools team someday? :)
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikim
nt: Pivotal is proprietary. It's a small company based in
SF and owned by VMWare. However, they officially give free unlimited access
perpetually to public projects and non-profits.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
_
iaWiki changes
to continuous deployment rather than scheduled weekly windows, Scrum's
emphasis on time-boxed sprints formed by planning meetings will feel
increasingly artificial and "un-agile".
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices
Via Hacker News: http://thehumanfactor.co/7-sins-of-doomed-teams/
I think Gluttony is the worst sin for us PMs. ;-) Something to ponder...
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
___
teampractices mailing list
teampractices
On Thu, Oct 31, 2013 at 9:14 AM, Andre Klapper wrote:
> On Tue, 2013-10-29 at 23:12 -0700, Steven Walling wrote:
> > My one worry is that prioritization in Bugzilla is less in our
> > control, and can sometimes be the subject of a tug-of-war with
> > community members.
>
iltype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap>,
I'm coming around to seeing Bugzilla as more useful for big picture
prioritization these days. I'd be happy to see how a Bugzilla-b
about
> how we could run the SOS and how it might differ from the Biweekly meeting.
>
Something inside me says that SOS is not the most healthy of acronyms to
use for a meeting to prevent cross-team failures. ;)
--
Steven Walling,
Product Manager
https://wik
47 matches
Mail list logo
