agile-alliance-brazil / submissions Goto Github PK

As an author
I want to receive an e-mail when an early review feedback is entered for my session
So that I can receive the feedback and improve it as early as possible

Em "Regras de Submissao":

• no texto "editar propostas existentes das quais você um dos autores.", corrigir para "das quais voce é um dos autores"
• no texto " tipo de sessão proposto", corrigir para "tipo de sessão proposta"

O texto "Se a sua sessão for uma Palestra, indique a duração adequada para ela. Para Tutoriais e Workshops recomendamos uma duração de 110 minutos." na submissao nao parece adequado. Da a entender que soh eh preciso informar a duracao se for uma palestra e o dado eh obrigatorio sempre.

Allow different translation of names and descriptions per conference for:

• Tracks
• Session Types
• Audience Levels

All data that is now static should be inside a conference. Meaning:

• All Dates
• Session types, levels and tracks (covered by issue #9)
• Preference
• Reviewers

Translations should also be prepended with a conference identifier to allow variable texts.

As an organizer
I want to be able to see how many early reviews the sessions on my track have already received
So that I can track the quality of my track

Acceptance Criteria:

• On organizer sessions page, a new column displaying the count of early reviews should be visible
• Clicking on the count should take me to the page that displays the full feedback, including the reviewer's name

Instead of having the standard error messages for rails/devise inside config/locale, we should add the rails-i18n gem and similars to simplify maintenance

The app is still running on Ruby 1.8.7.. That's too old. Let's upgrade to Ruby 1.9.3

As an organizer
I want to track progress on the early review phase
So that I can see how many reviews are missing before the deadline arrives and can take action before it expires

Acceptance Criteria:

• Display progress bar with current and total number of reviews needed for early feedback phase
• Only count one review per session for the purposes of the progress bar, even if the session has more than one review

We used to use SMTP to send e-mails, and migrated to Amazon SES. There are still 2 separate sections on config.yml, and the example file has configuration options that are not needed anymore.

As a reviewer
I want to be blocked from entering early feedback after the early feedback cycle
So that I don't break the review process by giving more feedback while the submission is still ongoing.

We currently need to maintain 4 different copies of each e-mail type we send:

• english and portuguese
• html and text

This issue is to reduce the duplication, by using something like markerb (http://blog.plataformatec.com.br/2011/06/multipart-templates-with-markerb/), to handle e-mail with some kind of markup and let the gem generate the html and text to make it more maintainable.

The date in the session submission e-mails have the dates hardcoded to the deadlines from 2011. We should change it to use the deadline embedded in the conference

If the user has provided a twitter username, we can use the twitter API to fetch a small version of their avatar and display it on the session details and on session listings

For 2012:

• Talk can only be 50 mins (not 110)
• Hands on can only be 110 mins (not 50)
• Mechanics/Process field shouldn't be required for Lightning Talks (hide)

Informational text says that minimum password length is for, but we're accepting 3. These should be consistent

After adding static pages per conference, there were still some hardcoded dates that we want to move to the DB

As a conference organizer
I want to change the reviewer invite email
In order to inform about the dynamics for the two round reviews and set work expectation

As an organizer
I want to update the text for the reviewer terms of agreement
So that it's updated to the current conference

Trying to add a session keyword or second author will search for username but not display list for auto complete

As an organizer
I want to invite a list of reviewers all at once
So that I don't have to do it by hand one by one

When the user is logged in and goes to "My profile" page, he should see all the information, not only the public available information.

As an agile brazil contributor
I want to contribute to jquery.ui.autocomplete to allow multiline autocomplete
So that I can remove duplication from sessions/_form and reviewers/_form

This happens when logged in in a tab, and trying to retrieve password in a separate tab.

When editing a session and changing the "keywords" field with multiple values (comma separated), only the first value is persisted

With the inclusion of shoulda-matchers, we can refactor controllers specs to be more readable. Also, we should not render_views for every single controller test, since it makes tests run slower. Maybe keep one happy-path test for each action with render_views, and not integrate views for the other tests. Once we build capybara tests, we probably don't need render_view coverage for view failures.

The registration system added a lot of complexity to the application and was built to the specific requirements we had in 2011. If we decide to support a registration system in the future, we should build it as a separate app, and expose some API that it could use to integrate with it.

Things to cleanup:

• Database tables related to registration
• PayPal integration (configs, certificates)
• Pre-Registration rake tasks
• Code:
  • routes
  • controllers
  • models
  • views
  • tests
  • helpers
  • mailers
  • lib

Rails 3 introduced asset pipelines to better handle assets.
We were using Jammit to minify our JS and compile our sass.
Ideally, we could use rails 3 asset pipeline and throw jammit away.

I removed the users resource from the :year scope in routes.rb, but the my_sessions route should still be specific to a given conference.

We should implement validations and update the JS to allow:

• Talks are always 50 minutes
• Hands On sessions are always 110 minutes

On the static pages, where we display the deadlines, we should try to calculate which one is bold based on the current date

If you're an author, but only have sessions submitted as the second author, the link "My sessions" is missing in the navigation menu

So that it's easier to talk with all reviewers each year. Everybody can email each other through this list and it only includes reviewers that have accepted participating through the system.

As a reviewer
I want to be able to enter extra feedback for sessions that already have an early review
So that I can provide more feedback to the authors

Acceptance Criteria:

• From the session description page, the link to "Review Session" should still be visible even after the first early review has been entered

Currently, the user's language preference is available in the User model, but is not a choice the user can pick when creating/editing his profile.

As an author of a session proposal
I want to receive an email when someone posts a comment to my proposal
In order to provide faster and better feedback and increase my chances to have my session approved

Conference date & location are simple data in the database.
That works for most locations since those don't change dramatically in Portuguese/English. However, a lot of months have slightly different names. It should be stored as an i18n key and corrected in i18n files.

We have a lot of DB migrations. After the registrations cleanup (#6), we should consolidate migrations into a single migration

We have some pending specs due to library upgrades. These should be reviewed to see if we can find another way to test the same behaviour or removed altogether.

While filling out a session proposal, there are some validations around the number of characters (maximum/minimum required). This story is to add some explanation around those in the labels, as well as inform a running counter of how many characters were already typed/left to type.

As a session author
In order to reduce my inbox size
I want to be able to set a user preference to stop receiving emails for every comment in my proposals

As a session author
In order to reduce my inbox size but still provide feedback when needed
I want to be able to set a session preference to stop receiving emails for every comment in that proposals

As a reviewer
I want to be able to see sessions that were submitted prior to the early review deadline that have not received reviews yet
So that I can review them

Acceptance criteria:

• Only show sessions that match reviewer's preferences (track/level of audience/conflict of interest)
• Only show sessions that have not yet received reviews
• Only show sessions submitted prior to the early submission deadline (create_at, not updated_at)

The reviewer receives an email with a link. Before accepting or rejecting the invitation in the link, he is required to either login or create a new user.

This app was built using TDD for unit testing, but doesn't have any integration/functional tests around user journeys. This issue is to add basic capybara infrastructure to be able to write those tests as we review/add features

As an author that submitted a session in the first review round
I want to see my sessions reviews as soon as they are entered
So that I can have early feedback to adapt them

Email field size is the only one that is very short. Increase to match all other fields.

If you create a user with country of Brazil, state is mandatory. If you try to later edit the profile for that user, and change the country, it won't remove the state

When entering an invalid phone during user registation/update, the error message is cryptic. We want it to include an example of a valid phone to help the user to fix it.

Different conferences had different backgrounds. Having the ability to maintain the look and feel of one conference after setting up a new one would be nice to have.

In order to have a stable environment, we froze gems to the exact version that the app relies on. We want to update the gems to the latest stable versions.

Rafael came up with suggestions on how to improve the instruction texts on the session submission form. We should use the improved version