Past events should not shown anymore on the website, they should not deleted but marked as past, so they can be shown in an archive.

Applicants should get an e-mail if they were admitted or rejected to the event. See #39

We need to show to the user that they submitted the new event or new application successfully since they are not able to see the new Event in index or show and also the application is not visible for the user after they save it.

-maybe the organizers don't have questions
-deadline 4 submission
-field where the organizers can type how many tickets they are giving
-events : big apply button (apply and back are left from scaffolding)

-homepage - applicant or organizer? show me conferences /or I want to submit a conference.
-organizer's name should not be shown to all

-event name and logo bigger
-Link to the code of conduct
-description of the application process
-questions don't need to be there
-application deadline
-venue of the conference (later: show conferences near me)
-Is it cool to have tags like "ruby conferences" or other types of conferences, so people can sort
-Apply-> button and a button to go back to the events page
-Connection of applicants with organizer via admin:
Applicants expect a "declination e-mail" if not chosen -> extract e-mails csv-> easily extract to excel
-Ux application designer

-to know in which side you are

-put the name of the conference first
-deadline for the applications to conference

For next versions- login and profile for applicants

-should we leave out questions? Organizers shouldn't have any say, just dietary info or t-shirts size---- think about it. Or optional maybe. They shouldn't be able to ask sensitive stuff. Rephrase: extra info ... like t-shirts and stuff.
Save event-> submit (change button)

Notification for the admin (E-Mail) that an event was submitted

past events not shown anymore in current events but in the past.... Do not erase them ... but most importantly leave current events.

-edit option for the admin in case the organizers submit it with typos
(maybe in the future the organizer could edit it himself? ) or some sort of preview?

- msg after organizers submit event - Annika will send the text. Info: The eventis not visisble until it is approved.

-E-mail notification also for organizers

Organizers -check boxes, if they are offering travel, accomodation, child care

design -Justine will be contacted

feedback: issue

figure out how to implement this

• DB contents --> CSV file, e.g. all applications per event
• Add a link to download the CSV file

-to know in which side you are, highlight the one you are on in the navigation bar

• submit event button is confusing - remove!

The admin should get a notification via email that an event was submitted.

For that have a look at http://guides.rubyonrails.org/action_mailer_basics.html

Save event-> submit (change button)

@bioshrimp if you want, you can start with that and be creative :) Probably you want to talk to Anika about her wishes.

• Justine and Lisa will be contacted

Put the username and password into Heroku.

• Form doesn't accept Start and End date at the same day

• event name should be on top and bigger

Make the site navigatable.

i.e. Home / Events / Submit Event / Contact ... on top of each page. What else would we need?

i.e. use *

We still need to copy the CSS from the Supply-Forms.

• 'show event' should not show Organizer email and organizer name

Ruby version: 2.1.5
Rails version: 4.2.2
Database: Postgresql

• Routes
• Controller
• View

Describe the application process for the
a) organizer
b) applicant

Idea: add an FAQ section

Users should be able apply for several events without having to type in all the information over and over.

As soon as possible! :)

• Name/Nickname
• Email address
• Event ID as foreign key
• Answers to questions

• if organizer submits something wrong/typos admin should be able to edit
  (edit page is at the moment only for approving/unapproving an event)

Would be nice to position both fields on same line.
Matt says the keyword is "float"

Possibility to distinguish approved events from non-approved (make new column in database)

Admin_index page: approved / non approved (checkbox?)

http://guides.rubyonrails.org/association_basics.html

Matt will ask questions about this. ;)

• Placeholder for description,
• button/link to list of events,
• button/link to new event form,
• imprint.

• homepage - applicant or organizer? show me conferences /or I want to submit a conference.

• Is it cool to have tags like "ruby conferences" or other types of conferences, so people can sort

-> we have to think whether it is good to use a gem like acts-as-taggable for that

Do we need all three? / What makes most sense?
--> Talk to Anika about this, too.

add big apply button
and think about positioning the button and the "back"link elsewhere

• Routes
• Controller
• View
  Form fields:
• Name/Nickname
• Email address
  Based on conference organizer's specifications:
• Include 1-3 other form fields

We need validations for events and applications.

See here being a preparation for next Monday (August, 24):
http://guides.rubyonrails.org/active_record_validations.html

Organizers can mark if they are covering travel expenses, accomodation, child care ...
Organizers can ask via checkboxes what t-shirt size applicant has and what kind of food she eats.

Read http://guides.rubyonrails.org/active_record_validations.html

We need validations for Event and Application. So that the forms are not accepted empty or with things that are not an email or a date.

Event: Organizer name, Organizer email, Description, Name, Start date and End date
(I guess not all 3 questions have to be there. Maybe an organizer doesn't need questions.)

Application: Name, Email
(Depending on the questions answers should also not be empty. )

Everybody is invited to work on this issue. Pick either event or application and make a new branch while working on the problem. And leave a comment here, if you'd like to work on it.

think about and come up with a solution: how can we support the orientation of the user in the navigation e.g. mark current site in navigation bar

• deadline 4 submission
• field where the organizers can type how many tickets they are giving
• venue of the conference (later: show conferences near me)
• Link to homepage
• Link to the code of conduct
• what is funded? travel, accomodation, ???
• description of the application process
• should we leave out questions? Organizers shouldn't have any say, just dietary info or t-shirts size---- think about it. Or optional maybe. They shouldn't be able to ask sensitive stuff. Rephrase: extra info ... like t-shirts and stuff.

• organizers should get an email after submitting an event with information what's going to happen (event has to be approved, ...)
  #39

• show information to the organizer after they submitted the event
• Annika will send the text

Info: The eventis not visisble until it is approved.

see also #59

• edit option for the admin in case the organizers submit it with typos
• add some sort of preview after submitting, so organizer can read it again and make corrections

• Look at design sketch in issue #2
• Decide on features
• Implement

deadline date should be added

• which controls the last possible application
• in the admin index the events should be sortable according to the deadlines

• make it possible for an organizer to add a picture or logo
• placeholder picture if no picture is uploaded

• question one is mandatory right now
• Anika says questions should not be there, because organizers could ask sensitive questions, maybe use as fields for stuff like dietary restrictions or T-shirt size

• how many tickets are available for the event
• for admin: how many people applied for the event
• for admin: how many tickets are still available

On the list of events: the admin should be able to delete events in case of spam or stupid stuff.