In T310826#8010467, @srishakatux wrote:

@QEDK Thanks for your prompt response :) I tried the !welcome command but I am not seeing the new message yet. Was the deploy successful?

In T310826#8009849, @srishakatux wrote:

@QEDK I've send a PR in your repo: https://github.com/QEDK/goodbot/pull/197. When you get a chance, could you please look into it and help merge? Thank you!

Just updated the bot so older projects don't show anymore and rather just link to newest project pages. If we remove the parsing aspect of the bot, it should be simple enough to update 1 link semi-annually (Outreachy winter), and 2 links annually (Outreachy summer + GSoC)

In T298502#7695409, @srishakatux wrote:

In T298502#7695266, @bd808 wrote:

Are these commands not actually used by the community? It doesn't seem like a large burden to have someone make a commit like https://github.com/QEDK/goodbot/commit/627f7e78ad7cc83a2ae9ef98402fbbd59f295c00 once a year. An alternate "wiki" approach to this might be to actually move that configuration to pages on mediawiki.org or wikitech.wikimedia.org and have the bot read (and cache) the config from there so that it could be edited without git access.

I think we can direct folks to https://www.mediawiki.org/wiki/Outreach_programs, from where they can navigate to the ongoing program pages. Also, it seems we are hard coding projects in the current setup: https://github.com/QEDK/goodbot/blob/master/templates/projects.json requiring frequent updating. As with other resources, it would be nice to stick to the same approach in the case of our programs IMO.

In T298502#7610299, @bd808 wrote:

The tool's maintainers (per https://toolsadmin.wikimedia.org/tools/id/goodbot) are @xSavitar, @Pavithraes, and @QEDK. Source code is at https://github.com/QEDK/goodbot.

• !projects data is taken from https://github.com/QEDK/goodbot/blob/master/templates/projects.json
• !gsoc data is taken from https://github.com/QEDK/goodbot/blob/master/config/config.json settings

I feel like the code for this bot should be moved to gerrit or gitlab to make it easier to collaborate on.
(<rant>generally projects like this that are intended as shared infrastructure should not end until the canonical code is somewhere other than an individual technical volunteer's personal github account.</rant>)

In T258841#7320512, @AntiCompositeNumber wrote:

The other option for GitHub is to use git+https with OAuth instead of git+ssh: https://docs.github.com/en/github/extending-github/git-automation-with-oauth-tokens. You can't limit an OAuth token to a single repository unless you use a machine user, but that's usually a good idea if you're writing automatically anyway.

For T289850 Gerrit also supports read/write git+https (docs). Both token and LDAP auth are enabled (T218750).

In T275294#6846224, @TonyBallioni wrote:

My general suggestion is not to only look at FOSS, but to look at what would fit our needs best. That could be something that’s open source, but it might be something else, and I don’t think we should limit ourselves.

Closing this as done. Thanks, @Gopavasanth !

In T272465#6762684, @JJMC89 wrote:

I don't know about PAWS, but Pywikibot shouldn't be killing a script before completion unless there was an error.

Pywikibot has the daemonize global option.

Is there any reason you are not ssh-ing into a tools account or using your local environment to do this? I don't mean to say that this isn't a problem for you, but that you have current workarounds for it, that's all.

I'd be happy to help! 👋

In T229735#6594344, @Aklapper wrote:

If your city administration's plan for the next decades is to build some street at some place, even if setting up that street may not start in the next 30 years because plans or money change, then you usually do not intentionally build houses in that very place to make everything deliberately more complicated to fix later on.

In T229735#6594262, @PerfektesChaos wrote:

It does not matter. It might be in 2 or 5 or 10 years.

If a page name scheme is reserved for system purposes it is the absolute contradiction of wisdom to ask over and over again for occupation of this name scheme for articles. They are blocked, they shall stay blocked, and nobody shall create a naming conflict against better knowledge. Those who want to set up articles in this field need to be creative and find other names. One day you would have to do that anyway, so start it right from the beginning which is causing least trouble.

You might pray that never ever the Coast Miwok create an active Wikipedia. If they do you will have to move and rename a lot of articles related to Crime Scene Investigation stories.

In T229735#6594099, @PerfektesChaos wrote:

These namespaces are reserved for future usage, and no community shall be permitted to put any single page under a name that will require struggle and moving and efforts later.

Since no one shall create any page here there is no need to give anybody the capability to create anything under reserved namespace numbers and name scheme.

If there is no clear roadmap for Gadgets 2.0, the namespace should be released back to the community for normal usage.

I will be working on the third point soon but not sure about passive replying without further talks with the community.

This project was completed successfully.

This project was completed successfully. One subtask is open for future development.

Each project however retains full control over their content. The Wikidata
integration was done prior to receiving community feedback and hence
there's no reason to not undo this given that work has been put in to make
it better for everyone - integration does not equate to it being better. As
Tgr said, this is not the place to relitigate, if you object to this, start
a discussion on English Wikipedia.

Done. 🎉