Currently organizer roles match WordPress roles, but that's pretty inflexible and was an idea for when the project was a WordPress application vs plugin.

Organizer role should be a taxonomy terms separate from WordPress roles.

Create a custom block for presenter(s). This block will allow 2 things:

• Selection of user(s) in network. Not necessarily in the site group, but in users across network. This will be an autocomplete field.
• Description / Bio of user(s).

The presentation will be data from the user (photo, name, profile link) and that description / bio.

Meta data will be saved to each user with the ID of the event and blog ID, so we can display information about the event on the users' profile somewhere.

We should also save this as meta data in the event.

Remove the block should remove meta data from user/event.

This was a misguided feature. I'm going to remove it and remove areas that are using it.

A block that will display the event start/end date and time. Can be basic for now, but should eventually have configuration options for display.

For these blocks, let's pass the event ID to them directly rather than via GatherPress object. These blocks should be functional when they are not on the event page, so someone could choose to attend/not attend and see the list of attendees. This requires a slight refactor of how data is passed to the blocks and will require an API calls and new endpoint to get info about how the status of the logged in user when viewing the event module and interacting with it.

Updated: Zoom Module v1 Scope
Start with simple link that can be Zoom or anything else (like Meetup does).

Queued: Zoom Module v2 Scope
Eventually explore integrating Zoom link as an embeddable block for events to make attending online super easy right from the browser.

TEST Plugin Integration

1. INSTALL WP Repo Available Integration (Mervin may have a test client he can sandbox this in)
2. CREATE Sample event + capture custom data for the RSVP
3. REPORT Back to GP team on the functionality available, and whether we can incorporate all/some into our next version release

• 1. Refresh phrasing for the description of the project
• 2. Add another layer to the docx
• 3. Update Repository Description (for GitHub meta)
• 4. Add icon to the repository itself

On new event in editor, setup a default template with common event blocks in displayed ready for configuration.

Styling and markup updates need to happen here. Also need to add a See all link to have a modal pop up and scroll through all attendees making API calls and loading. Block itself should limit what it shows for scaling.

Setup Git "GatherPress" to deploy automatically to "GatherPress.org"

• Created repository for the website (different from the plugin project). This was done in WingManWP's GitLab account, and attached to SpinUp WP for gatherpress.org
• Created submodule pulling in this gatherpress (project) repo
• Tested/confirmed automatic deployment of pushes to the "site" repo
• Debug why changes to this gatherpress repo, do not automatically push to the site repo (where this is a submodule)

class-buddypress.php and class-email.php are specific to BuddyPress. We want the plugin to be enhanced by using BuddyPress, but not require BuddyPress. There's a few @todo within code to allow BuddyPress components to be able to hook in when BuddyPress plugin is enabled.

This feature allows users without an account to RSVP to an event. Basic info (First name, Last name, Email, possibly other fields that can be added) will trigger and email send with a link to the address to confirm. Infrastructure can include a queuing system that deletes non-confirmations every 24-48 hours. More thought/discussion should be given to this feature to flesh it out a bit more.

with the description of GatherPress plugin, use cases, etc.

Last test with Local by Flywheel resulted in a fatal error, which appeared to be caused by autoloader. This issue has been addressed and this can be tested again.

Add the ability to have guests register for this event +/- a headcount limit

Also see CampTix
Also See #83

This feature allows users without an account to RSVP to an event. Basic info (First name, Last name, Email, possibly other fields that can be added) will trigger and email send with a link to the address to confirm. Infrastructure can include a queuing system that deletes non-confirmations every 24-48 hours. More thought/discussion should be given to this feature to flesh it out a bit more.

Also see CampTix
Also see #86

create class-settings.php that manages settings such as role names and other language that is configurable.

Refactor Event class; Add utility class (move Helpers to utility class); Attendee class may be merged into Event class. Event class no longer singleton but extends an event post when a post_id is supplied. Move some things from Event/Attendee classes to Setup class.

• Setup wp-env so local environment in Docker can be setup
• Add to README steps to setup
• Bonus if you have time: run unit tests and phpcs in Docker and add to README

Two custom tables we have:
wp_gp_attendees
wp_gp_event_extended

To be consistent, let's rename wp_gp_event_extended to wp_gp_events. This is a breaking change so best to do it now rather than later.

@MervinHernandez do a fresh install of this on a vanilla WP site, see what the experience is like.
Bring back comments.

Add a feature where an event can be recurring. Basic features include frequency of recurrence and ability to override contents of recurrence or do one-off updates on a recurring events content. WP Cron will create events (maybe default to X number out (maybe default to 4) that can be configured in global settings and overwritten in event recurrence settings.

• Remove tailwind CSS and include basic styling for blocks.
• Add body class gp-theme-THEME to allow easy theme styling

Feature Description

Updated: Zoom Module v1 Scope
Start with simple link that can be Zoom or anything else (like Meetup does).

Queued: Zoom Module v2 Scope
Eventually explore integrating Zoom link as an embeddable block for events to make attending online super easy right from the browser.

Test

• Only displayed if attendee is a confirmed attendee (not in the waiting list)

As of February 26, gatherpress.org is hosted by Mervin on SpinUp, and the codebase is in one of his GitLab repo's.

MOVE Repo from GitLab to GH (under GatherPress organization)

• MOVE the repository contents
• RECONNECT SpinUp site to refer to GH instead of GL repo

Tasks for Mervin

• 1. Make gatherpress.org MU
• 2. Add mike as a user
• 3. Link gatherpress.org to GitRepo
• 4. Add mike as SSH user on Spin2 (Mervin's)

Setup MU

• Subdirectory is fine ... let's not worry about subdomain for now

Noting observations as I go.

Most of the components for this are already in class-events.php, but there isn't a block to include this on the editor.

• Start in default location
• No configurations (will have config options in future)

In php8 sorting, such as usort, uasort, expect an integer, not a boolean. On settings page, changing casting from bool to int fixes the issue.

https://take.ms/JDJlb

Use the nametag icon in dashicons. It's cute and I think represents the project well.

Venue Feature v1
Add the ability to save venues and choose among saved venues in events. Venue will have name and address and include a block to display address and possibly Google map plot.

Venue Feature v2
Google Map integration

Support to PHP 7.0. WordPress supports to 5.6, but that should be going away soon. Also would require reworking of a lot of code.

Create a basic stylesheet for blocks. Use tailwinds to assist with styling, but don't rely on utility classes as they won't always work with themes well. Instead use @apply with tailwinds utility classes.

Upon activating plugin - flush permalinks.

Recommending we rename this to something more descript - "Menu Structure" I understand to be related to nav menu's or other structural item. In essence, not to the "Display Attendee Count by Reservation".

Currently the Upcoming and Past Events blocks are non-dynamic blocks and are rendered via an API endpoint in the editor. These blocks would be a lot more interesting if they were dynamic blocks and had features that allowed control of attending or not attending right from that block. It would be easier to maintain this block as well and we can combine common components and styling more easily.

Remove usage of axios for API calls and start using apiFetch.