Open Stack

On 2015-03-16 20:47:22 -0700 (-0700), Stefano Maffulli wrote:
[...]
> I think this is a different bug, one referring to the limitation
> of our current systems to identify voters (ergo requiring
> Individual membership for any contributor, including to docs).
[...]

Yes, just to summarize the current challenge there: our technical
elections require that the electorate both be code contributors (or
designated "extra ATCs") and be individual members of the
foundation. The problem there is that the foundation member database
is a separate system and maintained by an entirely separate group of
people from the code review system. With no distinct/unique index
keys in common, having a single place to query so we can build an
electorate list necessitated that one enforced subset inclusion in
the other. This is currently done by having the ICLA signing process
in the code review system check whether the user has a matching
foundation individual member account via an API call to the
foundation member database system.

Solutions under discussion mostly require a more robust API for the
foundation member database along with much more complex electorate
roll generation tooling to query and correlate both systems, noting
that there's nothing really linking those two systems and ensuring
consistency once we stop enforcing the current procedural
connection. Once we can safely migrate review.openstack.org to
authenticate against the same openstackid.org identity provider as
www.openstack.org uses, this should become much simpler again since
we'll have a way to force contributors to sign up for a foundation
account (though they'll no longer need to fill out the foundation
membership form when doing so).
-- 
Jeremy Stanley