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

Add issue template for local meetup organisers #446

Merged
merged 2 commits into from
Jul 8, 2024

Conversation

Nancy-Chauhan
Copy link
Contributor

This PR updates the issue template for tracking and managing local meetup organization tasks. The new template aims to provide a clear and structured way for organizers to detail their event plans, ensuring all necessary information is included and that the process is streamlined.

Copy link

netlify bot commented Jun 24, 2024

Deploy Preview for tag-env-sustainability ready!

Name Link
🔨 Latest commit c69f40d
🔍 Latest deploy log https://app.netlify.com/sites/tag-env-sustainability/deploys/668914f45b425e0008928728
😎 Deploy Preview https://deploy-preview-446--tag-env-sustainability.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@sunya-ch sunya-ch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for pushing this. I believe it will be helpful for local organizer to onboard the sustainability week event. Leave some comments.

@@ -0,0 +1,62 @@
name: Local Meetup Tracking/Action Item
description: Use this issue type to track and manage local meetup organization tasks. Avoid using this issue type for tasks expected to be closed within hours.
title: "[<Tracking>/<Action>] Cloud Native Sustainability Week 2024 <Meetup Location>"
Copy link
Contributor

@sunya-ch sunya-ch Jun 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How's about replace 2024 with <Year> to keep this general for the later year?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 we can add a <YEAR> field

@@ -0,0 +1,62 @@
name: Local Meetup Tracking/Action Item
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

10-action copy.yaml -> 10-local-meetup.yaml ?

@@ -0,0 +1,62 @@
name: Local Meetup Tracking/Action Item
description: Use this issue type to track and manage local meetup organization tasks. Avoid using this issue type for tasks expected to be closed within hours.
title: "[<Tracking>/<Action>] Cloud Native Sustainability Week 2024 <Meetup Location>"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[<Tracking>/<Action>] -> [Tracking] ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -0,0 +1,62 @@
name: Local Meetup Tracking/Action Item
description: Use this issue type to track and manage local meetup organization tasks. Avoid using this issue type for tasks expected to be closed within hours.
title: "[<Tracking>/<Action>] Cloud Native Sustainability Week 2024 <Meetup Location>"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 we can add a <YEAR> field

@@ -0,0 +1,62 @@
name: Local Meetup Tracking/Action Item
description: Use this issue type to track and manage local meetup organization tasks. Avoid using this issue type for tasks expected to be closed within hours.
title: "[<Tracking>/<Action>] Cloud Native Sustainability Week 2024 <Meetup Location>"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Comment on lines 43 to 44
4. [TAG ENV Lead] Assign lead organizer/co-lead to the issue.
5. Tag leads & co-leads if assistance is needed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we dont need these two steps

Suggested change
4. [TAG ENV Lead] Assign lead organizer/co-lead to the issue.
5. Tag leads & co-leads if assistance is needed.

Comment on lines 35 to 37
type: textarea
attributes:
label: To-Do
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these steps look like checkboxes. (see example CoC)

    type: checkboxes
    attributes:
      label: Code of Conduct
      description: By submitting this issue, you agree to follow our [Code of Conduct](https://www.cncf.io/conduct/).
      options:
        - label: I agree to follow this project's Code of Conduct
          required: true

type: textarea
attributes:
label: To-Do
description: What specific actions are needed to organize this meetup?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could add potentially

  • Joined one of the TAG ENV Sustainability Week Sync to talk about your event
  • Found a sponsor for the event
  • Found a location for the event
  • Set a date for the event
  • Announced the event
  • Reached out to the Cloud Native Sustainability Week Organizer team to promote the event

@leonardpahlke
Copy link
Member

Added a couple of comments @Nancy-Chauhan - thanks! this looks great

Copy link
Member

@leonardpahlke leonardpahlke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, lets refine it over time!

@leonardpahlke leonardpahlke merged commit 8034a94 into cncf:main Jul 8, 2024
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

3 participants