Page MenuHomePhabricator

Adoption request for GraphQL
Closed, ResolvedPublic

Description

I request being added as a co-maintainer of GraphQL. The tools admin link is https://admin.toolforge.org/tool/graphql
Following the Adoption policy, Either:

  • The tool has been non-functional for 14 days, per
  • Or, The current maintainer(s) have been inactive for 28 days, per

https://www.wikidata.org/wiki/Topic:Wsav4klh5xin9taq The tool's functional but the maintainer is not active and there is a bug (T291637) that has a patch that needs to be pushed and deployed

The current maintainer(s) have been notified on all of their:

Please could the TFSC :

  • check the tool's home directory for obvious secret information, following the Adoption policy instructions

Event Timeline

adding @Mooeypoo and @Tchanders as the other listed "Maintainers" in the 1st link.

Thanks for the ping @Quiddity.

@Lectrician1 I have no objections, but I also don't have a history of involvement of this project, so I've removed myself as a maintainer. Maybe @Mooeypoo could help more?

Unfortunately, I'm in the same boat; I've never actually been directly involved in the project. I had a very passing general interest in it while working on another GraphQL project -- and I worked with the original maintainer! -- but I don't think I can serve as a maintainer on this (or even fix bugs...)

No wiki credentials or other external secrets found in /data/project/graphql and its sub-directories.

I did notice that the web UI at https://graphql.toolforge.org/ loads a number of 3rd-party resources which can be seen in the report at https://csp-report.toolforge.org/search?ft=graphql. It would be ideal if the new maintainers looked into using the Toolforge privacy respecting CDNs instead.

Any update on this request?

@Mooeypoo are you willing to add @Lectrician1 as a co-maintainer or transfer maintainership of the tool to them outright? The Toolforge-standards-committee can follow the Abandoned tool policy to add them as well, but a friendly transfer seems a nicer outcome.

Yeah, I think that's a good resolution.
I might need guidance as to what to do to make this happen...

Yeah, I think that's a good resolution.
I might need guidance as to what to do to make this happen...

I was going to say this was trivial and then I realized that @Lectrician1 needs to take some steps first. Here is what will need to happen:

  1. @Lectrician1 needs to apply to become a Toolforge member by doing steps 2 and 3 from Portal:Toolforge/Quickstart:
    1. Add an ssh key to their Developer account
    2. Request Toolforge membership via https://toolsadmin.wikimedia.org/tools/membership/apply
  2. Any Toolforge admin (like me!) will then need to approve @Lectrician1's membership request.
  3. @Lectrician1 can then do step 4 from Portal:Toolforge/Quickstart
    1. Log out from https://toolsadmin.wikimedia.org/
    2. Log into https://toolsadmin.wikimedia.org/
  4. @Mooeypoo can then use the form at https://toolsadmin.wikimedia.org/tools/id/graphql/maintainers/ to add @Lectrician1 as a maintainer of the graphql tool.
  5. Profit!! At this point @Lectrician1 should be able to ssh to login.toolforge.org and become graphql to work on the tool. From there on y'all are on your own to figure out how to patch the application. The docs at https://wikitech.wikimedia.org/wiki/Help:Toolforge and the #wikimedia-cloud IRC channel may be helpful when and if you get stuck.

Okay, I am now a Toolforge member. Just need @Mooeypoo to add me as a maintainer.

Okay, I am now a Toolforge member. Just need @Mooeypoo to add me as a maintainer.

Done!