Change 739662 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] logstash: remove scholarships type from udp2log filters

https://gerrit.wikimedia.org/r/739662

Change 739667 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] mariadb: remove all grants related to scholarship app and its dumps

https://gerrit.wikimedia.org/r/739667

Should we, at some point, also drop the database?

Change 739667 merged by Marostegui:

[operations/puppet@production] mariadb: remove all grants related to scholarship app and its dumps

https://gerrit.wikimedia.org/r/739667

In T243037#7519246, @Marostegui wrote:

Should we, at some point, also drop the database?

Nevermind, I just saw that there's indeed a point to delete it :)

I just got pinged on T296166#7519256 on stopping backups of this database (this is a non-issue for me), what I want to raise here is that the order of the pending cleanup tasks may not be ideal- if backups are stopped AND database is deleted, there will be nothing to archive, as all existing backups will be purged in 3 months. Plus generating a public export, if required, may also be more difficult after the db is removed.

This database is tiny (15M) we can take a full mysqldump before dropping it if we want.

Being so small, I can store it for a few years on long-term backups (but it won't be there forever-it won't be a valid archival method-, just for a larger time than regular backups). Waiting for feedback.

In T243037#7519718, @jcrespo wrote:

Being so small, I can store it for a few years on long-term backups (but it won't be there forever-it won't be a valid archival method-, just for a larger time than regular backups). Waiting for feedback.

In T243037#5813119, @bd808 wrote:

In T243037#5812031, @Qgil wrote:

@soworu It would be useful to check with Legal how we can make any use of the existing data. Knowing who has applied for scholarship in previous Wikimanias and who was accepted / declined may be useful information for scholarship committees in the current Wikimania and future events.

That data is not retained in the Scholarships application. We purge the database as soon as the decisions are made each year.

It sounds like I never got around to purging the 2019 data if there is anything in the database at all other than some fixture data for building the UI and grouping data in reports. I have no expectation that there would be valuable data to save for any purpose in the database for the scholarships application at this time.

I have no expectation that there would be valuable data to save for any purpose

Thanks, that's useful. Better double checking rather than having unintended data loss. :-)

Change 739660 merged by Dzahn:

[operations/puppet@production] cache::text: remove config for scholarships.wikimedia.org

https://gerrit.wikimedia.org/r/739660

Change 739662 merged by Dzahn:

[operations/puppet@production] logstash: remove scholarships type from udp2log filters

https://gerrit.wikimedia.org/r/739662

Change 739658 merged by Dzahn:

[operations/puppet@production] wikimania_scholarships: delete module and profile, remove from miscweb

https://gerrit.wikimedia.org/r/739658

Mentioned in SAL (#wikimedia-operations) [2021-11-23T17:49:17Z] <mutante> miscweb1002 - rm -rf /srv/deployments/scholarships (T243037)

I do not have the permission to click "Deactivate Repository" on:

https://phabricator.wikimedia.org/source/wikimania-scholarships/manage/

@20after4 could you archive this ^ ?

Change 740907 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] cache/text_haproxy: remove scholarships.wikimedia.org config

https://gerrit.wikimedia.org/r/740907

Change 740907 merged by Dzahn:

[operations/puppet@production] cache/text_haproxy: remove scholarships.wikimedia.org config

https://gerrit.wikimedia.org/r/740907

In T243037#7524194, @Dzahn wrote:

I do not have the permission to click "Deactivate Repository" on:

https://phabricator.wikimedia.org/source/wikimania-scholarships/manage/

@20after4 could you archive this ^ ?

Right, Members of the project "Diffusion-Repository-Administrators" can take this action. and I'm not.
@mmodell: ^ping?

checked one box that had already been done by someone meanwhile (add Historical on the mediawiki.org page).

regarding " Archive the diffusion repository: rWWSC", it is currently "active" but "publishing disabled". Does that count as archived?

In T243037#7635884, @Aklapper wrote:

In T243037#7524194, @Dzahn wrote:

I do not have the permission to click "Deactivate Repository" on:

https://phabricator.wikimedia.org/source/wikimania-scholarships/manage/

@20after4 could you archive this ^ ?

Right, Members of the project "Diffusion-Repository-Administrators" can take this action. and I'm not.
@mmodell: ^ping?

Meanwhile I do have wider privileges on Phabricator and now I _could_ click that button to archive it and just did.

https://phabricator.wikimedia.org/source/wikimania-scholarships/manage/

Also was able to click "Archive" on the Phabricator project.

https://phabricator.wikimedia.org/project/manage/740/

Only open task on it is this one.

@bd808 Looks like I could also make the "readonly"-click on Gerrit. But there is another checkbox about emptying it. Is that still wanted/needed before making it readonly?

In T243037#8225404, @Dzahn wrote:

@bd808 Looks like I could also make the "readonly"-click on Gerrit. But there is another checkbox about emptying it. Is that still wanted/needed before making it readonly?

I think that is what is commonly done. https://gerrit.wikimedia.org/r/plugins/gitiles/wikibase/vuejs-components/+/c13b1ec9ab067769e169becb40d0d2cd8454d52a is an example from the first random Projects-Cleanup I looked up. If you are comfortable doing it, that would be great. If not I can get to it "soon".

Honestly I would just click on Archive and leave it be. Don't really see what we gain by actively deleting files from the repo.. as long as it's readonly.

Per {T243032} the Wikimedia-Wikimania-Scholarships application is being replaced with a new solution.

That task is private, and I can't find any info on MediaWiki.org about what the new solution is. Would someone be able to link to it from here or https://www.mediawiki.org/wiki/Wikimania_Scholarships_app ? There were a couple of questions at the ESEAP conference last week about it.

As COT Scholarship lead from 2020 where it was to be use before covid shut wikimania down and now we were preparing to use this tool for wikimania 2023 can it be brought back online as people want us to use the WMF based tool to protect the privacy of applicants with the WMF controls. Our timetable is to open scholarship application is 2 Jan 2023... cheers Gnangarra

@Reedy Can you "archive" Github projects? I am not sure what it means but sounds ike it needs WMF github org admin. (https://github.com/wikimedia/wikimedia-wikimania-scholarships)

@Marostegui We have an open checkbox "Delete scholarships database on m2-master.eqiad.wmnet" here but I am not sure if that is actionable by DBA or if it is whether it should be assigned as a separate ticket.

In T243037#8425288, @Dzahn wrote:

@Marostegui We have an open checkbox "Delete scholarships database on m2-master.eqiad.wmnet" here but I am not sure if that is actionable by DBA or if it is whether it should be assigned as a separate ticket.

We can do it yeah. I would like to ping @jcrespo first to make sure we have one last backup, before dropping it.
But once it is done, we can totally go ahead and drop it

For what is worth:

root@db1164:/srv/sqldata/scholarships# du -sh .
15M	.

@Marostegui ACK,sounds good, thank you :)

Adding "Wikimedia-GitHub" tag. If anyone is an admin for the Wikimedia org in Github, could you archive this one repo here for us? (see https://docs.github.com/en/repositories/archiving-a-github-repository) and the one checkbox on this ticket. Thank you!

I have archived https://github.com/wikimedia/wikimedia-wikimania-scholarships/

Aww, thanks @Aklapper :)

Change 861458 had a related patch set uploaded (by Dzahn; author: Dzahn):

[wikimedia/wikimania-scholarships@master] empty respository, leave ARCHIVED.md file around

https://gerrit.wikimedia.org/r/861458

Mentioned in SAL (#wikimedia-operations) [2022-11-29T10:07:23Z] <jynus> add temporary grants to scholarships for backups on db1117, db2160 T243037

Mentioned in SAL (#wikimedia-operations) [2022-11-29T10:30:53Z] <jynus> revoke temporary grants to scholarships for backups on db1117, db2160 T243037

In T243037#8425331, @Marostegui wrote:

In T243037#8425288, @Dzahn wrote:

@Marostegui We have an open checkbox "Delete scholarships database on m2-master.eqiad.wmnet" here but I am not sure if that is actionable by DBA or if it is whether it should be assigned as a separate ticket.

We can do it yeah. I would like to ping @jcrespo first to make sure we have one last backup, before dropping it.
But once it is done, we can totally go ahead and drop it

I made sure we have a backup on both datacenters and we can recover from it (you never know these days) by performing a full recovery on another host. I checked then that both the recovered db and the original one were the same.

This is the backup on eqiad, there is another one on codfw too:

Mentioned in SAL (#wikimedia-operations) [2022-11-29T11:47:39Z] <marostegui> Drop scholarships database from m2 T243037

Thank you Jaime!

Dropped from m2 master

root@db1164.eqiad.wmnet[(none)]> drop database if exists scholarships;
Query OK, 6 rows affected (0.014 sec)

root@db1164.eqiad.wmnet[(none)]>

Thank you Jaime and Manuel :) perfection

Change 861928 had a related patch set uploaded (by Dzahn; author: Dzahn):

[integration/config@master] zuul/layout: set scholarships app repo to archived

https://gerrit.wikimedia.org/r/861928

Change 861458 merged by Jforrester:

[wikimedia/wikimania-scholarships@master] empty respository, leave ARCHIVED.md file around

https://gerrit.wikimedia.org/r/861458

Change 861928 merged by jenkins-bot:

[integration/config@master] Zuul: [wikimedia/wikimania-scholarships] Set as archived

https://gerrit.wikimedia.org/r/861928

Mentioned in SAL (#wikimedia-releng) [2022-11-29T20:33:27Z] <James_F> Zuul: [wikimedia/wikimania-scholarships] Set as archived for T243037

Now this is done, can T243032 be made public?

@Samwilson If you ask me, I have no idea, I don't know why it was ever not public and had zero involvement in that ticket. Guess we have to ask @soworu

In T243037#8430689, @Samwilson wrote:

Now this is done, can T243032 be made public?

I can tell you that the ticket was about a project that has been cancelled. As far as I know there is currently no standing solution for Wikimania scholarship applications. This functionally puts us as a movement back where we were in 2013 with it being the responsibility of each Wikimania organizing team to find a solution for this recurring need.

Thanks @bd808, that's sort of what I thought.

I guess the main thing I'm worried about is that some Wikimania committee will find the old codebase and decide to run it somewhere, when actually there might be good reasons (security, presumably) that that should not be done.

In T243037#8433931, @Samwilson wrote:

I guess the main thing I'm worried about is that some Wikimania committee will find the old codebase and decide to run it somewhere, when actually there might be good reasons (security, presumably) that that should not be done.

There probably are a few libraries that need to be updated, but I don't know of any system scale security issues that the application had prior to being decommissioned. From my point of view, the WMF hosted Wikimania Scholarships app was shutdown because the core organizing group for Wikimanias within the Foundation said that they did not want to use it any more. This was convenient for me as well because @Niharika and I had not had official support for developing and maintaining the application for several years.

If the Foundation changes its mind again and wants to bring the app back that is possible. It would be a better fit for Kubernetes hosting if resurrected in my opinion, but the biggest thing it needs is an engineering team committed to providing support for the code base. It had this in 2013-2015, but reorgs and other personnel changes pushed it into the classically horrible "who touched it last" maintainer seat from 2016-2020.

Hi everyone,
I'm keen to know a few things, Firstly - if we had budget, would there be the resource to re-commission this for early Jan?
If so do we have any idea of budget and is there any records/documentation about the software so we can see how it would work alongside Fluxx that we use for scholarships etc?
Thanks!