some more work went into tweaking the language and structure. I have
another review scheduled with a content expert at Liip.

but I would also like to get an indication how to shape this further to fit
FIG.

I could envision moving the list of examples to a separate document that is
neither a PSR or by-law but that is updated once per year (or more often),
that is referenced from an inclusive language PSR similar to the other
resources.

wdyt?

regards
Lukas

On Wed, 19 Aug 2020 at 16:11, Lukas Kahwe Smith <sm...@pooteeweet.org>
wrote:

>
>
> On Tue, Aug 11, 2020 at 6:02 PM Alessandro Lai <alessandro.la...@gmail.com>
> wrote:
>
>> Thanks Lukas for the continued effort on this topic. You're basically
>> stumbling on a recurring problem that we have here at PHP-FIG: we don't
>> have a way to stipulate a "living document", something that is similar to a
>> PSR but can evolve.
>>
>> IMHO this could actually work if we write down a new bylaw that handles
>> this case, and it would solve similar issues like the coding standard (see
>> PSR-12) where the PSR can't keep up with how fast the language is evolving.
>> I'll give this some more thought and try to find a way to draft a bylaw
>> that encapsulates a basic solution to this.
>>
>
> thx!
>
> in the meantime, here is a first draft of a document about inclusive
> language
>
> https://docs.google.com/document/d/1-5iNw4xcfWLquVoV22QceYHFKdKode0VEhmQaC3fbcQ/edit#
>
> I have enabled comments/suggestions.
> It can become whatever .. a PSR, a by-law or something else. Once we have
> figured this out we can convert it to a PR.
>
> regards,
> Lukas
> --
> regards,
> Lukas
>
>
> --
regards,
Lukas

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/CAEFKHaE4yF0zZ3m1_yiH9_ZW-BQ_uoWmTQKn0g-oTK9bDKQ-kQ%40mail.gmail.com.

Reply via email to