To use Meetup we need to be able to email you. Please click one of the links below to resolve the problem:
Its MongoDB Madness, its a hackathon month. We of course want our UG to win the contest.
Can't wait to see what we can come up with .
Feel free to contact me directly before the meeting or if you wish to start before our next meeting. The Hackathon opens on March 1.
[masked]
it wasn't a hack night it was only a meeting of when we should hold it and for how long. plus to pick the dev teams we were going to break into
March 8
Well last night we only had a single attendee. I guess doing a hackathon around mongo wasn't appealing. It was my idea to 10gen to make it national and then it went international from there. We have a 173 members, I would like us to form some dev teams for the hackathon this month. I can organize the hackathon if you guys and gals are interested, the scope is very broad so Im sure we can do something amazing!! Send me a shout out for next months meeting. What you'd like presented etc. By the way the beer is still cold, but I doubt it will last the weekend :)
March 8
Sorry to hear about the attendance. My mother just came down from LA Thursday, and my plans just got side-tracked.
However, Some questions I would present are:
What could we do about pulling together code in a git or similar repository?
Do we need to be present in the same physical location for the hackathon to take place?
Can we do team communication through IRC or Google Groups?
Finally, what infrastructure (PaaS) would we be using to expose our newly coded application? I was using AppFog for a while, and found it really easy to get up and running with trivial amounts of administrivia.
March 8
I like that idea. Maybe you guys could checkout Drywall and see if it would help.
http://jedireza.github.com/dryw...![]()
March 4
It may seem a bit boring, but a nodejs mongo backed CMS with a caching document renderer (placing rendered documents, or portions of in mongo as well). Purely utilitarian, but should be doable in a limited time frame.
Given the time frame, in the above example, would be best if we could divide/conquer a division of tasks into sections...
- front-end(design) for articles/documents
- back-end(express) (account/backend/articles)
- caching renderer module, options for expiration rules on different paths... options to clear stale document paths (ex: paged results when a new document is added)
- data model (backend) (support for tags/groups, and related indexes)
Then the questions come in as to the front end... ooh/ahh factors.
- client-side routing
- shared rendering (initial render server-side)
February 26
Join or login to comment.