which assessment-specific repositories should be moved to this organization

[iantaylor-NOAA]

In the past we've used the lead assessment author's github account to host repositories containing all the files for an assessment (I think that https://github.com/melissamonk-NOAA/China2015 was probably the first). Then the repositories had the files associated with the StockAssessment_template which @melissamonk-NOAA created based on the 2015 China assessment and more recently all the files associated with the {sa4ss} package. We also now often have lots more stuff related to data processing not directly related to the assessment report.

Thanks to @kellijohnson-NOAA, the Lingcod_2021 repo was renamed and moved and is now here as https://github.com/nwfsc-assess/lingcod/.
And @okenk has just created https://github.com/nwfsc-assess/canary here in this organization.

I think that hosting these repos in this organization (whatever we want to call it, see #16) makes sense under the assumption that these assessments are going to be repeated in the future with a different year and different author, but many of the files may not need to change substantially. We can make a tag for each assessment year (plus pre-STAR drafts and whatever else makes sense) to in case revisiting the old state is necessary.

I'm pondering a few questions related to this that others might have thoughts on:

1. I get the pleasure of working on petrale sole in the year ahead. The previous assessment report, https://github.com/chantelwetzel-noaa/Petrale_2019, used the StockAssessment_template rather than sa4ss. Does it still make sense to migrate it over here or just make a fresh start and copy and paste the text as needed?
2. Is it worth migrating any other assessments to this organization that either are or aren't going to be assessed in 2023?
3. For the assessments hosted here, do we need to think about permissions for folks outside this organization who might be contributing to the assessments? There were two folks with access to Lingcod_2021 who got brought in automatically as "Outside collaborators" when the repo was moved and they now have write access just to the renamed lingcod repo (see https://github.com/orgs/nwfsc-assess/people). Does it make sense going forward to just grant collaborators write access to individual repos as needed?

[kellijohnson-NOAA]

1. I think that the choice to migrate a repository should be a direct reflection of should the original repository be deleted. If you can answer yes, then I see no need to migrate it. Just start fresh. If you feel uncomfortable deleting the original repository then to me that means there is information there and a "history" that is useful and should be saved/linked to the newest files.
2. I would like to see all assessment presented to the PFMC migrated to this new organization because it makes it much easier to search across assessments when you can search within an organization.
3. I agree with giving permissions to repositories as needed.

[chantelwetzel-noaa]

The other item that we should think about is notifications. Is there a way to restrict notifications to organization members to only specific repositories? I looked around and did not see anything right away. If we all open our assessment specific repos within this organization the number of notifications, particularly ones that do not pertain to most people, can become quickly overwhelming. However, I do not want to miss any notification on our existing tool repos.

In regard to @iantaylor-NOAA original questions:

1. I would suggest not deleting the petrale_2019 repo immediately since I think it could be useful tool to copy existing text into a new assessment document. After that conversion, I think we could delete the repo under my user account.

[iantaylor-NOAA]

We may be able to create assessment-specific teams within the future pfmc-assessments repo to be the initial default who get push requests for a new repository and therefore get assigned to be watchers by default.

However, a simpler solution may be to always initially create any assessment-specific repo on a personal github account, then add the people who you want to have push access, then move the repo to pfmc-assessments and only those same people will have push access and be watching by default. Others may chose to watch and the original group may choose to unwatch, but it won't default to all 16 members of the organization from the start.