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

USWDS-Team - Component lifecycle: Create demo proposal repo #333

Closed
3 tasks
Tracked by #5122
amyleadem opened this issue Feb 9, 2023 · 3 comments
Closed
3 tasks
Tracked by #5122

USWDS-Team - Component lifecycle: Create demo proposal repo #333

amyleadem opened this issue Feb 9, 2023 · 3 comments
Assignees
Labels
Type: Task Internal activity

Comments

@amyleadem
Copy link
Contributor

amyleadem commented Feb 9, 2023

Summary

Create a demo proposal repo that includes a proposal template, README, and labels. This will be an area to experiment before moving the repo into the uswds org in #334.

Tasks

  • Explain steps and provide instructions
  • Create proposal template
  • Create README
  • Create list of repo labels

Deliverables

Work in progress

Related work

@amyleadem amyleadem changed the title USWDS - Component lifecycle: Define the RFC/Proposal process USWDS - Component lifecycle: Create proposal template Mar 23, 2023
@amyleadem amyleadem self-assigned this Apr 24, 2023
@amyleadem amyleadem changed the title USWDS - Component lifecycle: Create proposal template USWDS - Component lifecycle: Create proposal template with instructions Jun 2, 2023
@amyleadem amyleadem added the Type: Task Internal activity label Jun 20, 2023
@sarah-sch
Copy link

@amyleadem - I took a quick look at the demo repo. Wow, it looks really great—thank you for all the work you have put into this!

Some minor feedback on the README file:

  • Just the first couple of heading could be more descriptive. Sharing some ideas below, although I am not 100% satisfied with these – would love for others to weigh in:
    o “Overview of the contribution process” instead of “About”
    o “Ways to contribute” instead of “Contribution”
    o “Help with GitHub” instead of “Contribution support”

  • The link to “A proposal template” under “Contribution” (in the bulleted list) is broken

After the success we had with content testing on the critical checklists, I wonder if we could do something similar here. If Jacline doesn’t have the bandwidth, perhaps it is something the content strategy team could help with—although I know we have a lot on our plates right now, so we would need to prioritize as a team.

@amyleadem amyleadem changed the title USWDS - Component lifecycle: Create proposal template with instructions USWDS - Component lifecycle: Create proposal template and README Jun 23, 2023
@amyleadem amyleadem changed the title USWDS - Component lifecycle: Create proposal template and README USWDS - Component lifecycle: Create proposal template and README in demo repo Jul 6, 2023
@amyleadem amyleadem changed the title USWDS - Component lifecycle: Create proposal template and README in demo repo USWDS - Component lifecycle: Create demo proposal template and README in demo repo Jan 22, 2024
@amyleadem amyleadem changed the title USWDS - Component lifecycle: Create demo proposal template and README in demo repo USWDS - Component lifecycle: Create demo proposal repo Jan 22, 2024
@amyleadem amyleadem transferred this issue from uswds/uswds Jan 30, 2024
@amyleadem amyleadem changed the title USWDS - Component lifecycle: Create demo proposal repo USWDS-Team - Component lifecycle: Create demo proposal repo Jan 30, 2024
@brunerae brunerae moved this from Review to Done in USWDS Core Project Data Feb 9, 2024
@brunerae
Copy link

brunerae commented Feb 9, 2024

Decision per 2/6 Component Lifecycle Proposals working session: we'll use Discussions to capture proposals.

See notes in Google Drive (🔒)

@amyleadem
Copy link
Contributor Author

Closing as complete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Task Internal activity
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants