search

MozillaFestival / open-leaders-6

Project tracking repo for Mozilla Open Leader 6
https://foundation.mozilla.org/en/opportunity/mozilla-open-leaders/
Creative Commons Attribution Share Alike 4.0 International
24 stars 7 forks source link

U.S. Forms System #71

Open annekainicUSDS opened 6 years ago

annekainicUSDS commented 6 years ago

Project Lead: @annekainicUSDS

Mentor: @ecleipteon

Welcome to OL6, Cohort C! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training :tada:.

Before Week 1 (Sept 12): Your first mentorship call

Before Week 2 (Sept 19): First Cohort Call (Open by Design)

Before Week 3 (Sept 26): Mentorship call

Before Week 4 (Oct 3): Cohort Call (Build for Understanding)

This issue is here to help you keep track of work during the first month of the program. Please refer to the OL6 Syllabus for more detailed weekly notes and assignments past week 4.

annekainicUSDS commented 6 years ago

Draft vision statement

We are working to improve the most common interaction between the government and the public, completing forms, so that people can better access the services and benefits they need. We are working open because we believe that open-sourcing software in the government, where possible, builds trust, promotes transparency, and ensures the best ideas are shaping our government.

annekainicUSDS commented 6 years ago

Open Canvas

https://docs.google.com/presentation/d/1vNe3QY8NPFSht6BTgLfyS1pUJLlt0AWKwUY3zEV1sM4/edit?usp=sharing

annekainicUSDS commented 6 years ago

Roadmap

Milestone: Completely extract references to original source code

We want our library to be completely separate from the original source code in which it was created. While most of this work was already completed, there are a few remaining items to clean up, captured in the following ticket. #211: Eliminate Vets.gov-isms

Milestone: Reimagine design and architecture of the library

Now that the library is a stand-alone product, what new direction might we want to take it in? How can we rethink some of the original design decisions to make them better and more scalable? #257: Investigate pulling out routing #205: Swappable architecture #203: User research #201: Non-linear navigation #283: Form builder #226: Explore generating pdfs of form output #170: Internationalization #141: Relationship with react-jsonschema-form library

Milestone: Stabilize the code and the process around it

We're still working through issues of publishing, documenting, and relationship with the open community. There are some concrete actions we can take here around this to make our project more stable. #270: New release process #218: Do not commit build artifacts #210: Versioning data and schema #104: What the library is and isn't #200: Reference documentation site #193: Design audit

fraguada commented 6 years ago

Important work you are doing! The vision statement is clear and concise. I've been following the Barcelona government open participation platform 'decidim' develop over the years. While the objective is different than the U.S. Forms System (has more to do with citizen participation in government), I think it is interesting to see governments open sourcing projects.

annekainicUSDS commented 6 years ago

Thanks, @fraguada! Decidim looks very cool, I'm excited to learn more about it.

owenjoseph commented 6 years ago

Hey @fraguada, I came here to browse our cohort's vision statements, and now I'm diving into 'decidim,' which sounds like it has some mission-overlap w/ our project. Thanks for sharing!

@annekainicUSDS Great vision statement - articulates the practicality as well as the immense importance of the project. Awesome!

annekainicUSDS commented 6 years ago

License

License: CC0 Link: https://github.com/usds/us-forms-system/blob/master/package.json#L25

README

Link: https://github.com/usds/us-forms-system/blob/master/README.md