Feedback from Make Meta and Community Teams

[patriciabt]

Feedback from Make Meta and Community Teams based on the tests conducted on https://demo.gatherpress.org/

Code of Conduct

• I agree to follow this project's Code of Conduct

[patriciabt]

Feedback from the demo site's feedback form:

• The anonymous registration was misunderstood, the feedback says "Anonymous is not working. I turned on anonymous sign up and but it is asking for me to register or log in".
  Maybe it's a confusing wording? people may think they do not need to log in, where we only offer attendees the option to appear without their name on the frontend, but organizers still see the names and attendees still need to log in

[patriciabt]

Feedback from the demo site's feedback form:

I went to edit post template and got an error. Error code is below in additional comments. I have an image of the error pop up if needed. https://demo.gatherpress.org/learn-wordpress-online-workshops/event/event-with-info-on-left/

got: TypeError: Cannot read properties of undefined (reading 'gatherpress_enable_initial_decline')

I cannot reproduce

[patriciabt]

Obviously the 2 comments above were for the other ticket :) (feedback from organizers), sorry!!

[peiraisotta]

Hi! I've started this document with the list of ideal requirements from the community team's side. Next week, during the community team monthly meeting, I'll ask everyone to add their preferred features. What is the deadline to provide you with the final feedback? Please, everyone, feel free to contribute to this document.

Thank you for moving this initiative forward.

[patriciabt]

@peiraisotta thank you so much!

There are 2 things here:

• Feature requests for the plugin
• Feature requests for the integration with .org

Most of your feature requests are related to the second one, and it's great, it's what we ask here in this ticket!
We talked a lot about that clear line during our last meetings, and for this, we need the Meta team to know what is needed for the integration

@angelasjin told us that we cannot involve the Meta team before the plugin itself gets enough feedback, because it's a lot of work.
We can understand that, not to make the Meta team work on an integration that would be useless if in the end the plugin is not accepted, or even if it is not ready, hence the demo site for current Meetup organizers.

We need to know!
Features:

1. What goes into the plugin itself (which is also a standalone event management plugin for any site)
2. What will go into an integration with .org.
3. What already exists. For example the integration with user profiles/BuddyPress is used there right? what about emailing users? is there a CRM? to not recreate what already exists, not do things differently, and what are the hooks we can plug into

And for 2 and 3, by which team:
A. What will be done by the GatherPress team (maybe then in an addon plugin, @mauteri?), with the info we need in point 3 above.
B. What can be done only by the Meta team
C. What can we build together.

About the deadline, it's not very clear, as we did not get a deadline by Angela for the feedback from current Meetup organizers on the demo site (we need as much as possible).

The list in your document is wonderful, it clears a lot. We are very much looking forward to have you in our meeting next week. It would be great to have @angelasjin and a Meta team member as well.

@mauteri can maybe explain further :)

[mauteri]

@patriciabt you hit all the points I would have said. :-)

I think it is important to get the Meta team to review the plugin before we dig too deep into requests that fall outside of the features that would fall into the general GatherPress plugin. Any feature request that falls into the general plugin is absolutely the responsibility of the GatherPress team to prioritize and execute on. Things that fall outside of that end up in a gray area as Patricia pointed out. Some things may be able to be handled by other plugins that the Meta team approves of to run on the WP network, others may need to be written. In the latter, we need to find someone that is able to lead that initiative. Basically, cross team, we'll need to figure out what the most pressing things are because each team is going to have different opinions. That will be a bit of a challenge, but mostly around communication.

[peiraisotta]

Thank you both. I am sorry but when you say "What goes into the plugin itself", I am not sure I understand what you mean. I hope that you can clarify this today during the weekly call. Thank you.

[mauteri]

Hi @peiraisotta, so what I mean is that the plugin itself is responsible for event management, and while we would love to use it in the context of the .org network, it is also a plugin that anyone can download and use for their own needs. So when requests come in that are very specific to the WordPress community or the .org network, we might not put those changes in the core GatherPress plugin (which is what i meant by "What goes into the plugin itself"), but rather put them in a separate companion plugin. Basically, we don't want to include code in the core plugin that has no context outside of the .org network. I hope that makes sense. Thanks!

[patriciabt]

Moved to the GatherPress-WordPress.org Integration Project