Sorry; I was/am recovering from COVID and was kind of a sloth in getting to
anything.  Thanks Jason for jumping in to help.  I put a bunch of thought
into this as you'll see below.  And I want to be involved as much as is
welcome.

Alejandro, I can't thank you enough for volunteering for the newsletter.
Coincidentally, Ishan shared the idea of this with me as well but I didn't
act on it.  I think a newsletter is the best communication tool for users
and potential users to get a sense of what's going on with Solr.  This
extends to us Solr committers; we are not always paying attention to
everything happening!  A newsletter could shine a light on such topics as:

* Events (conf, meetup, training, ...)
* Links to new blog/article posts.
       Not sure how to seek these out.  After the wide success of the
newsletter, we can hope people will tell *us* so we don't have to find
them.  The first few newsletters could actively solicit recommendations.
       I don't think we need a centralized place for new blog posts, e.g.
for Solr committers or Alejandro as someone suggested; plenty exist out
there with people posting everywhere already and that won't stop.  We might
want to link to them all in one place though.  Hmmm.
* Everything the PMC announces already (just links or possibly more)
** New Releases
** New committers & PMC members & PMC chair
** Security vulnerabilities
* Give kudos to Solr contributors this period that are not committers.
(just a list of names)
       Could partially automate this with "git log" and more.
* Active areas of development
* Active topics of discussion
* Let committers (or anyone in the community?) send messages to readers
like:
** ex: "who is actually using feature XYZ anyway?  No response means
deprecation!"    <--- yeah there we go, a threat to compel users to
subscribe LOL
** ex: Interest in a meetup for Solr in city X.

Even if it's "just links" (like Alejandro's first draft), it's better than
no newsletter at all.  Over time, we can hope for more.

--------

Jason's questions were spot on.

Editing:  I think everyone with edit access to the Solr "space" in
Confuence (mostly just commiters but + some others) should feel welcome to
add/edit without permission at any time and without coordination.
Confluence has tools to "watch" and see edit history.  Perhaps the
non-published page can be named this clearly like "NEXT-DRAFT" which will
later be renamed to a year-month like dated version once it's published,
and they can all live in one listing (i.e. under one parent page for the
newsletters).  Then treat it as read-only.  A "TEMPLATE" one might exist to
create the next "NEXT-DRAFT".  Alejandro can lead this effort and add much
of the content as he has time for.  He already has the first draft.

Publishing: Not sure either on how it should be published exactly.
Alejandro; what are you thinking?  Personally I think Confluence (in-place)
is fine.  Maybe start this way because it's simple & adequate?  We might
consider somewhere on the Solr website as an alternative.  There are many
places where you could share a link. For some mediums like email, publish
the newsletter content so nobody has to click the link (albeit still
provide it).  Ensure the formatting is reasonable.  Alejandro, where was
Brian Profit proposing that the ASF would share such a thing?  If the
newsletter is mostly a list of links (as it is in its current form, albeit
a draft), I think it should not be shared beyond Solr audiences (i.e. not
beyond users@s.a.o email & slack).

Periodicity:  I worry a little Alejandro if you or others feel this needs
to be monthly, that it'll maybe be too burdensome, or that some months are
simply not that interesting.  I recommend feeling free to be loose on the
periodicity.  Maybe shoot for bi-monthly-ish?  I think publishing soon
after a new release (we just did 9.4!) could be really useful for users
that might just want to pay attention to the newsletter for news on
releases.

Thanks again.  Looking forward to further discussion!

~ David


On Mon, Oct 16, 2023 at 10:17 AM Jason Gerlowski <gerlowsk...@gmail.com>
wrote:

> Hi Alejandro,
>
> Thanks for taking the initiative on this!  You should now have
> permission to create and edit pages in Confluence - let me know if
> you're not seeing that on your end.  Happy to help with some
> copy-editing once it's up there!
>
> Since this is the first of these newsletter proposals, maybe we should
> also use this thread to discuss a few "process" questions around the
> newsletter?  (Or maybe I missed these getting discussed elsewhere?)
>
> The biggest question I was curious about: what does "publication" look
> like for these newsletters?  Will it be published in "Confluence", or
> are we using Confluence for editing before eventually publishing in
> some other medium like annou...@solr.apache.org, the Solr website,
> etc.
>
> Best,
>
> Jason
>
> On Thu, Oct 12, 2023 at 7:09 PM Arrieta, Alejandro
> <aarri...@perrinsoftware.com> wrote:
> >
> > Hello Team,
> >
> > Newsletter on ASF social media:
> > I just returned home from Community over Code, where I talked with the
> > Asfinfra team, and they redirected me to talk with Brian Proffit.
> > I talked with him about the new Solr newsletter, and he told me to send
> him
> > what we want to publish, the date to publish, and the email with a copy
> to
> > the Solr PMC chair.
> > David Smiley, please confirm you are okay so I can email Brian to publish
> > the September 2023 newsletter.
> >
> > Apache Solr wiki newsletter:
> > As discussed during the conference, please give me edit authorization to
> > Solr Wiki to start uploading the newsletter there. My account should be
> > aarrieta and email aarri...@perrinsoftware.com
> >
> > Linkedin Apache Solr account/group:
> > The Asinfra team told me they do not create social media accounts. These
> > are created and managed by each project. We can request templates and
> > publishing guides from pr...@apache.org and mmp group.
> >
> > Kind Regards,
> > Alejandro Arrieta
> >
> >
> > On Tue, Oct 10, 2023 at 9:43 AM Bruno Roustant <bruno.roust...@gmail.com
> >
> > wrote:
> >
> > > +1 !
> > >
> > > Le lun. 9 oct. 2023 à 16:54, Eric Pugh <
> ep...@opensourceconnections.com> a
> > > écrit :
> > >
> > > > I’d love to see it on mastodon/twitterX/linkedin too….   I bet ASF PR
> > > > would love to see this as well ;-)
> > > >
> > > > > On Oct 8, 2023, at 5:36 PM, Alessandro Benedetti <
> a.benede...@sease.io
> > > >
> > > > wrote:
> > > > >
> > > > > +1 I think it's a wonderful idea!
> > > > >
> > > > > On Sun, 8 Oct 2023, 17:26 Arrieta, Alejandro, <
> > > > aarri...@perrinsoftware.com>
> > > > > wrote:
> > > > >
> > > > >> 0. Intro
> > > > >> Welcome to the Apache Solr Newsletter proposal September 2023. As
> this
> > > > is
> > > > >> the first newsletter proposal of 2023 we include Solr Community
> news
> > > > >> starting from January 2023:
> > > > >>
> > > > >> Welcome Alex Deparvu as Solr committer:
> > > > >> https://lists.apache.org/thread/fx4o3y55ypqy1n06kdbq5k8h4pjxlowj
> > > > >>
> > > > >> Welcome Marcus Eagan as Solr committer:
> > > > >> https://lists.apache.org/thread/2p2fjm18g39x2mknxqnbr3gfcx0q6rrx
> > > > >>
> > > > >> Welcome David Smiley as Solr's new PMC chair:
> > > > >> https://lists.apache.org/thread/yrp2yll52r0fm2pbhw17b62oln63fp33
> > > > >>
> > > > >> Welcome Andy Webb as Solr committer:
> > > > >> https://lists.apache.org/thread/k449v7jl4bwg6f7x707tvw5ch2dk8h3f
> > > > >>
> > > > >> Welcome Justin Sweeney as Solr committer:
> > > > >> https://lists.apache.org/thread/g588106pohdwok7gpwwcsxpgvwxwwh41
> > > > >>
> > > > >> Welcome Colvin Cowie as Solr committer:
> > > > >> https://lists.apache.org/thread/ngzjs0b3mb201d2shfvzdysdd5g6xqz1
> > > > >>
> > > > >> 1. Current versions
> > > > >> Solr 9.3.0:
> > > > >> https://solr.apache.org/downloads.html#solr-930
> > > > >>
> > > > >> Solr 8.11.2:
> > > > >> https://solr.apache.org/downloads.html#solr-8112
> > > > >>
> > > > >> Solr Operator v0.7.1:
> > > > >> https://solr.apache.org/operator/artifacts.html#solr-v071
> > > > >>
> > > > >> 2. Incoming versions
> > > > >> Solr 9.4.0
> > > > >> mailing list thread:
> > > > >> https://lists.apache.org/thread/j44golmqp4sjf2rk74pqktkrsc1do58r
> > > > >>
> > > > >> Solr 8.11.3
> > > > >> mailing list thread:
> > > > >> https://lists.apache.org/thread/j44golmqp4sjf2rk74pqktkrsc1do58r
> > > > >>
> > > > >> 3. Solr Improvement Proposals News
> > > > >> SIP-13: Cross Data Center Replication
> > > > >> mailing list thread:
> > > > >> https://lists.apache.org/thread/9y2qd7rs45049xbrt0gty40m4b5cv22y
> > > > >> wiki link:
> > > > >>
> > > > >>
> > > >
> > >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-13%3A+Cross+Data+Center+Replication
> > > > >>
> > > > >> SIP-14 Embedded Zookeeper
> > > > >> mailing list thread:
> > > > >> https://lists.apache.org/thread/mch6y4wsbqykcmfy4r76movmx1wz0375
> > > > >> wiki link:
> > > > >>
> > > >
> > >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-14+Embedded+Zookeeper
> > > > >>
> > > > >> SIP-15 Node roles
> > > > >> mailing list thread:
> > > > >> https://lists.apache.org/thread/kwq609jxckpdqk54fvghxs66jtk92kof
> > > > >> wiki link:
> > > > >>
> https://cwiki.apache.org/confluence/display/SOLR/SIP-15+Node+roles
> > > > >>
> > > > >> SIP-19 Adopt JSR-330 dependency injection
> > > > >> mailing list thread:
> > > > >> https://lists.apache.org/thread/9y2qd7rs45049xbrt0gty40m4b5cv22y
> > > > >> wiki link:
> > > > >>
> > > > >>
> > > >
> > >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-19+Adopt+JSR-330+dependency+injection
> > > > >>
> > > > >> 4. Links to blogs, videos, others related to Solr:
> > > > >> Apache Solr Community Virtual Meetup, September 2023:
> > > > >>
> > > > >>
> > > >
> > >
> https://www.meetup.com/apache-solr-virtual-community-meetups/events/296344421/
> > > > >>
> > > > >> DataImportHandler 9.3.0 released:
> > > > >> https://lists.apache.org/thread/8z65tf4jr2ppdm4xo5r1bygjzt8z8r3f
> > > > >>
> > > > >> 5. Upcoming Events & meetings
> > > > >> ASF Community over Code in Halifax, October 7-10 2023:
> > > > >> https://communityovercode.org/
> > > > >>
> > > > >> Apache Solr Community Virtual Meetup, October 2023:
> > > > >>
> https://www.meetup.com/apache-solr-virtual-community-meetups/events/
> > > > >>
> > > > >> 6. Connect with the Apache Solr Community
> > > > >> Subscribe to Apache Solr Virtual Meetup for monthly meeting:
> > > > >> https://www.meetup.com/apache-solr-virtual-community-meetups/
> > > > >>
> > > > >> Follow us on Twitter/X:
> > > > >> https://twitter.com/apachesolr
> > > > >>
> > > > >> Visit our mailing list, jira, irc and slack:
> > > > >> https://solr.apache.org/community.html
> > > > >>
> > > > >> How to contribute:
> > > > >> https://solr.apache.org/community.html#how-to-contribute
> > > > >>
> > > > >> Apache Solr website:
> > > > >> https://solr.apache.org/
> > > > >>
> > > > >> Apache Solr Operator website:
> > > > >> https://solr.apache.org/operator/
> > > > >>
> > > > >> Note: This is a proposal and I will start working on the October
> 2023
> > > > >> newsletter proposal and create a Jira to accept contributions.
> Maybe
> > > we
> > > > can
> > > > >> publish this on the Apache Solr web if accepted in the future.
> > > > >>
> > > > >> Kind Regards,
> > > > >> Alejandro Arrieta
> > > > >>
> > > >
> > > > _______________________
> > > > Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
> 434.466.1467 |
> > > > http://www.opensourceconnections.com <
> > > > http://www.opensourceconnections.com/> | My Free/Busy <
> > > > http://tinyurl.com/eric-cal>
> > > > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> > > >
> > >
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> > > >
> > > >
> > > > This e-mail and all contents, including attachments, is considered
> to be
> > > > Company Confidential unless explicitly stated otherwise, regardless
> of
> > > > whether attachments are marked as such.
> > > >
> > > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Reply via email to