You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Josh Fischer <jo...@joshfischer.io> on 2022/06/07 23:44:32 UTC
Monthly Member's Moment - July 2022
The June newsletter was recently sent to members-announce@a.o.
Let's target to release the next on July 5, 2022. Anyone want to take
point for July?
Link for next template is below:
https://cwiki.apache.org/confluence/x/Cg31D
Re: Monthly Member's Moment - July 2022
Posted by Jarek Potiuk <ja...@potiuk.com>.
I am just about to t send the moments tomorrow (pinged Infra again to come
back, if not, I will come up with something else) - any comments, feel free
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=217386250
On Mon, Jun 27, 2022 at 4:07 PM Josh Fischer <jo...@joshfischer.io> wrote:
> It’s really cool you reached out to the Infrastructure team. Well done,
> Jarek.
>
> On Mon, Jun 27, 2022 at 8:50 AM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > I prepared a draft which I tried to make a bit more "personal" :). I
> > have reached out to infra - to get a bit more personal message of what
> > they are doing for the "did you know" section (let's see).
> > I thought a bit and looked at past ones and I agree, brevity of this
> > message is a key, but also there is a risk that "short" messages are
> > stripped-off any personal touch. I tried to make it not-too long but
> > also not to "dry" either. Not sure if I succeeded.
> >
> > Draft
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=217386250
> > - any feedback/suggestions are most welcome also if any of you have
> > some personal story to share - feel free :).
> >
> > J.
> >
> > On Sat, Jun 11, 2022 at 9:49 PM Josh Fischer <jo...@joshfischer.io>
> wrote:
> > >
> > > Matt and Jarek,
> > >
> > > I think you both have good ideas. Getting more people to help with
> this
> > > report will allow for that unique flair.
> > >
> > > I’m looking forward to what comes out in the next report.
> > >
> > > - Josh
> > >
> > > On Sat, Jun 11, 2022 at 1:41 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > > If we are speaking of the future/experimenting - I think Members
> > Moments
> > > > should be much more personal and something that creates a sense of
> > > > participation in something extraordinary - so I would not compare
> this
> > to
> > > > "board reports". If we can make something that will interest people
> and
> > > > grab their attention and "sense of belonging" - that would be the
> best
> > > > format I think.
> > > >
> > > > I personally always kind of frown upon "repeated" regular reports -
> > always
> > > > showing the same points and in the same "form". They are needed of
> > course,
> > > > but maybe "members moment" should be less informative and more
> > "bringing
> > > > people together" (at least that's how I think about it).
> > > >
> > > > I'd even say as much as this - it would be great if every next "chief
> > > > editor" will add some personal touch to it in the way that the editor
> > feels
> > > > like :). Some "general" content should be similar - but I am thinking
> > about
> > > > inviting someone who would like to say a sentence about what they are
> > proud
> > > > of doing for the Foundation this month. Someone who would not
> normally
> > be
> > > > too "vocal" about it. I mentioned that initially when this
> discussion
> > > > started. But this might be different thing from the next person next
> > month
> > > > :),
> > > >
> > > > I think that might be the most important "task" of "chief editor" -
> to
> > come
> > > > up with something new and "personal touch" to it.
> > > >
> > > > J.
> > > >
> > > > On Wed, Jun 8, 2022 at 4:51 PM Matt Sicker <bo...@gmail.com> wrote:
> > > >
> > > > > I'd imagine some sort of top-line status report could be a level of
> > > > > detail that would work? Essentially, the main part of the email
> would
> > > > > be a few bullet points about what's going on, and a secondary part
> > > > > could go into more details on each point or link to further
> details.
> > > > > I'm imagining the type of report that leadership typically reads in
> > > > > other corporations. Not at the level of detail of board minutes of
> > > > > course.
> > > > >
> > > > > On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <jo...@joshfischer.io>
> > wrote:
> > > > > >
> > > > > > For sure. Make it the way you think it will be best for readers.
> > > > > >
> > > > > > On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com>
> > wrote:
> > > > > >
> > > > > > > I am happy to, but I am afraid as chief-editor I will opt for a
> > bit
> > > > > longer
> > > > > > > digest.
> > > > > > >
> > > > > > > BTW. I am thinking on how to experiment and see the actual
> > usefulness
> > > > > of it
> > > > > > > rather than "anecdotal feedback". The fact that few people
> > complained
> > > > > about
> > > > > > > messages being too long, does not mean that the others would
> not
> > like
> > > > > it a
> > > > > > > bit longer and more useful. I don't know how but will think
> > about it
> > > > -
> > > > > I
> > > > > > > would love to see some objective, measurable data on it to be
> > able to
> > > > > make
> > > > > > > decisions.
> > > > > > >
> > > > > > > J.
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <
> josh@joshfischer.io
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > The June newsletter was recently sent to
> members-announce@a.o.
> > > > > > > >
> > > > > > > > Let's target to release the next on July 5, 2022. Anyone
> want
> > to
> > > > > take
> > > > > > > > point for July?
> > > > > > > >
> > > > > > > > Link for next template is below:
> > > > > > > >
> > > > > > > > https://cwiki.apache.org/confluence/x/Cg31D
> > > > > > > >
> > > > > > >
> > > > > > --
> > > > > > 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
> >
> > --
> Sent from A Mobile Device
>
Re: Monthly Member's Moment - July 2022
Posted by Josh Fischer <jo...@joshfischer.io>.
It’s really cool you reached out to the Infrastructure team. Well done,
Jarek.
On Mon, Jun 27, 2022 at 8:50 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> I prepared a draft which I tried to make a bit more "personal" :). I
> have reached out to infra - to get a bit more personal message of what
> they are doing for the "did you know" section (let's see).
> I thought a bit and looked at past ones and I agree, brevity of this
> message is a key, but also there is a risk that "short" messages are
> stripped-off any personal touch. I tried to make it not-too long but
> also not to "dry" either. Not sure if I succeeded.
>
> Draft
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=217386250
> - any feedback/suggestions are most welcome also if any of you have
> some personal story to share - feel free :).
>
> J.
>
> On Sat, Jun 11, 2022 at 9:49 PM Josh Fischer <jo...@joshfischer.io> wrote:
> >
> > Matt and Jarek,
> >
> > I think you both have good ideas. Getting more people to help with this
> > report will allow for that unique flair.
> >
> > I’m looking forward to what comes out in the next report.
> >
> > - Josh
> >
> > On Sat, Jun 11, 2022 at 1:41 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > If we are speaking of the future/experimenting - I think Members
> Moments
> > > should be much more personal and something that creates a sense of
> > > participation in something extraordinary - so I would not compare this
> to
> > > "board reports". If we can make something that will interest people and
> > > grab their attention and "sense of belonging" - that would be the best
> > > format I think.
> > >
> > > I personally always kind of frown upon "repeated" regular reports -
> always
> > > showing the same points and in the same "form". They are needed of
> course,
> > > but maybe "members moment" should be less informative and more
> "bringing
> > > people together" (at least that's how I think about it).
> > >
> > > I'd even say as much as this - it would be great if every next "chief
> > > editor" will add some personal touch to it in the way that the editor
> feels
> > > like :). Some "general" content should be similar - but I am thinking
> about
> > > inviting someone who would like to say a sentence about what they are
> proud
> > > of doing for the Foundation this month. Someone who would not normally
> be
> > > too "vocal" about it. I mentioned that initially when this discussion
> > > started. But this might be different thing from the next person next
> month
> > > :),
> > >
> > > I think that might be the most important "task" of "chief editor" - to
> come
> > > up with something new and "personal touch" to it.
> > >
> > > J.
> > >
> > > On Wed, Jun 8, 2022 at 4:51 PM Matt Sicker <bo...@gmail.com> wrote:
> > >
> > > > I'd imagine some sort of top-line status report could be a level of
> > > > detail that would work? Essentially, the main part of the email would
> > > > be a few bullet points about what's going on, and a secondary part
> > > > could go into more details on each point or link to further details.
> > > > I'm imagining the type of report that leadership typically reads in
> > > > other corporations. Not at the level of detail of board minutes of
> > > > course.
> > > >
> > > > On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <jo...@joshfischer.io>
> wrote:
> > > > >
> > > > > For sure. Make it the way you think it will be best for readers.
> > > > >
> > > > > On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com>
> wrote:
> > > > >
> > > > > > I am happy to, but I am afraid as chief-editor I will opt for a
> bit
> > > > longer
> > > > > > digest.
> > > > > >
> > > > > > BTW. I am thinking on how to experiment and see the actual
> usefulness
> > > > of it
> > > > > > rather than "anecdotal feedback". The fact that few people
> complained
> > > > about
> > > > > > messages being too long, does not mean that the others would not
> like
> > > > it a
> > > > > > bit longer and more useful. I don't know how but will think
> about it
> > > -
> > > > I
> > > > > > would love to see some objective, measurable data on it to be
> able to
> > > > make
> > > > > > decisions.
> > > > > >
> > > > > > J.
> > > > > >
> > > > > >
> > > > > > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <josh@joshfischer.io
> >
> > > > wrote:
> > > > > >
> > > > > > > The June newsletter was recently sent to members-announce@a.o.
> > > > > > >
> > > > > > > Let's target to release the next on July 5, 2022. Anyone want
> to
> > > > take
> > > > > > > point for July?
> > > > > > >
> > > > > > > Link for next template is below:
> > > > > > >
> > > > > > > https://cwiki.apache.org/confluence/x/Cg31D
> > > > > > >
> > > > > >
> > > > > --
> > > > > 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
>
> --
Sent from A Mobile Device
Re: Monthly Member's Moment - July 2022
Posted by Jarek Potiuk <ja...@potiuk.com>.
I also created https://s.apache.org/private short URL. I always lose
far too much time to find it when I need it. This one should be
super-easy to type-in from memory.
On Mon, Jun 27, 2022 at 3:50 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> I prepared a draft which I tried to make a bit more "personal" :). I
> have reached out to infra - to get a bit more personal message of what
> they are doing for the "did you know" section (let's see).
> I thought a bit and looked at past ones and I agree, brevity of this
> message is a key, but also there is a risk that "short" messages are
> stripped-off any personal touch. I tried to make it not-too long but
> also not to "dry" either. Not sure if I succeeded.
>
> Draft https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=217386250
> - any feedback/suggestions are most welcome also if any of you have
> some personal story to share - feel free :).
>
> J.
>
> On Sat, Jun 11, 2022 at 9:49 PM Josh Fischer <jo...@joshfischer.io> wrote:
> >
> > Matt and Jarek,
> >
> > I think you both have good ideas. Getting more people to help with this
> > report will allow for that unique flair.
> >
> > I’m looking forward to what comes out in the next report.
> >
> > - Josh
> >
> > On Sat, Jun 11, 2022 at 1:41 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > If we are speaking of the future/experimenting - I think Members Moments
> > > should be much more personal and something that creates a sense of
> > > participation in something extraordinary - so I would not compare this to
> > > "board reports". If we can make something that will interest people and
> > > grab their attention and "sense of belonging" - that would be the best
> > > format I think.
> > >
> > > I personally always kind of frown upon "repeated" regular reports - always
> > > showing the same points and in the same "form". They are needed of course,
> > > but maybe "members moment" should be less informative and more "bringing
> > > people together" (at least that's how I think about it).
> > >
> > > I'd even say as much as this - it would be great if every next "chief
> > > editor" will add some personal touch to it in the way that the editor feels
> > > like :). Some "general" content should be similar - but I am thinking about
> > > inviting someone who would like to say a sentence about what they are proud
> > > of doing for the Foundation this month. Someone who would not normally be
> > > too "vocal" about it. I mentioned that initially when this discussion
> > > started. But this might be different thing from the next person next month
> > > :),
> > >
> > > I think that might be the most important "task" of "chief editor" - to come
> > > up with something new and "personal touch" to it.
> > >
> > > J.
> > >
> > > On Wed, Jun 8, 2022 at 4:51 PM Matt Sicker <bo...@gmail.com> wrote:
> > >
> > > > I'd imagine some sort of top-line status report could be a level of
> > > > detail that would work? Essentially, the main part of the email would
> > > > be a few bullet points about what's going on, and a secondary part
> > > > could go into more details on each point or link to further details.
> > > > I'm imagining the type of report that leadership typically reads in
> > > > other corporations. Not at the level of detail of board minutes of
> > > > course.
> > > >
> > > > On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <jo...@joshfischer.io> wrote:
> > > > >
> > > > > For sure. Make it the way you think it will be best for readers.
> > > > >
> > > > > On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> > > > >
> > > > > > I am happy to, but I am afraid as chief-editor I will opt for a bit
> > > > longer
> > > > > > digest.
> > > > > >
> > > > > > BTW. I am thinking on how to experiment and see the actual usefulness
> > > > of it
> > > > > > rather than "anecdotal feedback". The fact that few people complained
> > > > about
> > > > > > messages being too long, does not mean that the others would not like
> > > > it a
> > > > > > bit longer and more useful. I don't know how but will think about it
> > > -
> > > > I
> > > > > > would love to see some objective, measurable data on it to be able to
> > > > make
> > > > > > decisions.
> > > > > >
> > > > > > J.
> > > > > >
> > > > > >
> > > > > > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <jo...@joshfischer.io>
> > > > wrote:
> > > > > >
> > > > > > > The June newsletter was recently sent to members-announce@a.o.
> > > > > > >
> > > > > > > Let's target to release the next on July 5, 2022. Anyone want to
> > > > take
> > > > > > > point for July?
> > > > > > >
> > > > > > > Link for next template is below:
> > > > > > >
> > > > > > > https://cwiki.apache.org/confluence/x/Cg31D
> > > > > > >
> > > > > >
> > > > > --
> > > > > 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: Monthly Member's Moment - July 2022
Posted by Jarek Potiuk <ja...@potiuk.com>.
I prepared a draft which I tried to make a bit more "personal" :). I
have reached out to infra - to get a bit more personal message of what
they are doing for the "did you know" section (let's see).
I thought a bit and looked at past ones and I agree, brevity of this
message is a key, but also there is a risk that "short" messages are
stripped-off any personal touch. I tried to make it not-too long but
also not to "dry" either. Not sure if I succeeded.
Draft https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=217386250
- any feedback/suggestions are most welcome also if any of you have
some personal story to share - feel free :).
J.
On Sat, Jun 11, 2022 at 9:49 PM Josh Fischer <jo...@joshfischer.io> wrote:
>
> Matt and Jarek,
>
> I think you both have good ideas. Getting more people to help with this
> report will allow for that unique flair.
>
> I’m looking forward to what comes out in the next report.
>
> - Josh
>
> On Sat, Jun 11, 2022 at 1:41 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > If we are speaking of the future/experimenting - I think Members Moments
> > should be much more personal and something that creates a sense of
> > participation in something extraordinary - so I would not compare this to
> > "board reports". If we can make something that will interest people and
> > grab their attention and "sense of belonging" - that would be the best
> > format I think.
> >
> > I personally always kind of frown upon "repeated" regular reports - always
> > showing the same points and in the same "form". They are needed of course,
> > but maybe "members moment" should be less informative and more "bringing
> > people together" (at least that's how I think about it).
> >
> > I'd even say as much as this - it would be great if every next "chief
> > editor" will add some personal touch to it in the way that the editor feels
> > like :). Some "general" content should be similar - but I am thinking about
> > inviting someone who would like to say a sentence about what they are proud
> > of doing for the Foundation this month. Someone who would not normally be
> > too "vocal" about it. I mentioned that initially when this discussion
> > started. But this might be different thing from the next person next month
> > :),
> >
> > I think that might be the most important "task" of "chief editor" - to come
> > up with something new and "personal touch" to it.
> >
> > J.
> >
> > On Wed, Jun 8, 2022 at 4:51 PM Matt Sicker <bo...@gmail.com> wrote:
> >
> > > I'd imagine some sort of top-line status report could be a level of
> > > detail that would work? Essentially, the main part of the email would
> > > be a few bullet points about what's going on, and a secondary part
> > > could go into more details on each point or link to further details.
> > > I'm imagining the type of report that leadership typically reads in
> > > other corporations. Not at the level of detail of board minutes of
> > > course.
> > >
> > > On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <jo...@joshfischer.io> wrote:
> > > >
> > > > For sure. Make it the way you think it will be best for readers.
> > > >
> > > > On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> > > >
> > > > > I am happy to, but I am afraid as chief-editor I will opt for a bit
> > > longer
> > > > > digest.
> > > > >
> > > > > BTW. I am thinking on how to experiment and see the actual usefulness
> > > of it
> > > > > rather than "anecdotal feedback". The fact that few people complained
> > > about
> > > > > messages being too long, does not mean that the others would not like
> > > it a
> > > > > bit longer and more useful. I don't know how but will think about it
> > -
> > > I
> > > > > would love to see some objective, measurable data on it to be able to
> > > make
> > > > > decisions.
> > > > >
> > > > > J.
> > > > >
> > > > >
> > > > > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <jo...@joshfischer.io>
> > > wrote:
> > > > >
> > > > > > The June newsletter was recently sent to members-announce@a.o.
> > > > > >
> > > > > > Let's target to release the next on July 5, 2022. Anyone want to
> > > take
> > > > > > point for July?
> > > > > >
> > > > > > Link for next template is below:
> > > > > >
> > > > > > https://cwiki.apache.org/confluence/x/Cg31D
> > > > > >
> > > > >
> > > > --
> > > > 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: Monthly Member's Moment - July 2022
Posted by Josh Fischer <jo...@joshfischer.io>.
Matt and Jarek,
I think you both have good ideas. Getting more people to help with this
report will allow for that unique flair.
I’m looking forward to what comes out in the next report.
- Josh
On Sat, Jun 11, 2022 at 1:41 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> If we are speaking of the future/experimenting - I think Members Moments
> should be much more personal and something that creates a sense of
> participation in something extraordinary - so I would not compare this to
> "board reports". If we can make something that will interest people and
> grab their attention and "sense of belonging" - that would be the best
> format I think.
>
> I personally always kind of frown upon "repeated" regular reports - always
> showing the same points and in the same "form". They are needed of course,
> but maybe "members moment" should be less informative and more "bringing
> people together" (at least that's how I think about it).
>
> I'd even say as much as this - it would be great if every next "chief
> editor" will add some personal touch to it in the way that the editor feels
> like :). Some "general" content should be similar - but I am thinking about
> inviting someone who would like to say a sentence about what they are proud
> of doing for the Foundation this month. Someone who would not normally be
> too "vocal" about it. I mentioned that initially when this discussion
> started. But this might be different thing from the next person next month
> :),
>
> I think that might be the most important "task" of "chief editor" - to come
> up with something new and "personal touch" to it.
>
> J.
>
> On Wed, Jun 8, 2022 at 4:51 PM Matt Sicker <bo...@gmail.com> wrote:
>
> > I'd imagine some sort of top-line status report could be a level of
> > detail that would work? Essentially, the main part of the email would
> > be a few bullet points about what's going on, and a secondary part
> > could go into more details on each point or link to further details.
> > I'm imagining the type of report that leadership typically reads in
> > other corporations. Not at the level of detail of board minutes of
> > course.
> >
> > On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <jo...@joshfischer.io> wrote:
> > >
> > > For sure. Make it the way you think it will be best for readers.
> > >
> > > On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > > I am happy to, but I am afraid as chief-editor I will opt for a bit
> > longer
> > > > digest.
> > > >
> > > > BTW. I am thinking on how to experiment and see the actual usefulness
> > of it
> > > > rather than "anecdotal feedback". The fact that few people complained
> > about
> > > > messages being too long, does not mean that the others would not like
> > it a
> > > > bit longer and more useful. I don't know how but will think about it
> -
> > I
> > > > would love to see some objective, measurable data on it to be able to
> > make
> > > > decisions.
> > > >
> > > > J.
> > > >
> > > >
> > > > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <jo...@joshfischer.io>
> > wrote:
> > > >
> > > > > The June newsletter was recently sent to members-announce@a.o.
> > > > >
> > > > > Let's target to release the next on July 5, 2022. Anyone want to
> > take
> > > > > point for July?
> > > > >
> > > > > Link for next template is below:
> > > > >
> > > > > https://cwiki.apache.org/confluence/x/Cg31D
> > > > >
> > > >
> > > --
> > > 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: Monthly Member's Moment - July 2022
Posted by Jarek Potiuk <ja...@potiuk.com>.
If we are speaking of the future/experimenting - I think Members Moments
should be much more personal and something that creates a sense of
participation in something extraordinary - so I would not compare this to
"board reports". If we can make something that will interest people and
grab their attention and "sense of belonging" - that would be the best
format I think.
I personally always kind of frown upon "repeated" regular reports - always
showing the same points and in the same "form". They are needed of course,
but maybe "members moment" should be less informative and more "bringing
people together" (at least that's how I think about it).
I'd even say as much as this - it would be great if every next "chief
editor" will add some personal touch to it in the way that the editor feels
like :). Some "general" content should be similar - but I am thinking about
inviting someone who would like to say a sentence about what they are proud
of doing for the Foundation this month. Someone who would not normally be
too "vocal" about it. I mentioned that initially when this discussion
started. But this might be different thing from the next person next month
:),
I think that might be the most important "task" of "chief editor" - to come
up with something new and "personal touch" to it.
J.
On Wed, Jun 8, 2022 at 4:51 PM Matt Sicker <bo...@gmail.com> wrote:
> I'd imagine some sort of top-line status report could be a level of
> detail that would work? Essentially, the main part of the email would
> be a few bullet points about what's going on, and a secondary part
> could go into more details on each point or link to further details.
> I'm imagining the type of report that leadership typically reads in
> other corporations. Not at the level of detail of board minutes of
> course.
>
> On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <jo...@joshfischer.io> wrote:
> >
> > For sure. Make it the way you think it will be best for readers.
> >
> > On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > I am happy to, but I am afraid as chief-editor I will opt for a bit
> longer
> > > digest.
> > >
> > > BTW. I am thinking on how to experiment and see the actual usefulness
> of it
> > > rather than "anecdotal feedback". The fact that few people complained
> about
> > > messages being too long, does not mean that the others would not like
> it a
> > > bit longer and more useful. I don't know how but will think about it -
> I
> > > would love to see some objective, measurable data on it to be able to
> make
> > > decisions.
> > >
> > > J.
> > >
> > >
> > > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <jo...@joshfischer.io>
> wrote:
> > >
> > > > The June newsletter was recently sent to members-announce@a.o.
> > > >
> > > > Let's target to release the next on July 5, 2022. Anyone want to
> take
> > > > point for July?
> > > >
> > > > Link for next template is below:
> > > >
> > > > https://cwiki.apache.org/confluence/x/Cg31D
> > > >
> > >
> > --
> > 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: Monthly Member's Moment - July 2022
Posted by Matt Sicker <bo...@gmail.com>.
I'd imagine some sort of top-line status report could be a level of
detail that would work? Essentially, the main part of the email would
be a few bullet points about what's going on, and a secondary part
could go into more details on each point or link to further details.
I'm imagining the type of report that leadership typically reads in
other corporations. Not at the level of detail of board minutes of
course.
On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <jo...@joshfischer.io> wrote:
>
> For sure. Make it the way you think it will be best for readers.
>
> On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > I am happy to, but I am afraid as chief-editor I will opt for a bit longer
> > digest.
> >
> > BTW. I am thinking on how to experiment and see the actual usefulness of it
> > rather than "anecdotal feedback". The fact that few people complained about
> > messages being too long, does not mean that the others would not like it a
> > bit longer and more useful. I don't know how but will think about it - I
> > would love to see some objective, measurable data on it to be able to make
> > decisions.
> >
> > J.
> >
> >
> > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <jo...@joshfischer.io> wrote:
> >
> > > The June newsletter was recently sent to members-announce@a.o.
> > >
> > > Let's target to release the next on July 5, 2022. Anyone want to take
> > > point for July?
> > >
> > > Link for next template is below:
> > >
> > > https://cwiki.apache.org/confluence/x/Cg31D
> > >
> >
> --
> 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: Monthly Member's Moment - July 2022
Posted by Josh Fischer <jo...@joshfischer.io>.
For sure. Make it the way you think it will be best for readers.
On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> I am happy to, but I am afraid as chief-editor I will opt for a bit longer
> digest.
>
> BTW. I am thinking on how to experiment and see the actual usefulness of it
> rather than "anecdotal feedback". The fact that few people complained about
> messages being too long, does not mean that the others would not like it a
> bit longer and more useful. I don't know how but will think about it - I
> would love to see some objective, measurable data on it to be able to make
> decisions.
>
> J.
>
>
> On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <jo...@joshfischer.io> wrote:
>
> > The June newsletter was recently sent to members-announce@a.o.
> >
> > Let's target to release the next on July 5, 2022. Anyone want to take
> > point for July?
> >
> > Link for next template is below:
> >
> > https://cwiki.apache.org/confluence/x/Cg31D
> >
>
--
Sent from A Mobile Device
Re: Monthly Member's Moment - July 2022
Posted by Jarek Potiuk <ja...@potiuk.com>.
I am happy to, but I am afraid as chief-editor I will opt for a bit longer
digest.
BTW. I am thinking on how to experiment and see the actual usefulness of it
rather than "anecdotal feedback". The fact that few people complained about
messages being too long, does not mean that the others would not like it a
bit longer and more useful. I don't know how but will think about it - I
would love to see some objective, measurable data on it to be able to make
decisions.
J.
On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <jo...@joshfischer.io> wrote:
> The June newsletter was recently sent to members-announce@a.o.
>
> Let's target to release the next on July 5, 2022. Anyone want to take
> point for July?
>
> Link for next template is below:
>
> https://cwiki.apache.org/confluence/x/Cg31D
>