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

ER from TLDL: Think about converting Wins Google Form to a custom form #4387

Closed
7 tasks
Tracked by #4405
JessicaLucindaCheng opened this issue Apr 3, 2023 · 4 comments
Closed
7 tasks
Tracked by #4405
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Wins Page https://www.hackforla.org/wins/ ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours
Milestone

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Apr 3, 2023

TLDL stands for Task List Dev Leads.

Dependency

Emergent Requirement - Problem

Issue Description
Think about converting the Google form to a custom form on the site that we code, but then we would need a backend or way to send data to the Apps Script without revealing secrets. Also, is this already implemented? See:

Note: This was partially from the Wins form research conducted by UX Researcher Vivian

Who was involved

What happens if this is not addressed

We use the existing Google Form for submitting wins.

Resources

Recommended Action Items

  • Discuss with Website Team devs and PMs
  • Make a decision on whether we want to convert the Google Form to a custom form on the site that we code
  • Search and check
    • If an open issue exists that addresses this ER
    • If a closed issue exists that has already addressed this ER
  • If an open issue doesn't exist and this ER wasn't already fixed by a closed issue, make a new issue

Potential solutions [draft]

@JessicaLucindaCheng JessicaLucindaCheng added role: product Product Management Complexity: Large P-Feature: Wins Page https://www.hackforla.org/wins/ size: 1pt Can be done in 4-6 hours ready for product labels Apr 3, 2023
@JessicaLucindaCheng JessicaLucindaCheng changed the title ER from TLDL: Converting Google form to a custom form ER from TLDL: Think about converting Google form to a custom form Apr 3, 2023
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 3, 2023

@JessicaLucindaCheng See what my thoughts are re the various ways this issue could go.

  1. embedding the Google form, so it appears on the page (sure we could do that). I think we already have tried the code, there may have been a reason why we stopped.

  2. Making it an actual form on Jekyll. This will be a feature of the VRMS site in the future (when people become inactive it will ask them if they got jobs, etc.) and the current form works fine.

  3. If there was a way to populate a form with the projects automatically, from our repo, so we didn't have to keep updating it, that would be worth looking into.

@ExperimentsInHonesty ExperimentsInHonesty added role: back end/devOps Tasks for back-end developers ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Apr 3, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone Apr 3, 2023
@JessicaLucindaCheng JessicaLucindaCheng changed the title ER from TLDL: Think about converting Google form to a custom form ER from TLDL: Think about converting Wins Google Form to a custom form Apr 3, 2023
@JessicaLucindaCheng
Copy link
Member Author

Passing this to dev leads because Issues written as a result of ER #4390 will help PM(s) determine whether we convert Wins Google Form to a custom form

@JessicaLucindaCheng JessicaLucindaCheng added Dependency An issue is blocking the completion or starting of another issue and removed role: product Product Management labels Apr 23, 2023
@roslynwythe
Copy link
Member

@JessicaLucindaCheng I added this issue as a dependency on #4405

@JessicaLucindaCheng JessicaLucindaCheng added Issue Making: Level 2 Make issue(s) from an ER or Epic role: dev leads Tasks for technical leads role: back end/devOps Tasks for back-end developers ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: dev leads Tasks for technical leads labels Apr 25, 2023
@roslynwythe
Copy link
Member

roslynwythe commented Jun 2, 2023

@roslynwythe roslynwythe closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level label Oct 10, 2023
@JessicaLucindaCheng JessicaLucindaCheng added the ER Emergent Request label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Wins Page https://www.hackforla.org/wins/ ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours
Projects
Development

No branches or pull requests

3 participants