a note regarding net.shibboleth:parent-v3:2

[Tom Zeller]

> So I think it's all good, we just need to move the version for
> java-support down into opensaml-parent, and the spring-extensions into the
> IdP and anything else using it.
>
> Seems pretty minimal.

So this is now https://issues.shibboleth.net/jira/browse/JPAR-35,
which is empty right now except for the title "Remove internal and
thus circular managed dependencies from parent POM".

Updated the dev call wiki page with the above issue.

As a bit of procedure, I think the PMC should have a dedicated slot or
meeting on a regular schedule, with additional time allocated as
needed, maybe quarterly. It would be good to separate "how" discussion
from "what", since how-we-make-decisions should be decided by equal
voices, but technical decisions, the what-we-do should continue to be
weighted by merit, because that provides space for two good things to
become a third.

I like the notion of [DISCUSS] then [VOTE], but have no experience. I
think the PMC should probably make a statement like : such threads are
required prior to any release and this (TODO) is how that happens.

I also think a vote should follow a propose, second, all-in-favor,
all-opposed board room syntax, but leading such would be unfamiliar to
me.

>>Someone should work through this idea, hopefully it will be trivial. I
>>will unless someone else is already there, just let me know to avoid
>>duplication of effort.
>
> Just need to verify where every version is being managed from, but it
> looks like it's mostly right already.

Great.