First, has the question of "why" been answered for the mission statement?; the purpose.
On Wed, Nov 23, 2016 at 4:16 AM, Alexander Bezzubov <b...@apache.org> wrote: > Idea for such resource sounds great, and it could be a good place to post > the followup of recent GSoC Mentors Summit, that I'm working on right now. > > Enthusiastic +1. If you think that would be appropriate - I would be happy > to post it there, if somebody could grant the rights. > > -- > Alex > > On Wed, Nov 23, 2016 at 1:41 AM, Sharan Foga <sha...@apache.org> wrote: > > > Hi Rich > > > > Thanks for the response and offer of help. > > > > Initially I was thinking about including general updates about community > > development activities not captured elsewhere. For example I have been > > posting some Diversity Updates to this list so perhaps they would be > better > > incorporated and also reach a wider audience as part a blog post. > > > > Another aspect I've been thinking about (and this may have been discussed > > previously) is to have a strategy for what we want to community > development > > to achieve. I took another look at the diversity strategy ideas that I > put > > together on the wiki and think that there is a lot in common with what > the > > goal of community development is or could be. > > > > https://cwiki.apache.org/confluence/display/COMDEV/ > > Diversity+Strategy+Ideas > > > > I'm not sure if there is already have a mission statement or goal for > > community development and if not, then I think that the current diversity > > strategy ideas / outcomes could be tailored to become more generic to > > community development because the 3 ways mentioned of achieving the > > outcomes are very relevant to everything we would like community > > development to do. (and diversity is incorporated into it as part of the > > overall strategy) > > > > - Reach out and attract new contributors > > - Ensure that people that join Apache communities enjoy what they do and > > feel safe and appreciated > > - Maintain a positive culture of inclusiveness and openness > > > > For example a recent thread about GSOC could fit in the reach out and > > attract new contributors part, and the internal newsletter / > communications > > could fit under the maintaining a positive culture part, so could any > > potential metrics. > > > > I agree with you that we don't want to duplicate any effort, but we could > > cross link the content a bit more. We may also need to sit down and > define > > / write some goals we would like to achieve within a specific timeframe. > > For example with Apachecon NA announced – this is a good timeframe and > > milestone to set some goals around (and it sounds like sounds like you > > already have some in mind) > > > > So some potential topics for the blog could directly related to the > > Community Development strategy and the points that are being done in the > > various areas. > > - Outreach > > - Events > > - Communications > > - Metrics > > > > We could also include some informational areas based on stuff from the > > website > > - Answer an FAQ (could start with ones from the website) > > - Have some optional content such as Mentor Interview (or link to one), > > Speakers and How to Get one, Getting Started – Cross link to Wiki, > > Consensus, Lazy Consensus, The Apache Way lite, etc > > > > Anyway - these are my thoughts for now. Other ideas, feedback and > comments > > welcome. > > > > Thanks > > Sharan > > > > > > On 2016-11-22 14:51 (+0100), Rich Bowen <rbo...@rcbowen.com> wrote: > > > Yes, I'm interested in helping here. What kinds of things to you > imagine > > > we would have in such a posting? That is, do you have in idea of an > > outline? > > > > > > I've been batting about the idea of an *internal* newsletter, making > our > > > own community aware of the larger world of the ASF, which, to me, is a > > > critical aspect of Community Development. I have an outline/draft here: > > > https://docs.google.com/document/d/1JZJJbpsr4Oc8xHU61Glw2NpaJz- > > ePLIiXLhfCxRpznI/edit > > > - which might give some idea of what I have in mind. This seems like > > > perhaps a complementary thing to the blog post? > > > > > > I don't want to duplicate a lot of the effort that Sally makes for her > > > excellent weekly summary - > > > https://blogs.apache.org/foundation/entry/the_apache_news_round_up112 > - > > > but we can certainly reuse some of that content too. > > > > > > This is, of course, in line with our conversations last week about > > > addressing the proliferation of "Satellite" ASF projects, with no real > > > connection to the larger community. > > > > > > --Rich > > > > > > > > > On 11/21/2016 01:46 PM, Sharan Foga wrote: > > > > Hi All > > > > > > > > While drafting a blog communication regarding the Committer Survey > and > > I noticed that ComDev has a blog that we are not currently making use of. > > > > > > > > https://blogs.apache.org/comdev/ > > > > > > > > I think it would be good idea to setup a regular monthly update for > > the community. Generally I help prepare the monthly blog update for OFBiz > > (see link below for an example) > > > > > > > > https://blogs.apache.org/ofbiz/ > > > > > > > > and would be happy to set one up for ComDev too. The news would just > > be a summary of what has happened during the month. > > > > > > > > For OFBiz we have a small team of 3 that drafts and reviews the blog > > update before publishing so we could try something similar to see if it > > works. So if anyone is interested in helping prepare the monthly ComDev > > blog post then please let me know. > > > > > > > > Thanks > > > > Sharan > > > > > > > > ------------------------------------------------------------ > --------- > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > -- > > > Rich Bowen - rbo...@rcbowen.com - @rbowen > > > http://apachecon.com/ - @apachecon > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > >