Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add post on spring cleaning #635

Merged
merged 25 commits into from
Jun 7, 2023
Merged

Conversation

ateucher
Copy link
Collaborator

@ateucher ateucher commented Apr 14, 2023

A post describing tidyverse Spring Cleaning and the new public usethis::use_upkeep_issue().

Preview: https://deploy-preview-635--tidyverse-org.netlify.app/blog/2023/06/spring-cleaning-2023/

I'm looking for a better image...

I'm happy to take feedback here on the post, and in the PR for use_upkeep_issue()

@ateucher ateucher marked this pull request as ready for review April 14, 2023 23:24
@ateucher ateucher requested a review from tracykteal April 14, 2023 23:36
@ateucher ateucher requested review from hadley and jennybc April 20, 2023 23:00
Copy link
Member

@jennybc jennybc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One meta point that could possibly be brought out is some of the why. When your maintenance of something is very sporadic, there's the potential for a lot of friction (and dread/procrastination) when you return to a package after a long gap and have to get re-oriented to its idiosyncrasies. Making the occasional pass through (almost) everything, looking for opportunities to adopt current, shared practices can make it easier to dip in and out of different packages.

Part of my point is that this isn't really or only about good practices vs. bad or high quality vs. low. There's some value that comes simply from standardization.


Do you want to actually show an example of what use_upkeep_issue() does?

content/blog/spring-cleaning/index.Rmd Outdated Show resolved Hide resolved
content/blog/spring-cleaning/index.Rmd Outdated Show resolved Hide resolved
Copy link
Member

@hadley hadley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing this up!

content/blog/spring-cleaning/index.Rmd Outdated Show resolved Hide resolved
content/blog/spring-cleaning/index.Rmd Outdated Show resolved Hide resolved
content/blog/spring-cleaning/index.Rmd Outdated Show resolved Hide resolved
content/blog/spring-cleaning/index.Rmd Outdated Show resolved Hide resolved
content/blog/spring-cleaning/index.Rmd Outdated Show resolved Hide resolved
@ateucher
Copy link
Collaborator Author

One meta point that could possibly be brought out is some of the why. When your maintenance of something is very sporadic, there's the potential for a lot of friction (and dread/procrastination) when you return to a package after a long gap and have to get re-oriented to its idiosyncrasies. Making the occasional pass through (almost) everything, looking for opportunities to adopt current, shared practices can make it easier to dip in and out of different packages.

Part of my point is that this isn't really or only about good practices vs. bad or high quality vs. low. There's some value that comes simply from standardization.

@jennybc This is a great point - I added a paragraph in the intro, using a lot of your phrasing.

Do you want to actually show an example of what use_upkeep_issue() does?

Example added at the bottom - what do you think?

Copy link
Member

@tracykteal tracykteal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! I like how you bring in the information about people being able to try thins themselves sooner, and still kept the narrative.

Copy link
Member

@tracykteal tracykteal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes all look good!

@ateucher ateucher merged commit c47025e into tidyverse:main Jun 7, 2023
@ateucher ateucher deleted the spring-cleaning-post branch June 7, 2023 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants