GitHub user visortelle edited a comment on the discussion: Add more actionable elements to the site homepage
@asafm you asked not to merge any site PRs without approval by a reviewer. Probably, this proposal should also be approved by someone to avoid the extra work. But I have no idea by whom 🤷♂️ Let's say @jak78 or @lhotari gave a 👍 for a proposal. Should I start the implementation? There is no big green "Approve" button in GitHub discussions. Maybe I should go with the dev mailing list, or even with the PIP process? The mailing list is not good for discussions about the site improvements. Without a convenient way to attach images or videos, it's mostly useless. Probably I should cross-link the mailing list thread and the GitHub discussion. But this way we have multiple places where people discuss the same thing and cross-link pages multiple times. I saw that ASF states that mailing lists are good for long-living projects because services like GitHub are born and die, but email is eternal and useful when you need to find something that happened 15 years ago. Maybe it makes sense to just write a tool that periodically dumps GitHub issues and discussions to the mailing list archive format to be sure they are stored forever? Another problem with the dev mailing list is that only developers see it. I would like to see comments and reactions from users too. Users are part of the community! The [email protected] mailing list is rather dead than alive, everyone uses GitHub. I don't think it should be the PIP process for such small site changes. It would take too much time and community resources. For the site, it makes sense to quickly check if some improvement works or not and probably revert the change or find an alternative. If you read this to the end, then thank you for that. The comment turned out to be more than I expected 😆 GitHub link: https://github.com/apache/pulsar/discussions/22189#discussioncomment-8670732 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
