You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Rich Bowen <rb...@rcbowen.com> on 2022/03/10 15:00:57 UTC
Idea: Monthly Members Moment/Critical Committer Communications
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
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
Rich,
I will help make it happen.
- Josh
On Thu, Mar 10, 2022 at 9: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
>
> --
Sent from A Mobile Device
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
My thoughts too (and BTW. I think this is great to start discussion
before we do it).
I think asking people is one thing which is important, but often you
might get answers from people who are outspoken, loud, and have a lot
of time - which I think is not the crowd we want to engage.
As one of the "loud" people, I see the need of getting others engaged.
I think from earlier discussions we see that there is a huge group of
people that we miss on and while they might just start reading when
they see a positive and "personal" content, it's unlikely they will
engage now and tell what they need, I am afraid.
I personally think the big point of the idea here is to make people
more curious about what's going on, and make them aware that ASF might
be a "friendly" and "safe" (but also not welcoming to disruption)
environment - one where they will not be afraid to speak and
participate (and engage later).
This is my "big hairy goal" to achieve at least when I think of it :).
I thought a bit about it, I tried to think of what was the best way to
make "use" of the loud people we have to get to the "not loud" ones.
My proposal/idea (not super well formed though) is - maybe we could
reach out to some of those "loud" people like me and ask them
directly. We ask them to identify someone in their area of influence
who is "not loud", but does some fantastic things (and ask them
personally to provide some few paragraph statements of what they are
proud of. I think this might be the best way to "make a good use"
those loud people (like me) to do community building (this has few
nice properties - this might give the "loud" people some achievement,
and make them proud that they helped someone to step up, it might show
them that they can achieve more positive things by encouraging others
and few more things I can think of). This also has the potential of a
"snowball" effect as the people who step-up might later encourage
others.
I am not sure what's the best way to reach out to those "loud" people
- but maybe simply reaching out to them personally is best. Almost by
definition, we all know who those "loud" people are, we could probably
split between ourselves who we reach out to if we know them better or
interact with them. That might be a good seed and "test" if we can get
something this way.
WDYT?
J.
On Wed, Mar 30, 2022 at 6:35 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
> On Tue, 2022-03-29 at 15:51 -0500, Josh Fischer wrote:
> > Hey All,
> >
> > Some random thoughts/questions:
> >
> > I'm looking at the content on the newsletter page and my first few
> > thoughts
> > are "I don't know what to include" and probably more important "what
> > do
> > people want to read?". Would it be helpful to ask readers what they
> > want to
> > hear about in the newsletter? I see the line "*If you have a message
> > to
> > send to the membership, join us on the comdev mailing list
> > <ht...@community.apache.org> to find
> > out
> > how." *It's possible this line already takes care of that question.
> > Should
> > we try to engage readers via some other means? Whether it be a web
> > form or
> > something else? If so, how would we go about standing something like
> > this
> > up?
>
> While I'm open to anything, I think that keeping this as lightweight as
> possible is probably the path to actually succeeding. Perhaps just a
> Google Form initially to collect content suggestions.
>
> I'd also encourage us to keep the newsletter itself as brief as
> possible - just the stuff that members *must* know, and possibly links
> to places (the blog? project lists?) where they can dig deeper.
>
> That's, of course, just my opinion, and I am sure that if we are
> successful, it will evolve over time.
>
>
>
> ---------------------------------------------------------------------
> 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>.
On Tue, 2022-03-29 at 15:51 -0500, Josh Fischer wrote:
> Hey All,
>
> Some random thoughts/questions:
>
> I'm looking at the content on the newsletter page and my first few
> thoughts
> are "I don't know what to include" and probably more important "what
> do
> people want to read?". Would it be helpful to ask readers what they
> want to
> hear about in the newsletter? I see the line "*If you have a message
> to
> send to the membership, join us on the comdev mailing list
> <ht...@community.apache.org> to find
> out
> how." *It's possible this line already takes care of that question.
> Should
> we try to engage readers via some other means? Whether it be a web
> form or
> something else? If so, how would we go about standing something like
> this
> up?
While I'm open to anything, I think that keeping this as lightweight as
possible is probably the path to actually succeeding. Perhaps just a
Google Form initially to collect content suggestions.
I'd also encourage us to keep the newsletter itself as brief as
possible - just the stuff that members *must* know, and possibly links
to places (the blog? project lists?) where they can dig deeper.
That's, of course, just my opinion, and I am sure that if we are
successful, it will evolve over time.
---------------------------------------------------------------------
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>.
Hey All,
Some random thoughts/questions:
I'm looking at the content on the newsletter page and my first few thoughts
are "I don't know what to include" and probably more important "what do
people want to read?". Would it be helpful to ask readers what they want to
hear about in the newsletter? I see the line "*If you have a message to
send to the membership, join us on the comdev mailing list
<ht...@community.apache.org> to find out
how." *It's possible this line already takes care of that question. Should
we try to engage readers via some other means? Whether it be a web form or
something else? If so, how would we go about standing something like this
up?
On Tue, Mar 29, 2022 at 10:30 AM Rich Bowen <rb...@rcbowen.com> wrote:
> FYI, as some of you are aware, I started a new job earlier this month,
> and that is consuming *all* of my brain-cycles. If someone else wanted
> to step up and start organizing the April newsletter, that would be
> great - although we're alreay behind schedule for that. Failing that,
> it seems more likely that I would be able to be involved in a May
> newsletter. Please don't think that this has to be led by me - ideally,
> we'd each take turns as editor-in-chief, rather than create yet another
> SPOF. Thanks.
>
> On Thu, 2022-03-10 at 10:00 -0500, Rich Bowen 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
>
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
FYI, as some of you are aware, I started a new job earlier this month,
and that is consuming *all* of my brain-cycles. If someone else wanted
to step up and start organizing the April newsletter, that would be
great - although we're alreay behind schedule for that. Failing that,
it seems more likely that I would be able to be involved in a May
newsletter. Please don't think that this has to be led by me - ideally,
we'd each take turns as editor-in-chief, rather than create yet another
SPOF. Thanks.
On Thu, 2022-03-10 at 10:00 -0500, Rich Bowen 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
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Willem Jiang <wi...@gmail.com>.
big +1 to host the new letter draft to the wiki so every member can
add some news on that.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Mar 31, 2022 at 4:08 AM Sam Ruby <ru...@intertwingly.net> wrote:
>
> On Tue, Mar 22, 2022 at 12:46 PM Rich Bowen <rb...@rcbowen.com> wrote:
> >
> > Ok, looks like we have three volunteers - Josh Fisher, Dave Fisher, and
> > Andrew Wetmore. So I don't feel like I'm doing this alone, which is
> > good.
> >
> > What we need to do still is:
> >
> > 1) Pitch this to the membership to determine whether this should land
> > on members@ or members-notify@
> > 2) Write sample newsletter: https://hackmd.io/0eeIQ7wDQnKr-LAgN6QqLA
> > 3) Figure out intake tooling (could just be a Google Form) for getting
> > content in
> > 4) Figure out our schedule/deadlines to ensure that we get this out in
> > a predictable cadence.
> >
> > I'm going to draft a proposal to send to members@ (probably won't
> > happen today) and run it back past this thread, unless someone beats me
> > to it.
>
> I'm a big fan of Cunninham's law:
> https://meta.wikimedia.org/wiki/Cunningham%27s_Law
>
> Accordingly, I've taken the sample newsletter and posted it here:
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
>
> I've changed March to April. Added a mention of the June members
> meeting. Changed the link to the ASF board meeting to the April
> meeting. Added a link to the whimsy page that tracks members watch.
>
> The advantage of the "ASFP" wiki is that it is member private and all
> ASF members have update access.
>
> Unless there is a strong objection or better proposal the content of
> that page as it exists on April 5th will be sent to
> members-notify,subject to approval by Joe Brockmeier.
>
> - Sam Ruby
>
> > --Rich
> >
> > On Thu, 2022-03-10 at 10:00 -0500, Rich Bowen 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 Rich Bowen <rb...@rcbowen.com>.
On Wed, 2022-03-30 at 16:07 -0400, Sam Ruby wrote:
>
> I'm a big fan of Cunninham's law:
> https://meta.wikimedia.org/wiki/Cunningham%27s_Law
>
> Accordingly, I've taken the sample newsletter and posted it here:
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
>
> I've changed March to April. Added a mention of the June members
> meeting. Changed the link to the ASF board meeting to the April
> meeting. Added a link to the whimsy page that tracks members watch.
>
> The advantage of the "ASFP" wiki is that it is member private and all
> ASF members have update access.
>
> Unless there is a strong objection or better proposal the content of
> that page as it exists on April 5th will be sent to
> members-notify,subject to approval by Joe Brockmeier.
Sounds great to me.
---------------------------------------------------------------------
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 Bertrand Delacretaz <bd...@apache.org>.
Hi,
Le mar. 5 avr. 2022 à 15:21, Rich Bowen <rb...@rcbowen.com> a écrit :
> ...AFAIK, while there are a few things in the current draft
> that are not open to the public (ie, board meeting for example) there's
> no harm in informing the public - they just cannot participate...
I agree in principle, but we should clarify whether we are ok with
publishing private URLs.
Those are protected and there's already a good number of them out
there, but I think it's good to define, as a general principle,
whether we are ok with publishing URLs that only ASF members have
access to.
-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 Rich Bowen <rb...@rcbowen.com>.
On Tue, 2022-04-05 at 08:44 +0200, Bertrand Delacretaz wrote:
> Le lun. 4 avr. 2022 à 19:16, Priya Sharma
> <pr...@gmail.com> a écrit :
> >
> > I am also not able to view those pages (perhaps only ASF members
> > have
> > access)...
>
> That's correct, the ASFP wiki space is restricted to ASF members.
>
> It's not fantastic that we're discussing here and not letting people
> see that draft - OTOH that's more motivation to create a public
> version of those news, which would be a good thing. We might just
> send
> the public version here.
My initial proposal was to have a members version (with member-
confidential info) and a more general committers version for public
consumption. AFAIK, while there are a few things in the current draft
that are not open to the public (ie, board meeting for example) there's
no harm in informing the public - they just cannot participate.
---------------------------------------------------------------------
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 Bertrand Delacretaz <bd...@apache.org>.
Le lun. 4 avr. 2022 à 19:16, Priya Sharma
<pr...@gmail.com> a écrit :
>
> I am also not able to view those pages (perhaps only ASF members have
> access)...
That's correct, the ASFP wiki space is restricted to ASF members.
It's not fantastic that we're discussing here and not letting people
see that draft - OTOH that's more motivation to create a public
version of those news, which would be a good thing. We might just send
the public version here.
-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 Priya Sharma <pr...@gmail.com>.
I am also not able to view those pages (perhaps only ASF members have
access).
On Mon, 4 Apr 2022 at 19:47, Josh Fischer <jo...@joshfischer.io> wrote:
> I've tried to access both of the links that Betrand sent and I get a "Page
> not found" message in confluence.
>
> On Thu, Mar 31, 2022 at 3:15 AM Bertrand Delacretaz <
> bdelacretaz@apache.org>
> wrote:
>
> > Hi,
> >
> > Sam Ruby wrote:
> >
> > >... Accordingly, I've taken the sample newsletter and posted it here:
> > >
> >
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
> > ...
> >
> > I've changed the structure slightly, with
> > https://cwiki.apache.org/confluence/display/ASFP/Member+Moments being
> > the homepage of those (work-in-progress, restricted to ASF Members)
> > newsletters, displaying a list of its child pages. And moved your
> > suggested content to
> >
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
> > accordingly.
> >
> > I hope it works for you - Cunningham's law implies that what you
> > initially post is wrong so I had to fix it ;-)
> >
> > -Bertrand
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> >
>
--
Best Regards,
Priya
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
I've tried to access both of the links that Betrand sent and I get a "Page
not found" message in confluence.
On Thu, Mar 31, 2022 at 3:15 AM Bertrand Delacretaz <bd...@apache.org>
wrote:
> Hi,
>
> Sam Ruby wrote:
>
> >... Accordingly, I've taken the sample newsletter and posted it here:
> >
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
> ...
>
> I've changed the structure slightly, with
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moments being
> the homepage of those (work-in-progress, restricted to ASF Members)
> newsletters, displaying a list of its child pages. And moved your
> suggested content to
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
> accordingly.
>
> I hope it works for you - Cunningham's law implies that what you
> initially post is wrong so I had to fix it ;-)
>
> -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 Sam Ruby <ru...@intertwingly.net>.
On Thu, Mar 31, 2022 at 4:15 AM Bertrand Delacretaz
<bd...@apache.org> wrote:
>
> Hi,
>
> Sam Ruby wrote:
>
> >... Accordingly, I've taken the sample newsletter and posted it here:
> > https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022 ...
>
> I've changed the structure slightly, with
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moments being
> the homepage of those (work-in-progress, restricted to ASF Members)
> newsletters, displaying a list of its child pages. And moved your
> suggested content to
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
> accordingly.
>
> I hope it works for you - Cunningham's law implies that what you
> initially post is wrong so I had to fix it ;-)
Thanks! Now everybody join in. These pages aren't Rich's. They
aren't mine. They aren't Bertrands. They are ours.
Act like you own the place. Commit then review. Don't wait for
permission. Don't worry that it isn't perfect. And if you see
something that needs fixing - fix it!
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
- Sam Ruby
---------------------------------------------------------------------
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 Bertrand Delacretaz <bd...@apache.org>.
Hi,
Sam Ruby wrote:
>... Accordingly, I've taken the sample newsletter and posted it here:
> https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022 ...
I've changed the structure slightly, with
https://cwiki.apache.org/confluence/display/ASFP/Member+Moments being
the homepage of those (work-in-progress, restricted to ASF Members)
newsletters, displaying a list of its child pages. And moved your
suggested content to
https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
accordingly.
I hope it works for you - Cunningham's law implies that what you
initially post is wrong so I had to fix it ;-)
-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 Sam Ruby <ru...@intertwingly.net>.
On Tue, Mar 22, 2022 at 12:46 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
> Ok, looks like we have three volunteers - Josh Fisher, Dave Fisher, and
> Andrew Wetmore. So I don't feel like I'm doing this alone, which is
> good.
>
> What we need to do still is:
>
> 1) Pitch this to the membership to determine whether this should land
> on members@ or members-notify@
> 2) Write sample newsletter: https://hackmd.io/0eeIQ7wDQnKr-LAgN6QqLA
> 3) Figure out intake tooling (could just be a Google Form) for getting
> content in
> 4) Figure out our schedule/deadlines to ensure that we get this out in
> a predictable cadence.
>
> I'm going to draft a proposal to send to members@ (probably won't
> happen today) and run it back past this thread, unless someone beats me
> to it.
I'm a big fan of Cunninham's law:
https://meta.wikimedia.org/wiki/Cunningham%27s_Law
Accordingly, I've taken the sample newsletter and posted it here:
https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022
I've changed March to April. Added a mention of the June members
meeting. Changed the link to the ASF board meeting to the April
meeting. Added a link to the whimsy page that tracks members watch.
The advantage of the "ASFP" wiki is that it is member private and all
ASF members have update access.
Unless there is a strong objection or better proposal the content of
that page as it exists on April 5th will be sent to
members-notify,subject to approval by Joe Brockmeier.
- Sam Ruby
> --Rich
>
> On Thu, 2022-03-10 at 10:00 -0500, Rich Bowen 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
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Jarek Potiuk <ja...@potiuk.com>.
I am also happy to help. We need more positivity in members@ :D
On Tue, Mar 22, 2022 at 6:40 PM Priya Sharma
<pr...@gmail.com> wrote:
>
> Hey team,
> Please count me in. I will help make it happen.
>
> On Tue, 22 Mar 2022 at 22:43, Rich Bowen <rb...@rcbowen.com> wrote:
>
> > On Tue, 2022-03-22 at 17:54 +0100, Bertrand Delacretaz wrote:
> > > Hi,
> > >
> > > Le mar. 22 mars 2022 à 17:46, Rich Bowen <rb...@rcbowen.com> a écrit
> > > :
> > > > ...1) Pitch this to the membership to determine whether this should
> > > > land
> > > > on members@ or members-notify@..
> > >
> > > I think it's clearly members@ - the other list is meant for "formal
> > > notifications" [1], with minimal traffic.
> > >
> > > With a suitable subject line header such as [news] maybe.
> >
> > Sure, that is one option. The downside is that the goal of this is to
> > reach all members, and members@ is noisy, leading a lot of members to
> > basically mute it.
> > >
> >
> > OTOH, sending to members-notify would ensure that everyone receives it
> > (although they still might not read it), while having the negative that
> > it is "forcing" members to receive yet another communication they might
> > not want.
> >
> > I think that each has a clear advantage, and a clear disadvantage, and
> > that there's not an obvious "right" answer.
> >
> > I'd also like to discourage people from *responding* to the newsletter
> > (at least on the members@ list) because that invariably leads to
> > drifting from topic, and to the thread then getting ignored by folks
> > who are tired of yet another megathread.
> >
> > All of these are things that will go into my proposal draft.
> >
> >
> > > [1]
> > > https://whimsy.apache.org/board/minutes/Create_members_notify.html
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
> --
> Best Regards,
> Priya
---------------------------------------------------------------------
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 Priya Sharma <pr...@gmail.com>.
Hey team,
Please count me in. I will help make it happen.
On Tue, 22 Mar 2022 at 22:43, Rich Bowen <rb...@rcbowen.com> wrote:
> On Tue, 2022-03-22 at 17:54 +0100, Bertrand Delacretaz wrote:
> > Hi,
> >
> > Le mar. 22 mars 2022 à 17:46, Rich Bowen <rb...@rcbowen.com> a écrit
> > :
> > > ...1) Pitch this to the membership to determine whether this should
> > > land
> > > on members@ or members-notify@..
> >
> > I think it's clearly members@ - the other list is meant for "formal
> > notifications" [1], with minimal traffic.
> >
> > With a suitable subject line header such as [news] maybe.
>
> Sure, that is one option. The downside is that the goal of this is to
> reach all members, and members@ is noisy, leading a lot of members to
> basically mute it.
> >
>
> OTOH, sending to members-notify would ensure that everyone receives it
> (although they still might not read it), while having the negative that
> it is "forcing" members to receive yet another communication they might
> not want.
>
> I think that each has a clear advantage, and a clear disadvantage, and
> that there's not an obvious "right" answer.
>
> I'd also like to discourage people from *responding* to the newsletter
> (at least on the members@ list) because that invariably leads to
> drifting from topic, and to the thread then getting ignored by folks
> who are tired of yet another megathread.
>
> All of these are things that will go into my proposal draft.
>
>
> > [1]
> > https://whimsy.apache.org/board/minutes/Create_members_notify.html
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
Best Regards,
Priya
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
On Tue, 2022-03-22 at 17:54 +0100, Bertrand Delacretaz wrote:
> Hi,
>
> Le mar. 22 mars 2022 à 17:46, Rich Bowen <rb...@rcbowen.com> a écrit
> :
> > ...1) Pitch this to the membership to determine whether this should
> > land
> > on members@ or members-notify@..
>
> I think it's clearly members@ - the other list is meant for "formal
> notifications" [1], with minimal traffic.
>
> With a suitable subject line header such as [news] maybe.
Sure, that is one option. The downside is that the goal of this is to
reach all members, and members@ is noisy, leading a lot of members to
basically mute it.
>
OTOH, sending to members-notify would ensure that everyone receives it
(although they still might not read it), while having the negative that
it is "forcing" members to receive yet another communication they might
not want.
I think that each has a clear advantage, and a clear disadvantage, and
that there's not an obvious "right" answer.
I'd also like to discourage people from *responding* to the newsletter
(at least on the members@ list) because that invariably leads to
drifting from topic, and to the thread then getting ignored by folks
who are tired of yet another megathread.
All of these are things that will go into my proposal draft.
> [1]
> https://whimsy.apache.org/board/minutes/Create_members_notify.html
>
> ---------------------------------------------------------------------
> 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 Bertrand Delacretaz <bd...@apache.org>.
Hi,
Le mar. 22 mars 2022 à 17:46, Rich Bowen <rb...@rcbowen.com> a écrit :
> ...1) Pitch this to the membership to determine whether this should land
> on members@ or members-notify@..
I think it's clearly members@ - the other list is meant for "formal
notifications" [1], with minimal traffic.
With a suitable subject line header such as [news] maybe.
-Bertrand
[1] https://whimsy.apache.org/board/minutes/Create_members_notify.html
---------------------------------------------------------------------
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>.
Once a year member meetings are a bit long for us.
The regular newsletter can help us to create a rhythm for the community.
Please count me in, I really like the idea and want to make it happen.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Mar 23, 2022 at 12:46 AM Rich Bowen <rb...@rcbowen.com> wrote:
>
> Ok, looks like we have three volunteers - Josh Fisher, Dave Fisher, and
> Andrew Wetmore. So I don't feel like I'm doing this alone, which is
> good.
>
> What we need to do still is:
>
> 1) Pitch this to the membership to determine whether this should land
> on members@ or members-notify@
> 2) Write sample newsletter: https://hackmd.io/0eeIQ7wDQnKr-LAgN6QqLA
> 3) Figure out intake tooling (could just be a Google Form) for getting
> content in
> 4) Figure out our schedule/deadlines to ensure that we get this out in
> a predictable cadence.
>
> I'm going to draft a proposal to send to members@ (probably won't
> happen today) and run it back past this thread, unless someone beats me
> to it.
>
> --Rich
>
> On Thu, 2022-03-10 at 10:00 -0500, Rich Bowen 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
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Rich Bowen <rb...@rcbowen.com>.
Ok, looks like we have three volunteers - Josh Fisher, Dave Fisher, and
Andrew Wetmore. So I don't feel like I'm doing this alone, which is
good.
What we need to do still is:
1) Pitch this to the membership to determine whether this should land
on members@ or members-notify@
2) Write sample newsletter: https://hackmd.io/0eeIQ7wDQnKr-LAgN6QqLA
3) Figure out intake tooling (could just be a Google Form) for getting
content in
4) Figure out our schedule/deadlines to ensure that we get this out in
a predictable cadence.
I'm going to draft a proposal to send to members@ (probably won't
happen today) and run it back past this thread, unless someone beats me
to it.
--Rich
On Thu, 2022-03-10 at 10:00 -0500, Rich Bowen 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
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
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Josh Fischer <jo...@joshfischer.io>.
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 Josh Fischer <jo...@joshfischer.io>.
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 Sam Ruby <ru...@intertwingly.net>.
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 Josh Fischer <jo...@joshfischer.io>.
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.
- Josh
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
>
>
Re: Idea: Monthly Members Moment/Critical Committer Communications
Posted by Sam Ruby <ru...@intertwingly.net>.
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