Hi Jonathan, This only represents my opinion. It doesn't present any formal decisions.
In the past few years, the community has tried to make the project website to be focused on the project documentation and releases themselves. We encourage the community members to publish the blog posts including case studies, videos, interviews to different channels to help grow the exposure of the project. We have maintained a resources page <http://pulsar.apache.org/en/resources/> to collect those resources to help people discover those content. Even you are not able to publish the blog post to InfoQ, I would suggest you publish it to the DataStax blog. I would believe the DataStax blog actually has a broader audience than the Pulsar blog. It will actually help the Pulsar community drive more awareness. Once you publish it to the DataStax blog, you can add your link to the Pulsar resources page. - Sijie On Mon, Feb 8, 2021 at 11:02 AM Devin Bost <devin.b...@gmail.com> wrote: > Hi Jonathan, > > Thanks for giving thought to this subject. I think we can all agree that > increasing public awareness of the momentum and community strength behind > Pulsar is a common goal among members of the Pulsar community. I'm sure > many of us have run into similar challenges with increasing adoption of > Pulsar. > > I personally have had success with my videos on Pulsar, but I found that > broadcasting my videos to a wide list of channels was critical to getting > good visibility. (My video where I put the most effort into broadcasting on > numerous channels by leveraging Pulsar’s integration capabilities with > other technologies was by far my most viewed Pulsar video.) > > I think at this point the question is more a matter of how to best > accomplish increasing visibility of Pulsar in the market. > > I wonder if we can get some input from an SEO / web marketing expert on > this subject. > > -- > Devin G. Bost > > On Mon, Feb 8, 2021, 10:17 AM Jonathan Ellis <jbel...@gmail.com> wrote: > > > I checked the ASF mail archives to make sure this went through and > realized > > that somehow gmail stripped all paragraphing from my reply. Trying > again: > > > > I thank Sijie for the comment on my pull request [1]. I’m following up > > here because I think this is the kind of discussion best suited for the > > mailing list. As I understand it, Sijie's core objection is, > > > > “Currently, the community is trying to make the project blog focus on > > project updates such as releases, milestones, and etc, to keep it stay > > focused on the project itself.” > > > > I’m relatively new to Apache Pulsar, so I’m not sure if this represents a > > formal decision by the PMC, or just “the way we’ve done things.” Either > > way, I hope it's okay to revisit it. > > > > In my conversations so far with users and potential users of Pulsar, I > have > > found that our biggest weakness is a perceived lack of maturity. The > best > > way to fix this is to get more visibility on the people who are already > out > > there, successfully using Pulsar to solve interesting problems. “Heavy” > > articles written up at outlets like InfoQ have their place, but so do > > smaller posts like this one that can be produced quickly for a large > > variety of use cases. We need depth *and* breadth. This will let us > > establish the perception that Pulsar is for everyone, not just “experts.” > > > > Incorporating use cases on Pulsar’s own blog lets us take advantage of > one > > of our biggest marketing assets. We want newcomers to get the impression > > as soon as possible that *obviously*, lots of people use Pulsar > > successfully. This is also important for attracting new contributors as > > they see this is something growing and relevant to their interests. If > > they have to go digging for that information elsewhere, we’ve already > lost > > the attention span of a significant number of potential users and > > contributors. > > > > What does the rest of the community think about this? > > > > [1] https://github.com/apache/pulsar/pull/9463 > > > > On Fri, Feb 5, 2021 at 1:06 PM Jonathan Ellis <jbel...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > *I thank Sijie for the comment on my pull request [1]. I’m following > up > > > here because I think this is the kind of discussion best suited for the > > > mailing list. As I understand it, Sijie's core objection > is,“Currently, > > > the community is trying to make the project blog focus on project > updates > > > such as releases, milestones, and etc, to keep it stay focused on the > > > project itself.”I’m relatively new to Apache Pulsar, so I’m not sure if > > > this represents a formal decision by the PMC, or just “the way we’ve > done > > > things.” Either way, I hope it's okay to revisit it.In my > conversations > > so > > > far with users and potential users of Pulsar, I have found that our > > biggest > > > weakness is a perceived lack of maturity. The best way to fix this is > to > > > get more visibility on the people who are already out there, > successfully > > > using Pulsar to solve interesting problems. “Heavy” articles written > up > > at > > > outlets like InfoQ have their place, but so do smaller posts like this > > one > > > that can be produced quickly for a large variety of use cases. We need > > > depth *and* breadth. This will let us establish the perception that > > Pulsar > > > is for everyone, not just “experts.”Incorporating use cases on Pulsar’s > > own > > > blog lets us take advantage of one of our biggest marketing assets. We > > > want newcomers to get the impression as soon as possible that > > *obviously*, > > > lots of people use Pulsar successfully. This is also important for > > > attracting new contributors as they see this is something growing and > > > relevant to their interests. If they have to go digging for that > > > information elsewhere, we’ve already lost the attention span of a > > > significant number of potential users and contributors.What does the > rest > > > of the community think about this?[1] > > > https://github.com/apache/pulsar/pull/9463 > > > <https://github.com/apache/pulsar/pull/9463>* > > > > > > On Wed, Feb 3, 2021 at 5:18 PM Jonathan Ellis <jbel...@gmail.com> > wrote: > > > > > >> Hi all, > > >> > > >> I'd love to see more content on the Apache Pulsar blog showing how > much > > >> traction this project and community have gotten recently. To that > end, > > >> I've started collecting quick "five minute interview" use cases and > I've > > >> submitted a PR for the first. Looking forward to getting more > finished > > up! > > >> > > >> -- > > >> Jonathan Ellis > > >> co-founder, http://www.datastax.com > > >> @spyced > > >> > > > > > > > > > -- > > > Jonathan Ellis > > > co-founder, http://www.datastax.com > > > @spyced > > > > > > > > > -- > > Jonathan Ellis > > co-founder, http://www.datastax.com > > @spyced > > >
