If FIG is the standards body why has the FIG not formally changed it's name?
On Tuesday, August 9, 2016 at 12:54:04 PM UTC-4, Larry Garfield wrote: > > Given that there's ~9 specs being worked on currently in various stages, > the idea that FIG's work is "done" seems completely unsupportable. > > FIG is already the de facto PHP Standards Body. That much is very > clear; some here don't want to admit that, but that's very clear from > the Reddit thread on the subject, talks at conferences, impacts on > projects and tooling (PSR-2 preset in PHPStorm?) and general zeitgeist. > > As Michael noted previously, if a "new" body were to form one of two > things would happen: > > 1) FIG would continue, there'd be 2 competing standards bodies, and thus > no actual standards. This is the worst possible outcome for > interoperability and collaboration. > > 2) FIG would die off, either quickly or slowly, and the new group would > try to fill its ecological niche. That would be a very messy and > complicated process with an ugly, confusing transition period, which > benefits no one. The only way to minimize that would be for FIG to > actively shut itself down completely as soon as the new group is setup, > and publicly say "they're replacing us, kthxbye". Which... would have > the same net effect as FIG just evolving, but would be more logistically > complicated and confuse a bunch of people needlessly. > > FIG isn't "done". It's not "dead." It's just evolving. That's OK. > Really! We should be accustomed to this by now. PHP as a language and > community is one of the fastest evolving around. PHP has reinvented > itself in the last 6-7 years, and FIG has been a part of that. That's > something we should be proud of. > > But FIG can and should evolve along with PHP. We've done it before. > The FIG of 2009 is not at all what we are today. When the entirely > cowboy-free-for-all way of working on specs broke down, we changed the > process and added more formality. (FIG 2.0, which added the formal > Editor, Sponsor, and Coordinator.) It was an improvement. Now, we're > still growing and see a need to evolve our structure further. That > doesn't mean FIG is "done", just that we're evolving to improve > ourselves. In a few years, might the situation have changed further and > we need to tack again, with a FIG 4? Quite possibly! And when that > time comes we should be prepared to evolve with it. > > We, as a community and as FIG, should be looking forwards, how we can > continue to help PHP into the future. Not closing up shop because > "whelp, autoloading and coding standards are done, peace out." > > Closing up shop or turning into just a passive rubber-stamp for people > we refuse to let collaborate in our space is short-sighted and > ultimately self-defeating. > > The fact that there are 9 groups trying to build additional > collaborative standards within FIG should be a sign that people do see > value in FIG, and we're nowhere close to "done". If anything, it's a > sign of a potentially bright future for FIG and PHP, if we approach it > properly. > > --Larry Garfield > > On 08/09/2016 11:17 AM, Joe Ferguson wrote: > > By “standards for the language” I mean an official (or as close to > official as it can get) Standards for the PHP language. PHP has never (as > far as I’m aware) had a Standards Body. FIG is as close as we’ve come. My > observation is that FIG 3.0 should skip FIG and become that standards body. > > > >> On Aug 9, 2016, at 11:10, Alessandro Pellizzari <al...@amiran.it > <javascript:>> wrote: > >> > >> On 09/08/2016 16:37, Joe Ferguson wrote: > >> > >>> I would rather see FIG marked complete, and those leaders interested > in > >>> moving forward start a new PHP Standards Body that would adopt (not > >>> claim) the previous PSRs from FIG and begin work on more standards for > >>> the language, not frameworks or packages. > >> I partly agree with what you say, but what do you mean by "standards > for the language"? Could you give some examples? > >> > >> Bye. > > -- 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/65213942-a24d-4fa0-bf9e-02a288887fd8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
