I think that would be splendid, Don. :) I'd be happy to help out with getting this set up. I'm in favor of using Apache's blog infrastructure, at least at first, since it's ready to go and explicitly for this purpose. I like the sense of place it provides, vs. a loose topic on G+ / elsewhere.
- I'm not a fan of just posting links to articles elsewhere. There should be at least a short, complete passage for each post with a link to the full thing, if not a full repost. - Lazy approval sounds fine to me, since a PMC member has to post the content anyway. On Thu, Apr 10, 2014 at 3:23 PM, Donald Miner <dmi...@clearedgeit.com>wrote: > Is this something i can volunteer to help manage if nobody else wants to? > Do things like set it up, collect blog posts from authors, edit them, post > them, manage the draft and vote process, etc. > > Just putting that out there as i see it as a way i can contribute to the > community and i also personally think it is a good idea. > > -d > > > On Apr 10, 2014, at 1:59 PM, Mike Drob <mad...@cloudera.com> wrote: > > > > Not sure how I feel about the Google+ community. As the PMC, aren't we > > responsible for brand management? > > > > > >> On Thu, Apr 10, 2014 at 1:43 PM, Christopher <ctubb...@apache.org> > wrote: > >> > >> Personally, I'd find it easier to simply suggest people post to a > >> common Google+ topic/community, when there's something of community > >> interest to blog about, rather than maintain a monolithic blog. > >> > >> There may be others with the same topic/name, but this one is the one > >> I saw first: > >> https://plus.google.com/communities/117836301734017142321 > >> > >> -- > >> Christopher L Tubbs II > >> http://gravatar.com/ctubbsii > >> > >> > >>> On Thu, Apr 10, 2014 at 12:12 PM, <dlmar...@comcast.net> wrote: > >>> I am proposing a blog for the project to be hosted on the > >> blogs.apache.org site. There was a similar proposal last year on the > dev > >> list [1], but no vote or decision. Apache has a web page with setup > >> instructions [2], which also states that the PMC is responsible for the > >> blog content and for granting write access to the blog. The process for > >> setting up a blog is easy and defined in [2]. > >>> > >>> > >>> To move forward I think we need to resolve some items: > >>> > >>> 1. The bylaws don't define how to vote on blog content, but the default > >> vote is in a Lazy Approval fashion, with no defined timeframe. I'm > thinking > >> 3 days. Since the PMC is responsible for the content, should we enforce > >> something different, say, consensus or majority approval from active PMC > >> members over 3 days? > >>> > >>> 2. Guidelines for content. If we accept cross-posts from other sites or > >> blog posts from guest writers (non-contributors, non-committers), what > >> rules should be enforced (PMC is responsible for content)? For any > author, > >> can their employer or employer's products be mentioned? > >>> > >>> 3. Do the articles need to be Apache licensed? > >>> > >>> [1] > >> > http://mail-archives.apache.org/mod_mbox/accumulo-dev/201311.mbox/%3CCAD-fFU%2B7ZqoVGYMzN%3D09dv9fMSv%2BF32XbsMubsw9HTZ6n155rg%40mail.gmail.com%3E > >>> [2] http://www.apache.org/dev/project-blogs > >> > -- // Bill Havanki // Solutions Architect, Cloudera Govt Solutions // 443.686.9283
