Page MenuHomePhabricator
Create Task
Maniphest T103049

Enable Flow on Web APIs talk pages on mediawiki.org
Closed, ResolvedPublic
Actions

Description

Can I haz Flow on all talk pages of Category:Web APIs hub pages?

A few of these have a talk page already. None is LQT.

I'm not in the "flow bot" group so I can't run Special:EnableFlow. I added some of these to outdated Flow/Rollout page. Thanks!

Related Objects
Search...

Event Timeline

• Spage created this task.Jun 19 2015, 3:14 AM
• Spage assigned this task to • DannyH.
• Spage raised the priority of this task from to Needs Triage.
• Spage updated the task description. (Show Details)
• Spage added projects: StructuredDiscussions, Web-APIs-Hub.
• Spage subscribed.
Restricted Application added a project: Collaboration-Team-Triage. · View Herald TranscriptJun 19 2015, 3:14 AM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
• Spage added a parent task: T307: Announcing the Developer Hub prototype release.Jun 19 2015, 3:16 AM
Qgil subscribed.Jun 19 2015, 8:44 AM

This is a blocker of T101441: Goal: Integrate the new Web APIs hub with mediawiki.org in three months, not a blocker of T307: Announcing the Developer Hub prototype release now.

In mediawiki.org, this developer hub will be in an own namespace, so I think the easiest would be to enable Flow in all discussion pages of such namespace. Unless the entire mediawiki.org has been moved to Flow, of course. :)

Qgil added a parent task: T101441: Goal: Integrate the new Web APIs hub with mediawiki.org.Jun 19 2015, 8:45 AM
Qgil removed a parent task: T307: Announcing the Developer Hub prototype release.
Qgil mentioned this in T307: Announcing the Developer Hub prototype release.Jun 19 2015, 8:47 AM
Qgil added a subtask: T369: Implement a namespace in mediawiki.org to host the developer hub.
• DannyH added a comment.Jun 19 2015, 6:34 PM

Okay, I put Flow on the existing pages in the category. Do you know when the new namespace will be added?

• DannyH triaged this task as Medium priority.Jun 19 2015, 6:34 PM
Qgil added a comment.Jun 22 2015, 10:44 AM

We have committed to deliver T101441: Goal: Integrate the new Web APIs hub with mediawiki.org by the end of September. We will have time to sync.

• Spage added a comment.Jun 22 2015, 6:11 PM
In T103049#1383417, @DannyH wrote:

Okay, I put Flow on the existing pages in the category.

I <3 you man.

Do you know when the new namespace will be added?

When I have the strength to battle the nay-sayers :)
When I do so, I'll rename these pages and their talk pages, so I'll be testing out the "move Flow-enabled page" code path.

Qgil changed the status of subtask T369: Implement a namespace in mediawiki.org to host the developer hub from Open to Stalled.Jun 27 2015, 5:09 PM
• Spage closed subtask T369: Implement a namespace in mediawiki.org to host the developer hub as Declined.Jul 8 2015, 8:54 AM
Qgil added a comment.Aug 4 2015, 10:20 AM

According to our current plan, the Web Apis Hub would be the entire API: namespace in mediawiki.org. How does this fit with the plan for deploying Flow in mediawiki.org? Maybe we need a specific community consultation about this move.

• Mattflaschen-WMF subscribed.Aug 4 2015, 2:48 PM
• Spage renamed this task from Enable Flow on data and developer hub talk pages on mediawiki.org to Enable Flow on Web APIs talk pages on mediawiki.org.Aug 13 2015, 10:31 PM
• Spage updated the task description. (Show Details)
• Spage set Security to None.
• Spage added a subscriber: Quiddity.Aug 14 2015, 12:10 AM

I added a few new hub talk pages and one moved page to the task, and made it a checklist.

In T103049#1505920, @Qgil wrote:

According to our current plan, the Web Apis Hub would be the entire API: namespace in mediawiki.org. How does this fit with the plan for deploying Flow in mediawiki.org? Maybe we need a specific community consultation about this move.

@DannyH, can you comment? T107089: Enable Flow sitewide on Mediawiki.org has no blockers :) . @Quiddity said "no timetable beyond waiting until LQT is done (which is almost there...)"
We would need consultation if we enabled Flow just for the API namespace.

Some numbers: the API namespace already has about 150 top-level pages in English and 20 English subpages whose talk pages should be enabled. The other 400 pages are translations into other languages, I don't know if we should allow or discourage discussion on those. There are 77 API_talk pages currently (useful API query). A handful of translated subpages have talk pages with lonely unanswered questions , e.g. API_talk:Main_page/de.

Qgil added a comment.Aug 14 2015, 8:50 AM

The topic of discouraging discussions in translations is interesting, but it should be addressed in an own task, since it is not dependent on the technology of these Talk pages.

• Spage closed this task as Resolved.Aug 31 2015, 7:24 PM

Thanks @DannyH all done, until the next pages :)

Danny and Quiddity are writing a Flowify mw.org proposal, I would rather the rest of the API namespace ride that train.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits