Add more actionable elements to the site homepage #22189
Replies: 4 comments 5 replies
-
|
@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. This page states that I should first discuss the change with the committer https://pulsar.apache.org/contribute/ 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 😆 |
Beta Was this translation helpful? Give feedback.
-
|
On Mar 4, 2024, at 1:56 PM, Kiryl Valkovich 🛸 ***@***.***> wrote:
@asafm <https://github.com/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 <https://github.com/jak78> or @lhotari <https://github.com/lhotari> gave a 👍 for a proposal. Should I start the implementation? There is no big green "Approve" button in GitHub discussions.
This page states that I should discuss the change with the committer https://pulsar.apache.org/contribute/ <https://pulsar.apache.org/contribute/>
In this case apache/pulsar-site#809 (comment) <apache/pulsar-site#809 (comment)> I discussed it with @dave2wave <https://github.com/dave2wave> who is the PMC member.
Maybe I should go with the dev mailing list, or even with the PIP process?
You should discuss open the dev mailing list. And I suggest that you start with the subject “[DISCUSS] ….”. I don’t think a PIP is needed. The dev list preserves the discussion on ASF resources forever.
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.
Definitely link to the GitHub discussion in the email.
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?
We have the ability to send GitHub events to a mailing list. Ask on the dev@ mailing list to start that discussion.
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 ***@***.*** ***@***.***> mailing list is rather dead than alive, everyone uses GitHub.
Anyone can join the dev2 mailing list and at lists.apache.org <http://lists.apache.org/> you will find email from 25 years ago. Source control was typically CVS back then.
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.]
I agree. No PIP.
… If you read this to the end, then thank you for that. The comment turned out to be more than I expected 😆
—
Reply to this email directly, view it on GitHub <#22189 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHDMIYPN7QKT6YA7IZEFXHDYWS7WFAVCNFSM6AAAAABEFA27QOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DMNZQG4ZTE>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
@dave2wave thank you for the clarification. I sent the proposal to the mailing list. |
Beta Was this translation helpful? Give feedback.
-
|
The bar on top: I liked the idea of adding a link to GitHub and Slack. I prefer adding them here: I'm ok with showing how easy it is to spin up Pulsar locally. What were your thoughts on the structure of that section (title, paragraph, etc)? |
Beta Was this translation helpful? Give feedback.
-
Run Pulsar in a single command:
Observe the other deployment options | Helm | Bare metal | Docker | Docker-compose | |
Beta Was this translation helpful? Give feedback.
-
We can use two very different colors or icons for that. |
Beta Was this translation helpful? Give feedback.
-
|
For the title "Run Pulsar in a single command:" how about: "Deploy easily". Regarding the upper bar with GitHub/Slack link: Sorry, I'm not a fan of the idea. Let's see what others think. |
Beta Was this translation helpful? Give feedback.
-
|
I prefer 'Try it out' to 'Deploy easily' because using Pulsar standalone in production deployments is not recommended. |
Beta Was this translation helpful? Give feedback.
-
We can use it as a default announcement bar when there are no upcoming events or other announcements.
Apache Doris
Apache Pinot
Apache Doris
Apache Pinot
In the case of Pulsar, it may be the follwing one-liner:
Apache Pinot
Beta Was this translation helpful? Give feedback.
All reactions