Add Meeting Type “Inter”

Hi @wokat,

As I mentioned in my PR comment, our FAQ describes the process by which a website such as yours cad add custom meeting types. These are not imported into AA’s mobile Meeting Guide app.

Prior to AAWS/GSO taking over the Meeting Guide app, what can probably be described as an ad hoc process existed in which members agreed upon the most common meeting types. This process doesn’t exist any more, and while some may argue it is needed, I believe the plugin’s approach of allowing local meeting types is the best approach. In fact, I think your comments above highlight how difficult it would be to do it any differently.

For example, Group A prefers to use the term “Intersex” and “LGBTQI” while Group B has already been using “Inter” and “LGBTQ”. Which are correct? I’ve also seen reference to “LGBTQIA”. In some circles the “A” stands for “asexual” while in others it stands for “allies”, so they add another “A” to cover the other. An app that is trying to useful to the broader needs of AA probably better serves that purpose by avoiding type definitions that are so open to interpretation. However, I don’t speak for AA or GSO; neither do any of the plugin authors or maintainers. We need to keep the type definitions consistent with the app or we would break things quickly. A local definition you put in your site configuration is the best approach.

I did just think of an option for you to continue this discussion with broader input if you wish: start a thread in the TIAA Forum

Thanks, the meeting types local to our site work well.

Thank you for the link, too. Yes, I can see now how the LGBTQI-change could have become problematic.

And I had understood your reference in the PR to ?you seeing no effort“ to mean no discussion about the topic going on, yet. So here I’ve started one.

So while keeping the list of filter criteria applying to a local set of meetings short is quite important for UX I still can‘t help thinking that this particular subset of very specific properties seems exclusory when applied in this manner. Obviously not having the two other tags would make this discussion superfluous.

I will talk to my meeting contact to see, whether I should take it to TIAA, then.

Thanks.

I hope you do come to TIAA to discuss. In that forum, I’d be more open to sharing my beliefs about how this should look going forward. In this forum, I want to keep my comments very specific to maintenance of the plugin and interoperability with AA’s Meeting Guide App.

My seeing no effort is more regarding the broader AA community and GSO. The plugin, our dev page and this forum here is not a policy setting body. We strive to provide a service based on accepted and established guidelines.

Thanks for your understanding of what I realize can be a difficult issue.