This is a really nice proposal.
I also think that this does not solve anyway the issues of the FIG itself;
maybe the best option could be to push for both approaches? Nothing in the
FIG 3.0 proposal forbids that!
In fact, I think that the FIG 3.0 modification are good anyway, and that
the
Hi, all,
I was not monitoring the ML yesterday (getting some family Q.T. after a
trip) but I'll be keeping an eye on it today. I think we are all adults and
can abide by throttling rules in good faith. In the future, if you have any
concerns about the content or velocity of this (or any other
Dear Voting Members,
There is another way to solve the problems listed in the [FIG 3.0 summary][1]:
formally encourage the creation of a *-interop project as a prerequisite to a
FIG entrance vote. (Look to container-interop and async-interop as examples.)
* * *
Point by point from the FIG 3.0
> Downloading an email is 20-30 KB. Opening a forum page could be 1MB or
more.
Honestly this is kind of a ridiculous argument. But even if you consider
it, still a forum page is not 1MB per page, the css and js files will get
cached after your first request, so browsing subsequent pages won't
