What exactly does this mean?

I think what Jen had in mind was deleting/removing closed issues when we open source the repo. I don't know if that's a possible or something I think we should do but she asked me to look into it.

It appears that admins can permanently delete issues.

I am not sure if we want to do this since issues may contain historical information and there is no clear benefit to doing this. I think the only thing we want to do is make sure there is no sensitive information mentioned on GitHub but keeping issues should be fine.

I'll let @misskniss @kylecarbs weigh in before closing.

Waiting on response from others before moving forward on this.

Sounds like we don't want to delete closed issues but instead we want to check for any concerning content that shouldn't be public.

The following list of issues either mention sensitive information or a Notion/Shortcut link:

• https://github.com/coder/coder/issues/186
• https://github.com/coder/coder/issues/305
• https://github.com/coder/coder/issues/306
• https://github.com/coder/coder/issues/365
• Replace User Context with User machine #435
• https://github.com/coder/coder/issues/540
• https://github.com/coder/coder/issues/542
• https://github.com/coder/coder/issues/544
• https://github.com/coder/coder/issues/702
• https://github.com/coder/coder/issues/199
• Auto ON/OFF Support #269
• Auto ON/OFF Support #269
• Audit Log Support #277
• https://github.com/coder/coder/issues/367
• Create list for the audit logs we do/not want to show in the frontend #471
• Metrics Support - Enterprise #477
• User Support  #478
• Enterprise Licensing Support  #480
• RBAC Support  #519
• Reusable Visual components  #529
• Integration tests for each UI page  #546
• Separate visual components from glue components  #547
• Side Nav Support #582
• Admin Settings Support  #589
• User Preferences Support #590
• Allow for searching Users #595
• Support bulk edit and delete of users  #597
• Template CRUD - Backend & CLI #635

@bpmct is going to look through PRs and post his list as well.

The following list of PRs either mention sensitive information or a Notion/Shortcut link:

(there are some mentions of coder/m or cdr/m not added here. they do not mention sensitive IP, just implementations we are porting over)

• chore: Add XState machines to model flows #16 - mentions notion
• chore: Add initial jest tests + code coverage #13 - mentions notion
• feat(cdr): Approach 3 - Initial UI (port over cdr/m components) #8 - mentions notion
• refactor: Migrate from Next.js to pure webpack config #360 - mentions notion
• chore: improve coverage of cryptorand package #377 - mentions shortcut (kinda)
• chore: Add AGPLv3 license #841 - license talk

I edited descriptions to remove notion links from descriptions. A few cases that reference a notion link in a comment, but I am not concerned with those.

@tjcran did you edit my list too? I still see some sensitive information.

Also, ICYMI we need to edit these and then delete the revisions (otherwise that information will be visible when we open source).

Thank you both for making the lists like this. We can review the lists in the grooming session today as well if there are remaining questions.
CC: @jsjoeio @bpmct