New Features - Cucumber -Rspec- Users

[BenRuns]

I'm getting to the point where I'll be diving into the code written with a machete. I switched it over to rspec and added cucumber in the user_accounts branch. I like cucumber because it allows for near plain English description of features. It should be helpful if we want to develop this with non-programmers/designers or makers who want to add feedback. Having a high level scope also keeps me on task.

Here's what I am thinking on the schema. I'm sure it'll evolve to something much more complex. For a functional site, i just want users to be able to search for a space, post and post a project or join a project. Spaces should be able to add tools not on the list and makers will have tools too.. so I think a tool should be a separate model and should be be able to created.

I'm proud of what we did at the hackathon and all the work everyone put into this. But I'm not going to hesitate to delete code and make drastic changes.I will be using git to branch off new features amd please don't hesitate to call me out on a dumb move. There's enough copies around, we've been pretty diligent with using git, and there aren't any users of the site to complain about changes. If it breaks in the process, we'll fi it and if features suck, we'll drop them or make them better.

Ben

Spaces -has_many_users -has_many_tools

Projects - belongs_to_many users

Users - has_many_tools -has_many_skills -has_many_projects

[sealocal]

Sounds reasonable. Code is meant to be changed.

[BenRuns]

Some inspiration for the above https://www.youtube.com/watch?v=Oj4vXMRenFo