Sounds good Alejandro. You are defining the protocol (with collaborative input). We have freedom to pretty much do as we feel is best. It's not a voted artifact the project/PMC produces (which would have rules / ceremony). If you want to "publish" the newsletter at a certain date & time that is approaching, I recommend that you share a reminder of this a couple days or so in advance so we could have a last chance to edit / discuss. Maybe by default the deadline is simply the last hour of the last day of the month, and you might allow another day or two for you to clean it up as you see fit? If it's not substantial enough, tell us you have made this decision and propose a new possible date so that we know.
I think actual publishing will be simple -- rename the title, provide a date on the page, and send/publish it wherever you wish. ~ David On Wed, Oct 18, 2023 at 2:39 AM Arrieta, Alejandro < aarri...@perrinsoftware.com> wrote: > Hello Team, > > > I'm not very comfortable over-publicizing what I view as a first draft of > >the first edition. > Sure, no problem. Nothing shared. > > >What is 10-20-30 about? > The number of news/links available for that newsletter. We need to decide > on the minimum news (non-relevant, like a new release) to publish the > newsletter. If there is not enough news, we roll over them to next month. > > >At first you seemed super fixed on monthly, here you seem more > >flexible. > If we do not set an internal monthly release goal, it will continue to next > month. But if there is not enough/relevant news for one month, nothing to > do, move to next month. That is why I did not mention "monthly newsletter" > in my draft/proposal, but instead, to start working on the October edition. > > > BTW I just created > >https://cwiki.apache.org/confluence/display/SOLR/Newsletters as a parent > >for the newsletters. > Awesome. :-) > > We need to establish how a draft/proposal becomes official. Maybe there is > already a default protocol, like for the release candidates. > Send the draft/link to wiki to dev the first day of each month and wait YY > hours for votes. If we do not have enough news for that month, inform the > dev and move all news to next month. > > Note: I am just a member of the Solr community trying to help. I may not be > familiar with all the protocols or politics involved. :-) > > Kind Regards, > Alejandro Arrieta > > On Tue, Oct 17, 2023 at 7:49 PM David Smiley <david.w.smi...@gmail.com> > wrote: > > > On Tue, Oct 17, 2023 at 1:01 PM Arrieta, Alejandro < > > aarri...@perrinsoftware.com> wrote: > > > > > > > > Editing: I agree with David's comments. > > > I would add only one thing. The September edition is finished/over > unless > > > something is wrong with it and needs to be fixed. Draft or not draft > that > > > is the September edition. It is better to use our limited time > preparing > > > the October/November > > > > newsletter and make it better than the previous edition. > > > > > > > This is more about periodicity (covered below) than it is about editing. > > > > > > > I will share the September newsletter as Draft/Proposal on my social > > media > > > later today to make Solr noise :-) > > > > > > Publishing: > > > Anywhere it can be indexed by the googles and bings, and > PC/Tablet/Mobile > > > can access it. Solr Wiki is fine. > > > We need to make noise about it everywhere: LinkedIn, Twitter/X, > Mastodon, > > > mailing lists, ASF social media. > > > Here is one example of a newsletter from another project: > > > https://opensearch.org/blog/opensearch-newsletter-vol1-issue1/ > > > > > > There's something to be said for not dating a newsletter, as I see there > in > > the URL of that one. Flexibility. > > > > > > > Brian told me they can share on ASF social media accounts what we need > to > > > share, the newsletter, or a link to the newsletter. ASF publishes at > > least > > > once per one or two weeks project news on Linkedin. We need to send him > > > what and when to share it. > > > > > > > I'm not very comfortable over-publicizing what I view as a first draft of > > the first edition. > > > > I propose that *EITHER* (A): more text be put into the September > > newsletter, not to change the past, only to elaborate what happened in > the > > past :-). Then share it widely. In its current form, I think it's too > > draft-like to be our first inaugural newsletter. It will get attention; > > it's our first one. I want to impress people and not have Solr appear > > second rate simply because you ran out of time Alejandro. OR (B) let's > > make October's newsletter be the awesome one and that which will be > shared > > widely. Not September's newsletter. That is what I would most prefer; > we > > can announce both a new Solr version and also take the opportunity to > > highlight topics discussed at Community-over-Code. WDYT? > > > > > > > Periodicity: > > > -If we have enough news/links to share on the release date (first three > > > days of the month), the threshold can be 10-20-30 news. If we do not > have > > > that many, we do not release and join what we have next month. > > > IMHO, for the first months/releases, we can share old but still > relevant > > > links or highlight Solr documentation. > > > > > > > What is 10-20-30 about? > > > > > > > -If something relevant happens, like a new release or some CVE that we > > need > > > to comment on, we do a release even if we are short of news/links. When > > the > > > next major release process starts, users know Solr 10 is coming. > > > > > > > > Sure. At first you seemed super fixed on monthly, here you seem more > > flexible. Hey whatever. > > > > BTW I just created > > https://cwiki.apache.org/confluence/display/SOLR/Newsletters as a parent > > for the newsletters. > > >
