You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Misty Stanley-Jones <ms...@cloudera.com> on 2016/06/22 16:25:21 UTC

Company affiliations in the team list

All,

I noticed on http://hbase.apache.org/team-list.html that several of the
company affiliations are stale. I only keep track of the Cloudera ones, but
I'm sure several of the other ones are also no longer accurate.

At the very least, can everyone have a look over the list and update your
info if it is out of date? If you don't remember how to update it, it is in
the top-level pom.xml. Also, since it is part of the Maven project
configuration, it lives in each branch.

As a matter of policy, is it worth discussing the policy of listing
individual company affiliations in this context, since they often go out of
date? I think I understand (politically) why we list them, but it does seem
like a weak point from a maintenance and accuracy point of view.

Thanks,
Misty

Re: Company affiliations in the team list

Posted by Misty Stanley-Jones <ms...@cloudera.com>.
Filed https://issues.apache.org/jira/browse/HBASE-16426 to take care of
this. Thanks, all.

On Wed, Jun 22, 2016 at 10:47 AM, Andrew Purtell <an...@gmail.com>
wrote:

> I don't see the committer affiliation information as useful to the project
> except perhaps as indirect Powered-by marketing. That's actually had if
> comically out of date. It's certainly not useful or operative for project
> governance.
>
> > On Jun 22, 2016, at 10:42 AM, Enis Söztutar <en...@apache.org> wrote:
> >
> > It is on each individual committer to keep that up to date. But as people
> > move on, and stop being active more, it is easily forgotten. I am fine
> with
> > removing the affiliates since the usability is questionable.
> >
> > Enis
> >
> >> On Wed, Jun 22, 2016 at 9:35 AM, Sean Busbey <bu...@apache.org> wrote:
> >>
> >> On Wed, Jun 22, 2016 at 11:25 AM, Misty Stanley-Jones
> >> <ms...@cloudera.com> wrote:
> >>>
> >>> As a matter of policy, is it worth discussing the policy of listing
> >>> individual company affiliations in this context, since they often go
> out
> >> of
> >>> date? I think I understand (politically) why we list them, but it does
> >> seem
> >>> like a weak point from a maintenance and accuracy point of view.
> >>
> >> The impression I get from the current ASF Board is that they'd love it
> >> if we didn't list them at all. I don't have a strong personal
> >> attachment to publicly declaring the sponsor of my non-ASF-hat; I'm
> >> sure folks can find me on LinkedIn.
> >>
>

Re: Company affiliations in the team list

Posted by Andrew Purtell <an...@gmail.com>.
I don't see the committer affiliation information as useful to the project except perhaps as indirect Powered-by marketing. That's actually had if comically out of date. It's certainly not useful or operative for project governance. 

> On Jun 22, 2016, at 10:42 AM, Enis Söztutar <en...@apache.org> wrote:
> 
> It is on each individual committer to keep that up to date. But as people
> move on, and stop being active more, it is easily forgotten. I am fine with
> removing the affiliates since the usability is questionable.
> 
> Enis
> 
>> On Wed, Jun 22, 2016 at 9:35 AM, Sean Busbey <bu...@apache.org> wrote:
>> 
>> On Wed, Jun 22, 2016 at 11:25 AM, Misty Stanley-Jones
>> <ms...@cloudera.com> wrote:
>>> 
>>> As a matter of policy, is it worth discussing the policy of listing
>>> individual company affiliations in this context, since they often go out
>> of
>>> date? I think I understand (politically) why we list them, but it does
>> seem
>>> like a weak point from a maintenance and accuracy point of view.
>> 
>> The impression I get from the current ASF Board is that they'd love it
>> if we didn't list them at all. I don't have a strong personal
>> attachment to publicly declaring the sponsor of my non-ASF-hat; I'm
>> sure folks can find me on LinkedIn.
>> 

Re: Company affiliations in the team list

Posted by Enis Söztutar <en...@apache.org>.
It is on each individual committer to keep that up to date. But as people
move on, and stop being active more, it is easily forgotten. I am fine with
removing the affiliates since the usability is questionable.

Enis

On Wed, Jun 22, 2016 at 9:35 AM, Sean Busbey <bu...@apache.org> wrote:

> On Wed, Jun 22, 2016 at 11:25 AM, Misty Stanley-Jones
> <ms...@cloudera.com> wrote:
> >
> > As a matter of policy, is it worth discussing the policy of listing
> > individual company affiliations in this context, since they often go out
> of
> > date? I think I understand (politically) why we list them, but it does
> seem
> > like a weak point from a maintenance and accuracy point of view.
> >
>
> The impression I get from the current ASF Board is that they'd love it
> if we didn't list them at all. I don't have a strong personal
> attachment to publicly declaring the sponsor of my non-ASF-hat; I'm
> sure folks can find me on LinkedIn.
>

Re: Company affiliations in the team list

Posted by Sean Busbey <bu...@apache.org>.
On Wed, Jun 22, 2016 at 11:25 AM, Misty Stanley-Jones
<ms...@cloudera.com> wrote:
>
> As a matter of policy, is it worth discussing the policy of listing
> individual company affiliations in this context, since they often go out of
> date? I think I understand (politically) why we list them, but it does seem
> like a weak point from a maintenance and accuracy point of view.
>

The impression I get from the current ASF Board is that they'd love it
if we didn't list them at all. I don't have a strong personal
attachment to publicly declaring the sponsor of my non-ASF-hat; I'm
sure folks can find me on LinkedIn.