[
https://issues.apache.org/jira/browse/SOLR-16833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski resolved SOLR-16833.
------------------------------------
Resolution: Fixed
Done, thanks for the reminder Jan!
> Apache Solr's blog
> ------------------
>
> Key: SOLR-16833
> URL: https://issues.apache.org/jira/browse/SOLR-16833
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Assignee: Jason Gerlowski
> Priority: Major
> Attachments: Screenshot 2024-02-21 at 12.05.00 PM.png, Screenshot
> 2024-02-21 at 12.05.10 PM.png, Screenshot 2024-02-21 at 12.05.27 PM.png
>
>
> 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]
