search

ColoradoSchoolOfMines / mozzarella

Mozzarella is a web application made to help student computing clubs better collaborate and organize their projects, presentations, and even mailing list messages.
https://acm.mines.edu
GNU General Public License v3.0
7 stars 3 forks source link

Add a project listing page #13

Closed sumnerevans closed 6 years ago

sumnerevans commented 7 years ago

Maybe this can become part of Show and Tell.

TODO

jackrosenthal commented 7 years ago

If it needs database associations with things like Show & Tell project, then this might be a worthwhile feature. Otherwise, I think we could just list projects on the Wiki I proposed.

sumnerevans commented 7 years ago

My idea was that we would create this project listing page as a base to start integrating Show & Tell from.

jackrosenthal commented 7 years ago

Yes, in that case good idea.

sumnerevans commented 7 years ago

@bjessing suggested a design for this in #15.

sumnerevans commented 6 years ago

When Sam, Daichi and I made Show and Tell, we had a concept of Teams. I'm not sure that that is necessary though, I honestly think we can just have a list of people associated with each project.

Thoughts @jackrosenthal, @samsartor?

jackrosenthal commented 6 years ago

Fundamentally, isn't a team just a M:N xref between users and projects anyway? The way I see it is that there are equivalent ways to write this, one of them just names that xref a "team".

sumnerevans commented 6 years ago

Good point. One twist is that Team is M:N for users, but not projects (you can only have one team working on a project). The way we modeled it in Show and Tell was Person--M:N--Team--A:1--Project.

My opinion (and what I'm going to go ahead with for now, pending objections): No Team model, just have an M:N xref called "team".

Notes on this reasoning: I think that the fundamental question here is whether or not the concept of "Team" as a database model is useful to us.

I honestly think that the argument against is stronger. I don't know many named teams which have done more than one project. I also don't see a point in forcing people to make a Team when they were the only ones on the project.

Additionally converting the xref table to a Team model will be pretty trivial if we ever want to do so later.

jackrosenthal commented 6 years ago

The argument for a Team model is that there are some teams which stick together on a few projects and have a name (i.e. Sam, Robbie, and myself--Dream Team).

ACM projects are open to anyone, not an exclusive team. Therefore, I don't think this model is what we want.