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

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?)

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#1097640, @Spage wrote:

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/ .

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.

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.

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

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.

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