Page MenuHomePhabricator

Document Flow database schema
Open, MediumPublic2 Estimated Story Points

Description

We can use the same format and/or templates as https://www.mediawiki.org/wiki/Manual:Database_layout
and others in https://www.mediawiki.org/wiki/Category:MediaWiki_database_tables

See also https://www.mediawiki.org/wiki/Flow/Database


Trello card: p8b7XMjw

  • column: Send to Phabricator - Collaboration-Team board

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 20 2015, 2:06 AM
Mattflaschen-WMF renamed this task from Document Flow database schema (2) to Document Flow database schema.Feb 20 2015, 7:29 PM
Mattflaschen-WMF set Security to None.
Mattflaschen-WMF edited a custom field.
EBernhardson triaged this task as Medium priority.Feb 24 2015, 6:51 PM
EBernhardson added a subscriber: EBernhardson.
Niharika added a subscriber: Niharika.EditedMar 4 2015, 3:20 PM

@Mattflaschen, is this fitting for a Outreachy project? If yes, would you be interested in mentoring?

Bawolff added a subscriber: Bawolff.Mar 4 2015, 3:26 PM

Dcoument db schema seems inapropriate for GSOC. Possibly ok for OPW, but unless flow has an insanely complex db schema, seems like scope would be too smal.

I think GSOC and Outreachy (formerly OPW) are supposed to be roughly the same scope. I agree, not appropriate for a GSOC/Outreachy alone.

Maybe as part of a broader documentation project (talk to @Spage?)

Qgil added a subscriber: Qgil.Mar 4 2015, 9:06 PM

GSoC projects must involve writing... Code. Outreachy is more flexible, allowing for any type of projects in a free software project, including documentation.

In T90056#1089741, @Mattflaschen wrote:

Maybe as part of a broader documentation project (talk to @Spage?)

Obviously improving doc pages like https://www.mediawiki.org/wiki/Flow/Database is always welcome. The problem is they tend to be "WOUND" (write-once, update- never documentation) so they drift out of date leading to 2017's phab task "Update Flow database schema documentation on mediawiki.org".

If table documentation lived with code, developers would be more likely to update it with their git patches. The infrastructure work to reduce this is [T91626], and while researching how we document database tables I filed T91859: Update diagram of core database tables to MediaWiki 1.24 , which could be an excellent GSOC/Outreachy project.

In T90056#1089741, @Mattflaschen wrote:

Maybe as part of a broader documentation project (talk to @Spage?)

Obviously improving doc pages like https://www.mediawiki.org/wiki/Flow/Database is always welcome. The problem is they tend to be "WOUND" (write-once, update- never documentation) so they drift out of date leading to 2017's phab task "Update Flow database schema documentation on mediawiki.org".

If table documentation lived with code, developers would be more likely to update it with their git patches.

Best yet, it should be auto-generated from the SQL files on commit (similar to how https://doc.wikimedia.org/mediawiki-core/master/php/html/ is). There are tools we may be able to adopt, such as https://stackoverflow.com/a/5267797/ .

Qgil added a comment.Sep 23 2015, 9:06 AM

This is a message posted to all tasks under "Need Discussion" at Possible-Tech-Projects. Outreachy-Round-11 is around the corner. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.

Qgil added a comment.Sep 23 2015, 9:35 AM

This is a message sent to all Possible-Tech-Projects. The new round of Wikimedia Individual Engagement Grants is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after (T105414). If someone is interested in obtaining funds to push this task, this might be a good way.

Laucon added a subscriber: Laucon.Sep 29 2015, 4:11 PM

I would love to apply to this Possible-Tech-Project for the Outreach-Round-11. Should I add a proposal of some kind?

Qgil added a comment.Sep 29 2015, 5:55 PM
In T90056#1089741, @Mattflaschen wrote:

I think GSOC and Outreachy (formerly OPW) are supposed to be roughly the same scope. I agree, not appropriate for a GSOC/Outreachy alone.

Maybe as part of a broader documentation project (talk to @Spage?)

OK, so this is a too small project for Possible-Tech-Projects.

Milimetric added a subscriber: Milimetric.

One advice is to add comments in the create table statements for each column, that goes a long way.

Qgil removed a subscriber: Qgil.Apr 20 2017, 10:23 AM
Restricted Application added a project: Growth-Team. · View Herald TranscriptJul 18 2018, 6:56 PM
SBisson moved this task from Inbox to Triaged but Future on the Growth-Team board.Jul 20 2018, 5:52 PM