[Infrastructure] Member management database structure

[Wayne Thayer]

Martijn,

The schema looks quite comprehensive! Here are a few additional ideas to
consider:
- Interested Parties can be individuals. How will that be handled? (e.g.
create a dummy org for each individual?)
- If we're going to eventually use this system to drive mailing list
subscriptions, then we need to be able to define subcommittees. We may be
able to just use the existing group structure, but there are some
differences (e.g. subcommittees don't vote, and you need to be a member of
the WG to join a SC).
- I'm assuming that there won't be a "Forum" group since the bylaws dictate
that Forum membership is a function of WG membership. We'll just need to be
able to aggregate WG membership to create attendance lists for Forum
meetings.
- It'd be nice to add a column to member orgs to track IPR agreements. This
could be a URL to the signed agreement. Individual Interested Parties also
sign these agreements

Thanks,

Wayne


On Wed, Mar 9, 2022 at 9:47 AM Martijn Katerbarg via Infrastructure <
infrastructure at cabforum.org> wrote:

> Hi all,
>
>
>
> As just discussed on the call, attached is a diagram of the current
> database setup for the new member management system.
>
>
>
> As Wayne pointed out, there have been requests to have specific members
> (type people)  that should have voting rights in 1 WG, but not in another.
> This part has not been included in this version, but I’ll get working on
> that.
>
>
>
> Regards,
>
> Martijn
> _______________________________________________
> Infrastructure mailing list
> Infrastructure at cabforum.org
> https://lists.cabforum.org/mailman/listinfo/infrastructure
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/infrastructure/attachments/20220311/a3c54224/attachment.html>