Related to gitlab:fedora/websites-apps&4.
The Fedora Badges team is working on a progressive rewrite of the existing Badges stack. We are tracking this work transparently in a series of GitLab epics. One of the next major steps is database-related work with the old system, so developers on the new system can use it as a reference implementation.
Per discussion with @t0xic0der, we need to take the existing database schema from the old system, take a dump of the schema, and update the schema based on what is actually in use versus what is not in use. The deliverable from this task is a new database schema derived from the old system that removes unused columns. This will be used as a reference for designing the new system.
Note that this request only has to do with the database schema and not the data itself, per se.
The next Fedora Badges roundtable meeting is on 21 June. It would be great if this could be done by then, so we can move forward with our next steps in our project timeline.
The db is publicly available at https://infrastructure.fedoraproject.org/infra/db-dumps/tahrir.dump.xz
That would have the schema too, so does that give you what you need?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
@t0xic0der Could you clarify on the above please?
@kevin, hi there!
I plan on reworking the existing schema to better facilitate the changes we would want to introduce down the line. We want to inherit the data dump that you shared using an updated database schema and then, a smol part of it would be exported off to be used by the developers in their development environment.
Happy to elaborate if you have more questions.
@t0xic0der Do you think the above data dump linked by Kevin is sufficient for this ticket to unblock #11324, or should it be assigned to you for updating the schema?
@jflory7, the latter. The data dump gives me a starting point and tells me about the schema. Only after importing it and studying it - would I be able to make decisions regarding the updated schema and write scripts that help me transform it to a newer database.
Happy to assign this to you for that work, or if it makes more sense we could close this here and track the work in the badges ticketing system?
@kevin For now, let us use this issue tracker as the Badges work has been scoped under I&R for this quarter. Please go ahead and assign me the ticket as well. Thanks!
Metadata Update from @kevin: - Issue assigned to t0xic0der
@t0xic0der Is there any updates here?
Hi @pcreech17,
The developer database environment has been available for quite a while now. Albeit this is the one that is based on the older database schema but that should not stop folks from looking into it and contributing as well. Please check https://discussion.fedoraproject.org/t/fedora-badges-developer-database-environment-is-now-available/84168.
We are currently working our way through the application. It is only after all the endpoints are configured that we will be able to create a migration script that reads things from the existing database and imports them over to the new one with the fresh schema. Please check https://gitlab.com/fedora/websites-apps/fedora-badges/server.
Please feel free to participate in the process to speed things up. Here's the room where we have the development conversations https://chat.fedoraproject.org/#/room/#badges-devel:fedoraproject.org, here's the room where we have general conversations https://chat.fedoraproject.org/#/room/#badges:fedoraproject.org and here's where the codebase is maintained https://gitlab.com/fedora/websites-apps/fedora-badges.
Closing as complete
The database dump can be found here https://explorer.apexaltruism.net/login and can be interacted with.
Metadata Update from @t0xic0der: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.