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

SSG Staff Meeting: Feb 29, 2024 #4

Open
1 task done
AlexKollar opened this issue Feb 26, 2024 · 3 comments
Open
1 task done

SSG Staff Meeting: Feb 29, 2024 #4

AlexKollar opened this issue Feb 26, 2024 · 3 comments
Labels

Comments

@AlexKollar
Copy link
Contributor

AlexKollar commented Feb 26, 2024

Planning spring scheduled for Feb 29, 2024 at 9:15am

  • Add the event to discord if chillz has not yet.

Main points:

  • Setting up a new structure of organization for SSG. Focusing on The Staff Repo
  • SSG Youtube Channel / Podcast Planning
  • Instilling a heavier focus on the SSG Blog for aggregation of news related to the company.
  • Among other action items.
@AlexKollar AlexKollar converted this from a draft issue Feb 26, 2024
@AlexKollar AlexKollar changed the title SSG Staff Planning SSG Staff Meeting: Feb 29, 2024 Feb 26, 2024
@AlexKollar AlexKollar moved this from Inbox to In progress in SSG Staff Board Feb 26, 2024
@miked1213
Copy link

  • Can we also go over and clearly define what our product/Service is.
  • How will we make money from this product/service
  • pricing for product/service
  • target customer for product/service
  • sales structure

@AlexKollar
Copy link
Contributor Author

  • Can we also go over and clearly define what our product/Service is.

    • How will we make money from this product/service

    • pricing for product/service

    • target customer for product/service

    • sales structure

I feel these are good topics to at the very least discuss.

@AlexKollar
Copy link
Contributor Author

@GamerChillz when the meeting is over today. We should post the notes here once they have been converted to markdown.

This way it's all contained in one setting / area.

As for the blog, we should post a quick TL;DR on the meeting with the link to the full notes which will be here at the bottom under "Read the full meeting notes here" or something to that tune.

Feel free to get creative with what we call the notes.

For a while I was calling them "Patch Notes" when I would post them to discord.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In progress
Development

No branches or pull requests

2 participants