komunumo / komunumo-server Goto Github PK

On the left side of the grid in the first column, there is nice padding. On the right side of the last column, there is no padding. It looks like it has been "cut off". I want the same padding there as on the left side of the first column.

e.g. 45 min or 1:30 h

Past events are read-only, no validation is needed.

Was only used twice the last two years. If the event needs an agenda, it can be added to the description.

Logo and title must be configurable

e g. Edward Burns show only 2 events, should be 3!

Used in EventDialog…

• add new property type to the event entity
• type: enum (values: talk, workshop, interview, other)
• show event type on the website
• show event type in the grid in admin view

A sponsor is active when the actual date is between valid_from and valid_to.
The value of valid_to might be null if the sponsor contract renews automatically.

With design support from @Interactiondesigner based on the logo color schema.

Need some brainstorming with @simasch…

Generate a personalized link and send it to the speaker(s). The link will display a form with some fields end to enable the speaker(s) to update the event data and the speaker data (like the photo, bio, etc). If the event was in the past, the link will permanently redirect to the event page.

So we don't need to exchange all the data via email between the speaker(s) and the organizer, and by Jira between the organizer and Ursula, who will add it to the website. Streamlining the process…

Keywords work like tags and should be included in the event filter.

The verification and migration process is done manually using the Maven Flyway plugin. This should be done automatically on each start before the application accesses the database.

• add a new property members_only to the events entity (default: false)
• add members only option to event admin
• import members only option from jug.ch
• add validation for members only events to registration form

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• ⬆️ Update vaadin.version to v24.4.4 (com.vaadin:vaadin-maven-plugin, com.vaadin:vaadin-bom)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

• create a registration form using an email address, first name, and last name
• create a new entry in the member table
• handle registration event (add entry to event_member table)
• handle duplicate registrations
• handle cancelations (remove entry from event_member table)
• show number of registered members including guests on event grid in admin view
• add email address to newsletter

• add all missing properties to the event entity
• add all missing properties to the event view
• completing test data

Result: We have too many members after the import (more than 6'000 instead of a little more than 1'000).
Todo: Ask Ursula about her database model, how to identify active and inactive members.

Upload Bigmarker Excel file to update the attendee list of past events.

• create form (select event and upload file)
• read attendee data and update event_member table
• add missing attendees to table
• update no-show information

The save button is enabled by default when editing future events. It should be disabled until there is a modification.

All admins can be organizers. Each event has one organizer.

Events can not only be talks with abstracts. We have workshops, interviews, etc. Naming this field description feels better.

• create database table
• replace select box by combobox
• read values from database table
• allow custom values
• add custom value to database

Import existing data from the old database.

• Speakers
• Events
• Members
• Attendees
• Sponsors

This list is not yet final.

• create a mapping table event_member to store the associations of members to events
• create a registration form using an email address for members only
• handle registration event (add entry to event_member table)
• send registration info mail to attendee
• handle duplicate registrations
• handle cancelations (remove entry from event_member table)
• show number of registered members on event grid in admin view
• show number of registrations on the dashboard
• show rate of no-shows on the dashboard
• show monthly visitors per location on the dashboard

On the website, the event detail page should have a unique and permanent URL.

Possible template:
/events/<location>/<year>/<simplified-title>

Example:
/events/online/2021/java-17-release-party

• properties: id, firstname, lastname, email, photo, bio, twitter-handle, linkedin-url
• own view with grid and details
• main menu entry
• linked with events (n:n relationship)

Depending on the location, there might be only enough seats for a limited number of attendees.

• add property attendee_limit to the event property
• add property attendee_limit to the event admin
• add validation to the registration form
• show events as "sold out" or "fully booked"
• send email to the organizer when more than 80% of the limit is reached
• treat a limit of 0 as unlimited
• default limit is 0 (unlimited)

add property status to member entity

Type: enum
Values: member, guest