IITH / alumni-portal

Alumni portal for IIT Hyderabad
12 stars 11 forks source link

Design and architecture of the Alumni Portal #1

Closed tanmay-gp closed 10 years ago

tanmay-gp commented 10 years ago

Do we already have any design in mind for the Alumni portal/ has anyone given a thought on this? If yes, can we put up a basic flow of the alumni portal? Will this be managed officially by IITH or the students/ alumni will be managing it? Would be happy to hear more updates on the exact status of the portal.

rushiagr commented 10 years ago

@tanmay-gp91 hey, nice to hear from you here :)

We alumni have a plan in mind what we will require in the step one. But implementation is mostly going to come from existing IITH students. Since we came to know that it is the 'midsem' time in IITH, we've not started assigning the tasks. I'll talk with Pramod Rangarajan and let you know the details of what is being decided.

All of the above 'plan' is about 'what' is required. Not 'how' it is going to be done. If you are asking w.r.t. what technologies, we've left it to the student lead (Abhay Gupta) to decide. I would have personally loved to use some Python web framework, and bootstrap-like minimal UI, but as I won't have much time to actually 'code' something here, so I'm not enforcing anything on those guys as of yet :)

gupta-abhay commented 10 years ago

With regards to technology Python web framework (Django) is fine and so is minimal Bootstrap UI. With regards to database, I was thinking of MongoDB. All are welcome to give suggestions.

rushiagr commented 10 years ago

I don't think Mongo is necessary. MySQL should be more than enough to cater to needs of portal. But if the guys who're going to implement are interested in Mongo, I don't see any problem in that either :)

G8XSU commented 10 years ago

Shouldn't we go easy on technology stack and focus on completing it first?

tanmay-gp commented 10 years ago

I think technology stack also plays its part of importance if we are planning to build a software which would go on for years. Changing the technology stack and architecture after some cycles of development won't be a that good thing.

activatedgeek commented 10 years ago

I would agree on MySQL being far more than sufficient for this task.

Regarding the choice of technology stack, I would agree with @G8XSU . This task can easily be designed into certain modules which from an engineering perspective will not hurt in the future when the stack needs to be changed. In essence, no interleaving in any of the components. After all, we anyways need to keep up with the new technology some day or the other.

rushiagr commented 10 years ago

I'm going to post an initial draft of milestone 1 in a day or so, and close this issue then. We can carry the discussion there if required.. Thanks all for the inputs :)

rushiagr commented 10 years ago

Issue #2 posted. Let's carry on the discussion there