Fine-tuning the Architecture RfC process

List overview All Threads
Download

newer

older

Re: [Wikitech-l]...

Fw: [Wikimedia-l] Great editor for...

Quim Gil

8 Aug 2014 8 Aug '14

11:14 a.m.

Yesterday at the Wikimania Hackathon, Brion, Gabriel, Quim, Rachel, Robla, Tim, agreed on a series of little improvements to the Architecture RfC process in order to distribute the effort and move the driving force from the Engineering Community Team to the Architecture Committee.

...

From now on, Architecture RfC related tasks are handled in a Phabricator

project: http://fab.wmflabs.org/project/board/72/ While the RfCs themselves will continue to be documented at https://www.mediawiki.org/wiki/Requests_for_comment , in Phabricator we will create tasks to reflect the RfCs that have actions pending and/or are ready to be reviewed. This should help everybody understanding quickly what is missing in an RfC to go through the process, and who is in charge to work on what. The Architecture Committee will meet regularly and decide the future RfCs to be discussed. They will also run the RfC meetings. ECT will continue to help scheduling and announcing these meetings. You can find the details at https://www.mediawiki.org/wiki/Architecture_meetings We will be creating tasks for the RfCs scheduled or likely to be scheduled. If you are impatient or extremely helpful, you can create the tasks for the RfCs that you are promoting. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

Show replies by date

Legoktm

8 Aug 8 Aug

12:14 p.m.

On 8/8/14, 12:14 PM, Quim Gil wrote:

...

From now on, Architecture RfC related tasks are handled in a Phabricator project: http://fab.wmflabs.org/project/board/72/ While the RfCs themselves will continue to be documented at https://www.mediawiki.org/wiki/Requests_for_comment , in Phabricator we will create tasks to reflect the RfCs that have actions pending and/or are ready to be reviewed. This should help everybody understanding quickly what is missing in an RfC to go through the process, and who is in charge to work on what.

Can we please not use Phabricator until it's an actual production service? We still don't have IRC notifications, mailing lists, documentation, etc. Most people don't even look at it because, well, it's a test instance, not an actual thing people should be using. I'm also reminded of Mark's comments in [1]: If a URL has "wmflabs.org" in it...don't put anything, ANYTHING, important there. Just use Bugzilla, most RfCs are already using it to track issues anyways. -- Legoktm [1] http://lists.wikimedia.org/pipermail/wikitech-l/2013-August/071442.html

Bartosz Dziewoński

12:57 p.m.

There is a Phabricator IRC bot, actually, but it was taken down because it was just repeating information from other bots. W dniu piątek, 8 sierpnia 2014 Legoktm <legoktm.wikipedia(a)gmail.com> napisał(a):

...

On 8/8/14, 12:14 PM, Quim Gil wrote:

are

ready to be reviewed. This should help everybody understanding quickly

what

is missing in an RfC to go through the process, and who is in charge to work on what.

-- -- Matma Rex

Quim Gil

2:07 p.m.

Collateral summary: a transition to Phabricator has started, and this project is just taking advantage of it. On Fri, Aug 8, 2014 at 1:14 PM, Legoktm <legoktm.wikipedia(a)gmail.com> wrote:

...

Phabricator is supposed to become an actual production service within a few weeks. We are using it here for tracking tasks more than tracking bugs, and the workboard is a useful interface to see at a glance which RfCs are ready to be reviewed. Lack of IRC notifications is not a dealbreaker in this project, since we didn't have it either in the purely MediaWiki-base process we had before. Mailing lists... will be used in the same way. Documentation... what do you need? Please check and ask at https://www.mediawiki.org/wiki/Phabricator/Help Most people probably don't need to look at this project. For the architects and the few other people that have to follow it, I'm sure that notifications will work just fine. I'm also reminded of Mark's comments in [1]: If a URL has "wmflabs.org"

...

in it...don't put anything, ANYTHING, important there.

For what is worth, some projects are posting important information in this Phabricator instance, and its content is being backed up periodically.

Chad

5:10 p.m.

It's unfortunate that it's being used for prod data. I never intended that when it was set up. So yeah +1 to waiting until we have a real prod service. -Chad On Aug 8, 2014 3:07 PM, "Quim Gil" <qgil(a)wikimedia.org> wrote:

...

Collateral summary: a transition to Phabricator has started, and this project is just taking advantage of it. On Fri, Aug 8, 2014 at 1:14 PM, Legoktm <legoktm.wikipedia(a)gmail.com> wrote:

in it...don't put anything, ANYTHING, important there.

For what is worth, some projects are posting important information in this Phabricator instance, and its content is being backed up periodically. _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Quim Gil

9 Aug 9 Aug

10:03 a.m.

Alright, let's find a compromise: we will make sure that any Architecture task fitting in Bugzilla will have a Bugzilla report. We will continue using Phabricator for all the rest. Let's talk again when we have a Phabricator instance in production (in a few weeks, according to plans). For instance,"Schedule wednesday rfc meeting for european team next week Aug 13" http://fab.wmflabs.org/T528 could be closed as a perfectly INVALID report in Bugzilla, yet it has a function in our little project in Phabricator. If Labs goes down, we will manage. PS: It is a fact that we have "real work" projects in fab.wmflabs.org today, and thanks to this we are learning and testing a lot. It would have been crazy to go from "Test Foo Blah" tasks to Phabricator Day 1 without this phase of experimentation and compromises in between. On Fri, Aug 8, 2014 at 6:10 PM, Chad <innocentkiller(a)gmail.com> wrote:

...

Collateral summary: a transition to Phabricator has started, and this project is just taking advantage of it. On Fri, Aug 8, 2014 at 1:14 PM, Legoktm <legoktm.wikipedia(a)gmail.com> wrote:

Phabricator is supposed to become an actual production service within a

few

weeks. We are using it here for tracking tasks more than tracking bugs,

and

the workboard is a useful interface to see at a glance which RfCs are

ready

to be reviewed. Lack of IRC notifications is not a dealbreaker in this project, since we didn't have it either in the purely MediaWiki-base process we had before. Mailing lists... will be used in the same way. Documentation... what do

you

need? Please check and ask at https://www.mediawiki.org/wiki/Phabricator/Help Most people probably don't need to look at this project. For the

architects

and the few other people that have to follow it, I'm sure that notifications will work just fine. I'm also reminded of Mark's comments in [1]: If a URL has "wmflabs.org"

in it...don't put anything, ANYTHING, important there.

For what is worth, some projects are posting important information in

this

Phabricator instance, and its content is being backed up periodically. _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

_______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

svetlana

8 Aug 8 Aug

9:31 p.m.

On Fri, 8 Aug 2014, at 22:14, Legoktm wrote:

...

Just use Bugzilla, most RfCs are already using it to track issues anyways. -- Legoktm

+1 I find some folks use Trello. I can't even darned add a comment there. Svetlana

3572

days inactive

3573

days old

wikitech-l@lists.wikimedia.org

Manage subscription

6 comments

5 participants

tags (0)

participants (5)

Bartosz Dziewoński
Chad
Legoktm
Quim Gil
svetlana