On 15/01/2020 00:42, Joel Sherrill wrote:
> This will create a lot of paperwork which puts GNU project maintainers in a
> very bad position. In practice, ....
this is the sad reality of an organization where volunteers have not
been registered as equal members with equal votes in the corporate
entity, FSF, Inc
You are missing the point entirely. This is not about representation or voting,
this is about the burden of daily activities.
Before work can be submitted to any project (GNU or otherwise) which has
a contribution form, there must be a check before merging to ensure the
submitter has active paperwork. AFAIK for Apache, Eclipse, GNU, CLANG,
Go, etc, this is a simple "Is person X on the list? Yes/No". Once a maintainer
sees yes, that is a constant Yes for in the future.
With your on again/off again proposal, the project maintainer must check
EVERYTIME they merge a contribution from ANYONE.Anyone can change
their mind at any time and repeatedly.
The paperwork burden on FSF is bad but the impact on maintainers is worse.
[FWIW I
You seem to have missed the change from a simple Yes/No condition
that never changes after the No -> Yes transition to a condition which
must be evaluated EVERYTIME a submission is made.
This really complicates things for those doing the day to day work.
--joel
RTEMS