Git Product home page Git Product logo

dreams's People

Contributors

aerugo avatar amotenko avatar anikahar avatar basels avatar eladg avatar enoodle avatar jbastide avatar kasperhelweg avatar lioranaginsky-zz avatar nimast avatar orihoch avatar phouri avatar rootux avatar sh0oki avatar youvalkatz avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dreams's Issues

Add 'How can I help' Page

Take all the 'How other burners can join you' fields from different dreams and put them in one page - 'How can you help' -
Allowing people to directly browse what other dreamers need.

The page should contain:

  • Dream name (Link to the dream)
  • What does he look for
  • Dream image

(No need to show dream short description as users will drill into dreams when they see what they need)

Reset password for spark

If spark is enabled we should call the spark endpoint for reset password.
Right now can perhaps just redirect to the spark page of reset password.

Fix the search

Right now if we have a dream called: "My Dream" - and user search for "Dream" - it will NOT found it
it's an easy fix on the filterific side

Search Cop - Ability to search within all fields (30m by elisha time)

Upon 'Add my name' -> show a small dialog

The dialog would say:
"You want to help 'dream name'? Once you will approve we will send him a message with your mail so you can talk together and bring his dreams to the playa.
Yes! send my mail!"
Hebrew:
משהו כמו הודעה שאומרת
רוצה לעזור ל [שם החלום]? ברגע שתאשר, נשלח ל [שם החלום] הודעה עם המייל שלך ותוכלו לדבר ביניכם ולהביא חלומות לפלאייה
כפתור>> [אני מאשר לשלוח את המייל שלי]

Add tags to dream

Tags would allow users to get to dreams the care more for, faster. A later issue will make navigation tag-based (when a user wants to donate his hearts, or join a dream).

  • Tag system will allow admins and guides to add/remove tags from dreams. Tags can be predefined (YAML?) for now.
  • Tags should be translated.
  • All checkbox-based fields should automatically tagged as that (requires-fire, midburn-theme, ...)

Dokku - Add ability for the platform to run on AWS without Heroku

So this is the summary of our Devops needs:

The idea is to move from Heroku to something similar on AWS that support CI - The solution is Dokku - it uses heroku buildpacks so it will feel like home - https://github.com/heroku/heroku-buildpack-ruby

Notice:
A. We don't need a database - We have a postgres db on amazon we need to connect to this database. I will send you the credentials once the container is up.
B. Bonus - Future thought - Add a Checks file to make sure that new containers are really up (http://dokku.viewdocs.io/dokku/deployment/zero-downtime-deploys/#checks-examples).
C.The final URL would be dreams.midburn.org yet for now we can also use stagingdreams.midburn.org (Not set up yet)

I recommend you follow this guide:
https://blog.mebooks.co.nz/setting-up-your-own-paas-using-dokku/

And also read those guides for brevity:
http://www.rubyfleebie.com/how-to-use-dokku-on-digitalocean-and-deploy-rails-applications-like-a-pro/

And the genius Yuval Adam post about it:
http://blog.y3xz.com/blog/2014/01/29/dokku-as-an-heroku-replacement

Let's make it happen!

Add a soft closing of 'disable_open_new_dream'

Right now it disable on client and server side - add another variable
disable_open_new_dream_soft that close only client vs the old disable_open_new_dream which close client and server.
Also make sure that all env var are CAPS - so turn disable_open_new_dream_soft to DISABLE_OPEN_NEW_DREAM_SOFT

Add "safety-approved" indication

A guide/admin should be able to set a dream as 'safety approved'.
This field should include a checkbox and a textbox for comments.

An indication of whether the dream was approved should be visible to the dreamer.

Add more filter options

Currently there is only Updated by which does not seem to work and cannot be changed to any other sorting mechanism.

Suggest that by default the search is random.
Sorting options:

  1. Random
  2. Z->A
  3. A->Z
  4. Most funded
  5. Least funded

Ability to disable editing of some dream fields

Right now we have different section under dream fields - Managing the project, Safety file, etc..
We want to be able to lock those fields for editing (Possibly through env vars) -
We can extend the way 'safety file' var is behaving.

Make sure that guides and admins can still edit those fields even when they are locked
Make sure the lock is being handled front & back.
On the front side - Display the info on edit dream and make sure that users can't edit those.

Allow multiple creators to edit their dream

add permissions so a few users who are given permissoin can edit a dream
limit to types of permissions (i.e. only owner can edit bank account details or the project's name)

Add tax-required fields

For tax reasons, we need the Israeli ID number and address of the artist receiving a grant.
Need to add, for everyone that fills in his bank account details:

  • Address
  • ID number

Knowing from who the donation was made

On the product level - we need to decide if we want to share the information of the user that donated.

Then if yes - allow the user to choose if he wants to stay anonymous.
Then add a new place for the dreamer to know who donated

Add fields for person

Add 2 more boolean fields for person:
Has ticket?
Need early arrival?

Those should not be visible on the first New dream creation - only in the Edit page

Tags navigation

As a user or guide, exploring the system should be based on tags that are related to the dream,
This will allow:

  • Users to get to the dreams they care more for first
  • Guides and admins to filter complicated dreams and handle them first

When navigating to a dream, users should first see a list of tags (UI TBD).
Clicking a tag will show a short list of dreams, meeting it. Sort and default filters shouldn't be changed for now.

Each and every tag should have some properties, allowing creation of automatic web pages about it:

  1. Name
  2. Short description
  3. Longer Description

All properties should be translated to English.

#119 is a prerequisite for this.

Add a checkbox 'Holy fuck! This dream is great. Send my contact details to the dreamer'

Upon 'Donating to dream' Add checkbox that will be checked by default:
English:
'Holy fuck! This dream is great. Send my contact details to the dreamer'

Hebrew:
'הולי פאק! החלום הזה אדירר. שלח את פרטי הקשר שלי לבעל החלום'

The checkbox will be checked by default.
And if the user presses on the donate when it's checked then it will also 'click' on the 'Add my name to dream'

Safety file PDF/Document (deadline: 30/3)

We need to create a document with all dream fields required for safety assessment.
@rootux created an amazing Google Apps Script that does that, need to customize it a bit with the relevant list of questions.

חלקים מתוך תוכנת החלומות שיש להפוך לקובץ:
עדיף לשים את השאלות ואת התשובות אין צורך לשים את ההסברים והפירוט של השאלות
שם חלום (מספיק רק עברית)
סיכום החלום במשפט (מספיק רק עברית)
תיאור מלא של הרעיון
פירוט טכני וניראות - הכל
תיאור פיזי
מידות
כיצד המיצב נראה
חיבור לחשמל - כולל פירוט (כל נושא החשמל)
כיצד יעברו כבלי החשמל
חשמל ביום
הספק המיצב
אופי היצירה - מספיק רק החלק של אינטראקטיביות
הפעלת אש
סאונד
מבקש להישרף
פוטנציאל ביצוע - תוכנית עבודה
תיק בטיחות כל הנושאים והשאלות:
אבקש לצרף את התמונות והשרטוטים שהאמנים העלו
צמ"ה
דגשי בטיחות(הכל) חומרי גלם
רשימת כלי עבודה
ציוד בטיחות
אמצעי מיגון
הרמת מיצב
קיבוע המיצב
אבטחת המיצב
מיגון חלקים נעים
שילוט

Error - When Editing a dream through the admin backend

Open /admin panel.
Click a dream
Edit a dream
Hit Save.

ActiveModel::ForbiddenAttributesError in Admin::CampsController#update
ActiveModel::ForbiddenAttributesError

Extracted source (around line #21):
def sanitize_for_mass_assignment(attributes)
if attributes.respond_to?(:permitted?) && !attributes.permitted?
raise ActiveModel::ForbiddenAttributesError
else
attributes
end

activemodel (4.2.7.1) lib/active_model/forbidden_attributes_protection.rb:21:in `sanitize_for_mass_assignment'

Show important dates on the top of Dream/Edit

Create a new Special Dates table which will hold

  • Date
  • Description

Then show those dates at the top of 'Edit dream' and in the 'Me page' - Show dates in moment format

4 days left to submit a safety file
10 hours left to create new dreams

in the 'Edit dream' page they will be placed at the top of the page (Can be displayed with .alert class)

List of due-dates should be defined in a YAML file and be translatable.

Reused the FAQ page

Add FAQ page info on the hearts - Get information from Tal Shavit.
There is a FAQ page - Reuse it

Add ability to state what is the type of the image

1.Right now the first uploaded image is always displayed as the main image.
Right now add ability to set the image type as 'None' or 'Main Image' (Using db Enums - like person roles)

2.When loading image - set the 'main image' as the image that should be displayed as the background image in all dreams and in dream page

Add safety file comments

We need to do some UX and understand what is the best solution here.

Product thinking:
So we have 2 people roles in the system - The safety file. aka Guide - which will write the initial comments on the safety.
And the Dreamer which will act upon those comments.

What I have in mind - in the Show dream page add another section - Safety File - with all the fields from the safety - it's a new panel that is available only for the dream creator and the guides - The idea is to add a checkbox that can be marked by the guide as 'Passed' and also add a place where the guide can make comments on the 'safety' file - the Idea is that the dreamer can see it and act upon it.

I'm thinking whether the text box should be filled only by the guide or can the Dreamer also enter comments into that box - this may lead to situation where the dreamer 'deletes' the safety file comments which can be dangerous.
Yet otherwise the dreamer will need to announce the crew to recheck the safety sections.
Needs more Research on the Product side.

Integrate users with Midburn profiles

Integration can be done using SSO (if implemented already in profiles.midburn, talk to @alex_motenko on Slack) or by limiting registration to the current list of users defined in the system.

Add point_of_contact to dream

Adding a read-only (visible only to dream-creator/guide/admin but can be edited by guide/admin) field to a dream that will hold the point_of_contact email for the dream from.

Add english dream name and subtitle

Ability to set the dream name for english.
And when a user system lang is english make sure you display the dream name and subtitle in english

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.