The specs are running slow, I feel that will a little work we could speed the specs up considerably.

I'm personally gonna see if there is anywhere we can remove rails out of the specs. That should help get us a little bump in speed.

With queried email, pre-populate email for the iframe for organizations.

searching for a query and serial will limit exact serial matches, but the list of close serials is not pruned by query.

The current todo list for internationalization has various things that need to happen, but they aren't issues, and they aren't set up in a way that makes them easy to address.

We need defined and prioritized code updates for this.

When installing on a Digital Ocean droplet I found that it wouldn't install on a 512mb droplet giving errors like "Cannot allocate memory". Upgrading to 1gb resolved the issue.

Might be worth noting under Dependencies.

People get bikes sent to other emails and want some way to deal with that.

Trying out the search on the new page, and I get a popup saying "you have unsaved changes! are you sure you want to leave this page?"

Very confusing, given that I'm just trying to search, not update/save anything.

Hi,

I like the idea of the bikeindex, but I wish there was functionnality to search on numerous "local" sites of the bikeindex. Having a P2P or federated search would enable less centralisation and empower local communities to install their own hosted version of bikeindex.

If you update the bike but don't save, and try to leave it should tell you.

On the edit page, there's an option for an internal front cog (the only component I know of that this would fit is the Patterson), but no option for an internally geared rear hub (much more common).

Take you to admin/organizations index with error message that the organization doesn't exist.

LOW priority!

Right now we are using a random string, users have requested the ability to set their own vanity url.

I'd love this use this in Mexico.

It would be nice to use devise

The nuVinci line of hubs utilize continuously variable gearing (there is no discrete number of gears). The current UI won't allow for internal gearing to be noted without specifying a number of gears.

When I create a bike for myself using an account with no name filled in in the profile it sends me an email with no name at all, rather than defaulting to my email address as it should.

If you look in app/assets/javascripts/views/bikes/bikes_show.js.coffee you see the beginning of the move to make switching between images possible through keyboard.

It would be cool to be able to press right arrow and zoom in on the next image.

After enabling email changes (#22), we need to add the ability to manage multiple email accounts and merge together accounts.

Bike Index would create a widget for every user that they can embed on their blog that showcases their bikes. It would also say, "I’ve registered my bike on Bike Index so people can quickly find out if someone steals it. Have you?"

If someone has more than one bike, it has a slideshow of all of them.

Joseph (owner of Flyingpigeon) says:

I am having some trouble using Firefox on my Mac to register bikes - the CM/IN button doesn't drop down using this browser. Adding components also doesn't work using that browser on my computer(s). Chrome seems to handle those options with ease.

Getting Deprecated warnings when running specs.

[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.

Stolen Bike owners often want the ability to create fliers. We ought to make this easier for them.

Requirements for the PDF

• Always fits on a single page.
• It displays at least one picture of the bike (if the bike has one).
• It displays any named attributes that a bike has (model, year, frame material, etc.), only if they have been input.
• It displays as many components as it can (without going over the page limit).
• Shows the bike's url (preferably as a link, in case the pdf is sent digitally).
• Shows the bike's QR Code.
• The Bike Index logo is somewhere on the page.
• It prints nicely in B&W.
• It clearly highlights the fact that the bike is stolen and shows all stolen information if the bike is stolen.
• It opens the PDF in a new window.
• Only stolen bikes can generate pdfs.
• Anyone can view the PDF (not exclusively the bike owner).

I created my Bike Index account with my Facebook account, which has a Facebook-specific e-mail address. That's not the e-mail address that someone should contact me at if they find my bike stolen.

If I change the e-mail address of my listing, it presumes I've sold my bike and want to give it to another user. (This is a bad presumption, and these side-effects should be communicated more clearly in the UI.)

There's no way to change the e-mail address associated with my account (and my bikes) in the Preferences section, and there should be.

It would be great if the API response included the bike frame size. I'm working on a used bike marketplace webapp for bikes that have been registered on BikeIndex and would like to make the listings searchable by size.

Browsing is encrypted with HTTPS, but logging in isn't because forwarding to HTTPS isn't enforced on the homepage.

However, once I logout, the logout page is HTTPS and thus the login form is.

At the time of a user's attempt to register a bike, the user might only know the manufacturer and color of his or her bike (e.g., a black IRO). The user might not a) know offhand the bike's serial number or rear wheel size or b) be close enough to the bike to check or confirm this information. This user cannot add the bike to the index.

Allow users to add bikes with only manufacturer and color, without requiring the serial number or rear wheel size. Allow users to return to a bike's record to add this information when they have it available.

If a user is logged-in and goes to bikeindex.org, the first page he sees should be the listing of his bikes.

Part of the internationalization, but also just to not be stupid: http://astrails.com/blog/2013/8/6/stop-using-strftime

We've got some of the date formats in our localization file, but not enough of them.

Right now we are just searching for colors in the attribute box.

It would be awesome to add in more searchable items there, like handlebar type, wheel size and stuff

Attribute on bike that grabs all the attributes other than year, manufacturer and model (such as the description and components) and formats them for display.

Could be stored as an array so that we can run .to_sentence on it, or could just be a string.

We will need to truncate it, so putting the most important information first would be good.

Make the spokecard a printable PDF.

We need our own commenting system.

Requirements

• It should email messages to users when someone comments on their bike.
• It should allow threading
• It should load via an AJAX call, so that things can still be cached.
• Users should be able to turn off comments on their bike.

It might be less confusing if there was logic that changes the ownership email if it's being created by owner. The new email would say thank you rather than informing the owner who added the bike for them, and it would not imply that claiming the bike was necessary or possible (as it's claimed as soon as it's created in your own account).

If the user edits a bike and clicks "Save", the entry should be displayed in the "view" state, so he can proofread it in the same format that a passerby would read it in.

In the future, the view state and edit state could collapse into a single view, where only the owner has permission to make changes, but the information is displayed in the same fashion to both the owner and a passerby.

Someone made a request!

https://bikeindex.org/news/pdf-registration-certificates#comment-1708242411

Let's add created at to the PDF.

For the following page (https://bikeindex.org/stolen_bikes) in Safari, the footer and left column ("Contact" in particular") overlap. I'm guessing it's due to the smaller amount of content on this page.

The user can insert arbitrary HTML and Javascript into the 'personal text' section of the website.

This means that a malicious attacker can insert code causing of other logged in user to perform arbitrary action, including transferring bikes, changing passwords, etc.

Right now, uploading images blocks things (especially for mobile devices).

Perhaps we could show the the image is uploaded, then throw the processing in a background job and not worry about when it finishes.

We used to have an image uploader on the new bike registration page - but on mobile devices it would take 1 or 2 minutes to do, and sometimes it would fail and everything would be lost. It would be great to have an image uploader on the new bike registration page, and not have it suck.

By adding strong params now it will make the impending upgrade to rails 4 that much easier.

Found a small rails project you can work on @adherr!

We're using Chart.js to make some charts. I think a chart of the count of bikes that have been made each day in the past week would be good. For now let's put it in the admin section.

Some information about what we're looking for is in the view and the controller review method (also viewable on the Index as an Admin)

Make it. Contact me with questions.

There should be a top-level button on every page that takes the user to his bikes list (or to his bike's individual page if he has only one bike). "See your bike" (or "bikes", if the user has more than one) should be sufficient.

As it is now, it isn't super obvious that the user needs to click his truncated e-mail address to open a menu to find the "Your bikes" button.

It is common for the fork to be manufactured by a different company than the frame. If these components are both listed in the same section, there should be fields for the fork's make, model, color, year, and serial.

You should be able to browse and search by areas for stolen bikes.

Getting deprecated warning when running specs.

Digest::Digest is deprecated; use Digest

The component fields should be in their proper boxes - so hubs should be in the wheels box, fork and rear suspension in the frame and fork box and so on.

The site has a nicely contemporary visual design, but the placement of items on it feels haphazard.

For instance, on /user_home, the whole point of the page is to see my bikes, but they don't start to appear until the bottom fifth of the page. I didn't even see the "info about your lock" section until just now, because it's way below the fold (and below the things I'm looking for on that page).

Most of every page is taken up by a search bar (which despite being huge doesn't feel obvious) and a user menu (which likewise isn't super apparent unless you're actively looking for it).

For a free resource, it's in many ways good enough (and way better than any other bike registries I've seen), but the page layout could probably use some more consideration.

If I have some time later, maybe I can put together some mocks to show you what I mean.

To make it easier for people to verify bikes in the wild, we should have a short URL that's easy to type on a phone (and generates simpler QR codes). I've noticed that mybik.es is available.

We could set up a service that redirects http://mybik.es/12345 to http://www.bikeindex.org/bikes/12345

Notice the difference in QR complexity between the current URL and a shortened one.

@sethherr what do you think? Worth spending $10 of that Kickstarter bounty on?

Error messages disappear to quickly for people to read! They need to be more obvious, and be manually closed.

Most casual cyclists won't know want "seat tube length" means, but might be able to tell you they have a 20" or a 56cm bike. A better title for this field would be "size (seat tube length)."

It's also worth considering having an option for ordinal sizes like "S, M, L, XL." The goal of the form is to get as much information as possible from a user, which means it should match the cyclist's mental model as closely as possible.