You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Josh Fischer <jo...@joshfischer.io> on 2022/05/02 13:57:07 UTC
Re: Idea: Monthly Members Moment/Critical Committer Communications
The newsletter has been updated and just about ready for sending out.. Not
sure of the whos or hows of getting this across the foundation. Is there
a preferred way that I can get this distributed? Is this something only
a member can/should do?
On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io> wrote:
> We have room for another bullet point or two if anyone wants to add
> anything to the critical committer communications letter. We have about
> two weeks before it will be sent out. Link below.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
>
> - Josh
>
> On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net> wrote:
>
>> On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer <jo...@joshfischer.io> wrote:
>> >
>> > Created a starter with a few fun facts here:
>> > https://cwiki.apache.org/confluence/x/0YyFD
>> >
>> > Feel free to add or take away as you see fit.
>>
>> THANK YOU!
>>
>> > - Josh
>>
>> - Sam Ruby
>>
>> > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby <ru...@intertwingly.net> wrote:
>> >
>> > > Message has been posted. Next time it probably should be a pure plain
>> > > text version.
>> > >
>> > > Anybody want to get started on May? Create the wiki page, put some
>> > > content there, and then send it out the first week in May after others
>> > > have been given the opportunity to contribute.
>> > >
>> > > - Sam Ruby
>> > >
>> > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen <rb...@rcbowen.com>
>> wrote:
>> > > >
>> > > > Problem: Members (and, more generally, committers) are less engaged
>> with
>> > > > the larger Foundation than at any point in our history. Meanwhile,
>> the
>> > > > mechanisms for getting more engaged (eg, the members mailing list)
>> are a
>> > > > firehose of unrelated content that is very frustrating to the casual
>> > > > participant - even those who desire a deeper engagement - and, in
>> > > > practice, are completely off-putting. Committers, meanwhile, have no
>> > > > real avenue, outside of their project, for further engagement.
>> > > >
>> > > > I've been struggling with ways to address this for years, and they
>> all
>> > > > tend to founder on the rocks of "People should just be doing X!"
>> which,
>> > > > in each case, is true, but also dismissive and ultimately unhelpful.
>> > > >
>> > > > I would like to propose that we are more proactive about reaching
>> out to
>> > > > our community in tiny, consumable bites, that hint at a larger feast
>> > > > that they're missing out on.
>> > > >
>> > > > Here's my proposal, but I cannot (and will not) tackle this alone,
>> > > > because that guarantees failure, which guaranteed less
>> participation the
>> > > > next time we suggest something like this.
>> > > >
>> > > > Proposal/Brainstorming doc:
>> https://hackmd.io/JaLaGy56T8qT3ODABLVswA
>> > > >
>> > > > It's an intentionally simple idea - a minimum viable idea, one
>> might say.
>> > > >
>> > > > I want to know who's going to help make it a reality. Not
>> particularly
>> > > > interested in "that's a great idea", as much as "I will help make it
>> > > > happen."
>> > > >
>> > > > This will involve engagement with Events, M&P, and Board, at a
>> minimum,
>> > > > but over time we'd hopefully engage everyone at the Foundation in
>> > > > content creation. But, even then, I want to keep this tiny and
>> > > > consumable - content that you can absorb in 2-5 minutes, always
>> with a
>> > > > "to get more engaged ..." call to action aspect to it.
>> > > >
>> > > > Come help me develop community.
>> > > >
>> > > > --Rich
>> > > >
>> > > >
>> ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> > > > For additional commands, e-mail: dev-help@community.apache.org
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> > > For additional commands, e-mail: dev-help@community.apache.org
>> > >
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Willem Jiang <wi...@gmail.com>.
I just added the CFP information about ApacheCon Asia 2022.
Hope I can catch up with the train this month.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, May 2, 2022 at 11:03 PM Josh Fischer <jo...@joshfischer.io> wrote:
>
> Gotcha. I’ll send it out tomorrow!
>
> On Mon, May 2, 2022 at 9:49 AM Sam Ruby <ru...@intertwingly.net> wrote:
>
> > On Mon, May 2, 2022 at 10:39 AM Josh Fischer <jo...@joshfischer.io> wrote:
> > >
> > > I remember us agreeing to send it out on May 5. Since I'm not a member,
> > > I'll leave that up to either Rich or Sam to send out.
> >
> > I had sent the last one out on the first Tuesday of the month, which
> > happened to be the 5th last month. I'd recommend following a similar
> > pattern as that will avoid weekends. For some months, this may need
> > to be adjusted for holidays.
> >
> > To me, one of the purposes of this exercise is to see if someone other
> > than the usual hyper-volunteers steps up, so I won't be sending the
> > email.
> >
> > But I am a moderator for that list, and if I see content that matches
> > the wiki page in the moderation queue this week, I will approve it.
> > Whether the person sending it is an ASF member or not won't affect
> > whether or not I approve the content.
> >
> > - Sam Ruby
> >
> > > Thank ya
> > >
> > > On Mon, May 2, 2022 at 9:21 AM Rich Bowen <rb...@rcbowen.com> wrote:
> > >
> > > > The last one we sent, Sam sent directly to the members-notify list -
> > > > which does, indeed, need to be done by a member.
> > > >
> > > > I've added one more (member-specific) item to the highlights. I feel
> > > > like we're missing something important, but I cannot remember what it
> > > > is.
> > > >
> > > > What is our send date?
> > > >
> > > > On Mon, 2022-05-02 at 08:57 -0500, Josh Fischer wrote:
> > > > > The newsletter has been updated and just about ready for sending
> > > > > out.. Not
> > > > > sure of the whos or hows of getting this across the foundation. Is
> > > > > there
> > > > > a preferred way that I can get this distributed? Is this something
> > > > > only
> > > > > a member can/should do?
> > > > >
> > > > > On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io>
> > > > > wrote:
> > > > >
> > > > > > We have room for another bullet point or two if anyone wants to add
> > > > > > anything to the critical committer communications letter. We have
> > > > > > about
> > > > > > two weeks before it will be sent out. Link below.
> > > > > >
> > > > > >
> > > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
> > > > > >
> > > > > > - Josh
> > > > > >
> > > > > > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net>
> > > > > > wrote:
> > > > > >
> > > > > > > On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer
> > > > > > > <jo...@joshfischer.io> wrote:
> > > > > > > >
> > > > > > > > Created a starter with a few fun facts here:
> > > > > > > > https://cwiki.apache.org/confluence/x/0YyFD
> > > > > > > >
> > > > > > > > Feel free to add or take away as you see fit.
> > > > > > >
> > > > > > > THANK YOU!
> > > > > > >
> > > > > > > > - Josh
> > > > > > >
> > > > > > > - Sam Ruby
> > > > > > >
> > > > > > > > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby
> > > > > > > > <ru...@intertwingly.net> wrote:
> > > > > > > >
> > > > > > > > > Message has been posted. Next time it probably should be a
> > > > > > > > > pure plain
> > > > > > > > > text version.
> > > > > > > > >
> > > > > > > > > Anybody want to get started on May? Create the wiki page,
> > > > > > > > > put some
> > > > > > > > > content there, and then send it out the first week in May
> > > > > > > > > after others
> > > > > > > > > have been given the opportunity to contribute.
> > > > > > > > >
> > > > > > > > > - Sam Ruby
> > > > > > > > >
> > > > > > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen
> > > > > > > > > <rb...@rcbowen.com>
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Problem: Members (and, more generally, committers) are less
> > > > > > > > > > engaged
> > > > > > > with
> > > > > > > > > > the larger Foundation than at any point in our history.
> > > > > > > > > > Meanwhile,
> > > > > > > the
> > > > > > > > > > mechanisms for getting more engaged (eg, the members
> > > > > > > > > > mailing list)
> > > > > > > are a
> > > > > > > > > > firehose of unrelated content that is very frustrating to
> > > > > > > > > > the casual
> > > > > > > > > > participant - even those who desire a deeper engagement -
> > > > > > > > > > and, in
> > > > > > > > > > practice, are completely off-putting. Committers,
> > > > > > > > > > meanwhile, have no
> > > > > > > > > > real avenue, outside of their project, for further
> > > > > > > > > > engagement.
> > > > > > > > > >
> > > > > > > > > > I've been struggling with ways to address this for years,
> > > > > > > > > > and they
> > > > > > > all
> > > > > > > > > > tend to founder on the rocks of "People should just be
> > > > > > > > > > doing X!"
> > > > > > > which,
> > > > > > > > > > in each case, is true, but also dismissive and ultimately
> > > > > > > > > > unhelpful.
> > > > > > > > > >
> > > > > > > > > > I would like to propose that we are more proactive about
> > > > > > > > > > reaching
> > > > > > > out to
> > > > > > > > > > our community in tiny, consumable bites, that hint at a
> > > > > > > > > > larger feast
> > > > > > > > > > that they're missing out on.
> > > > > > > > > >
> > > > > > > > > > Here's my proposal, but I cannot (and will not) tackle this
> > > > > > > > > > alone,
> > > > > > > > > > because that guarantees failure, which guaranteed less
> > > > > > > participation the
> > > > > > > > > > next time we suggest something like this.
> > > > > > > > > >
> > > > > > > > > > Proposal/Brainstorming doc:
> > > > > > > https://hackmd.io/JaLaGy56T8qT3ODABLVswA
> > > > > > > > > >
> > > > > > > > > > It's an intentionally simple idea - a minimum viable idea,
> > > > > > > > > > one
> > > > > > > might say.
> > > > > > > > > >
> > > > > > > > > > I want to know who's going to help make it a reality. Not
> > > > > > > particularly
> > > > > > > > > > interested in "that's a great idea", as much as "I will
> > > > > > > > > > help make it
> > > > > > > > > > happen."
> > > > > > > > > >
> > > > > > > > > > This will involve engagement with Events, M&P, and Board,
> > > > > > > > > > at a
> > > > > > > minimum,
> > > > > > > > > > but over time we'd hopefully engage everyone at the
> > > > > > > > > > Foundation in
> > > > > > > > > > content creation. But, even then, I want to keep this tiny
> > > > > > > > > > and
> > > > > > > > > > consumable - content that you can absorb in 2-5 minutes,
> > > > > > > > > > always
> > > > > > > with a
> > > > > > > > > > "to get more engaged ..." call to action aspect to it.
> > > > > > > > > >
> > > > > > > > > > Come help me develop community.
> > > > > > > > > >
> > > > > > > > > > --Rich
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > -----------------------------------------------------------------
> > > > > > > ----
> > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > dev-help@community.apache.org
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > -------------------------------------------------------------
> > > > > > > > > --------
> > > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > > > > > For additional commands, e-mail:
> > > > > > > > > dev-help@community.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > > -----------------------------------------------------------------
> > > > > > > ----
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > > > For additional commands, e-mail: dev-help@community.apache.org
> > > > > > >
> > > > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > For additional commands, e-mail: dev-help@community.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> > --
> Sent from A Mobile Device
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Christian Grobmeier <gr...@apache.org>.
Thank you - I will make sure to add a bullet point to the next draft.
On Tue, May 3, 2022, at 12:38, Jarek Potiuk wrote:
> And re: Christian - privacy policy is important :). We can even say that
> some PMCs already converted to Matomo and we wait for others to catch up
> (peer-pressure :D).
> J.
>
> On Tue, May 3, 2022 at 12:35 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
>> I looked through it - I have one other comment/proposal: should we maybe
>> add a digest of discussions running on members@a.o ? I think a lot of
>> people does not follow up those and while it is easy to look at the list in
>> archives, maybe listing the discussions with one-line summary would be good
>> ?
>>
>> Happy to make such a digest if others agree it's a good idea.
>>
>> J.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
And re: Christian - privacy policy is important :). We can even say that
some PMCs already converted to Matomo and we wait for others to catch up
(peer-pressure :D).
J.
On Tue, May 3, 2022 at 12:35 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> I looked through it - I have one other comment/proposal: should we maybe
> add a digest of discussions running on members@a.o ? I think a lot of
> people does not follow up those and while it is easy to look at the list in
> archives, maybe listing the discussions with one-line summary would be good
> ?
>
> Happy to make such a digest if others agree it's a good idea.
>
> J.
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
Happy to take on July one (I have Airflow Summit last week of May so I
expect heavy down/recovery time right after).
On Tue, May 3, 2022 at 9:20 PM Josh Fischer <jo...@joshfischer.io> wrote:
> Yes, I will take point for the June newsletter.
>
>
> On Tue, May 3, 2022 at 2:08 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
> > On Tue, 2022-05-03 at 12:47 -0500, Josh Fischer wrote:
> > > Yeah! Next month let’s work on making the email cleaner. Less is
> > > more
> > > :-). I saw what was sent, it was still a bit much to parse through
> > > and
> > > understand.
> > >
> >
> > Thank you, Josh, for handling this. Are you willing to take point again
> > for June?
> >
> > --Rich
> >
> >
> > > On Tue, May 3, 2022 at 12:35 PM Sam Ruby <ru...@intertwingly.net>
> > > wrote:
> > >
> > > > On Tue, May 3, 2022 at 1:30 PM Craig Russell <ap...@gmail.com>
> > > > wrote:
> > > > >
> > > > > I could not find where we decided whether to use members@ or
> > > > members-notify@ but I approved it.
> > > >
> > > > As did I. :-)
> > > >
> > > > > If anyone objects to the mail list, we can have that discussion
> > > > > for next
> > > > time.
> > > > >
> > > > > Craig
> > > >
> > > > - Sam Ruby
> > > >
> > > > > > On May 3, 2022, at 10:16 AM, Josh Fischer <jo...@joshfischer.io>
> > > > > > wrote:
> > > > > >
> > > > > > sent.
> > > > > >
> > > > > > On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Good idea Rich. Converted all subjects to plain text,
> > > > > > > compressed them
> > > > so
> > > > > > > that they fit in three short bullet points (not too long
> > > > > > > paragraph,
> > > > still
> > > > > > > comprehensible) and added the link from Rich :)
> > > > > > >
> > > > > > >
> > > > > > > On Tue, May 3, 2022 at 6:12 PM Rich Bowen
> > > > > > > <rb...@rcbowen.com> wrote:
> > > > > > >
> > > > > > > > On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > > > > > > > > Sam Ruby, suggested a plain text version for this round
> > > > > > > > > of the
> > > > email.
> > > > > > > > > I
> > > > > > > > > **think** markdown was sent out last time and it didn't
> > > > > > > > > look good,
> > > > > > > > > making
> > > > > > > > > it harder to read/ understand .
> > > > > > > > >
> > > > > > > > > If we can find a way to make all the links easy to read,
> > > > > > > > > let's do
> > > > it.
> > > > > > > > > If
> > > > > > > > > not, we might want to move them to an additional,
> > > > > > > > > external apache
> > > > > > > > > wiki link
> > > > > > > > > page and add a single link directing readers to the
> > > > > > > > > additional link
> > > > > > > > > page.
> > > > > > > > >
> > > > > > > >
> > > > > > > > https://lists.apache.org/list?members@apache.org:2022-4 is
> > > > > > > > a
> > > > possible
> > > > > > > > link to that, in that it lists all of the threads that were
> > > > > > > > active in
> > > > > > > > April.
> > > > > > > >
> > > > > > > > > > You mean the links to text ? We can do it of course but
> > > > > > > > > > I have a
> > > > > > > > > > feeling
> > > > > > > > > > that that defeats the purpose a bit because it allows
> > > > > > > > > > the readers
> > > > > > > > > > to jump
> > > > > > > > > > straight to the discussion :).
> > > > > > > > > > I updated it now to have bullet-points instead - and as
> > > > > > > > > > long as it
> > > > > > > > > > is not
> > > > > > > > > > too long, that might be better visually.
> > > > > > > > > > But if you feel like we need to decrease the number of
> > > > > > > > > > links, I am
> > > > > > > > > > ok with
> > > > > > > > > > removing the links as well.
> > > > > > > > > >
> > > > > > > > > > J.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Tue, May 3, 2022 at 4:56 PM Josh Fischer
> > > > > > > > > > <jo...@joshfischer.io>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Any way we can convert your addition to text? I feel
> > > > > > > > > > > it may be a
> > > > > > > > > > > lot to
> > > > > > > > > > > sift through visually.
> > > > > > > > > > >
> > > > > > > > > > > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk
> > > > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Updated. I think it's cool.
> > > > > > > > > > > > I limited it to only discussions started in April.
> > > > > > > > > > > >
> > > > > > > > > > > > Seems we have a small enough number of discussions
> > > > > > > > > > > > starting
> > > > > > > > > > > > every
> > > > > > > > > > month,
> > > > > > > > > > > to
> > > > > > > > > > > > fit one small paragraph easily - and seeing just
> > > > > > > > > > > > subjects of
> > > > > > > > > > > > the
> > > > > > > > > > > > discussions with links directly to the discussions
> > > > > > > > > > > > might be a
> > > > > > > > > > > > nice
> > > > > > > > > > > > reminder/refresher/information for those who missed
> > > > > > > > > > > > it.
> > > > > > > > > > > >
> > > > > > > > > > > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk
> > > > > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > > One option is to put that digest on a separate
> > > > > > > > > > > > > > page, and
> > > > > > > > > > > > > > just
> > > > > > > > > > > provide a
> > > > > > > > > > > > > link to it?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Or maybe simply put it in one paragraph/long line
> > > > > > > > > > > > > with links
> > > > > > > > > > > > > to
> > > > > > > > > > > relevant
> > > > > > > > > > > > > discussions :). I will try to do it and we can
> > > > > > > > > > > > > decide if it
> > > > > > > > > > > > > makes
> > > > > > > > > > > sense.
> > > > > > > > > > > > > Let me try.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > > > > > > > > > > > <jo...@joshfischer.io>
> > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I plan on sending the newsletter in a few
> > > > > > > > > > > > > > hours. If
> > > > > > > > > > > > > > someone wants
> > > > > > > > > > to
> > > > > > > > > > > > add
> > > > > > > > > > > > > > anymore details please add them asap.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > > > > > > > > > > > > <rb...@rcbowen.com>
> > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Tue, 2022-05-03 at 12:35 +0200, Jarek
> > > > > > > > > > > > > > > Potiuk wrote:
> > > > > > > > > > > > > > > > I looked through it - I have one other
> > > > > > > > > > > > > > > > comment/proposal: should
> > > > > > > > > > we
> > > > > > > > > > > > > > > > maybe
> > > > > > > > > > > > > > > > add a digest of discussions running on
> > > > > > > > > > > > > > > > members@a.o ? I
> > > > > > > > > > > > > > > > think a
> > > > > > > > > > > lot
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > people does not follow up those and while
> > > > > > > > > > > > > > > > it is easy to
> > > > > > > > > > > > > > > > look at
> > > > > > > > > > > the
> > > > > > > > > > > > > > > > list in
> > > > > > > > > > > > > > > > archives, maybe listing the discussions
> > > > > > > > > > > > > > > > with one-line
> > > > > > > > > > > > > > > > summary
> > > > > > > > > > > would
> > > > > > > > > > > > > > > > be good
> > > > > > > > > > > > > > > > ?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Happy to make such a digest if others agree
> > > > > > > > > > > > > > > > it's a good
> > > > > > > > > > > > > > > > idea.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Yes, but ... I think it's very important that
> > > > > > > > > > > > > > > we don't
> > > > > > > > > > > > > > > make the
> > > > > > > > > > > email
> > > > > > > > > > > > > > > longer than one screen-full, as that will
> > > > > > > > > > > > > > > undermine the
> > > > > > > > > > > > > > > point here
> > > > > > > > > > > of
> > > > > > > > > > > > > > > it being only the most important things that
> > > > > > > > > > > > > > > every member
> > > > > > > > > > > > > > > MUST
> > > > > > > > > > know.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > One option is to put that digest on a
> > > > > > > > > > > > > > > separate page, and
> > > > > > > > > > > > > > > just
> > > > > > > > > > > provide
> > > > > > > > > > > > a
> > > > > > > > > > > > > > > link to it?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > -----------------------------------------------------
> > > > > > > > > > > ------------
> > > > > > > > > > > ----
> > > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > > > > dev-help@community.apache.org
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Sent from A Mobile Device
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -----------------------------------------------------------
> > > > > > > > ----------
> > > > > > > > To unsubscribe, e-mail:
> > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > For additional commands, e-mail:
> > > > > > > > dev-help@community.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > > > > Craig L Russell
> > > > > clr@apache.org
> > > > >
> > > > >
> > > > > -----------------------------------------------------------------
> > > > > ----
> > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > For additional commands, e-mail: dev-help@community.apache.org
> > > > >
> > > >
> > > > -------------------------------------------------------------------
> > > > --
> > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > For additional commands, e-mail: dev-help@community.apache.org
> > > >
> > > > --
> > > Sent from A Mobile Device
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> > --
> Sent from A Mobile Device
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
On Tue, 2022-05-03 at 14:20 -0500, Josh Fischer wrote:
> Yes, I will take point for the June newsletter.
Please start a new thread for each month's newsletter. This one is
getting pretty unweildy to search through. :)
Thanks!
--Rich
>
> On Tue, May 3, 2022 at 2:08 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
> > On Tue, 2022-05-03 at 12:47 -0500, Josh Fischer wrote:
> > > Yeah! Next month let’s work on making the email cleaner. Less
> > > is
> > > more
> > > :-). I saw what was sent, it was still a bit much to parse
> > > through
> > > and
> > > understand.
> > >
> >
> > Thank you, Josh, for handling this. Are you willing to take point
> > again
> > for June?
> >
> > --Rich
> >
> >
> > > On Tue, May 3, 2022 at 12:35 PM Sam Ruby <ru...@intertwingly.net>
> > > wrote:
> > >
> > > > On Tue, May 3, 2022 at 1:30 PM Craig Russell
> > > > <ap...@gmail.com>
> > > > wrote:
> > > > >
> > > > > I could not find where we decided whether to use members@ or
> > > > members-notify@ but I approved it.
> > > >
> > > > As did I. :-)
> > > >
> > > > > If anyone objects to the mail list, we can have that
> > > > > discussion
> > > > > for next
> > > > time.
> > > > >
> > > > > Craig
> > > >
> > > > - Sam Ruby
> > > >
> > > > > > On May 3, 2022, at 10:16 AM, Josh Fischer
> > > > > > <jo...@joshfischer.io>
> > > > > > wrote:
> > > > > >
> > > > > > sent.
> > > > > >
> > > > > > On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk
> > > > > > <ja...@potiuk.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Good idea Rich. Converted all subjects to plain text,
> > > > > > > compressed them
> > > > so
> > > > > > > that they fit in three short bullet points (not too long
> > > > > > > paragraph,
> > > > still
> > > > > > > comprehensible) and added the link from Rich :)
> > > > > > >
> > > > > > >
> > > > > > > On Tue, May 3, 2022 at 6:12 PM Rich Bowen
> > > > > > > <rb...@rcbowen.com> wrote:
> > > > > > >
> > > > > > > > On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > > > > > > > > Sam Ruby, suggested a plain text version for this
> > > > > > > > > round
> > > > > > > > > of the
> > > > email.
> > > > > > > > > I
> > > > > > > > > **think** markdown was sent out last time and it
> > > > > > > > > didn't
> > > > > > > > > look good,
> > > > > > > > > making
> > > > > > > > > it harder to read/ understand .
> > > > > > > > >
> > > > > > > > > If we can find a way to make all the links easy to
> > > > > > > > > read,
> > > > > > > > > let's do
> > > > it.
> > > > > > > > > If
> > > > > > > > > not, we might want to move them to an additional,
> > > > > > > > > external apache
> > > > > > > > > wiki link
> > > > > > > > > page and add a single link directing readers to the
> > > > > > > > > additional link
> > > > > > > > > page.
> > > > > > > > >
> > > > > > > >
> > > > > > > > https://lists.apache.org/list?members@apache.org:2022-4
> > > > > > > > is
> > > > > > > > a
> > > > possible
> > > > > > > > link to that, in that it lists all of the threads that
> > > > > > > > were
> > > > > > > > active in
> > > > > > > > April.
> > > > > > > >
> > > > > > > > > > You mean the links to text ? We can do it of course
> > > > > > > > > > but
> > > > > > > > > > I have a
> > > > > > > > > > feeling
> > > > > > > > > > that that defeats the purpose a bit because it
> > > > > > > > > > allows
> > > > > > > > > > the readers
> > > > > > > > > > to jump
> > > > > > > > > > straight to the discussion :).
> > > > > > > > > > I updated it now to have bullet-points instead -
> > > > > > > > > > and as
> > > > > > > > > > long as it
> > > > > > > > > > is not
> > > > > > > > > > too long, that might be better visually.
> > > > > > > > > > But if you feel like we need to decrease the number
> > > > > > > > > > of
> > > > > > > > > > links, I am
> > > > > > > > > > ok with
> > > > > > > > > > removing the links as well.
> > > > > > > > > >
> > > > > > > > > > J.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Tue, May 3, 2022 at 4:56 PM Josh Fischer
> > > > > > > > > > <jo...@joshfischer.io>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Any way we can convert your addition to text? I
> > > > > > > > > > > feel
> > > > > > > > > > > it may be a
> > > > > > > > > > > lot to
> > > > > > > > > > > sift through visually.
> > > > > > > > > > >
> > > > > > > > > > > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk
> > > > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Updated. I think it's cool.
> > > > > > > > > > > > I limited it to only discussions started in
> > > > > > > > > > > > April.
> > > > > > > > > > > >
> > > > > > > > > > > > Seems we have a small enough number of
> > > > > > > > > > > > discussions
> > > > > > > > > > > > starting
> > > > > > > > > > > > every
> > > > > > > > > > month,
> > > > > > > > > > > to
> > > > > > > > > > > > fit one small paragraph easily - and seeing
> > > > > > > > > > > > just
> > > > > > > > > > > > subjects of
> > > > > > > > > > > > the
> > > > > > > > > > > > discussions with links directly to the
> > > > > > > > > > > > discussions
> > > > > > > > > > > > might be a
> > > > > > > > > > > > nice
> > > > > > > > > > > > reminder/refresher/information for those who
> > > > > > > > > > > > missed
> > > > > > > > > > > > it.
> > > > > > > > > > > >
> > > > > > > > > > > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk
> > > > > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > > One option is to put that digest on a
> > > > > > > > > > > > > > separate
> > > > > > > > > > > > > > page, and
> > > > > > > > > > > > > > just
> > > > > > > > > > > provide a
> > > > > > > > > > > > > link to it?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Or maybe simply put it in one paragraph/long
> > > > > > > > > > > > > line
> > > > > > > > > > > > > with links
> > > > > > > > > > > > > to
> > > > > > > > > > > relevant
> > > > > > > > > > > > > discussions :). I will try to do it and we
> > > > > > > > > > > > > can
> > > > > > > > > > > > > decide if it
> > > > > > > > > > > > > makes
> > > > > > > > > > > sense.
> > > > > > > > > > > > > Let me try.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > > > > > > > > > > > <jo...@joshfischer.io>
> > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I plan on sending the newsletter in a few
> > > > > > > > > > > > > > hours. If
> > > > > > > > > > > > > > someone wants
> > > > > > > > > > to
> > > > > > > > > > > > add
> > > > > > > > > > > > > > anymore details please add them asap.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > > > > > > > > > > > > <rb...@rcbowen.com>
> > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Tue, 2022-05-03 at 12:35 +0200, Jarek
> > > > > > > > > > > > > > > Potiuk wrote:
> > > > > > > > > > > > > > > > I looked through it - I have one other
> > > > > > > > > > > > > > > > comment/proposal: should
> > > > > > > > > > we
> > > > > > > > > > > > > > > > maybe
> > > > > > > > > > > > > > > > add a digest of discussions running on
> > > > > > > > > > > > > > > > members@a.o ? I
> > > > > > > > > > > > > > > > think a
> > > > > > > > > > > lot
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > people does not follow up those and
> > > > > > > > > > > > > > > > while
> > > > > > > > > > > > > > > > it is easy to
> > > > > > > > > > > > > > > > look at
> > > > > > > > > > > the
> > > > > > > > > > > > > > > > list in
> > > > > > > > > > > > > > > > archives, maybe listing the discussions
> > > > > > > > > > > > > > > > with one-line
> > > > > > > > > > > > > > > > summary
> > > > > > > > > > > would
> > > > > > > > > > > > > > > > be good
> > > > > > > > > > > > > > > > ?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Happy to make such a digest if others
> > > > > > > > > > > > > > > > agree
> > > > > > > > > > > > > > > > it's a good
> > > > > > > > > > > > > > > > idea.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Yes, but ... I think it's very important
> > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > we don't
> > > > > > > > > > > > > > > make the
> > > > > > > > > > > email
> > > > > > > > > > > > > > > longer than one screen-full, as that will
> > > > > > > > > > > > > > > undermine the
> > > > > > > > > > > > > > > point here
> > > > > > > > > > > of
> > > > > > > > > > > > > > > it being only the most important things
> > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > every member
> > > > > > > > > > > > > > > MUST
> > > > > > > > > > know.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > One option is to put that digest on a
> > > > > > > > > > > > > > > separate page, and
> > > > > > > > > > > > > > > just
> > > > > > > > > > > provide
> > > > > > > > > > > > a
> > > > > > > > > > > > > > > link to it?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > -------------------------------------------------
> > > > > > > > > > > ----
> > > > > > > > > > > ------------
> > > > > > > > > > > ----
> > > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > > > > dev-help@community.apache.org
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Sent from A Mobile Device
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -------------------------------------------------------
> > > > > > > > ----
> > > > > > > > ----------
> > > > > > > > To unsubscribe, e-mail:
> > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > For additional commands, e-mail:
> > > > > > > > dev-help@community.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > > > > Craig L Russell
> > > > > clr@apache.org
> > > > >
> > > > >
> > > > > -------------------------------------------------------------
> > > > > ----
> > > > > ----
> > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > For additional commands, e-mail:
> > > > > dev-help@community.apache.org
> > > > >
> > > >
> > > > ---------------------------------------------------------------
> > > > ----
> > > > --
> > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > For additional commands, e-mail: dev-help@community.apache.org
> > > >
> > > > --
> > > Sent from A Mobile Device
> >
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> > --
> Sent from A Mobile Device
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
Yes, I will take point for the June newsletter.
On Tue, May 3, 2022 at 2:08 PM Rich Bowen <rb...@rcbowen.com> wrote:
> On Tue, 2022-05-03 at 12:47 -0500, Josh Fischer wrote:
> > Yeah! Next month let’s work on making the email cleaner. Less is
> > more
> > :-). I saw what was sent, it was still a bit much to parse through
> > and
> > understand.
> >
>
> Thank you, Josh, for handling this. Are you willing to take point again
> for June?
>
> --Rich
>
>
> > On Tue, May 3, 2022 at 12:35 PM Sam Ruby <ru...@intertwingly.net>
> > wrote:
> >
> > > On Tue, May 3, 2022 at 1:30 PM Craig Russell <ap...@gmail.com>
> > > wrote:
> > > >
> > > > I could not find where we decided whether to use members@ or
> > > members-notify@ but I approved it.
> > >
> > > As did I. :-)
> > >
> > > > If anyone objects to the mail list, we can have that discussion
> > > > for next
> > > time.
> > > >
> > > > Craig
> > >
> > > - Sam Ruby
> > >
> > > > > On May 3, 2022, at 10:16 AM, Josh Fischer <jo...@joshfischer.io>
> > > > > wrote:
> > > > >
> > > > > sent.
> > > > >
> > > > > On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com>
> > > > > wrote:
> > > > >
> > > > > > Good idea Rich. Converted all subjects to plain text,
> > > > > > compressed them
> > > so
> > > > > > that they fit in three short bullet points (not too long
> > > > > > paragraph,
> > > still
> > > > > > comprehensible) and added the link from Rich :)
> > > > > >
> > > > > >
> > > > > > On Tue, May 3, 2022 at 6:12 PM Rich Bowen
> > > > > > <rb...@rcbowen.com> wrote:
> > > > > >
> > > > > > > On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > > > > > > > Sam Ruby, suggested a plain text version for this round
> > > > > > > > of the
> > > email.
> > > > > > > > I
> > > > > > > > **think** markdown was sent out last time and it didn't
> > > > > > > > look good,
> > > > > > > > making
> > > > > > > > it harder to read/ understand .
> > > > > > > >
> > > > > > > > If we can find a way to make all the links easy to read,
> > > > > > > > let's do
> > > it.
> > > > > > > > If
> > > > > > > > not, we might want to move them to an additional,
> > > > > > > > external apache
> > > > > > > > wiki link
> > > > > > > > page and add a single link directing readers to the
> > > > > > > > additional link
> > > > > > > > page.
> > > > > > > >
> > > > > > >
> > > > > > > https://lists.apache.org/list?members@apache.org:2022-4 is
> > > > > > > a
> > > possible
> > > > > > > link to that, in that it lists all of the threads that were
> > > > > > > active in
> > > > > > > April.
> > > > > > >
> > > > > > > > > You mean the links to text ? We can do it of course but
> > > > > > > > > I have a
> > > > > > > > > feeling
> > > > > > > > > that that defeats the purpose a bit because it allows
> > > > > > > > > the readers
> > > > > > > > > to jump
> > > > > > > > > straight to the discussion :).
> > > > > > > > > I updated it now to have bullet-points instead - and as
> > > > > > > > > long as it
> > > > > > > > > is not
> > > > > > > > > too long, that might be better visually.
> > > > > > > > > But if you feel like we need to decrease the number of
> > > > > > > > > links, I am
> > > > > > > > > ok with
> > > > > > > > > removing the links as well.
> > > > > > > > >
> > > > > > > > > J.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, May 3, 2022 at 4:56 PM Josh Fischer
> > > > > > > > > <jo...@joshfischer.io>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Any way we can convert your addition to text? I feel
> > > > > > > > > > it may be a
> > > > > > > > > > lot to
> > > > > > > > > > sift through visually.
> > > > > > > > > >
> > > > > > > > > > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk
> > > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Updated. I think it's cool.
> > > > > > > > > > > I limited it to only discussions started in April.
> > > > > > > > > > >
> > > > > > > > > > > Seems we have a small enough number of discussions
> > > > > > > > > > > starting
> > > > > > > > > > > every
> > > > > > > > > month,
> > > > > > > > > > to
> > > > > > > > > > > fit one small paragraph easily - and seeing just
> > > > > > > > > > > subjects of
> > > > > > > > > > > the
> > > > > > > > > > > discussions with links directly to the discussions
> > > > > > > > > > > might be a
> > > > > > > > > > > nice
> > > > > > > > > > > reminder/refresher/information for those who missed
> > > > > > > > > > > it.
> > > > > > > > > > >
> > > > > > > > > > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk
> > > > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > > One option is to put that digest on a separate
> > > > > > > > > > > > > page, and
> > > > > > > > > > > > > just
> > > > > > > > > > provide a
> > > > > > > > > > > > link to it?
> > > > > > > > > > > >
> > > > > > > > > > > > Or maybe simply put it in one paragraph/long line
> > > > > > > > > > > > with links
> > > > > > > > > > > > to
> > > > > > > > > > relevant
> > > > > > > > > > > > discussions :). I will try to do it and we can
> > > > > > > > > > > > decide if it
> > > > > > > > > > > > makes
> > > > > > > > > > sense.
> > > > > > > > > > > > Let me try.
> > > > > > > > > > > >
> > > > > > > > > > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > > > > > > > > > > <jo...@joshfischer.io>
> > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > I plan on sending the newsletter in a few
> > > > > > > > > > > > > hours. If
> > > > > > > > > > > > > someone wants
> > > > > > > > > to
> > > > > > > > > > > add
> > > > > > > > > > > > > anymore details please add them asap.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > > > > > > > > > > > <rb...@rcbowen.com>
> > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > On Tue, 2022-05-03 at 12:35 +0200, Jarek
> > > > > > > > > > > > > > Potiuk wrote:
> > > > > > > > > > > > > > > I looked through it - I have one other
> > > > > > > > > > > > > > > comment/proposal: should
> > > > > > > > > we
> > > > > > > > > > > > > > > maybe
> > > > > > > > > > > > > > > add a digest of discussions running on
> > > > > > > > > > > > > > > members@a.o ? I
> > > > > > > > > > > > > > > think a
> > > > > > > > > > lot
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > people does not follow up those and while
> > > > > > > > > > > > > > > it is easy to
> > > > > > > > > > > > > > > look at
> > > > > > > > > > the
> > > > > > > > > > > > > > > list in
> > > > > > > > > > > > > > > archives, maybe listing the discussions
> > > > > > > > > > > > > > > with one-line
> > > > > > > > > > > > > > > summary
> > > > > > > > > > would
> > > > > > > > > > > > > > > be good
> > > > > > > > > > > > > > > ?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Happy to make such a digest if others agree
> > > > > > > > > > > > > > > it's a good
> > > > > > > > > > > > > > > idea.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Yes, but ... I think it's very important that
> > > > > > > > > > > > > > we don't
> > > > > > > > > > > > > > make the
> > > > > > > > > > email
> > > > > > > > > > > > > > longer than one screen-full, as that will
> > > > > > > > > > > > > > undermine the
> > > > > > > > > > > > > > point here
> > > > > > > > > > of
> > > > > > > > > > > > > > it being only the most important things that
> > > > > > > > > > > > > > every member
> > > > > > > > > > > > > > MUST
> > > > > > > > > know.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > One option is to put that digest on a
> > > > > > > > > > > > > > separate page, and
> > > > > > > > > > > > > > just
> > > > > > > > > > provide
> > > > > > > > > > > a
> > > > > > > > > > > > > > link to it?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > -----------------------------------------------------
> > > > > > > > > > ------------
> > > > > > > > > > ----
> > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > > > dev-help@community.apache.org
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > Sent from A Mobile Device
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > -----------------------------------------------------------
> > > > > > > ----------
> > > > > > > To unsubscribe, e-mail:
> > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > For additional commands, e-mail:
> > > > > > > dev-help@community.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> > > > Craig L Russell
> > > > clr@apache.org
> > > >
> > > >
> > > > -----------------------------------------------------------------
> > > > ----
> > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > For additional commands, e-mail: dev-help@community.apache.org
> > > >
> > >
> > > -------------------------------------------------------------------
> > > --
> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > For additional commands, e-mail: dev-help@community.apache.org
> > >
> > > --
> > Sent from A Mobile Device
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
> --
Sent from A Mobile Device
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
On Tue, 2022-05-03 at 12:47 -0500, Josh Fischer wrote:
> Yeah! Next month let’s work on making the email cleaner. Less is
> more
> :-). I saw what was sent, it was still a bit much to parse through
> and
> understand.
>
Thank you, Josh, for handling this. Are you willing to take point again
for June?
--Rich
> On Tue, May 3, 2022 at 12:35 PM Sam Ruby <ru...@intertwingly.net>
> wrote:
>
> > On Tue, May 3, 2022 at 1:30 PM Craig Russell <ap...@gmail.com>
> > wrote:
> > >
> > > I could not find where we decided whether to use members@ or
> > members-notify@ but I approved it.
> >
> > As did I. :-)
> >
> > > If anyone objects to the mail list, we can have that discussion
> > > for next
> > time.
> > >
> > > Craig
> >
> > - Sam Ruby
> >
> > > > On May 3, 2022, at 10:16 AM, Josh Fischer <jo...@joshfischer.io>
> > > > wrote:
> > > >
> > > > sent.
> > > >
> > > > On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com>
> > > > wrote:
> > > >
> > > > > Good idea Rich. Converted all subjects to plain text,
> > > > > compressed them
> > so
> > > > > that they fit in three short bullet points (not too long
> > > > > paragraph,
> > still
> > > > > comprehensible) and added the link from Rich :)
> > > > >
> > > > >
> > > > > On Tue, May 3, 2022 at 6:12 PM Rich Bowen
> > > > > <rb...@rcbowen.com> wrote:
> > > > >
> > > > > > On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > > > > > > Sam Ruby, suggested a plain text version for this round
> > > > > > > of the
> > email.
> > > > > > > I
> > > > > > > **think** markdown was sent out last time and it didn't
> > > > > > > look good,
> > > > > > > making
> > > > > > > it harder to read/ understand .
> > > > > > >
> > > > > > > If we can find a way to make all the links easy to read,
> > > > > > > let's do
> > it.
> > > > > > > If
> > > > > > > not, we might want to move them to an additional,
> > > > > > > external apache
> > > > > > > wiki link
> > > > > > > page and add a single link directing readers to the
> > > > > > > additional link
> > > > > > > page.
> > > > > > >
> > > > > >
> > > > > > https://lists.apache.org/list?members@apache.org:2022-4 is
> > > > > > a
> > possible
> > > > > > link to that, in that it lists all of the threads that were
> > > > > > active in
> > > > > > April.
> > > > > >
> > > > > > > > You mean the links to text ? We can do it of course but
> > > > > > > > I have a
> > > > > > > > feeling
> > > > > > > > that that defeats the purpose a bit because it allows
> > > > > > > > the readers
> > > > > > > > to jump
> > > > > > > > straight to the discussion :).
> > > > > > > > I updated it now to have bullet-points instead - and as
> > > > > > > > long as it
> > > > > > > > is not
> > > > > > > > too long, that might be better visually.
> > > > > > > > But if you feel like we need to decrease the number of
> > > > > > > > links, I am
> > > > > > > > ok with
> > > > > > > > removing the links as well.
> > > > > > > >
> > > > > > > > J.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, May 3, 2022 at 4:56 PM Josh Fischer
> > > > > > > > <jo...@joshfischer.io>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Any way we can convert your addition to text? I feel
> > > > > > > > > it may be a
> > > > > > > > > lot to
> > > > > > > > > sift through visually.
> > > > > > > > >
> > > > > > > > > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk
> > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Updated. I think it's cool.
> > > > > > > > > > I limited it to only discussions started in April.
> > > > > > > > > >
> > > > > > > > > > Seems we have a small enough number of discussions
> > > > > > > > > > starting
> > > > > > > > > > every
> > > > > > > > month,
> > > > > > > > > to
> > > > > > > > > > fit one small paragraph easily - and seeing just
> > > > > > > > > > subjects of
> > > > > > > > > > the
> > > > > > > > > > discussions with links directly to the discussions
> > > > > > > > > > might be a
> > > > > > > > > > nice
> > > > > > > > > > reminder/refresher/information for those who missed
> > > > > > > > > > it.
> > > > > > > > > >
> > > > > > > > > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk
> > > > > > > > > > <ja...@potiuk.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > > One option is to put that digest on a separate
> > > > > > > > > > > > page, and
> > > > > > > > > > > > just
> > > > > > > > > provide a
> > > > > > > > > > > link to it?
> > > > > > > > > > >
> > > > > > > > > > > Or maybe simply put it in one paragraph/long line
> > > > > > > > > > > with links
> > > > > > > > > > > to
> > > > > > > > > relevant
> > > > > > > > > > > discussions :). I will try to do it and we can
> > > > > > > > > > > decide if it
> > > > > > > > > > > makes
> > > > > > > > > sense.
> > > > > > > > > > > Let me try.
> > > > > > > > > > >
> > > > > > > > > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > > > > > > > > > <jo...@joshfischer.io>
> > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I plan on sending the newsletter in a few
> > > > > > > > > > > > hours. If
> > > > > > > > > > > > someone wants
> > > > > > > > to
> > > > > > > > > > add
> > > > > > > > > > > > anymore details please add them asap.
> > > > > > > > > > > >
> > > > > > > > > > > > On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > > > > > > > > > > <rb...@rcbowen.com>
> > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > On Tue, 2022-05-03 at 12:35 +0200, Jarek
> > > > > > > > > > > > > Potiuk wrote:
> > > > > > > > > > > > > > I looked through it - I have one other
> > > > > > > > > > > > > > comment/proposal: should
> > > > > > > > we
> > > > > > > > > > > > > > maybe
> > > > > > > > > > > > > > add a digest of discussions running on
> > > > > > > > > > > > > > members@a.o ? I
> > > > > > > > > > > > > > think a
> > > > > > > > > lot
> > > > > > > > > > > > > > of
> > > > > > > > > > > > > > people does not follow up those and while
> > > > > > > > > > > > > > it is easy to
> > > > > > > > > > > > > > look at
> > > > > > > > > the
> > > > > > > > > > > > > > list in
> > > > > > > > > > > > > > archives, maybe listing the discussions
> > > > > > > > > > > > > > with one-line
> > > > > > > > > > > > > > summary
> > > > > > > > > would
> > > > > > > > > > > > > > be good
> > > > > > > > > > > > > > ?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Happy to make such a digest if others agree
> > > > > > > > > > > > > > it's a good
> > > > > > > > > > > > > > idea.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Yes, but ... I think it's very important that
> > > > > > > > > > > > > we don't
> > > > > > > > > > > > > make the
> > > > > > > > > email
> > > > > > > > > > > > > longer than one screen-full, as that will
> > > > > > > > > > > > > undermine the
> > > > > > > > > > > > > point here
> > > > > > > > > of
> > > > > > > > > > > > > it being only the most important things that
> > > > > > > > > > > > > every member
> > > > > > > > > > > > > MUST
> > > > > > > > know.
> > > > > > > > > > > > >
> > > > > > > > > > > > > One option is to put that digest on a
> > > > > > > > > > > > > separate page, and
> > > > > > > > > > > > > just
> > > > > > > > > provide
> > > > > > > > > > a
> > > > > > > > > > > > > link to it?
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > -----------------------------------------------------
> > > > > > > > > ------------
> > > > > > > > > ----
> > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > > dev-help@community.apache.org
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > Sent from A Mobile Device
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > > -----------------------------------------------------------
> > > > > > ----------
> > > > > > To unsubscribe, e-mail:
> > > > > > dev-unsubscribe@community.apache.org
> > > > > > For additional commands, e-mail:
> > > > > > dev-help@community.apache.org
> > > > > >
> > > > > >
> > > > >
> > >
> > > Craig L Russell
> > > clr@apache.org
> > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > For additional commands, e-mail: dev-help@community.apache.org
> > >
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> > --
> Sent from A Mobile Device
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
+1
On Tue, May 3, 2022 at 7:47 PM Josh Fischer <jo...@joshfischer.io> wrote:
> Yeah! Next month let’s work on making the email cleaner. Less is more
> :-). I saw what was sent, it was still a bit much to parse through and
> understand.
>
>
>
>
>
> On Tue, May 3, 2022 at 12:35 PM Sam Ruby <ru...@intertwingly.net> wrote:
>
> > On Tue, May 3, 2022 at 1:30 PM Craig Russell <ap...@gmail.com>
> wrote:
> > >
> > > I could not find where we decided whether to use members@ or
> > members-notify@ but I approved it.
> >
> > As did I. :-)
> >
> > > If anyone objects to the mail list, we can have that discussion for
> next
> > time.
> > >
> > > Craig
> >
> > - Sam Ruby
> >
> > > > On May 3, 2022, at 10:16 AM, Josh Fischer <jo...@joshfischer.io>
> wrote:
> > > >
> > > > sent.
> > > >
> > > > On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com>
> wrote:
> > > >
> > > >> Good idea Rich. Converted all subjects to plain text, compressed
> them
> > so
> > > >> that they fit in three short bullet points (not too long paragraph,
> > still
> > > >> comprehensible) and added the link from Rich :)
> > > >>
> > > >>
> > > >> On Tue, May 3, 2022 at 6:12 PM Rich Bowen <rb...@rcbowen.com>
> wrote:
> > > >>
> > > >>> On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > > >>>> Sam Ruby, suggested a plain text version for this round of the
> > email.
> > > >>>> I
> > > >>>> **think** markdown was sent out last time and it didn't look good,
> > > >>>> making
> > > >>>> it harder to read/ understand .
> > > >>>>
> > > >>>> If we can find a way to make all the links easy to read, let's do
> > it.
> > > >>>> If
> > > >>>> not, we might want to move them to an additional, external apache
> > > >>>> wiki link
> > > >>>> page and add a single link directing readers to the additional
> link
> > > >>>> page.
> > > >>>>
> > > >>>
> > > >>> https://lists.apache.org/list?members@apache.org:2022-4 is a
> > possible
> > > >>> link to that, in that it lists all of the threads that were active
> in
> > > >>> April.
> > > >>>
> > > >>>>> You mean the links to text ? We can do it of course but I have a
> > > >>>>> feeling
> > > >>>>> that that defeats the purpose a bit because it allows the readers
> > > >>>>> to jump
> > > >>>>> straight to the discussion :).
> > > >>>>> I updated it now to have bullet-points instead - and as long as
> it
> > > >>>>> is not
> > > >>>>> too long, that might be better visually.
> > > >>>>> But if you feel like we need to decrease the number of links, I
> am
> > > >>>>> ok with
> > > >>>>> removing the links as well.
> > > >>>>>
> > > >>>>> J.
> > > >>>>>
> > > >>>>>
> > > >>>>> On Tue, May 3, 2022 at 4:56 PM Josh Fischer <josh@joshfischer.io
> >
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> Any way we can convert your addition to text? I feel it may be
> a
> > > >>>>>> lot to
> > > >>>>>> sift through visually.
> > > >>>>>>
> > > >>>>>> On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com>
> > > >>>>>> wrote:
> > > >>>>>>
> > > >>>>>>> Updated. I think it's cool.
> > > >>>>>>> I limited it to only discussions started in April.
> > > >>>>>>>
> > > >>>>>>> Seems we have a small enough number of discussions starting
> > > >>>>>>> every
> > > >>>>> month,
> > > >>>>>> to
> > > >>>>>>> fit one small paragraph easily - and seeing just subjects of
> > > >>>>>>> the
> > > >>>>>>> discussions with links directly to the discussions might be a
> > > >>>>>>> nice
> > > >>>>>>> reminder/refresher/information for those who missed it.
> > > >>>>>>>
> > > >>>>>>> On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com>
> > > >>>>>>> wrote:
> > > >>>>>>>
> > > >>>>>>>>> One option is to put that digest on a separate page, and
> > > >>>>>>>>> just
> > > >>>>>> provide a
> > > >>>>>>>> link to it?
> > > >>>>>>>>
> > > >>>>>>>> Or maybe simply put it in one paragraph/long line with links
> > > >>>>>>>> to
> > > >>>>>> relevant
> > > >>>>>>>> discussions :). I will try to do it and we can decide if it
> > > >>>>>>>> makes
> > > >>>>>> sense.
> > > >>>>>>>> Let me try.
> > > >>>>>>>>
> > > >>>>>>>> On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > >>>>>>>> <jo...@joshfischer.io>
> > > >>>>>> wrote:
> > > >>>>>>>>
> > > >>>>>>>>> I plan on sending the newsletter in a few hours. If
> > > >>>>>>>>> someone wants
> > > >>>>> to
> > > >>>>>>> add
> > > >>>>>>>>> anymore details please add them asap.
> > > >>>>>>>>>
> > > >>>>>>>>> On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > >>>>>>>>> <rb...@rcbowen.com>
> > > >>>>> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>>> On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > > >>>>>>>>>>> I looked through it - I have one other
> > > >>>>>>>>>>> comment/proposal: should
> > > >>>>> we
> > > >>>>>>>>>>> maybe
> > > >>>>>>>>>>> add a digest of discussions running on members@a.o ? I
> > > >>>>>>>>>>> think a
> > > >>>>>> lot
> > > >>>>>>>>>>> of
> > > >>>>>>>>>>> people does not follow up those and while it is easy to
> > > >>>>>>>>>>> look at
> > > >>>>>> the
> > > >>>>>>>>>>> list in
> > > >>>>>>>>>>> archives, maybe listing the discussions with one-line
> > > >>>>>>>>>>> summary
> > > >>>>>> would
> > > >>>>>>>>>>> be good
> > > >>>>>>>>>>> ?
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Happy to make such a digest if others agree it's a good
> > > >>>>>>>>>>> idea.
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> Yes, but ... I think it's very important that we don't
> > > >>>>>>>>>> make the
> > > >>>>>> email
> > > >>>>>>>>>> longer than one screen-full, as that will undermine the
> > > >>>>>>>>>> point here
> > > >>>>>> of
> > > >>>>>>>>>> it being only the most important things that every member
> > > >>>>>>>>>> MUST
> > > >>>>> know.
> > > >>>>>>>>>>
> > > >>>>>>>>>> One option is to put that digest on a separate page, and
> > > >>>>>>>>>> just
> > > >>>>>> provide
> > > >>>>>>> a
> > > >>>>>>>>>> link to it?
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>
> -----------------------------------------------------------------
> > > >>>>>> ----
> > > >>>>>>>>>> To unsubscribe, e-mail:
> > > >>>>>>>>>> dev-unsubscribe@community.apache.org
> > > >>>>>>>>>> For additional commands, e-mail:
> > > >>>>>>>>>> dev-help@community.apache.org
> > > >>>>>>>>>>
> > > >>>>>>>>>> --
> > > >>>>>>>>> Sent from A Mobile Device
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>
> > > >>>
> > > >>>
> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > >>> For additional commands, e-mail: dev-help@community.apache.org
> > > >>>
> > > >>>
> > > >>
> > >
> > > Craig L Russell
> > > clr@apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > For additional commands, e-mail: dev-help@community.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> > --
> Sent from A Mobile Device
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
Yeah! Next month let’s work on making the email cleaner. Less is more
:-). I saw what was sent, it was still a bit much to parse through and
understand.
On Tue, May 3, 2022 at 12:35 PM Sam Ruby <ru...@intertwingly.net> wrote:
> On Tue, May 3, 2022 at 1:30 PM Craig Russell <ap...@gmail.com> wrote:
> >
> > I could not find where we decided whether to use members@ or
> members-notify@ but I approved it.
>
> As did I. :-)
>
> > If anyone objects to the mail list, we can have that discussion for next
> time.
> >
> > Craig
>
> - Sam Ruby
>
> > > On May 3, 2022, at 10:16 AM, Josh Fischer <jo...@joshfischer.io> wrote:
> > >
> > > sent.
> > >
> > > On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > >> Good idea Rich. Converted all subjects to plain text, compressed them
> so
> > >> that they fit in three short bullet points (not too long paragraph,
> still
> > >> comprehensible) and added the link from Rich :)
> > >>
> > >>
> > >> On Tue, May 3, 2022 at 6:12 PM Rich Bowen <rb...@rcbowen.com> wrote:
> > >>
> > >>> On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > >>>> Sam Ruby, suggested a plain text version for this round of the
> email.
> > >>>> I
> > >>>> **think** markdown was sent out last time and it didn't look good,
> > >>>> making
> > >>>> it harder to read/ understand .
> > >>>>
> > >>>> If we can find a way to make all the links easy to read, let's do
> it.
> > >>>> If
> > >>>> not, we might want to move them to an additional, external apache
> > >>>> wiki link
> > >>>> page and add a single link directing readers to the additional link
> > >>>> page.
> > >>>>
> > >>>
> > >>> https://lists.apache.org/list?members@apache.org:2022-4 is a
> possible
> > >>> link to that, in that it lists all of the threads that were active in
> > >>> April.
> > >>>
> > >>>>> You mean the links to text ? We can do it of course but I have a
> > >>>>> feeling
> > >>>>> that that defeats the purpose a bit because it allows the readers
> > >>>>> to jump
> > >>>>> straight to the discussion :).
> > >>>>> I updated it now to have bullet-points instead - and as long as it
> > >>>>> is not
> > >>>>> too long, that might be better visually.
> > >>>>> But if you feel like we need to decrease the number of links, I am
> > >>>>> ok with
> > >>>>> removing the links as well.
> > >>>>>
> > >>>>> J.
> > >>>>>
> > >>>>>
> > >>>>> On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Any way we can convert your addition to text? I feel it may be a
> > >>>>>> lot to
> > >>>>>> sift through visually.
> > >>>>>>
> > >>>>>> On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> Updated. I think it's cool.
> > >>>>>>> I limited it to only discussions started in April.
> > >>>>>>>
> > >>>>>>> Seems we have a small enough number of discussions starting
> > >>>>>>> every
> > >>>>> month,
> > >>>>>> to
> > >>>>>>> fit one small paragraph easily - and seeing just subjects of
> > >>>>>>> the
> > >>>>>>> discussions with links directly to the discussions might be a
> > >>>>>>> nice
> > >>>>>>> reminder/refresher/information for those who missed it.
> > >>>>>>>
> > >>>>>>> On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com>
> > >>>>>>> wrote:
> > >>>>>>>
> > >>>>>>>>> One option is to put that digest on a separate page, and
> > >>>>>>>>> just
> > >>>>>> provide a
> > >>>>>>>> link to it?
> > >>>>>>>>
> > >>>>>>>> Or maybe simply put it in one paragraph/long line with links
> > >>>>>>>> to
> > >>>>>> relevant
> > >>>>>>>> discussions :). I will try to do it and we can decide if it
> > >>>>>>>> makes
> > >>>>>> sense.
> > >>>>>>>> Let me try.
> > >>>>>>>>
> > >>>>>>>> On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > >>>>>>>> <jo...@joshfischer.io>
> > >>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>>> I plan on sending the newsletter in a few hours. If
> > >>>>>>>>> someone wants
> > >>>>> to
> > >>>>>>> add
> > >>>>>>>>> anymore details please add them asap.
> > >>>>>>>>>
> > >>>>>>>>> On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > >>>>>>>>> <rb...@rcbowen.com>
> > >>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > >>>>>>>>>>> I looked through it - I have one other
> > >>>>>>>>>>> comment/proposal: should
> > >>>>> we
> > >>>>>>>>>>> maybe
> > >>>>>>>>>>> add a digest of discussions running on members@a.o ? I
> > >>>>>>>>>>> think a
> > >>>>>> lot
> > >>>>>>>>>>> of
> > >>>>>>>>>>> people does not follow up those and while it is easy to
> > >>>>>>>>>>> look at
> > >>>>>> the
> > >>>>>>>>>>> list in
> > >>>>>>>>>>> archives, maybe listing the discussions with one-line
> > >>>>>>>>>>> summary
> > >>>>>> would
> > >>>>>>>>>>> be good
> > >>>>>>>>>>> ?
> > >>>>>>>>>>>
> > >>>>>>>>>>> Happy to make such a digest if others agree it's a good
> > >>>>>>>>>>> idea.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> Yes, but ... I think it's very important that we don't
> > >>>>>>>>>> make the
> > >>>>>> email
> > >>>>>>>>>> longer than one screen-full, as that will undermine the
> > >>>>>>>>>> point here
> > >>>>>> of
> > >>>>>>>>>> it being only the most important things that every member
> > >>>>>>>>>> MUST
> > >>>>> know.
> > >>>>>>>>>>
> > >>>>>>>>>> One option is to put that digest on a separate page, and
> > >>>>>>>>>> just
> > >>>>>> provide
> > >>>>>>> a
> > >>>>>>>>>> link to it?
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>> -----------------------------------------------------------------
> > >>>>>> ----
> > >>>>>>>>>> To unsubscribe, e-mail:
> > >>>>>>>>>> dev-unsubscribe@community.apache.org
> > >>>>>>>>>> For additional commands, e-mail:
> > >>>>>>>>>> dev-help@community.apache.org
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>> Sent from A Mobile Device
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > >>> For additional commands, e-mail: dev-help@community.apache.org
> > >>>
> > >>>
> > >>
> >
> > Craig L Russell
> > clr@apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
> --
Sent from A Mobile Device
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Sam Ruby <ru...@intertwingly.net>.
On Tue, May 3, 2022 at 1:30 PM Craig Russell <ap...@gmail.com> wrote:
>
> I could not find where we decided whether to use members@ or members-notify@ but I approved it.
As did I. :-)
> If anyone objects to the mail list, we can have that discussion for next time.
>
> Craig
- Sam Ruby
> > On May 3, 2022, at 10:16 AM, Josh Fischer <jo...@joshfischer.io> wrote:
> >
> > sent.
> >
> > On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> >> Good idea Rich. Converted all subjects to plain text, compressed them so
> >> that they fit in three short bullet points (not too long paragraph, still
> >> comprehensible) and added the link from Rich :)
> >>
> >>
> >> On Tue, May 3, 2022 at 6:12 PM Rich Bowen <rb...@rcbowen.com> wrote:
> >>
> >>> On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> >>>> Sam Ruby, suggested a plain text version for this round of the email.
> >>>> I
> >>>> **think** markdown was sent out last time and it didn't look good,
> >>>> making
> >>>> it harder to read/ understand .
> >>>>
> >>>> If we can find a way to make all the links easy to read, let's do it.
> >>>> If
> >>>> not, we might want to move them to an additional, external apache
> >>>> wiki link
> >>>> page and add a single link directing readers to the additional link
> >>>> page.
> >>>>
> >>>
> >>> https://lists.apache.org/list?members@apache.org:2022-4 is a possible
> >>> link to that, in that it lists all of the threads that were active in
> >>> April.
> >>>
> >>>>> You mean the links to text ? We can do it of course but I have a
> >>>>> feeling
> >>>>> that that defeats the purpose a bit because it allows the readers
> >>>>> to jump
> >>>>> straight to the discussion :).
> >>>>> I updated it now to have bullet-points instead - and as long as it
> >>>>> is not
> >>>>> too long, that might be better visually.
> >>>>> But if you feel like we need to decrease the number of links, I am
> >>>>> ok with
> >>>>> removing the links as well.
> >>>>>
> >>>>> J.
> >>>>>
> >>>>>
> >>>>> On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io>
> >>>>> wrote:
> >>>>>
> >>>>>> Any way we can convert your addition to text? I feel it may be a
> >>>>>> lot to
> >>>>>> sift through visually.
> >>>>>>
> >>>>>> On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Updated. I think it's cool.
> >>>>>>> I limited it to only discussions started in April.
> >>>>>>>
> >>>>>>> Seems we have a small enough number of discussions starting
> >>>>>>> every
> >>>>> month,
> >>>>>> to
> >>>>>>> fit one small paragraph easily - and seeing just subjects of
> >>>>>>> the
> >>>>>>> discussions with links directly to the discussions might be a
> >>>>>>> nice
> >>>>>>> reminder/refresher/information for those who missed it.
> >>>>>>>
> >>>>>>> On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>>> One option is to put that digest on a separate page, and
> >>>>>>>>> just
> >>>>>> provide a
> >>>>>>>> link to it?
> >>>>>>>>
> >>>>>>>> Or maybe simply put it in one paragraph/long line with links
> >>>>>>>> to
> >>>>>> relevant
> >>>>>>>> discussions :). I will try to do it and we can decide if it
> >>>>>>>> makes
> >>>>>> sense.
> >>>>>>>> Let me try.
> >>>>>>>>
> >>>>>>>> On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> >>>>>>>> <jo...@joshfischer.io>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> I plan on sending the newsletter in a few hours. If
> >>>>>>>>> someone wants
> >>>>> to
> >>>>>>> add
> >>>>>>>>> anymore details please add them asap.
> >>>>>>>>>
> >>>>>>>>> On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> >>>>>>>>> <rb...@rcbowen.com>
> >>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> >>>>>>>>>>> I looked through it - I have one other
> >>>>>>>>>>> comment/proposal: should
> >>>>> we
> >>>>>>>>>>> maybe
> >>>>>>>>>>> add a digest of discussions running on members@a.o ? I
> >>>>>>>>>>> think a
> >>>>>> lot
> >>>>>>>>>>> of
> >>>>>>>>>>> people does not follow up those and while it is easy to
> >>>>>>>>>>> look at
> >>>>>> the
> >>>>>>>>>>> list in
> >>>>>>>>>>> archives, maybe listing the discussions with one-line
> >>>>>>>>>>> summary
> >>>>>> would
> >>>>>>>>>>> be good
> >>>>>>>>>>> ?
> >>>>>>>>>>>
> >>>>>>>>>>> Happy to make such a digest if others agree it's a good
> >>>>>>>>>>> idea.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Yes, but ... I think it's very important that we don't
> >>>>>>>>>> make the
> >>>>>> email
> >>>>>>>>>> longer than one screen-full, as that will undermine the
> >>>>>>>>>> point here
> >>>>>> of
> >>>>>>>>>> it being only the most important things that every member
> >>>>>>>>>> MUST
> >>>>> know.
> >>>>>>>>>>
> >>>>>>>>>> One option is to put that digest on a separate page, and
> >>>>>>>>>> just
> >>>>>> provide
> >>>>>>> a
> >>>>>>>>>> link to it?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> -----------------------------------------------------------------
> >>>>>> ----
> >>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>> dev-unsubscribe@community.apache.org
> >>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>> dev-help@community.apache.org
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>> Sent from A Mobile Device
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >>> For additional commands, e-mail: dev-help@community.apache.org
> >>>
> >>>
> >>
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
Agree. Makes perfect sense Bertrand. The reason for members-notify@ is very
clearly stated in the minutes and it's not that :).
J.
On Wed, May 4, 2022 at 10:26 AM Bertrand Delacretaz <bd...@apache.org>
wrote:
> -Hi,
>
> Le mar. 3 mai 2022 à 19:31, Craig Russell <ap...@gmail.com> a écrit :
> > I could not find where we decided whether to use members@ or
> members-notify@ but I approved it.
> > If anyone objects to the mail list, we can have that discussion for next
> time....
>
> I do object to using members-notify@ for those news, as that's outside of
> the scope defined at [1]. That list was created "for the limited purpose of
> sending formal notifications to the membership as a whole", because some
> members clearly expressed their objection to getting "too much email" from
> the ASF.
>
> Another objection has been raised on board@, let's discuss there.
>
> Going forward I suggest sending to members@ with a [NEWS] subject line
> header. And don't get me wrong, I like this initiative!
>
> -Bertrand
>
>
> [1]
>
> https://www.apache.org/foundation/records/minutes/2020/board_minutes_2020_05_20.txt
> - search for "members-notify"
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Bertrand Delacretaz <bd...@apache.org>.
-Hi,
Le mar. 3 mai 2022 à 19:31, Craig Russell <ap...@gmail.com> a écrit :
> I could not find where we decided whether to use members@ or
members-notify@ but I approved it.
> If anyone objects to the mail list, we can have that discussion for next
time....
I do object to using members-notify@ for those news, as that's outside of
the scope defined at [1]. That list was created "for the limited purpose of
sending formal notifications to the membership as a whole", because some
members clearly expressed their objection to getting "too much email" from
the ASF.
Another objection has been raised on board@, let's discuss there.
Going forward I suggest sending to members@ with a [NEWS] subject line
header. And don't get me wrong, I like this initiative!
-Bertrand
[1]
https://www.apache.org/foundation/records/minutes/2020/board_minutes_2020_05_20.txt
- search for "members-notify"
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Craig Russell <ap...@gmail.com>.
I could not find where we decided whether to use members@ or members-notify@ but I approved it.
If anyone objects to the mail list, we can have that discussion for next time.
Craig
> On May 3, 2022, at 10:16 AM, Josh Fischer <jo...@joshfischer.io> wrote:
>
> sent.
>
> On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
>> Good idea Rich. Converted all subjects to plain text, compressed them so
>> that they fit in three short bullet points (not too long paragraph, still
>> comprehensible) and added the link from Rich :)
>>
>>
>> On Tue, May 3, 2022 at 6:12 PM Rich Bowen <rb...@rcbowen.com> wrote:
>>
>>> On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
>>>> Sam Ruby, suggested a plain text version for this round of the email.
>>>> I
>>>> **think** markdown was sent out last time and it didn't look good,
>>>> making
>>>> it harder to read/ understand .
>>>>
>>>> If we can find a way to make all the links easy to read, let's do it.
>>>> If
>>>> not, we might want to move them to an additional, external apache
>>>> wiki link
>>>> page and add a single link directing readers to the additional link
>>>> page.
>>>>
>>>
>>> https://lists.apache.org/list?members@apache.org:2022-4 is a possible
>>> link to that, in that it lists all of the threads that were active in
>>> April.
>>>
>>>>> You mean the links to text ? We can do it of course but I have a
>>>>> feeling
>>>>> that that defeats the purpose a bit because it allows the readers
>>>>> to jump
>>>>> straight to the discussion :).
>>>>> I updated it now to have bullet-points instead - and as long as it
>>>>> is not
>>>>> too long, that might be better visually.
>>>>> But if you feel like we need to decrease the number of links, I am
>>>>> ok with
>>>>> removing the links as well.
>>>>>
>>>>> J.
>>>>>
>>>>>
>>>>> On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io>
>>>>> wrote:
>>>>>
>>>>>> Any way we can convert your addition to text? I feel it may be a
>>>>>> lot to
>>>>>> sift through visually.
>>>>>>
>>>>>> On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Updated. I think it's cool.
>>>>>>> I limited it to only discussions started in April.
>>>>>>>
>>>>>>> Seems we have a small enough number of discussions starting
>>>>>>> every
>>>>> month,
>>>>>> to
>>>>>>> fit one small paragraph easily - and seeing just subjects of
>>>>>>> the
>>>>>>> discussions with links directly to the discussions might be a
>>>>>>> nice
>>>>>>> reminder/refresher/information for those who missed it.
>>>>>>>
>>>>>>> On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>> One option is to put that digest on a separate page, and
>>>>>>>>> just
>>>>>> provide a
>>>>>>>> link to it?
>>>>>>>>
>>>>>>>> Or maybe simply put it in one paragraph/long line with links
>>>>>>>> to
>>>>>> relevant
>>>>>>>> discussions :). I will try to do it and we can decide if it
>>>>>>>> makes
>>>>>> sense.
>>>>>>>> Let me try.
>>>>>>>>
>>>>>>>> On Tue, May 3, 2022 at 2:44 PM Josh Fischer
>>>>>>>> <jo...@joshfischer.io>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I plan on sending the newsletter in a few hours. If
>>>>>>>>> someone wants
>>>>> to
>>>>>>> add
>>>>>>>>> anymore details please add them asap.
>>>>>>>>>
>>>>>>>>> On Tue, May 3, 2022 at 7:39 AM Rich Bowen
>>>>>>>>> <rb...@rcbowen.com>
>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
>>>>>>>>>>> I looked through it - I have one other
>>>>>>>>>>> comment/proposal: should
>>>>> we
>>>>>>>>>>> maybe
>>>>>>>>>>> add a digest of discussions running on members@a.o ? I
>>>>>>>>>>> think a
>>>>>> lot
>>>>>>>>>>> of
>>>>>>>>>>> people does not follow up those and while it is easy to
>>>>>>>>>>> look at
>>>>>> the
>>>>>>>>>>> list in
>>>>>>>>>>> archives, maybe listing the discussions with one-line
>>>>>>>>>>> summary
>>>>>> would
>>>>>>>>>>> be good
>>>>>>>>>>> ?
>>>>>>>>>>>
>>>>>>>>>>> Happy to make such a digest if others agree it's a good
>>>>>>>>>>> idea.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Yes, but ... I think it's very important that we don't
>>>>>>>>>> make the
>>>>>> email
>>>>>>>>>> longer than one screen-full, as that will undermine the
>>>>>>>>>> point here
>>>>>> of
>>>>>>>>>> it being only the most important things that every member
>>>>>>>>>> MUST
>>>>> know.
>>>>>>>>>>
>>>>>>>>>> One option is to put that digest on a separate page, and
>>>>>>>>>> just
>>>>>> provide
>>>>>>> a
>>>>>>>>>> link to it?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> ----
>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>> dev-unsubscribe@community.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> dev-help@community.apache.org
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>> Sent from A Mobile Device
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>>
>>
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
sent.
On Tue, May 3, 2022 at 12:05 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> Good idea Rich. Converted all subjects to plain text, compressed them so
> that they fit in three short bullet points (not too long paragraph, still
> comprehensible) and added the link from Rich :)
>
>
> On Tue, May 3, 2022 at 6:12 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
> > On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > > Sam Ruby, suggested a plain text version for this round of the email.
> > > I
> > > **think** markdown was sent out last time and it didn't look good,
> > > making
> > > it harder to read/ understand .
> > >
> > > If we can find a way to make all the links easy to read, let's do it.
> > > If
> > > not, we might want to move them to an additional, external apache
> > > wiki link
> > > page and add a single link directing readers to the additional link
> > > page.
> > >
> >
> > https://lists.apache.org/list?members@apache.org:2022-4 is a possible
> > link to that, in that it lists all of the threads that were active in
> > April.
> >
> > > > You mean the links to text ? We can do it of course but I have a
> > > > feeling
> > > > that that defeats the purpose a bit because it allows the readers
> > > > to jump
> > > > straight to the discussion :).
> > > > I updated it now to have bullet-points instead - and as long as it
> > > > is not
> > > > too long, that might be better visually.
> > > > But if you feel like we need to decrease the number of links, I am
> > > > ok with
> > > > removing the links as well.
> > > >
> > > > J.
> > > >
> > > >
> > > > On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io>
> > > > wrote:
> > > >
> > > > > Any way we can convert your addition to text? I feel it may be a
> > > > > lot to
> > > > > sift through visually.
> > > > >
> > > > > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com>
> > > > > wrote:
> > > > >
> > > > > > Updated. I think it's cool.
> > > > > > I limited it to only discussions started in April.
> > > > > >
> > > > > > Seems we have a small enough number of discussions starting
> > > > > > every
> > > > month,
> > > > > to
> > > > > > fit one small paragraph easily - and seeing just subjects of
> > > > > > the
> > > > > > discussions with links directly to the discussions might be a
> > > > > > nice
> > > > > > reminder/refresher/information for those who missed it.
> > > > > >
> > > > > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com>
> > > > > > wrote:
> > > > > >
> > > > > > > > One option is to put that digest on a separate page, and
> > > > > > > > just
> > > > > provide a
> > > > > > > link to it?
> > > > > > >
> > > > > > > Or maybe simply put it in one paragraph/long line with links
> > > > > > > to
> > > > > relevant
> > > > > > > discussions :). I will try to do it and we can decide if it
> > > > > > > makes
> > > > > sense.
> > > > > > > Let me try.
> > > > > > >
> > > > > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > > > > > <jo...@joshfischer.io>
> > > > > wrote:
> > > > > > >
> > > > > > > > I plan on sending the newsletter in a few hours. If
> > > > > > > > someone wants
> > > > to
> > > > > > add
> > > > > > > > anymore details please add them asap.
> > > > > > > >
> > > > > > > > On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > > > > > > <rb...@rcbowen.com>
> > > > wrote:
> > > > > > > >
> > > > > > > > > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > > > > > > > > > I looked through it - I have one other
> > > > > > > > > > comment/proposal: should
> > > > we
> > > > > > > > > > maybe
> > > > > > > > > > add a digest of discussions running on members@a.o ? I
> > > > > > > > > > think a
> > > > > lot
> > > > > > > > > > of
> > > > > > > > > > people does not follow up those and while it is easy to
> > > > > > > > > > look at
> > > > > the
> > > > > > > > > > list in
> > > > > > > > > > archives, maybe listing the discussions with one-line
> > > > > > > > > > summary
> > > > > would
> > > > > > > > > > be good
> > > > > > > > > > ?
> > > > > > > > > >
> > > > > > > > > > Happy to make such a digest if others agree it's a good
> > > > > > > > > > idea.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Yes, but ... I think it's very important that we don't
> > > > > > > > > make the
> > > > > email
> > > > > > > > > longer than one screen-full, as that will undermine the
> > > > > > > > > point here
> > > > > of
> > > > > > > > > it being only the most important things that every member
> > > > > > > > > MUST
> > > > know.
> > > > > > > > >
> > > > > > > > > One option is to put that digest on a separate page, and
> > > > > > > > > just
> > > > > provide
> > > > > > a
> > > > > > > > > link to it?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > -----------------------------------------------------------------
> > > > > ----
> > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > > For additional commands, e-mail:
> > > > > > > > > dev-help@community.apache.org
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > Sent from A Mobile Device
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> >
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
Good idea Rich. Converted all subjects to plain text, compressed them so
that they fit in three short bullet points (not too long paragraph, still
comprehensible) and added the link from Rich :)
On Tue, May 3, 2022 at 6:12 PM Rich Bowen <rb...@rcbowen.com> wrote:
> On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> > Sam Ruby, suggested a plain text version for this round of the email.
> > I
> > **think** markdown was sent out last time and it didn't look good,
> > making
> > it harder to read/ understand .
> >
> > If we can find a way to make all the links easy to read, let's do it.
> > If
> > not, we might want to move them to an additional, external apache
> > wiki link
> > page and add a single link directing readers to the additional link
> > page.
> >
>
> https://lists.apache.org/list?members@apache.org:2022-4 is a possible
> link to that, in that it lists all of the threads that were active in
> April.
>
> > > You mean the links to text ? We can do it of course but I have a
> > > feeling
> > > that that defeats the purpose a bit because it allows the readers
> > > to jump
> > > straight to the discussion :).
> > > I updated it now to have bullet-points instead - and as long as it
> > > is not
> > > too long, that might be better visually.
> > > But if you feel like we need to decrease the number of links, I am
> > > ok with
> > > removing the links as well.
> > >
> > > J.
> > >
> > >
> > > On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io>
> > > wrote:
> > >
> > > > Any way we can convert your addition to text? I feel it may be a
> > > > lot to
> > > > sift through visually.
> > > >
> > > > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com>
> > > > wrote:
> > > >
> > > > > Updated. I think it's cool.
> > > > > I limited it to only discussions started in April.
> > > > >
> > > > > Seems we have a small enough number of discussions starting
> > > > > every
> > > month,
> > > > to
> > > > > fit one small paragraph easily - and seeing just subjects of
> > > > > the
> > > > > discussions with links directly to the discussions might be a
> > > > > nice
> > > > > reminder/refresher/information for those who missed it.
> > > > >
> > > > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com>
> > > > > wrote:
> > > > >
> > > > > > > One option is to put that digest on a separate page, and
> > > > > > > just
> > > > provide a
> > > > > > link to it?
> > > > > >
> > > > > > Or maybe simply put it in one paragraph/long line with links
> > > > > > to
> > > > relevant
> > > > > > discussions :). I will try to do it and we can decide if it
> > > > > > makes
> > > > sense.
> > > > > > Let me try.
> > > > > >
> > > > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > > > > <jo...@joshfischer.io>
> > > > wrote:
> > > > > >
> > > > > > > I plan on sending the newsletter in a few hours. If
> > > > > > > someone wants
> > > to
> > > > > add
> > > > > > > anymore details please add them asap.
> > > > > > >
> > > > > > > On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > > > > > <rb...@rcbowen.com>
> > > wrote:
> > > > > > >
> > > > > > > > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > > > > > > > > I looked through it - I have one other
> > > > > > > > > comment/proposal: should
> > > we
> > > > > > > > > maybe
> > > > > > > > > add a digest of discussions running on members@a.o ? I
> > > > > > > > > think a
> > > > lot
> > > > > > > > > of
> > > > > > > > > people does not follow up those and while it is easy to
> > > > > > > > > look at
> > > > the
> > > > > > > > > list in
> > > > > > > > > archives, maybe listing the discussions with one-line
> > > > > > > > > summary
> > > > would
> > > > > > > > > be good
> > > > > > > > > ?
> > > > > > > > >
> > > > > > > > > Happy to make such a digest if others agree it's a good
> > > > > > > > > idea.
> > > > > > > >
> > > > > > > >
> > > > > > > > Yes, but ... I think it's very important that we don't
> > > > > > > > make the
> > > > email
> > > > > > > > longer than one screen-full, as that will undermine the
> > > > > > > > point here
> > > > of
> > > > > > > > it being only the most important things that every member
> > > > > > > > MUST
> > > know.
> > > > > > > >
> > > > > > > > One option is to put that digest on a separate page, and
> > > > > > > > just
> > > > provide
> > > > > a
> > > > > > > > link to it?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > -----------------------------------------------------------------
> > > > ----
> > > > > > > > To unsubscribe, e-mail:
> > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > For additional commands, e-mail:
> > > > > > > > dev-help@community.apache.org
> > > > > > > >
> > > > > > > > --
> > > > > > > Sent from A Mobile Device
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
On Tue, 2022-05-03 at 10:56 -0500, Josh Fischer wrote:
> Sam Ruby, suggested a plain text version for this round of the email.
> I
> **think** markdown was sent out last time and it didn't look good,
> making
> it harder to read/ understand .
>
> If we can find a way to make all the links easy to read, let's do it.
> If
> not, we might want to move them to an additional, external apache
> wiki link
> page and add a single link directing readers to the additional link
> page.
>
https://lists.apache.org/list?members@apache.org:2022-4 is a possible
link to that, in that it lists all of the threads that were active in
April.
> > You mean the links to text ? We can do it of course but I have a
> > feeling
> > that that defeats the purpose a bit because it allows the readers
> > to jump
> > straight to the discussion :).
> > I updated it now to have bullet-points instead - and as long as it
> > is not
> > too long, that might be better visually.
> > But if you feel like we need to decrease the number of links, I am
> > ok with
> > removing the links as well.
> >
> > J.
> >
> >
> > On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io>
> > wrote:
> >
> > > Any way we can convert your addition to text? I feel it may be a
> > > lot to
> > > sift through visually.
> > >
> > > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com>
> > > wrote:
> > >
> > > > Updated. I think it's cool.
> > > > I limited it to only discussions started in April.
> > > >
> > > > Seems we have a small enough number of discussions starting
> > > > every
> > month,
> > > to
> > > > fit one small paragraph easily - and seeing just subjects of
> > > > the
> > > > discussions with links directly to the discussions might be a
> > > > nice
> > > > reminder/refresher/information for those who missed it.
> > > >
> > > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com>
> > > > wrote:
> > > >
> > > > > > One option is to put that digest on a separate page, and
> > > > > > just
> > > provide a
> > > > > link to it?
> > > > >
> > > > > Or maybe simply put it in one paragraph/long line with links
> > > > > to
> > > relevant
> > > > > discussions :). I will try to do it and we can decide if it
> > > > > makes
> > > sense.
> > > > > Let me try.
> > > > >
> > > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer
> > > > > <jo...@joshfischer.io>
> > > wrote:
> > > > >
> > > > > > I plan on sending the newsletter in a few hours. If
> > > > > > someone wants
> > to
> > > > add
> > > > > > anymore details please add them asap.
> > > > > >
> > > > > > On Tue, May 3, 2022 at 7:39 AM Rich Bowen
> > > > > > <rb...@rcbowen.com>
> > wrote:
> > > > > >
> > > > > > > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > > > > > > > I looked through it - I have one other
> > > > > > > > comment/proposal: should
> > we
> > > > > > > > maybe
> > > > > > > > add a digest of discussions running on members@a.o ? I
> > > > > > > > think a
> > > lot
> > > > > > > > of
> > > > > > > > people does not follow up those and while it is easy to
> > > > > > > > look at
> > > the
> > > > > > > > list in
> > > > > > > > archives, maybe listing the discussions with one-line
> > > > > > > > summary
> > > would
> > > > > > > > be good
> > > > > > > > ?
> > > > > > > >
> > > > > > > > Happy to make such a digest if others agree it's a good
> > > > > > > > idea.
> > > > > > >
> > > > > > >
> > > > > > > Yes, but ... I think it's very important that we don't
> > > > > > > make the
> > > email
> > > > > > > longer than one screen-full, as that will undermine the
> > > > > > > point here
> > > of
> > > > > > > it being only the most important things that every member
> > > > > > > MUST
> > know.
> > > > > > >
> > > > > > > One option is to put that digest on a separate page, and
> > > > > > > just
> > > provide
> > > > a
> > > > > > > link to it?
> > > > > > >
> > > > > > >
> > > > > > >
> > > -----------------------------------------------------------------
> > > ----
> > > > > > > To unsubscribe, e-mail:
> > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > For additional commands, e-mail:
> > > > > > > dev-help@community.apache.org
> > > > > > >
> > > > > > > --
> > > > > > Sent from A Mobile Device
> > > > > >
> > > > >
> > > >
> > >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
Sam Ruby, suggested a plain text version for this round of the email. I
**think** markdown was sent out last time and it didn't look good, making
it harder to read/ understand .
If we can find a way to make all the links easy to read, let's do it. If
not, we might want to move them to an additional, external apache wiki link
page and add a single link directing readers to the additional link page.
On Tue, May 3, 2022 at 10:46 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> You mean the links to text ? We can do it of course but I have a feeling
> that that defeats the purpose a bit because it allows the readers to jump
> straight to the discussion :).
> I updated it now to have bullet-points instead - and as long as it is not
> too long, that might be better visually.
> But if you feel like we need to decrease the number of links, I am ok with
> removing the links as well.
>
> J.
>
>
> On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io> wrote:
>
> > Any way we can convert your addition to text? I feel it may be a lot to
> > sift through visually.
> >
> > On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > Updated. I think it's cool.
> > > I limited it to only discussions started in April.
> > >
> > > Seems we have a small enough number of discussions starting every
> month,
> > to
> > > fit one small paragraph easily - and seeing just subjects of the
> > > discussions with links directly to the discussions might be a nice
> > > reminder/refresher/information for those who missed it.
> > >
> > > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > > > One option is to put that digest on a separate page, and just
> > provide a
> > > > link to it?
> > > >
> > > > Or maybe simply put it in one paragraph/long line with links to
> > relevant
> > > > discussions :). I will try to do it and we can decide if it makes
> > sense.
> > > > Let me try.
> > > >
> > > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer <jo...@joshfischer.io>
> > wrote:
> > > >
> > > >> I plan on sending the newsletter in a few hours. If someone wants
> to
> > > add
> > > >> anymore details please add them asap.
> > > >>
> > > >> On Tue, May 3, 2022 at 7:39 AM Rich Bowen <rb...@rcbowen.com>
> wrote:
> > > >>
> > > >> > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > > >> > > I looked through it - I have one other comment/proposal: should
> we
> > > >> > > maybe
> > > >> > > add a digest of discussions running on members@a.o ? I think a
> > lot
> > > >> > > of
> > > >> > > people does not follow up those and while it is easy to look at
> > the
> > > >> > > list in
> > > >> > > archives, maybe listing the discussions with one-line summary
> > would
> > > >> > > be good
> > > >> > > ?
> > > >> > >
> > > >> > > Happy to make such a digest if others agree it's a good idea.
> > > >> >
> > > >> >
> > > >> > Yes, but ... I think it's very important that we don't make the
> > email
> > > >> > longer than one screen-full, as that will undermine the point here
> > of
> > > >> > it being only the most important things that every member MUST
> know.
> > > >> >
> > > >> > One option is to put that digest on a separate page, and just
> > provide
> > > a
> > > >> > link to it?
> > > >> >
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > >> > For additional commands, e-mail: dev-help@community.apache.org
> > > >> >
> > > >> > --
> > > >> Sent from A Mobile Device
> > > >>
> > > >
> > >
> >
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
You mean the links to text ? We can do it of course but I have a feeling
that that defeats the purpose a bit because it allows the readers to jump
straight to the discussion :).
I updated it now to have bullet-points instead - and as long as it is not
too long, that might be better visually.
But if you feel like we need to decrease the number of links, I am ok with
removing the links as well.
J.
On Tue, May 3, 2022 at 4:56 PM Josh Fischer <jo...@joshfischer.io> wrote:
> Any way we can convert your addition to text? I feel it may be a lot to
> sift through visually.
>
> On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > Updated. I think it's cool.
> > I limited it to only discussions started in April.
> >
> > Seems we have a small enough number of discussions starting every month,
> to
> > fit one small paragraph easily - and seeing just subjects of the
> > discussions with links directly to the discussions might be a nice
> > reminder/refresher/information for those who missed it.
> >
> > On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > > One option is to put that digest on a separate page, and just
> provide a
> > > link to it?
> > >
> > > Or maybe simply put it in one paragraph/long line with links to
> relevant
> > > discussions :). I will try to do it and we can decide if it makes
> sense.
> > > Let me try.
> > >
> > > On Tue, May 3, 2022 at 2:44 PM Josh Fischer <jo...@joshfischer.io>
> wrote:
> > >
> > >> I plan on sending the newsletter in a few hours. If someone wants to
> > add
> > >> anymore details please add them asap.
> > >>
> > >> On Tue, May 3, 2022 at 7:39 AM Rich Bowen <rb...@rcbowen.com> wrote:
> > >>
> > >> > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > >> > > I looked through it - I have one other comment/proposal: should we
> > >> > > maybe
> > >> > > add a digest of discussions running on members@a.o ? I think a
> lot
> > >> > > of
> > >> > > people does not follow up those and while it is easy to look at
> the
> > >> > > list in
> > >> > > archives, maybe listing the discussions with one-line summary
> would
> > >> > > be good
> > >> > > ?
> > >> > >
> > >> > > Happy to make such a digest if others agree it's a good idea.
> > >> >
> > >> >
> > >> > Yes, but ... I think it's very important that we don't make the
> email
> > >> > longer than one screen-full, as that will undermine the point here
> of
> > >> > it being only the most important things that every member MUST know.
> > >> >
> > >> > One option is to put that digest on a separate page, and just
> provide
> > a
> > >> > link to it?
> > >> >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > >> > For additional commands, e-mail: dev-help@community.apache.org
> > >> >
> > >> > --
> > >> Sent from A Mobile Device
> > >>
> > >
> >
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
Any way we can convert your addition to text? I feel it may be a lot to
sift through visually.
On Tue, May 3, 2022 at 8:32 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> Updated. I think it's cool.
> I limited it to only discussions started in April.
>
> Seems we have a small enough number of discussions starting every month, to
> fit one small paragraph easily - and seeing just subjects of the
> discussions with links directly to the discussions might be a nice
> reminder/refresher/information for those who missed it.
>
> On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > > One option is to put that digest on a separate page, and just provide a
> > link to it?
> >
> > Or maybe simply put it in one paragraph/long line with links to relevant
> > discussions :). I will try to do it and we can decide if it makes sense.
> > Let me try.
> >
> > On Tue, May 3, 2022 at 2:44 PM Josh Fischer <jo...@joshfischer.io> wrote:
> >
> >> I plan on sending the newsletter in a few hours. If someone wants to
> add
> >> anymore details please add them asap.
> >>
> >> On Tue, May 3, 2022 at 7:39 AM Rich Bowen <rb...@rcbowen.com> wrote:
> >>
> >> > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> >> > > I looked through it - I have one other comment/proposal: should we
> >> > > maybe
> >> > > add a digest of discussions running on members@a.o ? I think a lot
> >> > > of
> >> > > people does not follow up those and while it is easy to look at the
> >> > > list in
> >> > > archives, maybe listing the discussions with one-line summary would
> >> > > be good
> >> > > ?
> >> > >
> >> > > Happy to make such a digest if others agree it's a good idea.
> >> >
> >> >
> >> > Yes, but ... I think it's very important that we don't make the email
> >> > longer than one screen-full, as that will undermine the point here of
> >> > it being only the most important things that every member MUST know.
> >> >
> >> > One option is to put that digest on a separate page, and just provide
> a
> >> > link to it?
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> > For additional commands, e-mail: dev-help@community.apache.org
> >> >
> >> > --
> >> Sent from A Mobile Device
> >>
> >
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
Updated. I think it's cool.
I limited it to only discussions started in April.
Seems we have a small enough number of discussions starting every month, to
fit one small paragraph easily - and seeing just subjects of the
discussions with links directly to the discussions might be a nice
reminder/refresher/information for those who missed it.
On Tue, May 3, 2022 at 3:18 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> > One option is to put that digest on a separate page, and just provide a
> link to it?
>
> Or maybe simply put it in one paragraph/long line with links to relevant
> discussions :). I will try to do it and we can decide if it makes sense.
> Let me try.
>
> On Tue, May 3, 2022 at 2:44 PM Josh Fischer <jo...@joshfischer.io> wrote:
>
>> I plan on sending the newsletter in a few hours. If someone wants to add
>> anymore details please add them asap.
>>
>> On Tue, May 3, 2022 at 7:39 AM Rich Bowen <rb...@rcbowen.com> wrote:
>>
>> > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
>> > > I looked through it - I have one other comment/proposal: should we
>> > > maybe
>> > > add a digest of discussions running on members@a.o ? I think a lot
>> > > of
>> > > people does not follow up those and while it is easy to look at the
>> > > list in
>> > > archives, maybe listing the discussions with one-line summary would
>> > > be good
>> > > ?
>> > >
>> > > Happy to make such a digest if others agree it's a good idea.
>> >
>> >
>> > Yes, but ... I think it's very important that we don't make the email
>> > longer than one screen-full, as that will undermine the point here of
>> > it being only the most important things that every member MUST know.
>> >
>> > One option is to put that digest on a separate page, and just provide a
>> > link to it?
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> > For additional commands, e-mail: dev-help@community.apache.org
>> >
>> > --
>> Sent from A Mobile Device
>>
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
> One option is to put that digest on a separate page, and just provide a
link to it?
Or maybe simply put it in one paragraph/long line with links to relevant
discussions :). I will try to do it and we can decide if it makes sense.
Let me try.
On Tue, May 3, 2022 at 2:44 PM Josh Fischer <jo...@joshfischer.io> wrote:
> I plan on sending the newsletter in a few hours. If someone wants to add
> anymore details please add them asap.
>
> On Tue, May 3, 2022 at 7:39 AM Rich Bowen <rb...@rcbowen.com> wrote:
>
> > On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > > I looked through it - I have one other comment/proposal: should we
> > > maybe
> > > add a digest of discussions running on members@a.o ? I think a lot
> > > of
> > > people does not follow up those and while it is easy to look at the
> > > list in
> > > archives, maybe listing the discussions with one-line summary would
> > > be good
> > > ?
> > >
> > > Happy to make such a digest if others agree it's a good idea.
> >
> >
> > Yes, but ... I think it's very important that we don't make the email
> > longer than one screen-full, as that will undermine the point here of
> > it being only the most important things that every member MUST know.
> >
> > One option is to put that digest on a separate page, and just provide a
> > link to it?
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> > --
> Sent from A Mobile Device
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
I plan on sending the newsletter in a few hours. If someone wants to add
anymore details please add them asap.
On Tue, May 3, 2022 at 7:39 AM Rich Bowen <rb...@rcbowen.com> wrote:
> On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> > I looked through it - I have one other comment/proposal: should we
> > maybe
> > add a digest of discussions running on members@a.o ? I think a lot
> > of
> > people does not follow up those and while it is easy to look at the
> > list in
> > archives, maybe listing the discussions with one-line summary would
> > be good
> > ?
> >
> > Happy to make such a digest if others agree it's a good idea.
>
>
> Yes, but ... I think it's very important that we don't make the email
> longer than one screen-full, as that will undermine the point here of
> it being only the most important things that every member MUST know.
>
> One option is to put that digest on a separate page, and just provide a
> link to it?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
> --
Sent from A Mobile Device
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
On Tue, 2022-05-03 at 12:35 +0200, Jarek Potiuk wrote:
> I looked through it - I have one other comment/proposal: should we
> maybe
> add a digest of discussions running on members@a.o ? I think a lot
> of
> people does not follow up those and while it is easy to look at the
> list in
> archives, maybe listing the discussions with one-line summary would
> be good
> ?
>
> Happy to make such a digest if others agree it's a good idea.
Yes, but ... I think it's very important that we don't make the email
longer than one screen-full, as that will undermine the point here of
it being only the most important things that every member MUST know.
One option is to put that digest on a separate page, and just provide a
link to it?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
I looked through it - I have one other comment/proposal: should we maybe
add a digest of discussions running on members@a.o ? I think a lot of
people does not follow up those and while it is easy to look at the list in
archives, maybe listing the discussions with one-line summary would be good
?
Happy to make such a digest if others agree it's a good idea.
J.
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
Le mar. 3 mai 2022 à 08:22, Christian Grobmeier <gr...@apache.org> a écrit :
> Is the move to the new privacy policy interesting enough to be added to the bullet points?
> It’s a boring topic topic too many but maybe worth to mention due to its impact on websites..
Definitely worth mentioning IMO.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Christian Grobmeier <gr...@apache.org>.
Hi
Is the move to the new privacy policy interesting enough to be added to the bullet points? It’s a boring topic topic too many but maybe worth to mention due to its impact on websites
Cheers
--
The Apache Software Foundation
V.P., Data Privacy
On Mon, May 2, 2022, at 17:03, Josh Fischer wrote:
> Gotcha. I’ll send it out tomorrow!
>
> On Mon, May 2, 2022 at 9:49 AM Sam Ruby <ru...@intertwingly.net> wrote:
>
>> On Mon, May 2, 2022 at 10:39 AM Josh Fischer <jo...@joshfischer.io> wrote:
>> >
>> > I remember us agreeing to send it out on May 5. Since I'm not a member,
>> > I'll leave that up to either Rich or Sam to send out.
>>
>> I had sent the last one out on the first Tuesday of the month, which
>> happened to be the 5th last month. I'd recommend following a similar
>> pattern as that will avoid weekends. For some months, this may need
>> to be adjusted for holidays.
>>
>> To me, one of the purposes of this exercise is to see if someone other
>> than the usual hyper-volunteers steps up, so I won't be sending the
>> email.
>>
>> But I am a moderator for that list, and if I see content that matches
>> the wiki page in the moderation queue this week, I will approve it.
>> Whether the person sending it is an ASF member or not won't affect
>> whether or not I approve the content.
>>
>> - Sam Ruby
>>
>> > Thank ya
>> >
>> > On Mon, May 2, 2022 at 9:21 AM Rich Bowen <rb...@rcbowen.com> wrote:
>> >
>> > > The last one we sent, Sam sent directly to the members-notify list -
>> > > which does, indeed, need to be done by a member.
>> > >
>> > > I've added one more (member-specific) item to the highlights. I feel
>> > > like we're missing something important, but I cannot remember what it
>> > > is.
>> > >
>> > > What is our send date?
>> > >
>> > > On Mon, 2022-05-02 at 08:57 -0500, Josh Fischer wrote:
>> > > > The newsletter has been updated and just about ready for sending
>> > > > out.. Not
>> > > > sure of the whos or hows of getting this across the foundation. Is
>> > > > there
>> > > > a preferred way that I can get this distributed? Is this something
>> > > > only
>> > > > a member can/should do?
>> > > >
>> > > > On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io>
>> > > > wrote:
>> > > >
>> > > > > We have room for another bullet point or two if anyone wants to add
>> > > > > anything to the critical committer communications letter. We have
>> > > > > about
>> > > > > two weeks before it will be sent out. Link below.
>> > > > >
>> > > > >
>> > >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
>> > > > >
>> > > > > - Josh
>> > > > >
>> > > > > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net>
>> > > > > wrote:
>> > > > >
>> > > > > > On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer
>> > > > > > <jo...@joshfischer.io> wrote:
>> > > > > > >
>> > > > > > > Created a starter with a few fun facts here:
>> > > > > > > https://cwiki.apache.org/confluence/x/0YyFD
>> > > > > > >
>> > > > > > > Feel free to add or take away as you see fit.
>> > > > > >
>> > > > > > THANK YOU!
>> > > > > >
>> > > > > > > - Josh
>> > > > > >
>> > > > > > - Sam Ruby
>> > > > > >
>> > > > > > > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby
>> > > > > > > <ru...@intertwingly.net> wrote:
>> > > > > > >
>> > > > > > > > Message has been posted. Next time it probably should be a
>> > > > > > > > pure plain
>> > > > > > > > text version.
>> > > > > > > >
>> > > > > > > > Anybody want to get started on May? Create the wiki page,
>> > > > > > > > put some
>> > > > > > > > content there, and then send it out the first week in May
>> > > > > > > > after others
>> > > > > > > > have been given the opportunity to contribute.
>> > > > > > > >
>> > > > > > > > - Sam Ruby
>> > > > > > > >
>> > > > > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen
>> > > > > > > > <rb...@rcbowen.com>
>> > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > Problem: Members (and, more generally, committers) are less
>> > > > > > > > > engaged
>> > > > > > with
>> > > > > > > > > the larger Foundation than at any point in our history.
>> > > > > > > > > Meanwhile,
>> > > > > > the
>> > > > > > > > > mechanisms for getting more engaged (eg, the members
>> > > > > > > > > mailing list)
>> > > > > > are a
>> > > > > > > > > firehose of unrelated content that is very frustrating to
>> > > > > > > > > the casual
>> > > > > > > > > participant - even those who desire a deeper engagement -
>> > > > > > > > > and, in
>> > > > > > > > > practice, are completely off-putting. Committers,
>> > > > > > > > > meanwhile, have no
>> > > > > > > > > real avenue, outside of their project, for further
>> > > > > > > > > engagement.
>> > > > > > > > >
>> > > > > > > > > I've been struggling with ways to address this for years,
>> > > > > > > > > and they
>> > > > > > all
>> > > > > > > > > tend to founder on the rocks of "People should just be
>> > > > > > > > > doing X!"
>> > > > > > which,
>> > > > > > > > > in each case, is true, but also dismissive and ultimately
>> > > > > > > > > unhelpful.
>> > > > > > > > >
>> > > > > > > > > I would like to propose that we are more proactive about
>> > > > > > > > > reaching
>> > > > > > out to
>> > > > > > > > > our community in tiny, consumable bites, that hint at a
>> > > > > > > > > larger feast
>> > > > > > > > > that they're missing out on.
>> > > > > > > > >
>> > > > > > > > > Here's my proposal, but I cannot (and will not) tackle this
>> > > > > > > > > alone,
>> > > > > > > > > because that guarantees failure, which guaranteed less
>> > > > > > participation the
>> > > > > > > > > next time we suggest something like this.
>> > > > > > > > >
>> > > > > > > > > Proposal/Brainstorming doc:
>> > > > > > https://hackmd.io/JaLaGy56T8qT3ODABLVswA
>> > > > > > > > >
>> > > > > > > > > It's an intentionally simple idea - a minimum viable idea,
>> > > > > > > > > one
>> > > > > > might say.
>> > > > > > > > >
>> > > > > > > > > I want to know who's going to help make it a reality. Not
>> > > > > > particularly
>> > > > > > > > > interested in "that's a great idea", as much as "I will
>> > > > > > > > > help make it
>> > > > > > > > > happen."
>> > > > > > > > >
>> > > > > > > > > This will involve engagement with Events, M&P, and Board,
>> > > > > > > > > at a
>> > > > > > minimum,
>> > > > > > > > > but over time we'd hopefully engage everyone at the
>> > > > > > > > > Foundation in
>> > > > > > > > > content creation. But, even then, I want to keep this tiny
>> > > > > > > > > and
>> > > > > > > > > consumable - content that you can absorb in 2-5 minutes,
>> > > > > > > > > always
>> > > > > > with a
>> > > > > > > > > "to get more engaged ..." call to action aspect to it.
>> > > > > > > > >
>> > > > > > > > > Come help me develop community.
>> > > > > > > > >
>> > > > > > > > > --Rich
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > -----------------------------------------------------------------
>> > > > > > ----
>> > > > > > > > > To unsubscribe, e-mail:
>> > > > > > > > > dev-unsubscribe@community.apache.org
>> > > > > > > > > For additional commands, e-mail:
>> > > > > > > > > dev-help@community.apache.org
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > > -------------------------------------------------------------
>> > > > > > > > --------
>> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> > > > > > > > For additional commands, e-mail:
>> > > > > > > > dev-help@community.apache.org
>> > > > > > > >
>> > > > > > > >
>> > > > > >
>> > > > > > -----------------------------------------------------------------
>> > > > > > ----
>> > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> > > > > > For additional commands, e-mail: dev-help@community.apache.org
>> > > > > >
>> > > > > >
>> > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> > > For additional commands, e-mail: dev-help@community.apache.org
>> > >
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>> --
> Sent from A Mobile Device
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
Gotcha. I’ll send it out tomorrow!
On Mon, May 2, 2022 at 9:49 AM Sam Ruby <ru...@intertwingly.net> wrote:
> On Mon, May 2, 2022 at 10:39 AM Josh Fischer <jo...@joshfischer.io> wrote:
> >
> > I remember us agreeing to send it out on May 5. Since I'm not a member,
> > I'll leave that up to either Rich or Sam to send out.
>
> I had sent the last one out on the first Tuesday of the month, which
> happened to be the 5th last month. I'd recommend following a similar
> pattern as that will avoid weekends. For some months, this may need
> to be adjusted for holidays.
>
> To me, one of the purposes of this exercise is to see if someone other
> than the usual hyper-volunteers steps up, so I won't be sending the
> email.
>
> But I am a moderator for that list, and if I see content that matches
> the wiki page in the moderation queue this week, I will approve it.
> Whether the person sending it is an ASF member or not won't affect
> whether or not I approve the content.
>
> - Sam Ruby
>
> > Thank ya
> >
> > On Mon, May 2, 2022 at 9:21 AM Rich Bowen <rb...@rcbowen.com> wrote:
> >
> > > The last one we sent, Sam sent directly to the members-notify list -
> > > which does, indeed, need to be done by a member.
> > >
> > > I've added one more (member-specific) item to the highlights. I feel
> > > like we're missing something important, but I cannot remember what it
> > > is.
> > >
> > > What is our send date?
> > >
> > > On Mon, 2022-05-02 at 08:57 -0500, Josh Fischer wrote:
> > > > The newsletter has been updated and just about ready for sending
> > > > out.. Not
> > > > sure of the whos or hows of getting this across the foundation. Is
> > > > there
> > > > a preferred way that I can get this distributed? Is this something
> > > > only
> > > > a member can/should do?
> > > >
> > > > On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io>
> > > > wrote:
> > > >
> > > > > We have room for another bullet point or two if anyone wants to add
> > > > > anything to the critical committer communications letter. We have
> > > > > about
> > > > > two weeks before it will be sent out. Link below.
> > > > >
> > > > >
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
> > > > >
> > > > > - Josh
> > > > >
> > > > > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net>
> > > > > wrote:
> > > > >
> > > > > > On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer
> > > > > > <jo...@joshfischer.io> wrote:
> > > > > > >
> > > > > > > Created a starter with a few fun facts here:
> > > > > > > https://cwiki.apache.org/confluence/x/0YyFD
> > > > > > >
> > > > > > > Feel free to add or take away as you see fit.
> > > > > >
> > > > > > THANK YOU!
> > > > > >
> > > > > > > - Josh
> > > > > >
> > > > > > - Sam Ruby
> > > > > >
> > > > > > > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby
> > > > > > > <ru...@intertwingly.net> wrote:
> > > > > > >
> > > > > > > > Message has been posted. Next time it probably should be a
> > > > > > > > pure plain
> > > > > > > > text version.
> > > > > > > >
> > > > > > > > Anybody want to get started on May? Create the wiki page,
> > > > > > > > put some
> > > > > > > > content there, and then send it out the first week in May
> > > > > > > > after others
> > > > > > > > have been given the opportunity to contribute.
> > > > > > > >
> > > > > > > > - Sam Ruby
> > > > > > > >
> > > > > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen
> > > > > > > > <rb...@rcbowen.com>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Problem: Members (and, more generally, committers) are less
> > > > > > > > > engaged
> > > > > > with
> > > > > > > > > the larger Foundation than at any point in our history.
> > > > > > > > > Meanwhile,
> > > > > > the
> > > > > > > > > mechanisms for getting more engaged (eg, the members
> > > > > > > > > mailing list)
> > > > > > are a
> > > > > > > > > firehose of unrelated content that is very frustrating to
> > > > > > > > > the casual
> > > > > > > > > participant - even those who desire a deeper engagement -
> > > > > > > > > and, in
> > > > > > > > > practice, are completely off-putting. Committers,
> > > > > > > > > meanwhile, have no
> > > > > > > > > real avenue, outside of their project, for further
> > > > > > > > > engagement.
> > > > > > > > >
> > > > > > > > > I've been struggling with ways to address this for years,
> > > > > > > > > and they
> > > > > > all
> > > > > > > > > tend to founder on the rocks of "People should just be
> > > > > > > > > doing X!"
> > > > > > which,
> > > > > > > > > in each case, is true, but also dismissive and ultimately
> > > > > > > > > unhelpful.
> > > > > > > > >
> > > > > > > > > I would like to propose that we are more proactive about
> > > > > > > > > reaching
> > > > > > out to
> > > > > > > > > our community in tiny, consumable bites, that hint at a
> > > > > > > > > larger feast
> > > > > > > > > that they're missing out on.
> > > > > > > > >
> > > > > > > > > Here's my proposal, but I cannot (and will not) tackle this
> > > > > > > > > alone,
> > > > > > > > > because that guarantees failure, which guaranteed less
> > > > > > participation the
> > > > > > > > > next time we suggest something like this.
> > > > > > > > >
> > > > > > > > > Proposal/Brainstorming doc:
> > > > > > https://hackmd.io/JaLaGy56T8qT3ODABLVswA
> > > > > > > > >
> > > > > > > > > It's an intentionally simple idea - a minimum viable idea,
> > > > > > > > > one
> > > > > > might say.
> > > > > > > > >
> > > > > > > > > I want to know who's going to help make it a reality. Not
> > > > > > particularly
> > > > > > > > > interested in "that's a great idea", as much as "I will
> > > > > > > > > help make it
> > > > > > > > > happen."
> > > > > > > > >
> > > > > > > > > This will involve engagement with Events, M&P, and Board,
> > > > > > > > > at a
> > > > > > minimum,
> > > > > > > > > but over time we'd hopefully engage everyone at the
> > > > > > > > > Foundation in
> > > > > > > > > content creation. But, even then, I want to keep this tiny
> > > > > > > > > and
> > > > > > > > > consumable - content that you can absorb in 2-5 minutes,
> > > > > > > > > always
> > > > > > with a
> > > > > > > > > "to get more engaged ..." call to action aspect to it.
> > > > > > > > >
> > > > > > > > > Come help me develop community.
> > > > > > > > >
> > > > > > > > > --Rich
> > > > > > > > >
> > > > > > > > >
> > > > > > -----------------------------------------------------------------
> > > > > > ----
> > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > > For additional commands, e-mail:
> > > > > > > > > dev-help@community.apache.org
> > > > > > > > >
> > > > > > > >
> > > > > > > > -------------------------------------------------------------
> > > > > > > > --------
> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > > > > For additional commands, e-mail:
> > > > > > > > dev-help@community.apache.org
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > > -----------------------------------------------------------------
> > > > > > ----
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > > For additional commands, e-mail: dev-help@community.apache.org
> > > > > >
> > > > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > For additional commands, e-mail: dev-help@community.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
> --
Sent from A Mobile Device
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, May 2, 2022 at 10:39 AM Josh Fischer <jo...@joshfischer.io> wrote:
>
> I remember us agreeing to send it out on May 5. Since I'm not a member,
> I'll leave that up to either Rich or Sam to send out.
I had sent the last one out on the first Tuesday of the month, which
happened to be the 5th last month. I'd recommend following a similar
pattern as that will avoid weekends. For some months, this may need
to be adjusted for holidays.
To me, one of the purposes of this exercise is to see if someone other
than the usual hyper-volunteers steps up, so I won't be sending the
email.
But I am a moderator for that list, and if I see content that matches
the wiki page in the moderation queue this week, I will approve it.
Whether the person sending it is an ASF member or not won't affect
whether or not I approve the content.
- Sam Ruby
> Thank ya
>
> On Mon, May 2, 2022 at 9:21 AM Rich Bowen <rb...@rcbowen.com> wrote:
>
> > The last one we sent, Sam sent directly to the members-notify list -
> > which does, indeed, need to be done by a member.
> >
> > I've added one more (member-specific) item to the highlights. I feel
> > like we're missing something important, but I cannot remember what it
> > is.
> >
> > What is our send date?
> >
> > On Mon, 2022-05-02 at 08:57 -0500, Josh Fischer wrote:
> > > The newsletter has been updated and just about ready for sending
> > > out.. Not
> > > sure of the whos or hows of getting this across the foundation. Is
> > > there
> > > a preferred way that I can get this distributed? Is this something
> > > only
> > > a member can/should do?
> > >
> > > On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io>
> > > wrote:
> > >
> > > > We have room for another bullet point or two if anyone wants to add
> > > > anything to the critical committer communications letter. We have
> > > > about
> > > > two weeks before it will be sent out. Link below.
> > > >
> > > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
> > > >
> > > > - Josh
> > > >
> > > > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net>
> > > > wrote:
> > > >
> > > > > On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer
> > > > > <jo...@joshfischer.io> wrote:
> > > > > >
> > > > > > Created a starter with a few fun facts here:
> > > > > > https://cwiki.apache.org/confluence/x/0YyFD
> > > > > >
> > > > > > Feel free to add or take away as you see fit.
> > > > >
> > > > > THANK YOU!
> > > > >
> > > > > > - Josh
> > > > >
> > > > > - Sam Ruby
> > > > >
> > > > > > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby
> > > > > > <ru...@intertwingly.net> wrote:
> > > > > >
> > > > > > > Message has been posted. Next time it probably should be a
> > > > > > > pure plain
> > > > > > > text version.
> > > > > > >
> > > > > > > Anybody want to get started on May? Create the wiki page,
> > > > > > > put some
> > > > > > > content there, and then send it out the first week in May
> > > > > > > after others
> > > > > > > have been given the opportunity to contribute.
> > > > > > >
> > > > > > > - Sam Ruby
> > > > > > >
> > > > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen
> > > > > > > <rb...@rcbowen.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > > Problem: Members (and, more generally, committers) are less
> > > > > > > > engaged
> > > > > with
> > > > > > > > the larger Foundation than at any point in our history.
> > > > > > > > Meanwhile,
> > > > > the
> > > > > > > > mechanisms for getting more engaged (eg, the members
> > > > > > > > mailing list)
> > > > > are a
> > > > > > > > firehose of unrelated content that is very frustrating to
> > > > > > > > the casual
> > > > > > > > participant - even those who desire a deeper engagement -
> > > > > > > > and, in
> > > > > > > > practice, are completely off-putting. Committers,
> > > > > > > > meanwhile, have no
> > > > > > > > real avenue, outside of their project, for further
> > > > > > > > engagement.
> > > > > > > >
> > > > > > > > I've been struggling with ways to address this for years,
> > > > > > > > and they
> > > > > all
> > > > > > > > tend to founder on the rocks of "People should just be
> > > > > > > > doing X!"
> > > > > which,
> > > > > > > > in each case, is true, but also dismissive and ultimately
> > > > > > > > unhelpful.
> > > > > > > >
> > > > > > > > I would like to propose that we are more proactive about
> > > > > > > > reaching
> > > > > out to
> > > > > > > > our community in tiny, consumable bites, that hint at a
> > > > > > > > larger feast
> > > > > > > > that they're missing out on.
> > > > > > > >
> > > > > > > > Here's my proposal, but I cannot (and will not) tackle this
> > > > > > > > alone,
> > > > > > > > because that guarantees failure, which guaranteed less
> > > > > participation the
> > > > > > > > next time we suggest something like this.
> > > > > > > >
> > > > > > > > Proposal/Brainstorming doc:
> > > > > https://hackmd.io/JaLaGy56T8qT3ODABLVswA
> > > > > > > >
> > > > > > > > It's an intentionally simple idea - a minimum viable idea,
> > > > > > > > one
> > > > > might say.
> > > > > > > >
> > > > > > > > I want to know who's going to help make it a reality. Not
> > > > > particularly
> > > > > > > > interested in "that's a great idea", as much as "I will
> > > > > > > > help make it
> > > > > > > > happen."
> > > > > > > >
> > > > > > > > This will involve engagement with Events, M&P, and Board,
> > > > > > > > at a
> > > > > minimum,
> > > > > > > > but over time we'd hopefully engage everyone at the
> > > > > > > > Foundation in
> > > > > > > > content creation. But, even then, I want to keep this tiny
> > > > > > > > and
> > > > > > > > consumable - content that you can absorb in 2-5 minutes,
> > > > > > > > always
> > > > > with a
> > > > > > > > "to get more engaged ..." call to action aspect to it.
> > > > > > > >
> > > > > > > > Come help me develop community.
> > > > > > > >
> > > > > > > > --Rich
> > > > > > > >
> > > > > > > >
> > > > > -----------------------------------------------------------------
> > > > > ----
> > > > > > > > To unsubscribe, e-mail:
> > > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > > For additional commands, e-mail:
> > > > > > > > dev-help@community.apache.org
> > > > > > > >
> > > > > > >
> > > > > > > -------------------------------------------------------------
> > > > > > > --------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > > > For additional commands, e-mail:
> > > > > > > dev-help@community.apache.org
> > > > > > >
> > > > > > >
> > > > >
> > > > > -----------------------------------------------------------------
> > > > > ----
> > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > For additional commands, e-mail: dev-help@community.apache.org
> > > > >
> > > > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
I remember us agreeing to send it out on May 5. Since I'm not a member,
I'll leave that up to either Rich or Sam to send out.
Thank ya
On Mon, May 2, 2022 at 9:21 AM Rich Bowen <rb...@rcbowen.com> wrote:
> The last one we sent, Sam sent directly to the members-notify list -
> which does, indeed, need to be done by a member.
>
> I've added one more (member-specific) item to the highlights. I feel
> like we're missing something important, but I cannot remember what it
> is.
>
> What is our send date?
>
> On Mon, 2022-05-02 at 08:57 -0500, Josh Fischer wrote:
> > The newsletter has been updated and just about ready for sending
> > out.. Not
> > sure of the whos or hows of getting this across the foundation. Is
> > there
> > a preferred way that I can get this distributed? Is this something
> > only
> > a member can/should do?
> >
> > On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io>
> > wrote:
> >
> > > We have room for another bullet point or two if anyone wants to add
> > > anything to the critical committer communications letter. We have
> > > about
> > > two weeks before it will be sent out. Link below.
> > >
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
> > >
> > > - Josh
> > >
> > > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net>
> > > wrote:
> > >
> > > > On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer
> > > > <jo...@joshfischer.io> wrote:
> > > > >
> > > > > Created a starter with a few fun facts here:
> > > > > https://cwiki.apache.org/confluence/x/0YyFD
> > > > >
> > > > > Feel free to add or take away as you see fit.
> > > >
> > > > THANK YOU!
> > > >
> > > > > - Josh
> > > >
> > > > - Sam Ruby
> > > >
> > > > > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby
> > > > > <ru...@intertwingly.net> wrote:
> > > > >
> > > > > > Message has been posted. Next time it probably should be a
> > > > > > pure plain
> > > > > > text version.
> > > > > >
> > > > > > Anybody want to get started on May? Create the wiki page,
> > > > > > put some
> > > > > > content there, and then send it out the first week in May
> > > > > > after others
> > > > > > have been given the opportunity to contribute.
> > > > > >
> > > > > > - Sam Ruby
> > > > > >
> > > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen
> > > > > > <rb...@rcbowen.com>
> > > > wrote:
> > > > > > >
> > > > > > > Problem: Members (and, more generally, committers) are less
> > > > > > > engaged
> > > > with
> > > > > > > the larger Foundation than at any point in our history.
> > > > > > > Meanwhile,
> > > > the
> > > > > > > mechanisms for getting more engaged (eg, the members
> > > > > > > mailing list)
> > > > are a
> > > > > > > firehose of unrelated content that is very frustrating to
> > > > > > > the casual
> > > > > > > participant - even those who desire a deeper engagement -
> > > > > > > and, in
> > > > > > > practice, are completely off-putting. Committers,
> > > > > > > meanwhile, have no
> > > > > > > real avenue, outside of their project, for further
> > > > > > > engagement.
> > > > > > >
> > > > > > > I've been struggling with ways to address this for years,
> > > > > > > and they
> > > > all
> > > > > > > tend to founder on the rocks of "People should just be
> > > > > > > doing X!"
> > > > which,
> > > > > > > in each case, is true, but also dismissive and ultimately
> > > > > > > unhelpful.
> > > > > > >
> > > > > > > I would like to propose that we are more proactive about
> > > > > > > reaching
> > > > out to
> > > > > > > our community in tiny, consumable bites, that hint at a
> > > > > > > larger feast
> > > > > > > that they're missing out on.
> > > > > > >
> > > > > > > Here's my proposal, but I cannot (and will not) tackle this
> > > > > > > alone,
> > > > > > > because that guarantees failure, which guaranteed less
> > > > participation the
> > > > > > > next time we suggest something like this.
> > > > > > >
> > > > > > > Proposal/Brainstorming doc:
> > > > https://hackmd.io/JaLaGy56T8qT3ODABLVswA
> > > > > > >
> > > > > > > It's an intentionally simple idea - a minimum viable idea,
> > > > > > > one
> > > > might say.
> > > > > > >
> > > > > > > I want to know who's going to help make it a reality. Not
> > > > particularly
> > > > > > > interested in "that's a great idea", as much as "I will
> > > > > > > help make it
> > > > > > > happen."
> > > > > > >
> > > > > > > This will involve engagement with Events, M&P, and Board,
> > > > > > > at a
> > > > minimum,
> > > > > > > but over time we'd hopefully engage everyone at the
> > > > > > > Foundation in
> > > > > > > content creation. But, even then, I want to keep this tiny
> > > > > > > and
> > > > > > > consumable - content that you can absorb in 2-5 minutes,
> > > > > > > always
> > > > with a
> > > > > > > "to get more engaged ..." call to action aspect to it.
> > > > > > >
> > > > > > > Come help me develop community.
> > > > > > >
> > > > > > > --Rich
> > > > > > >
> > > > > > >
> > > > -----------------------------------------------------------------
> > > > ----
> > > > > > > To unsubscribe, e-mail:
> > > > > > > dev-unsubscribe@community.apache.org
> > > > > > > For additional commands, e-mail:
> > > > > > > dev-help@community.apache.org
> > > > > > >
> > > > > >
> > > > > > -------------------------------------------------------------
> > > > > > --------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > > For additional commands, e-mail:
> > > > > > dev-help@community.apache.org
> > > > > >
> > > > > >
> > > >
> > > > -----------------------------------------------------------------
> > > > ----
> > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > For additional commands, e-mail: dev-help@community.apache.org
> > > >
> > > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
The last one we sent, Sam sent directly to the members-notify list -
which does, indeed, need to be done by a member.
I've added one more (member-specific) item to the highlights. I feel
like we're missing something important, but I cannot remember what it
is.
What is our send date?
On Mon, 2022-05-02 at 08:57 -0500, Josh Fischer wrote:
> The newsletter has been updated and just about ready for sending
> out.. Not
> sure of the whos or hows of getting this across the foundation. Is
> there
> a preferred way that I can get this distributed? Is this something
> only
> a member can/should do?
>
> On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io>
> wrote:
>
> > We have room for another bullet point or two if anyone wants to add
> > anything to the critical committer communications letter. We have
> > about
> > two weeks before it will be sent out. Link below.
> >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
> >
> > - Josh
> >
> > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net>
> > wrote:
> >
> > > On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer
> > > <jo...@joshfischer.io> wrote:
> > > >
> > > > Created a starter with a few fun facts here:
> > > > https://cwiki.apache.org/confluence/x/0YyFD
> > > >
> > > > Feel free to add or take away as you see fit.
> > >
> > > THANK YOU!
> > >
> > > > - Josh
> > >
> > > - Sam Ruby
> > >
> > > > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby
> > > > <ru...@intertwingly.net> wrote:
> > > >
> > > > > Message has been posted. Next time it probably should be a
> > > > > pure plain
> > > > > text version.
> > > > >
> > > > > Anybody want to get started on May? Create the wiki page,
> > > > > put some
> > > > > content there, and then send it out the first week in May
> > > > > after others
> > > > > have been given the opportunity to contribute.
> > > > >
> > > > > - Sam Ruby
> > > > >
> > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen
> > > > > <rb...@rcbowen.com>
> > > wrote:
> > > > > >
> > > > > > Problem: Members (and, more generally, committers) are less
> > > > > > engaged
> > > with
> > > > > > the larger Foundation than at any point in our history.
> > > > > > Meanwhile,
> > > the
> > > > > > mechanisms for getting more engaged (eg, the members
> > > > > > mailing list)
> > > are a
> > > > > > firehose of unrelated content that is very frustrating to
> > > > > > the casual
> > > > > > participant - even those who desire a deeper engagement -
> > > > > > and, in
> > > > > > practice, are completely off-putting. Committers,
> > > > > > meanwhile, have no
> > > > > > real avenue, outside of their project, for further
> > > > > > engagement.
> > > > > >
> > > > > > I've been struggling with ways to address this for years,
> > > > > > and they
> > > all
> > > > > > tend to founder on the rocks of "People should just be
> > > > > > doing X!"
> > > which,
> > > > > > in each case, is true, but also dismissive and ultimately
> > > > > > unhelpful.
> > > > > >
> > > > > > I would like to propose that we are more proactive about
> > > > > > reaching
> > > out to
> > > > > > our community in tiny, consumable bites, that hint at a
> > > > > > larger feast
> > > > > > that they're missing out on.
> > > > > >
> > > > > > Here's my proposal, but I cannot (and will not) tackle this
> > > > > > alone,
> > > > > > because that guarantees failure, which guaranteed less
> > > participation the
> > > > > > next time we suggest something like this.
> > > > > >
> > > > > > Proposal/Brainstorming doc:
> > > https://hackmd.io/JaLaGy56T8qT3ODABLVswA
> > > > > >
> > > > > > It's an intentionally simple idea - a minimum viable idea,
> > > > > > one
> > > might say.
> > > > > >
> > > > > > I want to know who's going to help make it a reality. Not
> > > particularly
> > > > > > interested in "that's a great idea", as much as "I will
> > > > > > help make it
> > > > > > happen."
> > > > > >
> > > > > > This will involve engagement with Events, M&P, and Board,
> > > > > > at a
> > > minimum,
> > > > > > but over time we'd hopefully engage everyone at the
> > > > > > Foundation in
> > > > > > content creation. But, even then, I want to keep this tiny
> > > > > > and
> > > > > > consumable - content that you can absorb in 2-5 minutes,
> > > > > > always
> > > with a
> > > > > > "to get more engaged ..." call to action aspect to it.
> > > > > >
> > > > > > Come help me develop community.
> > > > > >
> > > > > > --Rich
> > > > > >
> > > > > >
> > > -----------------------------------------------------------------
> > > ----
> > > > > > To unsubscribe, e-mail:
> > > > > > dev-unsubscribe@community.apache.org
> > > > > > For additional commands, e-mail:
> > > > > > dev-help@community.apache.org
> > > > > >
> > > > >
> > > > > -------------------------------------------------------------
> > > > > --------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > > > For additional commands, e-mail:
> > > > > dev-help@community.apache.org
> > > > >
> > > > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > For additional commands, e-mail: dev-help@community.apache.org
> > >
> > >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, May 2, 2022 at 9:57 AM Josh Fischer <jo...@joshfischer.io> wrote:
>
> The newsletter has been updated and just about ready for sending out.. Not
> sure of the whos or hows of getting this across the foundation. Is there
> a preferred way that I can get this distributed? Is this something only
> a member can/should do?
Emails sent to members-notify@apache.org will be placed into a
moderation queue, and if approved, will be sent to all ASF members.
So anybody can send the email, but in general, there is no guarantee
that such emsils will get approved. In this case, however, approval
is virtually guaranteed as the email is expected.
I'd recommend sending the emails as plain text. My attempt last month
to copy/paste from the wiki resulted in sub-optimal formatting.
Thanks for following up!
- Sam Ruby
> On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <jo...@joshfischer.io> wrote:
>
> > We have room for another bullet point or two if anyone wants to add
> > anything to the critical committer communications letter. We have about
> > two weeks before it will be sent out. Link below.
> >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929
> >
> > - Josh
> >
> > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net> wrote:
> >
> >> On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer <jo...@joshfischer.io> wrote:
> >> >
> >> > Created a starter with a few fun facts here:
> >> > https://cwiki.apache.org/confluence/x/0YyFD
> >> >
> >> > Feel free to add or take away as you see fit.
> >>
> >> THANK YOU!
> >>
> >> > - Josh
> >>
> >> - Sam Ruby
> >>
> >> > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby <ru...@intertwingly.net> wrote:
> >> >
> >> > > Message has been posted. Next time it probably should be a pure plain
> >> > > text version.
> >> > >
> >> > > Anybody want to get started on May? Create the wiki page, put some
> >> > > content there, and then send it out the first week in May after others
> >> > > have been given the opportunity to contribute.
> >> > >
> >> > > - Sam Ruby
> >> > >
> >> > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen <rb...@rcbowen.com>
> >> wrote:
> >> > > >
> >> > > > Problem: Members (and, more generally, committers) are less engaged
> >> with
> >> > > > the larger Foundation than at any point in our history. Meanwhile,
> >> the
> >> > > > mechanisms for getting more engaged (eg, the members mailing list)
> >> are a
> >> > > > firehose of unrelated content that is very frustrating to the casual
> >> > > > participant - even those who desire a deeper engagement - and, in
> >> > > > practice, are completely off-putting. Committers, meanwhile, have no
> >> > > > real avenue, outside of their project, for further engagement.
> >> > > >
> >> > > > I've been struggling with ways to address this for years, and they
> >> all
> >> > > > tend to founder on the rocks of "People should just be doing X!"
> >> which,
> >> > > > in each case, is true, but also dismissive and ultimately unhelpful.
> >> > > >
> >> > > > I would like to propose that we are more proactive about reaching
> >> out to
> >> > > > our community in tiny, consumable bites, that hint at a larger feast
> >> > > > that they're missing out on.
> >> > > >
> >> > > > Here's my proposal, but I cannot (and will not) tackle this alone,
> >> > > > because that guarantees failure, which guaranteed less
> >> participation the
> >> > > > next time we suggest something like this.
> >> > > >
> >> > > > Proposal/Brainstorming doc:
> >> https://hackmd.io/JaLaGy56T8qT3ODABLVswA
> >> > > >
> >> > > > It's an intentionally simple idea - a minimum viable idea, one
> >> might say.
> >> > > >
> >> > > > I want to know who's going to help make it a reality. Not
> >> particularly
> >> > > > interested in "that's a great idea", as much as "I will help make it
> >> > > > happen."
> >> > > >
> >> > > > This will involve engagement with Events, M&P, and Board, at a
> >> minimum,
> >> > > > but over time we'd hopefully engage everyone at the Foundation in
> >> > > > content creation. But, even then, I want to keep this tiny and
> >> > > > consumable - content that you can absorb in 2-5 minutes, always
> >> with a
> >> > > > "to get more engaged ..." call to action aspect to it.
> >> > > >
> >> > > > Come help me develop community.
> >> > > >
> >> > > > --Rich
> >> > > >
> >> > > >
> >> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> > > > For additional commands, e-mail: dev-help@community.apache.org
> >> > > >
> >> > >
> >> > > ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> > > For additional commands, e-mail: dev-help@community.apache.org
> >> > >
> >> > >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org