You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flume.apache.org by Eric Sammer <es...@cloudera.com> on 2012/05/24 19:29:55 UTC
[DISCUSS] Expanding contributors to Flume
Flume'ers:
Flume has been progressing wonderfully as an ASF Incubator project lately
in terms of community activity, code, releases, and even docs (gasp!). One
of the requirements for graduation (to a top level project, or TLP) is
committer diversity. In other words, committers should come from a variety
of backgrounds and, specifically, not from a single employer. We happen to
have a large number of Cloudera employees, mostly because that's where
Flume came from, historically. The discussion I wanted to start with
everyone was, what, if anything, can we do to help folks dive into Flume
and begin contributing[1]?
Thanks!
[1] Remember that contributions come in forms other than code (docs, site
maintenance / design / logos, testing) although code is fantastic!
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: [DISCUSS] Expanding contributors to Flume
Posted by Juhani Connolly <ju...@cyberagent.co.jp>.
Hey, sorry I'm late in responding to this. Getting back to Japan,
catching up and jetlag...
I think the state of documentation now is definitely a lot better.
Right now there are a couple of difficult issues:
- There is still the ghost of OG hanging around... Nobody really
supports it much(a lot of the committers now, including me, haven't
actually used it or lookd at the code much).
- The majority of current committers are from cloudera(nothing wrong
with it, just historical). Outsiders can feel there may be pressure to
align with them, even though there really isn't some kind of groupthink
as one might be concerned from a single organisation.
- There's a catch22 with usage and visibility. A lot of more visible
organisations don't want to use something still in the incubator, so
there is less visibility, attracting fewer people.
- I actually think most of the more pressing issues with flume are more
or less sorted now. When I started contributing, there was some big
holes I was worried about and wanted to help fix. Now most of the work
to be done is less "interesting" and generally adding polish.
I'm not entirely sure about solutions to a lot of these problems.
One thing that could be good is having more documentation on developing
plugins, as well as encouraging contribution of such plugins to get
people involved?
On 05/25/2012 02:29 AM, Eric Sammer wrote:
> Flume'ers:
>
> Flume has been progressing wonderfully as an ASF Incubator project lately
> in terms of community activity, code, releases, and even docs (gasp!). One
> of the requirements for graduation (to a top level project, or TLP) is
> committer diversity. In other words, committers should come from a variety
> of backgrounds and, specifically, not from a single employer. We happen to
> have a large number of Cloudera employees, mostly because that's where
> Flume came from, historically. The discussion I wanted to start with
> everyone was, what, if anything, can we do to help folks dive into Flume
> and begin contributing[1]?
>
> Thanks!
>
> [1] Remember that contributions come in forms other than code (docs, site
> maintenance / design / logos, testing) although code is fantastic!
Re: [DISCUSS] Expanding contributors to Flume
Posted by Eric Sammer <es...@cloudera.com>.
Arun:
On Thu, May 24, 2012 at 10:53 AM, Arun C Murthy <ac...@hortonworks.com> wrote:
> Having seen how Apache Hadoop has progressed, I'd say things like docs,
> site-maintenence etc. are critical (though, I'd be the last to claim Hadoop
> is a shining example).
>
Totally agree.
> If I land up at https://cwiki.apache.org/FLUME/ lots of links (including
> Dev guides, arch docs etc.) lead straight to cloudera.com/org links which
> doesn't help. It also leads to _perception_ (whether it's deserved or not)
> that this is oriented towards one employer and user questions like
> http://s.apache.org/33t.
>
Absolutely fair points. Any links on the ASF wiki that link to Cloudera for
canonical reference docs are bugs left over from incomplete migration of
Flume from being a Cloudera project to an ASF project. I thought we got all
of those. I guess publishing the docs that are part of the build to the
website require project karma, but the wiki stuff should be easy for
someone to help with (wink, wink, nudge, nudge everyone :)), but we should
prioritize this.
I would love to convince someone to help with wiki pruning / maintenance.
I'll file bugs for publishing the non-wiki docs to the site if they don't
already exist.
> #my2c
>
> Arun
>
>
> On May 24, 2012, at 10:29 AM, Eric Sammer wrote:
>
> Flume'ers:
>
> Flume has been progressing wonderfully as an ASF Incubator project lately
> in terms of community activity, code, releases, and even docs (gasp!). One
> of the requirements for graduation (to a top level project, or TLP) is
> committer diversity. In other words, committers should come from a variety
> of backgrounds and, specifically, not from a single employer. We happen to
> have a large number of Cloudera employees, mostly because that's where
> Flume came from, historically. The discussion I wanted to start with
> everyone was, what, if anything, can we do to help folks dive into Flume
> and begin contributing[1]?
>
> Thanks!
>
> [1] Remember that contributions come in forms other than code (docs, site
> maintenance / design / logos, testing) although code is fantastic!
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
>
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: [DISCUSS] Expanding contributors to Flume
Posted by Eric Sammer <es...@cloudera.com>.
Arun:
On Thu, May 24, 2012 at 10:53 AM, Arun C Murthy <ac...@hortonworks.com> wrote:
> Having seen how Apache Hadoop has progressed, I'd say things like docs,
> site-maintenence etc. are critical (though, I'd be the last to claim Hadoop
> is a shining example).
>
Totally agree.
> If I land up at https://cwiki.apache.org/FLUME/ lots of links (including
> Dev guides, arch docs etc.) lead straight to cloudera.com/org links which
> doesn't help. It also leads to _perception_ (whether it's deserved or not)
> that this is oriented towards one employer and user questions like
> http://s.apache.org/33t.
>
Absolutely fair points. Any links on the ASF wiki that link to Cloudera for
canonical reference docs are bugs left over from incomplete migration of
Flume from being a Cloudera project to an ASF project. I thought we got all
of those. I guess publishing the docs that are part of the build to the
website require project karma, but the wiki stuff should be easy for
someone to help with (wink, wink, nudge, nudge everyone :)), but we should
prioritize this.
I would love to convince someone to help with wiki pruning / maintenance.
I'll file bugs for publishing the non-wiki docs to the site if they don't
already exist.
> #my2c
>
> Arun
>
>
> On May 24, 2012, at 10:29 AM, Eric Sammer wrote:
>
> Flume'ers:
>
> Flume has been progressing wonderfully as an ASF Incubator project lately
> in terms of community activity, code, releases, and even docs (gasp!). One
> of the requirements for graduation (to a top level project, or TLP) is
> committer diversity. In other words, committers should come from a variety
> of backgrounds and, specifically, not from a single employer. We happen to
> have a large number of Cloudera employees, mostly because that's where
> Flume came from, historically. The discussion I wanted to start with
> everyone was, what, if anything, can we do to help folks dive into Flume
> and begin contributing[1]?
>
> Thanks!
>
> [1] Remember that contributions come in forms other than code (docs, site
> maintenance / design / logos, testing) although code is fantastic!
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
>
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: [DISCUSS] Expanding contributors to Flume
Posted by Ralph Goers <ra...@dslextreme.com>.
Thanks for that feedback. That is very useful.
Let me ask the question in the opposite fashion - what is the major roadblock that is keeping you from participating more? If it is still the docs and links that is OK, but if those were fixed would you then be able to contribute?
Ralph
On May 24, 2012, at 10:53 AM, Arun C Murthy wrote:
> Having seen how Apache Hadoop has progressed, I'd say things like docs, site-maintenence etc. are critical (though, I'd be the last to claim Hadoop is a shining example).
>
> If I land up at https://cwiki.apache.org/FLUME/ lots of links (including Dev guides, arch docs etc.) lead straight to cloudera.com/org links which doesn't help. It also leads to _perception_ (whether it's deserved or not) that this is oriented towards one employer and user questions like http://s.apache.org/33t.
>
> #my2c
>
> Arun
>
> On May 24, 2012, at 10:29 AM, Eric Sammer wrote:
>
>> Flume'ers:
>>
>> Flume has been progressing wonderfully as an ASF Incubator project lately
>> in terms of community activity, code, releases, and even docs (gasp!). One
>> of the requirements for graduation (to a top level project, or TLP) is
>> committer diversity. In other words, committers should come from a variety
>> of backgrounds and, specifically, not from a single employer. We happen to
>> have a large number of Cloudera employees, mostly because that's where
>> Flume came from, historically. The discussion I wanted to start with
>> everyone was, what, if anything, can we do to help folks dive into Flume
>> and begin contributing[1]?
>>
>> Thanks!
>>
>> [1] Remember that contributions come in forms other than code (docs, site
>> maintenance / design / logos, testing) although code is fantastic!
>> --
>> Eric Sammer
>> twitter: esammer
>> data: www.cloudera.com
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
Re: [DISCUSS] Expanding contributors to Flume
Posted by Arun C Murthy <ac...@hortonworks.com>.
Having seen how Apache Hadoop has progressed, I'd say things like docs, site-maintenence etc. are critical (though, I'd be the last to claim Hadoop is a shining example).
If I land up at https://cwiki.apache.org/FLUME/ lots of links (including Dev guides, arch docs etc.) lead straight to cloudera.com/org links which doesn't help. It also leads to _perception_ (whether it's deserved or not) that this is oriented towards one employer and user questions like http://s.apache.org/33t.
#my2c
Arun
On May 24, 2012, at 10:29 AM, Eric Sammer wrote:
> Flume'ers:
>
> Flume has been progressing wonderfully as an ASF Incubator project lately
> in terms of community activity, code, releases, and even docs (gasp!). One
> of the requirements for graduation (to a top level project, or TLP) is
> committer diversity. In other words, committers should come from a variety
> of backgrounds and, specifically, not from a single employer. We happen to
> have a large number of Cloudera employees, mostly because that's where
> Flume came from, historically. The discussion I wanted to start with
> everyone was, what, if anything, can we do to help folks dive into Flume
> and begin contributing[1]?
>
> Thanks!
>
> [1] Remember that contributions come in forms other than code (docs, site
> maintenance / design / logos, testing) although code is fantastic!
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
Re: [DISCUSS] Expanding contributors to Flume
Posted by Arun C Murthy <ac...@hortonworks.com>.
Having seen how Apache Hadoop has progressed, I'd say things like docs, site-maintenence etc. are critical (though, I'd be the last to claim Hadoop is a shining example).
If I land up at https://cwiki.apache.org/FLUME/ lots of links (including Dev guides, arch docs etc.) lead straight to cloudera.com/org links which doesn't help. It also leads to _perception_ (whether it's deserved or not) that this is oriented towards one employer and user questions like http://s.apache.org/33t.
#my2c
Arun
On May 24, 2012, at 10:29 AM, Eric Sammer wrote:
> Flume'ers:
>
> Flume has been progressing wonderfully as an ASF Incubator project lately
> in terms of community activity, code, releases, and even docs (gasp!). One
> of the requirements for graduation (to a top level project, or TLP) is
> committer diversity. In other words, committers should come from a variety
> of backgrounds and, specifically, not from a single employer. We happen to
> have a large number of Cloudera employees, mostly because that's where
> Flume came from, historically. The discussion I wanted to start with
> everyone was, what, if anything, can we do to help folks dive into Flume
> and begin contributing[1]?
>
> Thanks!
>
> [1] Remember that contributions come in forms other than code (docs, site
> maintenance / design / logos, testing) although code is fantastic!
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/