You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by dl...@comcast.net on 2014/04/10 18:12:51 UTC
[PROPOSAL] Accumulo Blog
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
Re: [PROPOSAL] Accumulo Blog
Posted by David Medinets <da...@gmail.com>.
Cell-Level Security wasn't patented?
On Thu, Apr 10, 2014 at 12:43 PM, Sean Busbey <bu...@cloudera.com> wrote:
> On Thu, Apr 10, 2014 at 9:33 AM, <dl...@comcast.net> wrote:
>
> >
> >
> > From: "David Medinets" <da...@gmail.com>
> >
> > Can links to articles be posted or should the whole article be included
> in
> > the post?
> >
> > Not sure, might be up to us.
> >
> >
> I'd much rather we not do links only. If I'm coming to our blog as a
> centralized point, I don't want to have to go somewhere else to actually
> get content.
>
> For example, here's a reposting the HBase folks did on cell level security
> in 0.98 from the Intel blogs:
>
> https://blogs.apache.org/hbase/entry/hbase_cell_security
>
>
>
> > Are the posts branded as Accumulo or the individual contributor?
> >
> > From what I can see on the site, the author is listed.
> >
> >
> >
>
> Posts are branded as both the project and the individual. The HBase example
> above also does a good job of showing this.
>
>
> --
> Sean
>
Re: [PROPOSAL] Accumulo Blog
Posted by Sean Busbey <bu...@cloudera.com>.
On Thu, Apr 10, 2014 at 9:33 AM, <dl...@comcast.net> wrote:
>
>
> From: "David Medinets" <da...@gmail.com>
>
> Can links to articles be posted or should the whole article be included in
> the post?
>
> Not sure, might be up to us.
>
>
I'd much rather we not do links only. If I'm coming to our blog as a
centralized point, I don't want to have to go somewhere else to actually
get content.
For example, here's a reposting the HBase folks did on cell level security
in 0.98 from the Intel blogs:
https://blogs.apache.org/hbase/entry/hbase_cell_security
> Are the posts branded as Accumulo or the individual contributor?
>
> From what I can see on the site, the author is listed.
>
>
>
Posts are branded as both the project and the individual. The HBase example
above also does a good job of showing this.
--
Sean
Re: [PROPOSAL] Accumulo Blog
Posted by dl...@comcast.net.
----- Original Message -----
From: "David Medinets" <da...@gmail.com>
To: "accumulo-dev" <de...@accumulo.apache.org>
Sent: Thursday, April 10, 2014 12:27:37 PM
Subject: Re: [PROPOSAL] Accumulo Blog
Can links to articles be posted or should the whole article be included in
the post?
Not sure, might be up to us.
Are the posts branded as Accumulo or the individual contributor?
>From what I can see on the site, the author is listed.
On Thu, Apr 10, 2014 at 12:12 PM, <dl...@comcast.net> wrote:
> I am proposing a blog for the project to be hosted on the blogs.apache.orgsite. 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
>
>
Re: [PROPOSAL] Accumulo Blog
Posted by David Medinets <da...@gmail.com>.
Can links to articles be posted or should the whole article be included in
the post?
Are the posts branded as Accumulo or the individual contributor?
On Thu, Apr 10, 2014 at 12:12 PM, <dl...@comcast.net> wrote:
> I am proposing a blog for the project to be hosted on the blogs.apache.orgsite. 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
>
>
Re: [PROPOSAL] Accumulo Blog
Posted by dl...@comcast.net.
----- Original Message -----
From: "Sean Busbey" <bu...@cloudera.com>
To: "dev@accumulo apache. org" <de...@accumulo.apache.org>
Sent: Thursday, April 10, 2014 12:24:21 PM
Subject: Re: [PROPOSAL] Accumulo Blog
On Thu, Apr 10, 2014 at 9:12 AM, <dl...@comcast.net> wrote:
> I am proposing a blog for the project to be hosted on the blogs.apache.orgsite. 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].
>
>
yay!
>
> 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?
>
>
Personally, I think Lazy Approval and 3 days is fine. Can PMC members see
posts that are in draft status? If so, I think a note that a given draft is
going to be published in {X | X > 3} days should be sufficient.
Yes - the setup page shows how to do this.
> 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?
>
I think so long as a PMC member is willing to act as reviewer (and it
follows the above lazy approval process), it should be fine.
Personally, I don't think something related to Accumulo being commercial
should preclude it from what we bring to the community's attention.
>
> 3. Do the articles need to be Apache licensed?
>
>
Related: what license do we want applied to the blog posts we author?
I don't see any obvious licensing info on the Apache hosted blog posts.
--
Sean
Re: [PROPOSAL] Accumulo Blog
Posted by Josh Elser <jo...@gmail.com>.
On 4/10/14, 12:24 PM, Sean Busbey wrote:
>> 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?
>> >
> I think so long as a PMC member is willing to act as reviewer (and it
> follows the above lazy approval process), it should be fine.
>
> Personally, I don't think something related to Accumulo being commercial
> should preclude it from what we bring to the community's attention.
>
As long as we're not biased or preferential to one over another, I don't
see this as an issue, either.
Re: [PROPOSAL] Accumulo Blog
Posted by Sean Busbey <bu...@cloudera.com>.
On Thu, Apr 10, 2014 at 9:12 AM, <dl...@comcast.net> wrote:
> I am proposing a blog for the project to be hosted on the blogs.apache.orgsite. 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].
>
>
yay!
>
> 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?
>
>
Personally, I think Lazy Approval and 3 days is fine. Can PMC members see
posts that are in draft status? If so, I think a note that a given draft is
going to be published in {X | X > 3} days should be sufficient.
> 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?
>
I think so long as a PMC member is willing to act as reviewer (and it
follows the above lazy approval process), it should be fine.
Personally, I don't think something related to Accumulo being commercial
should preclude it from what we bring to the community's attention.
>
> 3. Do the articles need to be Apache licensed?
>
>
Related: what license do we want applied to the blog posts we author?
I don't see any obvious licensing info on the Apache hosted blog posts.
--
Sean
Re: [PROPOSAL] Accumulo Blog
Posted by Christopher <ct...@apache.org>.
Seems reasonable. I just thought the organic, informal, open,
topic-subscription model, was a good one. No formal maintenance/effort
required.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Thu, Apr 10, 2014 at 4:15 PM, Corey Nolet <cj...@gmail.com> wrote:
> Chris, would you be in favor of forwarding blog posts to G+ so that it can
> still be provided to that community?
>
>
> On Thu, Apr 10, 2014 at 4:14 PM, Corey Nolet <cj...@gmail.com> wrote:
>
>> I'm in favor of full reposts wherever possible. It may be duplication of
>> content, but it validates for many that the content has been approved by
>> the community. While the content is being republished, I'm still in favor
>> of posting a link to the original blog post (if applicable).
>>
>> I find a blog useful when it's from a reputable source, it's easy to find,
>> and what I need is right there. I, personally, wouldn't find it as useful
>> if I searched a blog and then had to go somewhere else to find the actual
>> content.
>>
>>
>> On Thu, Apr 10, 2014 at 3:54 PM, Bill Havanki <bh...@clouderagovt.com>wrote:
>>
>>> 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 <dminer@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 <ma...@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 <ct...@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, <dl...@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
>>>
>>
>>
Re: [PROPOSAL] Accumulo Blog
Posted by Corey Nolet <cj...@gmail.com>.
Chris, would you be in favor of forwarding blog posts to G+ so that it can
still be provided to that community?
On Thu, Apr 10, 2014 at 4:14 PM, Corey Nolet <cj...@gmail.com> wrote:
> I'm in favor of full reposts wherever possible. It may be duplication of
> content, but it validates for many that the content has been approved by
> the community. While the content is being republished, I'm still in favor
> of posting a link to the original blog post (if applicable).
>
> I find a blog useful when it's from a reputable source, it's easy to find,
> and what I need is right there. I, personally, wouldn't find it as useful
> if I searched a blog and then had to go somewhere else to find the actual
> content.
>
>
> On Thu, Apr 10, 2014 at 3:54 PM, Bill Havanki <bh...@clouderagovt.com>wrote:
>
>> 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 <dminer@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 <ma...@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 <ct...@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, <dl...@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
>>
>
>
Re: [PROPOSAL] Accumulo Blog
Posted by Corey Nolet <cj...@gmail.com>.
I'm in favor of full reposts wherever possible. It may be duplication of
content, but it validates for many that the content has been approved by
the community. While the content is being republished, I'm still in favor
of posting a link to the original blog post (if applicable).
I find a blog useful when it's from a reputable source, it's easy to find,
and what I need is right there. I, personally, wouldn't find it as useful
if I searched a blog and then had to go somewhere else to find the actual
content.
On Thu, Apr 10, 2014 at 3:54 PM, Bill Havanki <bh...@clouderagovt.com>wrote:
> 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 <dminer@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 <ma...@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 <ct...@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, <dl...@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
>
Re: [PROPOSAL] Accumulo Blog
Posted by Bill Havanki <bh...@clouderagovt.com>.
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 <dm...@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 <ma...@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 <ct...@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, <dl...@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
Re: [PROPOSAL] Accumulo Blog
Posted by Donald Miner <dm...@clearedgeit.com>.
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 <ma...@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 <ct...@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, <dl...@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
>>
Re: [PROPOSAL] Accumulo Blog
Posted by Mike Drob <ma...@cloudera.com>.
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 <ct...@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, <dl...@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
> >
>
Re: [PROPOSAL] Accumulo Blog
Posted by Sean Busbey <bu...@cloudera.com>.
On Thu, Apr 10, 2014 at 10:43 AM, Christopher <ct...@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.
>
>
Christopher, should we take this as a -1 or just a statement that you,
personally, don't wish to help with the maintenance of the blog?
--
Sean
Re: [PROPOSAL] Accumulo Blog
Posted by Christopher <ct...@apache.org>.
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, <dl...@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
>