Projects :has_one hackweek about hackweek

[cornelius]

I would do a many-to-many relationship, so a project can be reused or continue at a later hack week without losing the history.

[hennevogel]

Do you really think this is necessary? What's the use case? If I hacked a project in hack week 9 and want to continue it in hack week 10 I can simply change the hackweek attribute to "10" and be done with it.

[cornelius]

The use case would be to still be able to see, which projects were being worked on at hack week 9. So this list wouldn't change, even if I continue the project at a later hack week.

[hennevogel]

I doubt that anyone want's to see this "overview"...

[cornelius]

I had this use case when organizing the last hack week quite a bit. Finding out what happened at previous hack weeks helps with understanding what to expect, get inspired, and who to poke. As a general principle I think it's a good idea to not throw away data we have. Even if you doubt that anyone wants to see it, never underestimate the creativity of people to find weird use cases. For us it shouldn't be a lot of effort to do a many-to-many relationship instead a one-to-many. That sounds pretty standard.