We'd love to have your opinion about what features are most important to our community. Please choose the ones that are most important and then drag them into the priority order you think is best. Obviously we can't do everything, so your opinion counts!
The poll is at the bottom - unfortunately you can't understand the poll if you don't read through the feature descriptions, so please take just a few minutes to read through these. When you're doing the poll, select the features that are most important to you and then drag them up or down to rank their importance.
(The official discussion of features is in the leadership forum.
- Responsiveness: We need to be able to use responsiveness to prod members, disable their hosting status, or remove accounts. See Move responsiveness into user object, views, tokens (Estimate: 16 hours)
- Visual redesign of site, mobile-friendly: Website design preferences and standards change over time, and ours is already getting dated. Unfortunately the world is changing around us and although the site was designed for a web browser on a computer, more and more people are using a variety of mobile devices, which don't work well with the current design. Probably the most important reason for a redesign is to make it mobile-friendly, so it's easily viewed on a smaller device. (Estimate: 120 hours)
- Drupal 7 Upgrade Survey and Estimate: To know where we are with a Drupal upgrade and what it may cost, we'll need to prepare a number of user stories to determine what the features are, then review our custom code to see what is going to be required. (Estimate: 80 hours).
- Add info like wifi, birthyear/age, and facebook page to user profile. Our user profile data hasn't been updated in a few years, and several additions have been repeatedly requested. The idea of birth year is just to be able to display age or approximate age. See [misc other items to user profile] (Estimate: 25 hours)(https://github.com/warmshowers/Warmshowers.org/issues/206)
- Add filtering to map and text search: When searching for a host, many guests want to be able to limit what they see in map or text search based on responsiveness, last login, max number of guests possible, etc. (Estimate: 60 hours)
- Traveler profile improvements: Our current profile is based on the original spreadsheet download from before 2005! Most of the items on the profile tell about a host, but provide little prompting about what a host might want to know about a guest. A host probably wants to know about the guest's current trip, perhaps previous trips, style of travel, etc. See Traveler profile with formalized hosting request (Estimate: 40 hours)
- Simplified hosting request: Currently hosting requests are just a free-form private message, and there are lots of problems with them (ambiguity, inadequate information, etc.). If we made a specific "hosting request" then 1) guests could standardize some of their repetitive information, 2) the date would be explicit, 3) hosts could explicitly offer, 4) guests could explicitly accept the offer. (Note that a personal message component would always be required, and only one host could be contacted at a time, as at present). This would open the door to lots of important followups, including tracking how many hosting "events" happen, prompting both parties for feedback, preventing collisions on hosting dates, and showing both guests and hosts what they have arranged. (Estimate: 80 hours)
- Traveler Location tracking: Many hosts want to know where their guests are right now, and many travelers want to be able to find and contact other travelers going their way or who are nearby. This option would require a new map page, improvements to the profile page, HTML5 geolocation options (so that the location could easily be updated using the site) and updates to the mobile apps to let them report traveler location. (All features would be opt-in only, of course). (Estimate: 80 hours)
- Scale back the auto-available feature: A couple of years ago we implemented a feature that required people to say when they'd be back when setting themselves "not available". And... it automatically makes them available again on that date now. This seems to have the unintended consequence of quite a number of members marked "available" who actually aren't. A simple approach to improve this is to remove the automatic changing to "available", but leave the email in place. See issue (Estimate: 10 hours; also requires translation)
- Add message access in-app for apps: Add message access to at least the Android app and possibly the IOS app. (Android estimate: 120 hours)
- Android app visual redesign: The Android app has a dated visual appearance and a bit of an odd UI. See issue with mockups. (Estimate: 120 hours)
- Text Search Improvements: Currently one text box lets you search for fullname, username, email, town/city, but it's a bit of a mess and can be much improved. 1) Separate boxes for user and location name search, 2) Best-effort matching when people provide a state/province/country (which currently just fails).
- Double-blind feedback: We have a system problem where negative or neutral feedback sometimes provokes retaliatory feedback, leading to conflict and problems. It's critical for all members to feel "safe" leaving feedback, so this is an important problem. In double-blind feedback, new feedback is not actually published visibly until the other party has given feedback or a particular time period has passed. Both are notified when the other leaves feedback, but they don't see it right away. This encourages reasonable, non-retaliatory feedback. This feature will require significant community education. (Estimate: 30 hours)
- Required-by-2016 Site Security Upgrade: The version of Drupal on which Warmshowers.org is built will cease to be maintained from a security perspective in early 2016. It also depends on an obsolete version of the PHP language (PHP 5.3) which is hardly supported now and will be completely abandoned in 2017. To resolve this we have to upgrade the site to Drupal 7. Unfortunately, the Drupal project chooses to break APIs freely when doing major releases, so this is a major job, and has not yet been fully estimated. It will almost certainly require a minimum of 400 hours of work. Warmshowers.org is currently running a secure version of Drupal on a server maintained properly with security patches. We just want to make sure we can still say that next year. See issue. (Note that this is not included in the poll, as it's non-negotiable, we just have to figure out how to get it done.)
Results of the 2015 poll: