seattlerb / seattlerb.org Goto Github PK

We could benefit from a simple blog to post updates and the like on.

http://www.seattlerb.org/members is 500 right now.

We're getting overrun with spam submissions on the talks page. I deleted 60+ a few days ago and it's filling up again.

It looks like there's a 'spam' field on the form that we're not checking in the controller, perhaps we should do that? https://github.com/seattlerb/seattlerb.org/blob/master/app/views/talks/_form.html.erb#L24

The speakers are listed for the upcoming talks now. Yay!
Unfortunately the style is off. Boo!

Need a form with all the information in the current "dudes" table (soon to be member).

create_table "dudes", :force => true do |t|
t.string "name"
t.string "email"
t.text "bio", :limit => 255
t.string "website"
t.datetime "created_at"
t.datetime "updated_at"
t.string "ruby_gems_id"
t.boolean "featured", :default => false
t.string "twitter"
t.string "github"
t.string "image_url"
end

Extra bonus credit would include validating the twitter, github, and ruby_gems_id fields.

Name and ruby_gems_id are required.

Generic suck

I've gotten a few emails from Heroku about this:
https://devcenter.heroku.com/articles/moving-to-the-current-routing-stack

This is a reminder that Heroku is turning off the legacy “.heroku.com” routing path on September 29th 2014. This is part of an effort to standardize on a single, fast, highly available and scalable routing stack for all customers.

You are receiving this email because one or more of your apps is still using the legacy routing and you must take action to ensure continued operation of those apps after the September 29th deadline.

The following domains which are still receiving legacy traffic are:

seattlerb.heroku.com

Also, you may use the Legacy Routing Analyzer to see which of your apps are affected. Login to your Heroku account and click here.

We recommend that you migrate those affected apps away from the legacy routing infrastructure as soon as possible.

For instructions on how to make the move, please visit this Heroku Dev Center article.

We know that changing DNS settings for live apps requires care and planning, and we will assist with guidance and advice for you to make the necessary updates. If you have any questions about this topic, feel free to open a support ticket.

We will continue to send reminders over the next several weeks to owners and collaborators on apps that continue to use the legacy routing infrastructure.

Should be optional, but I'm not sure we need this. Discuss?

If a speaker submitting a talk has a specific event when they want to speak at, they should be able to indicate this on the talk submission form.

This depends on the Event model having been implemented in #31.

How I used ruby to schedule my bowel movements.

http://www.seattlerb.org/suggestions

derp

It either needs to gracefully not have an image or, better(?), update the image.

The member images are not being displayed due to the Twitter API being outdated.

Version 1.1 requires the app to authenticate via Oauth, we need to sign up for keys here https://dev.twitter.com/apps

Would it be easiest to just use the twitter gem https://github.com/sferik/twitter to help with all the OAuth fun?

I can start working on this, but don't know if I can create the keys

We need a section for our study groups. It should highlight the groups that are currently active as well as list the books we've done in the past (and have an area for us to write multi-person reviews of the books).

Having an exception tracker email us when something was broken on the site would have given us a heads up about #80, for example. There are a bunch with free plans on heroku, honeybadger is the one I've had the most recent exposure to:

https://addons.heroku.com/honeybadger

We're currently not getting admin notifications of new talks and users see a 500 page when they submit one. #80 #82

Seeing this running the tests:

[deprecated] I18n.enforce_available_locales will default to true in the future.
If you really want to skip validation of your locale you can set
I18n.enforce_available_locales = false to avoid this message.

Yo no hablo i18n.

Please document type of License for this code.
I have seen other repositories add it to README file or have a separate file.
Thanks.

http://arnklint.com/super-simple-spam-protection-in-rails

As per the Heroku docs (https://devcenter.heroku.com/articles/rails-asset-pipeline), it's not required (though, yes, they state it as the first recommendation for getting the asset pipeline to play nice with their read-only environment).

The real issue here is that it makes for very large, and noisy, commits whenever any of the javascript/css stuff changes. As @phiggins mentions in #15, it's also somewhat unnecessary.

Finally, it's causing unnecessary bloat in the repo -- running (bundle exec) rake assets:precompile only generates new code (making a few modifications), and doesn't clean up the old pre-compiled stuff. This can be avoided by using rake assets:clean, but why add the extra requirement for something that is so specific to the production environment's quirks?

Also, very little causes more git conflicts than messing around with compiled asset code.

April will not be on the first tuesday. How to show that easily?

I got a 500 error when submitting a new talk proposal on this page:

http://www.seattlerb.org/talks

I thought it might be an intermittent error, so I tried re-submitting 2 more times. It was only then that I realized that despite the error page, the talks were being persisted to the DB. So now there are 3 copies of my proposal in your system:

http://www.seattlerb.org/talks/424
http://www.seattlerb.org/talks/425
http://www.seattlerb.org/talks/426

When someone submits a new talk through our talk submission form, admins should get an email about it. The email should contain most of the information in the submission.

This feature will be done when:

• A talk submission queues an email to admins who have opted-in to notifications.
• Bonus points: An admin should be able to opt-in or opt-out of these notifications. This should probably just be a boolean flag that is exposed in the admin panel.

The site is hosted on heroku, and there are a few free email options that can be investigated:

• Sendgrid: https://addons.heroku.com/sendgrid
• Postmark: https://addons.heroku.com/postmark

... and possibly more. The key things we're looking for are simplicity and no cost.

Right now you can't tell if a talk is scheduled or not. It would be nice if each talk summary would state if/when it was scheduled.

Regular maintenance has not been performed to the site. The site is not using an up-to-date version of most of its dependencies.

These things should probably be done:

• Upgrade rails to a more recent version. Upgrading to the latest 3.2 release, then to 4.0 (or 4.1 if released) is probably a good strategy.
• Upgrade ruby to a more recent version. This will probably involve monkeying with the heroku deployment stuff.
• Upgrade other dependencies: gems, twitter bootstrap, etc.

The current process of scheduling talks for the individual meetups is completely external to this website and manual.

This feature will be done when:

• An admin can mark a talk submission as accepted.
• An email is sent to the talk submitter with the acceptance information.
• Bonus points: an admin can associate the talk with an event (this depends on the Event model having been implemented in #31.)

This one is a bit open ended because I'm not sure what form it should take. It could be as simple as a few database columns and an extension to the admin panel, but if you have a better idea please pitch it here.

@phiggins suggested this

Currently the only way to view information about a submitted talk is to look at all of them at seattlerb.org/talks. It would be great if each talk had its own individually linkable page.

This feature will be done when:

• Each submitted talk has its own page. This doesn't need to be fancy, but some nice formatting would be appreciated.
• The talks index page displays a link for each of the individual talks.
• Bonus points: integrate comments through a service such as disqus to allow interaction with the speakers, for the speaker to post followups or slides, etc.
• Bonus points: if #27 is completed before this, include the link in the email sent to admins.

With talks potentially getting more attention in #28, it would be great to have a page like our current /talks page for past talks.

This feature will be done when:

• There is a page on the site I can visit to see past talks.
• A link to the past talks page is visible in relevant locations. Probably just on the talks page is a good start.

It would be handy for implementing new features on the site if we had Events stored in the database. There should be one Event record for each of our monthly events (the hack nights will be handled seperately). For now, an event needs to have a date when it will take place and be associated with Talks.

Our schedule is fairly regular and so this could probably be automated to just have the events created for the next 3 months or so. Optionally, this could just be a function of the admin panel where Events are added manually.

This feature will be done when:

• Events are stored in the database with a date and can be associated with Talks.
• The front page should show the next meetup with the date and any scheduled speakers.
• Bonus points: Add a page showing past events with the date and speakers.

We have a bunch of books available for loan, but they're currently hosted statically on my website. It'd be great if we had a simple lending library.

Right now if someone provides a large description of their talk, everyone else following it gets pushed WAY down. Provide some JS / CSS magic to make this look more reasonable until you want to read the full description. Prolly just want to provide a [more] link and have it go to the talk's detail page, now that we have them.

If I am creating or editing a talk in the admin panel, right now for the Event selection I see this:

This output is particularly unhelpful. It would be awesome if the date the event was scheduled for was listed instead.

We can't upgrade to rails 4 until we do other infrastructure upgrades first (see: #40 and #39).

Once the spam problems are solved in #18, it would be nice to get an email or something when someone submits a talk. Bonus points for adding a column on the admins table so that we could turn if on and off for individuals.

The site currently depends on an old version of rails. It should be upgraded to the latest version of rails 3.2, currently 3.2.17. Unfortunately, we can't upgrade to rails 4 until we do other infrastructure upgrades first (see: #40 and #39).

I'd like to be able to close issues and stuff.

Clarify the two different kinds of "users":

Rename dudes to something better.
Rename users to admins.

In our app/assets/javascripts and app/assets/stylesheets directories we have the bootstrap js and css files checked in to the project. We can just load these from a CDN like http://www.bootstrapcdn.com/ instead.

Make sure to use the same versions we're using now!

Twitter API version revved and our shit is broke.

This depends on getting the app to the cedar stack as described in #39.

Besides just not being the New Hotness, using the Bamboo stack limits us to using ruby 1.8.7 or 1.9.2: https://devcenter.heroku.com/articles/bamboo

Unfortunately it looks like a heroku app owner will have to do this and it sounds like somewhat of a tedious, manual process: https://devcenter.heroku.com/articles/cedar-migration

There seems to be some stuff a non-owner can do though, judging from the migration doc above.