[
https://issues.apache.org/jira/browse/SOLR-16833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793470#comment-17793470
]
Alessandro Benedetti commented on SOLR-16833:
---------------------------------------------
I believe that it is a great idea to have a blog section on the official Solr
website, but my view is that ideally to maximise the amount of content to offer
to the community, it should be an aggregator of blog posts and blogs talking
about Solr rather than a new resource from scratch.
I have no prior knowledge about blog aggregators, but I think it would be
wonderful to have a sort of submission page, PMC reviews and on approval, the
blog is added to the aggregator (and I am talking about the original blog, with
the link, not a copy).
Let me explain from a pragmatic(not provocative) perspective:
More or less the kind of blog authors we are looking at are:
- freelancers - their brand is their person, if they don't have a famous blog
they will be the ideal contributors to a new Solr blog, they will be able to
contribute to the community and get back recognition from that. If they have
their famous blog they will unlikely get involved.
- Small companies people - they already publish on their small company blog,
they are unlikely to get involved
- professionals with a permanent job - they may be happy to contribute in their
spare time or during work, but depending on their company rules, they may not
be allowed to write on blogs that are not their company's blog
My personal view:
I have owned a blog since 2014-ish (that then evolved into Sease's blog) and
I've been leading an initiative at the University of Padua for a couple of
seminars about scientific blogging to encourage students on the matter
(together with professors Gianmaria Silvello and Nicola Ferro).
Given that I do this for a living, whenever I have some time/funding to blog
about Apache Solr I am and I will use my company's blog.
I wrote and funded many blog posts about Apache Solr (as you can imagine my
employees get paid to write our blogs), writing them on my company's blog it's
my way to donate to the community and get back a bit of recognition reinforcing
my company's brand as "Apache Solr specialists".
Just to openly say that I think it is a great idea, but pragmatically in my
opinion we could maximise it if rendered an aggregator (and I guess we can add
blog posts retro-actively because I am pretty sure many would be happy to add
their past blog posts to get more visibility).
My two cents!
> Apache Solr's blog
> ------------------
>
> Key: SOLR-16833
> URL: https://issues.apache.org/jira/browse/SOLR-16833
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Priority: Major
>
> Context: [~dep4b] reached out to me regarding my previous proposal for a
> community blog. Perhaps he wants to spearhead this? Thanks Eric! My dad is
> unwell, so I'll be out of action for another week. This is just a quick
> jotting down of my notes regarding my thoughts, plans.
>
> Proposal:
> Apache Solr should have an official blog. We should blog on the official blog
> often, regarding features, tips/tricks etc. To this effect, [~dsmiley] and I
> agreed over a call that he will volunteer to write frequent Solr news (what
> happened in past month) type posts.
> To set us up with this, I had planned to start a blog seciton on our page,
> using some pelican theme. Unfortunately, life intervened before I could start.
> We should do something like this
> ([https://snipcart.com/blog/pelican-blog-tutorial-search-comments)] and add
> section in our current Solr site (solr-site repo).
> Post that, all posts could be written up as PRs to that repo, and approving
> it can publish the blog post to the site. I think we already have necessary
> plumbing to have staging and prod for the pelican site, so all this should be
> easy to do operationally.
> Another aspect would be that non-committers can also submit PRs to publish
> blog posts, which could be super cool.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
