Hi all, Multiple responses inline.
* * * > On Aug 29, 2016, at 10:20, Korvin Szanto <korvinsza...@gmail.com> wrote: > > I just don't see why this is at all necessary, what does this get us other > than a new name? To me it seems like this is just a semantic runaround for > what old fig will be once fig 3.0 passes. >From my original blog post, the benefits (among others) are these: - As a brand-new organization, it can define its vision and mission without in-group rivalry. - It can curate its membership, bringing in only the people and projects that adhere to its vision (and keeping out those who do not). - It can establish any organizational structure (hierarchical or otherwise) from the outset, without having to worry about precedent or prior expectations. - It can have any code of conduct it wants as part of its foundational structure. - Whatever negative baggage is perceived as being part of the FIG is dropped. Joe Ferguson paraphrased this as "green fields." (If nothing else, think of the biggest benefit as the ability to exclude that pesky, pernicious, Paul M. Jones without needing a vote to do it.) > IMO once FIG 3.0 is around for a little bit of time, FIG 2.0 will become just > a slide on someones presentation and that's all. What does it matter if that > slide says "Gone: Disbanded then remade into FIG 3.0" vs "Gone: Reformed as > FIG 3.0"? The new group (if any arises) will be a new and different creation, with a new and different name. It may resemble the FIG in some ways, but it most definitely will *not* be the same. It will be a break from, not a continuation of, the FIG. As such I don't see why anybody would confuse it with FIG, especially if the new group behaves properly and actively distances itself from FIG and the FIG's PSRs, as it should. * * * > On Aug 29, 2016, at 10:39, Lukas Kahwe Smith <sm...@pooteeweet.org> wrote: > > the bulk of the community doesn’t care about our by-laws, they are about > PSRs, so to the community “disbanding” FIG will just be confusion about why > suddenly PSRs would live on another site/github repo .. I see no reason why they would live on another site or Github repo. Perhaps I was insufficiently explicit earlier. To be more clear: I would expect the sites and repos to continue to exist where they are now, kept in place without significant or substantial changes, by the archivist(s). Their purpose is to maintain the PSRs as they are, and to keep the FIG- and PSR-related names occupied so they cannot be used by later actors. I agree about the importance of bylaws vs PSRs: the real value of this organization is expressed in its productive output (PSRs) not in its bylaws (which serve no useful purpose outside the group, and perhaps not that much of a useful purpose inside the group). * * * > On Aug 29, 2016, at 17:51, Christopher Pitt <cgp...@gmail.com> wrote: > > Also skipped the async stuff (event loops and promises), which are also > *-interop projects. I don't see an "async" PSR listed (unless you mean the Event Manager PSR, in which case it was indeed included my original list). If you can link to the one you think I skipped, I'll be happy to remedy. > My point was less about things that are *-interop and more all these things > having started as projects under the FIG banner, with their natural > conclusion set for the same. I think you presume too much. For example, that there is a "natural conclusion" to something being started as a "draft"; there is no guarantee that they will ever finish as "accepted" PSRs, or that they cannot ever be withdrawn, or otherwise disposed of by some means. Some early PSRs (notably 4, but others too) transitioned from one process to another; transitioning to some other as-yet undetermined process would not be out of line. -- Paul M. Jones http://paul-m-jones.com -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/3015F6EF-1DDD-4C4C-80AF-CD7CD0C7ED30%40gmail.com. For more options, visit https://groups.google.com/d/optout.
