describe process of recruiting new editors for #998

[mpadge]

---

Checklist for dev guide maintainers, do not delete 😸

• Review of the content in the initial language.
• News item.
• Translation of the content in other languages.
• Review of the translations.

[mpadge]

For #998

[maelle]

@mpadge please link this PR to the issue, see https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue

[maelle]

Thank you!!

Please add a news item.

[maelle]

plus the list of guest editors?

[mpadge]

yeah, but we don't have a formal version of that, as far as i know?

[maelle]

See the bottom of https://devguide.ropensci.org/softwarereview_intro.html#editors-and-reviewers for instance. Now I see I have some debugging to do

[maelle]

@mpadge please re-request a review once you've handled all TODOs 😸

[mpadge]

@mpadge please re-request a review once you've handled all TODOs 😸

Thanks, I think that meant just updating booknews, right? Which I've now done. The review checkbox is now what I'll re-request from you, and the other 2 happen after that. I think that's right 🤞

[maelle]

No, there's also:

• describe process of recruiting new editors for #998 #1042 (comment)
• https://github.com/ropensci/dev_guide/pull/1042/changes#r3989358117 i.e. adding that editors are added to this channel, that they're pinged to ensure they understand the context.

Thanks!

[mpadge]

@mpadge please link this PR to the issue, see docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue

Yeah, right, and a huge GRRRR 🐻 from me, because that's a stooopid thing GitHub just kinda dropped. I have always linked from PR titles, like I did here. And that always worked ... until some uncertain, recent time, when somebody decided to switch it off. GRRRR and #998

[mpadge]

• * describe process of recruiting new editors for #998 #1042 (comment)

• * #1042 (changes) i.e. adding that editors are added to this channel, that they're pinged to ensure they understand the context.

👍

[maelle]

@mpadge you now need to add something like Fix #993 at the beginning of your very first comment below the PR title. 😇

[maelle]

can you add a cross ref here? if there's no crossref on that section please add one. After that I will generate the translations, that will have the same crossref IDs.

[mpadge]

@mpadge you now need to add something like Fix #993 at the beginning of your very first comment below the PR title. 😇

Wow, thanks for letting me know. I did the pull-down menu thing, which seems to have done it. Coz that's like, totally heaps easier than just writing the linked issue number in the PR title, of course 😆 Why have humans write things when you can force them to click buttons and navigate nested menu hierarchies?

[maelle]

Not to make you even angrier at the interface but the issue number in the title cannot actually be clicked:

[mpadge]

Blue = clickable, and me = (... no response ...)

I've seen it work. I've seen it not work. I've seen it work on page-scroll, when the title condenses like this:

And I've seen it not work.

And I have no opinions, because that's a waste of my emotional energy that I reserve for other things.

[maelle]

For future PRs: please don't merge main into the PR branch.

[mpadge]

For future PRs: please don't merge main into the PR branch.

Yeah, I got that one now. sorry yet again 🙏