Archive of publicly documented best practices

[jdhoffa]

This issue is meant simply as an archive of any useful practices that have been documented publicly by software teams of repute.

Just because a ticket appears here, does not mean that our team endorses it.

[jdhoffa]

Google:
https://github.com/google/eng-practices

[jdhoffa]

lifecycle R package:

R pkg {lifecycle} has pretty good descriptions of lifecycle stages/states:
https://lifecycle.r-lib.org/articles/stages.html

Thanks @cjyetman

[jdhoffa]

ROpenSci definition of a maintainer:

not necessarily equivalent for us, but this is how ROpenSci defines their "maintainers"
https://ropensci.org/blog/2023/02/07/what-does-it-mean-to-maintain-a-package/

Thanks @cjyetman

[jdhoffa]

tidyverse styleguide:
https://github.com/tidyverse/style

[jdhoffa]

tidyverse design principles:
https://github.com/tidyverse/design

[jdhoffa]

tidyups This is how tidyverse team proposes, discusses and documents potentially large scale changes that affect the whole ecosystem.... @cjyetman this seems like something that could tie in very well and naturally with what we currently do in Tech Reviews?
https://github.com/tidyverse/tidyups?tab=readme-ov-file

[jdhoffa]

code-review This is how the tidyverse team documents their code review standards:
https://github.com/tidyverse/code-review

[jdhoffa]

website-analytics This is how tidyverse tracks their google analytics to determine useful metrics:
https://github.com/tidyverse/website-analytics

[cjyetman]

tidyups This is how tidyverse team proposes, discusses and documents potentially large scale changes that affect the whole ecosystem.... @cjyetman this seems like something that could tie in very well and naturally with what we currently do in Tech Reviews?

https://github.com/tidyverse/tidyups?tab=readme-ov-file

I saw this a while ago... may have subconsciously impacted my "tech proposals" on sharepoint 😁

[jdhoffa]

:-)

I wonder if it's more suitable way to track the tech decisions we come to, than somewhere on SharePoint? I don't know about you but I rarely use sharepoint/ onedrive/ any of the MS file storage things, everything I care about is just on GitHub hahaha

[cjyetman]

:-)

I wonder if it's more suitable way to track the tech decisions we come to, than somewhere on SharePoint? I don't know about you but I rarely use sharepoint/ onedrive/ any of the MS file storage things, everything I care about is just on GitHub hahaha

I'm not opposed to that... I think the main reason I was using SharePoint was for hodie's benefit.