Add davidwboswell to auto-assign

Signed-off-by: Ry Jones <ry@linux.com>

Author: ryjones

.github/ISSUE_TEMPLATE/project-onboarding.md

@@ -3,7 +3,7 @@ name: Project onboarding for projects
 about: Create a checklist of tasks for a project to complete the onboarding process
 title: "[PROJECT ONBOARDING] PROJECT NAME"
 labels: project onboarding
-assignees: ryjones, jwagantall
+assignees: ryjones, jwagantall, davidwboswell
 ---
 
 This document lists tasks that maintainers need to do to onboard a new project to LFDT.  LFDT staff are here and happy to help with these.
@@ -13,27 +13,27 @@ This document lists tasks that maintainers need to do to onboard a new project t
 Note that many tasks require having a project name picked out, so sorting out branding should be a priority.
 
 - [ ] Pick a name for the project – see our [Naming Guidelines](https://github.com/LF-Decentralized-Trust/wiki/wiki/Naming-Guidelines) for guidance
-- [ ] Pick a logo for the project – you can work with our Marketing Lead on this or design a logo with your own designers. Note that if you design the logo you’ll need to sign a document to transfer the logo to the Linux Foundation so that we can file a trademark application for it.  
-- [ ] Work with LFDT staff to pick a preferred project announcement date~~  
-- [ ] Draft a blog post announcing your project and describe what the project is, why it is being open source and how people can get involved~~  
+- [ ] Pick a logo for the project – you can work with our Marketing Lead on this or design a logo with your own designers. Note that if you design the logo you’ll need to sign a document to transfer the logo to the Linux Foundation so that we can file a trademark application for it.
+- [ ] Work with LFDT staff to pick a preferred project announcement date
+- [ ] Draft a blog post announcing your project and describe what the project is, why it is being open source and how people can get involved
   - [ ] **Optional:** We recommend that project maintainers plan for an introductory virtual meetup a few weeks after the announcement. [Meetup scheduled for Wednesday, October 22](https://www.meetup.com/lfdt-sf/events/311189782).
 
 ### Infrastructure Tasks:
 
-- [ ] Work with LFDT staff to move your project to a LFDT hosted Github organization.  
-  - [ ] Review [TAC’s guidance on Github best](https://lf-decentralized-trust.github.io/governance/guidelines/) practices to follow  
-  - [ ] Review [repository structure](https://lf-decentralized-trust.github.io/governance/governing-documents/repository-structure/) documentation  
-- [ ] Work with LFDT staff to set up Discord channel(s) and public project calls  
+- [ ] Work with LFDT staff to move your project to a LFDT hosted Github organization.
+  - [ ] Review [TAC’s guidance on Github best](https://lf-decentralized-trust.github.io/governance/guidelines/) practices to follow
+  - [ ] Review [repository structure](https://lf-decentralized-trust.github.io/governance/governing-documents/repository-structure/) documentation
+- [ ] Work with LFDT staff to set up Discord channel(s) and public project calls
   - [ ] **Optional:** Set up a mailing list for the project. Most projects don’t use mailing lists, but this is available if you’re interested
 
 ### Governance Tasks:
 
-- [ ] Review [draft project charter](LINK) and propose any edits for LFDT staff to review and approve  
-- [ ] Deal with any other agreements as needed – some projects need a Contribution Agreement or Logo Transfer if they are contributing a previously held name and/or logo for the project 
+- [ ] Review [draft project charter](LINK) and propose any edits for LFDT staff to review and approve
+- [ ] Deal with any other agreements as needed – some projects need a Contribution Agreement or Logo Transfer if they are contributing a previously held name and/or logo for the project
 - [ ] Note that there will be quarterly reports to be filed with the Technical Advisory Council, the group that provides oversight for all LFDT projects. Details about quarterly and annual reports are at: [https://lf-decentralized-trust.github.io/governance/project-updates/](https://lf-decentralized-trust.github.io/governance/project-updates/)
 
 ### Community Engagement Tasks:
 
-- [ ] Work with staff on a community engagement plan. Review the [Raising the Profile of Your Project or Lab presentation](https://docs.google.com/presentation/d/13nji_R-op77ERT-AV3-CbOOZwAOjtvq33RRGnjpL3Gc/edit#slide=id.g389f50bd17_0_59) for examples of activities we can help you with to bring more users and contributors into your project.tab=t.0)  
-- [ ] Consider having at least one PROJECT maintainer nominate themselves for the [2026 Technical Advisory Council election](https://lf-decentralized-trust.github.io/governance/member-info/election-timeline/#nomination-timeline) – nominations open on Oct 13\.  
+- [ ] Work with staff on a community engagement plan. Review the [Raising the Profile of Your Project or Lab presentation](https://docs.google.com/presentation/d/13nji_R-op77ERT-AV3-CbOOZwAOjtvq33RRGnjpL3Gc/edit#slide=id.g389f50bd17_0_59) for examples of activities we can help you with to bring more users and contributors into your project.tab=t.0)
+- [ ] Consider having at least one PROJECT maintainer nominate themselves for the [2026 Technical Advisory Council election](https://lf-decentralized-trust.github.io/governance/member-info/election-timeline/#nomination-timeline) – nominations open on Oct 13\.
 - [ ] Consider having PROJECT maintainers attend [LFDT Maintainer Days in New York on January 26-27](https://github.com/LF-Decentralized-Trust/wiki/wiki/Maintainer-Days) and consider running a session on PROJECT there