Not sure how important it is to list committers on the Geode website. I
suppose it helps create and sustain the concept of community. The lead-in
to the list suggests that the reader may want to join the community, and
will be rewarded by seeing their name on the list.
I checked out a few other Apache big data project websites (Ambari, Helix
and Phoenix). Each has a "Team" link with a list of committers and PMC
members.


On Wed, Dec 7, 2016 at 12:05 PM, Mark Bretl <mbr...@apache.org> wrote:

> I have added the rest of the committers from the original list which I
> could, it shows up correctly in Whimsy but not in the Phonebook yet. There
> are people on the website list which do not have Apache IDs, so there is
> still some difference between the two lists.
>
> If we don't want to manage two lists, I would suggest since the Apache list
> is the official list anyone who wants to be listed as a member of the Geode
> community, have an Apache ID and be added to the Committers list, even if
> they do not commit 'code'.
>
> Thoughts?
>
> --Mark
>
>
>
> On Tue, Dec 6, 2016 at 1:53 PM, Mark Bretl <mbr...@apache.org> wrote:
>
> > Note: Moved to Dev list...
> >
> > Hey Dave,
> >
> > I am working on adding committers back to the official unix group, which
> > Whimsy is using. The website will always be a secondary source, however,
> we
> > could link to the phonebook instead of listing directly on the website.
> > Since Whimsy requires credentials, I don't think that would be good
> choice
> >
> > I am working on re-adding committers which are missing from the TLP
> > transition.
> >
> > --Mark
> >
> > [1] http://people.apache.org/phonebook.html?unix=geode
> >
> > On Tue, Dec 6, 2016 at 1:33 PM, Dave Barnes <dbar...@pivotal.io> wrote:
> >
> >> The whimsy committers roster differs from the Geode website's Community
> >> list of committers. Is the website list obsolete, or would there be
> value
> >> in updating it to match the whimsy list? (Adopting a 2-list policy
> incurs
> >> some overhead going forward..)
> >>
> >
> >
>

Reply via email to