I'd like a command with a link to astro.new and an explanatory text to help people send reproductions. Here is what the text could contain:

• recommend using stackblitz
• explain that you just need a GitHub account
• Keep the reproduction minimal (don't copy-paste all your project code in there)

This is not exhaustive

We have quite a few repos/projects named Houston! It might make sense to talk about this project a little more generically, although our bot in Discord can absolutely be named Houston still 😉

(work in progress, to be updated)

TODO

This repo seems to be missing an open source license - we should add one.

Problem

It is very convenient in Discord to create a survey simply by making a post and pinging a target group then asking to react depending on a choice option. Each emoji counts as one entry from one participant.
It is on the other side very hard to collect those votes or opinions in order to take actions with the target group interested on something.

Solutions

Existing Solutions

Solutions have been suggested to scrape a web browser, but they are not optimal because Discord is smart by lazy loading entries, so an automated scroll and scrape mechanism is needed which si complicated.

Bot Solution

A bot could easily collect the user names and provide them in a list, it is yet to be defined in which form, e.g. command or backend service. A message id would have to be given from which all emojis list votes can be provided.

It would be helpful if we had a command that automates some of the annoying, repetitive parts of posting an announcement about the weekly community call! cc @ElianCodes.

Requirements:

• Role-restricted slash command (@maintainers). Can be posted in any channel.
• Automates the following fields in an embed:
  • WHEN: Localized timestamp when the event begins (a shortcut might be to just use "at the top of the hour")
  • WHERE: Link to the #stage channel (it has historically been #stage OR #chat so this might need to be dynamic?)
    • Possible? Share the link to the existing community call event.
  • WHAT Provide an option to customize the announcement message
    • Optionally, link to the agenda for the call? Could just be part of the message, I guess
  • WHO: Option to ping certain roles or just @notify-events? Default would probably be no pings.

Just an idea, but it would be a nice quality of life improvement for any maintainers to have a /ptal command (PTAL stands for "Please Take a Look").

This command would could accept a few types of links. It would make sense to require at least one link but allow up to three.

• A link to GitHub
• A link to a preview deployment on Vercel or Netlify
• A link to a document on Notion or HackMD

This command could also accept an extended description for the message. If a GitHub link is included, maybe the description and title could be auto-populated from the PR?

The output of this command would be a nicely formatted message with pretty links to the relevant pages. Here are some examples from the Docs, Platform, and UI teams. Currently this is all done manually and the formatting is inconsistent.

We have a well-documented governance process for nominating new members as maintainers/core maintainers for Astro.

These nominations happen in a new thread in the #core or #maintainers channel.

Unfortunately, as the team grows, manually tallying votes becomes increasingly difficult. The process involves hunting down a list of all the currently active maintainers + core, removing any core-in-residency members (no voting privileges), then cross-checking all of the responses to verify that you've correctly recorded everyone's response.

As such, I've been tracking recent nominations in a separate spreadsheet. It'd be nice to have a new /vote command that creates an embed for users to click "Yes / No / Abstain". When a button is pressed, the bot could update an anonymous tally in whatever db we end up using and reply in the thread with the number of votes remaining.

I'm sure there could be further automations in the future, but that seems like a good starting place.

Should trim HTML-comments before posting.

See https://discord.com/channels/830184174198718474/1055240348970000454/1161674261233156177

as this point is important for the development of Houston discord bot, I would like to pin it on an issue so that we can remember it.

Original message idea from @natemoo-re on discord discussion

in the future, we can discuss this point and consider if we either want to stick to github issues to centralize all tasks or if we fallback on another tool less intrusive to the repo and keep github issues for code specific changes, candidates would be creating a github project, although that is also an overhead and yet another place for tasks, we could use the github wiki for both documentation and open tasks at the same place.

This prevents the numerous times I have set the stats report to every second

After feedback, it has become clear that the docs command needs some rethinking. Opened this issue to gather feedback and possible changes