Skip to content

Update Project Profile: GreenEarthOS #8523

Closed
0 of 1 issue completed
Closed

Description

@nadiaspn0503

Overview

The project team from GreenEarthOS needs its project description updated, so that the current project information can be displayed on the Hack for LA website

Action Items

  • Review the Project Update Data below and find the desired changes to the description under "Update the Description?"
  • Create a new issue using the update project description template
  • Customize the title with name of project
  • Customize the body
    • In the ER, go to the value under the line "Project Card URL"
      • Copy the file name
      • On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
    • In the copy blocks below the line that starts, "Find the description variable and change the following:" add the current description text and the new text
    • On the checkbox line below, "- [ ] Verify the changes by viewing..." replace the brackets with the name of the project
    • For resource 2, find the project on the https://www.hackforla.org/projects/ page
      • click on its link
      • copy the page URL
      • replace brackets on resource 2 with the URL
  • Choose Create button
  • Under Relationships, add this epic or ER as a parent to the issue you just created
  • Add milestone 03.02 Onboarding flow
  • Review, and if ready, apply label ready for merge team

When you have completed making the issue to update the description:

  • move this issue into the Questions/Review column
  • add the ready for product label

Project Name

GreenEarthOS

Project Card URL

green-earth-os.md

Update the Title?

NO

Title

No response

Update the Description?

YES

Description

Change GreenEarthOS text so

description: The GreenEarthOS project seeks to create and publish a map of the current climate project support landscape including gaps. Once the landscape has been created the project will work to create visible guidance for open source projects and project ideators on how to navigate the landscape and connect with players at every appropriate stage (recruiting, mentoring, partnerships, packaging and funding) ; thereby reducing barriers to currently under represented communities.

becomes

description: The GreenEarthOS project seeks to create and publish a map of the current climate project support landscape including gaps. Once the landscape has been created the project will work to create visible guidance for open source projects and project ideators on how to navigate the landscape and connect with players at every appropriate stage (recruiting, mentoring, partnerships, packaging, and funding) ; thereby reducing barriers to currently under represented communities.

Update the Hero Image?

NO

Hero Image

No response

Update the Image?

NO

Image

No response

Update the Technologies?

NO

Technologies (maximum 26 characters per technology name)

No response

Update the Partner(s)?

NO

Partners

No response

Update the Tools?

NO

Tools

No response

Update GitHub Link?

NO

GitHub Link

No response

Do you have any additional (other than your primary) GitHub repositories that your volunteers make issues or PRs against?

NO

If yes, list the repo URLs here

No response

Update Slack Link?

NO

Slack Link

No response

Update Test Site Link?

NO

Test Site Link

No response

Update Demo Site Link?

NO

Demo Site Link

No response

Update Site Link?

NO

Site link

No response

Remove person(s) and info from Leadership?

NO

If YES on remove person(s), edit the below to provide the information required. If NO, delete the template in the field below:

Name:

Add person(s) and info to Leadership?

NO

If YES on add person(s), edit the below to provide the information required. If NO, delete the template in the field below:

Name:
GitHub Handle:
Role:
Slack Member ID:

Project Status

On Hold

Additional Instructions for Website Team Leads After This Issue is Submitted (do NOT edit text below)

Here are the instructions for how to process this request to make it ready for issues to be made out of it: #7478 (comment)

Activity

  1. harmeshgv commented on Feb 21, 2026

    @harmeshgv
  2. 14 remaining items

  3. moved this from New Issue Approval to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Boardon May 27, 2026
  4. self-assigned this
    on May 31, 2026
  5. HackforLABot commented on May 31, 2026

    @HackforLABot
    Contributor

    Hi @egcuriel, thank you for taking up this issue! Hfla appreciates you :)

    Do let fellow developers know about your:-
    i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
    ii. ETA: (When do you expect this issue to be completed?)

    You're awesome!

    P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

  6. HackforLABot commented on May 31, 2026

    @HackforLABot
    Contributor

    Hi @egcuriel, thank you for taking up this issue! Hfla appreciates you :)

    Do let fellow developers know about your:-
    i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
    ii. ETA: (When do you expect this issue to be completed?)

    You're awesome!

    P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

  7. egcuriel commented on May 31, 2026

    @egcuriel
    Member

    ETA: 06/02/26 EOD
    Availability: M-Sun (5 pm - 11 pm)

  8. moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Boardon May 31, 2026
  9. moved this from In progress (actively working) to Questions / In Review in P: HfLA Website: Project Boardon Jun 1, 2026
  10. daras-cu commented on Jun 10, 2026

    @daras-cu
    Member

    Thanks for making this issue!

  11. moved this from Questions / In Review to QA in P: HfLA Website: Project Boardon Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelComplexity: SmallTake this type of issues after the successful merge of your second good first issueIssue Making: Level 1Make issues from a template and a spreadsheetP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicready for productrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframe

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions