Rename bot from MeeseeksDev to community selected name

[matthewfeickert]

Renaming is still a TODO item, but I feel that belongs to a new issue.

Originally posted by @bsipocz in #99 (comment)

There is a consensus that the bot (and this repository) should be renamed from @meeseeksdev (https://github.com/scientific-python/MeeseeksDev/) to a new name selected by the Scientific Python community. There should be some discussion and voting on that.

[matthewfeickert]

I will say that I very much appreciate how for JOSS our bot is named @editorialbot (https://github.com/editorialbot) as its name conveys what its purpose is for the most part (assisting the editorial and review team in the administrative actions for submission review and publishing). I would personally like to see a bot with a similar name that describes its service/use to the Scientific Python community over something that is more inside jokey. I would suggest @backportbot but the bot currently does more than just backport PRs (even if that is its primary use case).

[bsipocz]

@matthewfeickert - a lot of brainstorming went into the rename last year, I would suggest not ignoring that. Also, I really like that this bot always had a personality (and some of the other bots I liked, had it too, with baldrick being the favourite), as well as it does a lot of things, so limiting the possibilities with something like backportbot isn't really that appealing to me personally.

[bsipocz]

btw, the app is already called lumberbot-app, so another reason for not starting the naming brainstrom from scratch

[matthewfeickert]

a lot of brainstorming went into the rename last year, I would suggest not ignoring that

@bsipocz Is this publicly available? If not, then please make it so. I'm not ignoring things I don't know about.

the app is already called lumberbot-app, so another reason for not starting the naming brainstrom from scratch

Is there a reason that this isn't the name of the bot you interact with through GitHub comments already (other than it is confusing and doesn't tell you anything about what the bot does)?

as well as it does a lot of things, so limiting the possibilities with something like backportbot isn't really that appealing to me personally.

Yes, this is what I said:

I would suggest @backportbot but the bot currently does more than just backport PRs (even if that is its primary use case).

so seems we're on the same page here. 👍

(Sorry for so many edits, I'm writing fast between meetings and no cleary)

[bsipocz]

Is there a reason that this isn't the name of the bot you interact with through GitHub comments already (other than it is confusing and doesn't tell you anything about what the bot does)?

The rename hasn't been finalized.

For the name brainstorming: whatever is in writing is public, I recall we made a photo of the whiteboard, too, but I would need to dig through the worklog of the previous summit, and issues linked around it and that archeology need to wait until I have some more time.

[matthewfeickert]

For the name brainstorming: whatever is in writing is public, I recall we made a photo of the whiteboard, too, but I would need to dig through the worklog of the previous summit, and issues linked around it and that archeology need to wait until I have some more time.

To mark off a few places looked so far, the Developer Summit 2023 Worklog doesn't have any mention of the bot at all, nor does the "CI Infrastructure" issue (scientific-python/summit-2023#3). I don't have access to the developer-summit-2023 channel on the Scientific Python Discord server, so maybe the photo you're thinking of is there?

@bsipocz do you remember who else was involved in the renaming discussion with you at the 2023 summit? I'll make the assumption of @Carreau given his majority of the maintainership of the bot.

[Carreau]

I'm not sure it was 100% captured, but there was a rough in-person consensus. I don't have a particular skin in the game wrt renaming. the @mention does not matter, it's regex based so we don't even need a @

[krassowski]

Regardless of the name chosen I would love to have an @mention which is:

• easier/shorter to type than MeseeksDev
• implies that I am calling a bot so that I do not have to explain it to new users each time
• suggested by GitHub back to me so that I do not have to triple check if I spelt it right (which roughly implies having an account named the same as the @mention)

Indeed @editorialbot looks like ticks all the boxes above Format like @editorial-bot would be good too. I also agree that backportbot is not appealing and it would be confusing when it is used for tagging issues with labels.

When I think about this both, i think about it as a "helper", "contributor", "assistant" ("-bot").

I am indifferent to lumberbot, but it is just slightly better than MeseeksDev as it is still opaque to new contributors and non-native speakers of English.

[flying-sheep]

If we keep the @, we must harmonize the app name with the @mention. I really hope for their sake that the account behind @meeseeksdev is inactive, because it’s pretty much unusable for getting all these mentions all the time. I say any name where we can’t actually get the GitHub handle is a non-starter.

Or as @Carreau said: just don’t use the @, e.g. pre-commit.ci accepts commands using pre-commit.ci: do the thing (without the code tag)