Now you can submit / claim Engineering Community tasks

List overview All Threads
Download

newer

older

Open issues for next MediaWiki...

Re: [Wikitech-l] [Wikimedia-l]...

Quim Gil

22 Oct 2014 22 Oct '14

4:45 a.m.

Following the activity of the Engineering Community team has never been simple, not even for ourselves. Proposing Engineering Community tasks effectively was even more complex. Here is an attempt to change this: https://phabricator.wikimedia.org/tag/engineering-community/ Since the beginning of this month, we are using Phabricator to organize the Engineering Community team work. https://phabricator.wikimedia.org/tag/ect-october-2014/board/ You can watch, comment, and get involved. You can also submit and claim tasks. What should we be working on next month? How can we facilitate more tech community work done by more people? See you there. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

Show replies by date

David Cuenca

22 Oct 22 Oct

12:45 p.m.

New subject: Now you can submit / claim Engineering Community tasks

Wouldn't be better to have nested projects? GsoC might need a project per year with subprojects for each student to manage their task, is project nesting possible on Phabricator? And what about sister projects? Will each one have a project? Thanks Micru On Wed, Oct 22, 2014 at 3:45 AM, Quim Gil <qgil(a)wikimedia.org> wrote:

...

-- Etiamsi omnes, ego non

Andre Klapper

2:53 p.m.

Hi Micru, On Wed, 2014-10-22 at 11:45 +0200, David Cuenca wrote:

...

Wouldn't be better to have nested projects? GsoC might need a project per year with subprojects for each student to manage their task, is project nesting possible on Phabricator?

Subprojects are not (yet) supported in Phabricator. Upstream ticket: https://secure.phabricator.com/T3670

...

And what about sister projects? Will each one have a project?

A task in Phabricator can have between zero and unlimited associated projects. (This is different from Bugzilla where a ticket must have exactly one product and exactly one component.) Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

Quim Gil

4:31 p.m.

New subject: Now you can submit / claim Engineering Community tasks

On Wed, Oct 22, 2014 at 4:53 AM, Andre Klapper <aklapper(a)wikimedia.org> wrote:

...

Hi Micru, On Wed, 2014-10-22 at 11:45 +0200, David Cuenca wrote:

Wouldn't be better to have nested projects? GsoC might need a project

per

...

year with subprojects for each student to manage their task, is project

nesting possible on Phabricator?

What you are proposing is exactly what we plan to do right now with FOSS OPW Round 9 projects (deadline for submissions: today). https://phabricator.wikimedia.org/T564 Subprojects are not (yet) supported in Phabricator.

...

Upstream ticket: https://secure.phabricator.com/T3670

Tagging describes Phabricator projects a lot better than nesting. In Phabricator, projects are tags and tags are projects. This means that even if the "subproject" concept is officially missing today, you can organize your work in a similar way.

...

And what about sister projects? Will each one have a project? A task in Phabricator can have between zero and unlimited associated projects. (This is different from Bugzilla where a ticket must have exactly one product and exactly one component.)

Exactly. If sister projects want to have Phabricator projects, they could have them. But there us hundreds of them, so we better coordinate first. David, thank you for providing a good excuse to create this task: https://phabricator.wikimedia.org/T802 See you there! ;)

David Cuenca

6:02 p.m.

New subject: Now you can submit / claim Engineering Community tasks

On Wed, Oct 22, 2014 at 3:31 PM, Quim Gil <qgil(a)wikimedia.org> wrote:

...

I partially agree, but just *partially* :) Tagging is just a poor man's version of classing, since it doesn't let you define the relationship between tags. True that you can put any task in several projects/tags, the problem is that the project structure is nevertheless flat: https://phabricator.wikimedia.org/project/query/all/ Which will become cumbersome to navigate for occasional visitors as the number of projects goes up. Exactly. If sister projects want to have Phabricator projects, they could

...

have them. But there us hundreds of them, so we better coordinate first. David, thank you for providing a good excuse to create this task:

Hundreds of them? :D Last time I checked there were between 1 and 12 sisters projects, depending on whom you ask. But if you meant to create projects for each language version of each sister project, then I agree that it would be too much. OTOH, with a proper organization it could be innovative to manage far-reaching content projects through phabricator ;) Cheers, Micru

Quim Gil

23 Oct 23 Oct

5:38 p.m.

New subject: Now you can submit / claim Engineering Community tasks

As a practical example, if you want to join or influence the Engineering Community work for November, now is the right time to do it: https://phabricator.wikimedia.org/tag/ect-november-2014/ On Wed, Oct 22, 2014 at 8:02 AM, David Cuenca <dacuetu(a)gmail.com> wrote:

...

Tagging is just a poor man's version of classing, since it doesn't let you define the relationship between tags. True that you can put any task in several projects/tags, the problem is that the project structure is nevertheless flat: https://phabricator.wikimedia.org/project/query/all/ Which will become cumbersome to navigate for occasional visitors as the number of projects goes up.

Sure, but after years of Bugzilla we have also seen that the rigid tree structure of https://bugzilla.wikimedia.org/describecomponents.cgi causes many problems too, and occasional visitors probably find it cumbersome anyway. If we want a high level overview of the projects, we can always have a wiki page identifying the main teams/projects, the starting points to understand the hundreds of projects that we will have soon. Now there is a task to discuss this. :) https://phabricator.wikimedia.org/T833

3466

days inactive

3467

days old

wikitech-l@lists.wikimedia.org

Manage subscription

5 comments

3 participants

tags (0)

participants (3)

Andre Klapper
David Cuenca
Quim Gil