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

Convert Suggest a feature or new content for HackforLA.org to Github Form Issue #2293

Open
3 of 11 tasks
adrian-zaragoza opened this issue Sep 21, 2021 · 4 comments
Open
3 of 11 tasks
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Ready for Prioritization role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours

Comments

@adrian-zaragoza
Copy link
Member

adrian-zaragoza commented Sep 21, 2021

Dependency

  • Waiting to see if anyone uses this issue to suggest improvements and the fields we want are stable. When proven stable this issue can be released.

Overview

As an issue creator, we want to implement issue templates for issue creation to streamline and simplify the process. The current issue forms require the person to replace the text, and is less user-friendly compared to GitHub Form issues.

Action Items

  • Add a title to this issue template by changing this line
title: ''

to

title: Suggest a feature or new content for the HackforLA.org website
Partial work for #2293
  • put this issue in icebox, with the following dependency text and unassign yourself.
### Dependency
- [ ] Waiting to see if anyone uses this issue to suggest improvements and the fields we want are stable. When proven stable this issue can be released.
  • Define the form elements and their behavior
    • Review with product and Front End Lead
  • Create a suggest-a-feature-or-new-content-for-hackforla-org.yml file in your own fork in: gh-pages/.github/ISSUE_TEMPLATE
  • Follow GitHub form syntax readings below to code a similar form to the current issue template.
  • Get Sign-off by Product on the proposed template before making a PR
  • Delete suggest-a-feature-or-new-content-for-hackforla-org.md file in this folder
  • Add the person who made the pr to this issue as an additional assignee and then close the issue

Resources/Instructions

@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 21, 2021
@adrian-zaragoza adrian-zaragoza added Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: front end Tasks for front end developers Complexity: Small Take this type of issues after the successful merge of your second good first issue and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 21, 2021
@macho-catt macho-catt added role: back end/devOps Tasks for back-end developers Ready for Prioritization Complexity: Medium and removed role: front end Tasks for front end developers Complexity: Small Take this type of issues after the successful merge of your second good first issue labels Oct 5, 2021
@ExperimentsInHonesty ExperimentsInHonesty added the Dependency An issue is blocking the completion or starting of another issue label Oct 24, 2021
@SAUMILDHANKAR SAUMILDHANKAR added the size: 2pt Can be done in 7-12 hours label Jun 19, 2022
@ExperimentsInHonesty ExperimentsInHonesty added this to the 03.01 Roadmaps milestone Mar 16, 2023
@ExperimentsInHonesty ExperimentsInHonesty added manual dependency release and removed Dependency An issue is blocking the completion or starting of another issue manual dependency release labels Aug 5, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Complexity: Small Take this type of issues after the successful merge of your second good first issue and removed Complexity: Medium ready for product manual dependency release labels Sep 17, 2024
@terrencejihoonjung terrencejihoonjung self-assigned this Sep 21, 2024
@terrencejihoonjung terrencejihoonjung moved this from Prioritized backlog to In progress (actively working) in P: HfLA Website: Project Board Sep 21, 2024
@HackforLABot

This comment was marked as outdated.

@HackforLABot HackforLABot moved this from In progress (actively working) to New Issue Approval in P: HfLA Website: Project Board Sep 21, 2024
@t-will-gillis t-will-gillis added Complexity: Medium and removed Complexity: Small Take this type of issues after the successful merge of your second good first issue labels Sep 29, 2024
@mmcclanahan mmcclanahan self-assigned this Oct 3, 2024
@HackforLABot

This comment was marked as off-topic.

@mmcclanahan

This comment was marked as outdated.

@mmcclanahan mmcclanahan moved this from Prioritized backlog to In progress (actively working) in P: HfLA Website: Project Board Oct 3, 2024
@mmcclanahan mmcclanahan moved this from In progress (actively working) to Ice box in P: HfLA Website: Project Board Oct 5, 2024
@mmcclanahan mmcclanahan removed their assignment Oct 5, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Ice box to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Oct 7, 2024
@floydferrer floydferrer self-assigned this Nov 24, 2024
@HackforLABot
Copy link
Contributor

Hello @floydferrer, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

@HackforLABot HackforLABot moved this from Prioritized backlog to New Issue Approval in P: HfLA Website: Project Board Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Ready for Prioritization role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours
Projects
Status: New Issue Approval
Development

No branches or pull requests

10 participants