rcemmett edited this page Dec 3, 2012 · 14 revisions

Welcome to the 403-kamal wiki!

To view our documents please click on the pages tab and follow the links.

Week of October 1st:

What we said we were going to do this week:

  • It was the first week together in a group so we had not had an opportunity to come up a plan for last week

What we did this week:

  • Made decisions on what technologies we were going to use like Django, Postgres SQL, and html/css/javascript
  • Did research into the specific APIs that we will be using when interacting with users’ social media pages.
  • Created mock ups for our web page and did a lot of design for our UI
  • Experimented with the technologies that we will be using

What we’re going to do next week:

  • Toby: Django, project serving

  • Ryan: Django, postgres

  • Hampton: Facebook API

  • Kevin: Twitter API

  • Brandon: Google+ API

  • Meg: javascript, frontend/backend protocol

  • Chee Wei: InstaFeed log-in Credentials

  • Research Twitter Bootstrap as an option(?)

  • Figure out repository structure and push to repository

Issues:

  • There weren’t really issues with getting our tasks done as they mostly involved research and experimentation

Week of October 8th:

What we said we were going to do this week:

  • Toby: Django, project serving

  • Ryan: Django, postgres

  • Hampton: Facebook API

  • Kevin: Twitter API

  • Brandon: Google+ API

  • Meg: javascript, frontend/backend protocol

  • Chee Wei: InstaFeed log-in Credentials

  • Research Twitter Bootstrap as an option(?)

  • Figure out repository structure and push to repository

What we did this week:

This week we were all able to get our technology stack setup on all of our personal dev machines. We explored all of the APIs for the social media websites that we need to interact with and even found a couple of libraries that we will use for these APIs. We also made the decision to host our website on Heroku so we downloaded their toolkit and uploaded a simple app to see how the process worked. Finally we put the framework for our app on github so that we could all start with the same base files.

What we’re going to do next week:

Now that we have all of our technology decisions made we plan on getting a simple home page on Heroku that can interact with all of the APIs We plan on experimenting with different protocols between our front end and back end Finally we will do more experimentation with the Django libraries to see how it will interact with our front end.

Issues:

One of the main issues that we ran into was setting up PostgreSQL and psycopg2. For some reason psycopg2 ran into a lot of dependency issues and wouldn’t install properly at first. Another issue that we experienced was how we would interact with our individual installations of PostgresSQL since our passwords and user names have to be stored in settings.py

Week of October 15th:

What we said we were going to do this week:

Now that we have all of our technology decisions made we plan on getting a simple home page on Heroku that can interact with all of the APIs We plan on experimenting with different protocols between our front end and back end Finally we will do more experimentation with the Django libraries to see how it will interact with our front end.

What we did this week:

This week we were able to get a simple front page and login page working from a local host. We were able to do a little bit of work with heroku, getting our app set up so that it could easily be hosted by heroku We integrated a couple of the API scripts that we were experimenting with into our code base We were able to explore a lot of the capabilities that Django provided for us like user login and account information protection/storage

What we’re going to do next week:

Next week we will begin working towards our preliminary feature set We plan on getting our app deployed to heroku so that it can be viewed from any computer and not just our dev machines We will get our first social media feeds up and running in their most simple form

Issues:

We ran into a little trouble in understanding how apps worked in projects for the Django framework but we were able to figure out their role and how they should work with the management python modules.

Week of October 22th:

What we said we were going to do this week:

Next week we will begin working towards our preliminary feature set We plan on getting our app deployed to heroku so that it can be viewed from any computer and not just our dev machines We will get our first social media feeds up and running in their most simple form

What we did this week:

This week we were able to work out how we were going to log people into their social media sites, store this information, and then use that to gather information on their behalf We also worked towards getting our database models set up and working with the user login framework that django provides. Our app is now deployed on heroku though it does not have most of the features that we want for our first release so it is more like a placeholder.

What we’re going to do next week:

Next week we hope to have the ability to sign users up for our site. We will also have a functional framework for getting users twitter/facebook tokens, storing them, and then using them to gather posts. We want to be able to see facebook/twitter posts on our feed page though they may not be formatted in a very good way.

Issues:

The biggest issue that we have run into so far is what our front end is responsible for and what our back is responsible for. We know that we need to do a lot of communication between the two ends but there has been a couple of times, like with twitter authentication, that it has become ambiguous on who will do what.

Week of October 29th:

What we said we were going to do this week:

Next week we hope to have the ability to sign users up for our site. We will also have a functional framework for getting users twitter/facebook tokens, storing them, and then using them to gather posts. We want to be able to see facebook/twitter posts on our feed page though they may not be formatted in a very good way.

What we did this week:

This week we added the functionality for users to sign into our site. We can now have users attach their social media accounts to our site and store their tokens in our database so that we can pull/post from their feeds We have the ability to post to users social media pages and pull their data so that it can be displayed on our feed

What we’re going to do next week:

Next week we will spend time refining much of the functionality that we have now so that it works with fewer glitches Start integrating google+ into our app so that it will be at least close to ready for our next release Continue working on all other features that we wish to have finished by our next release Issues:

Our largest issue that we dealt with was the callback url that facebook was giving us and pretty much facebook in general. It breaks many of the conventions that have been established for http requests which made it very difficult to parse the access token.

Week of November 5th:

What we said we were going to do this week:

Next week we will spend time refining much of the functionality that we have now so that it works with fewer glitches Start integrating google+ into our app so that it will be at least close to ready for our next release Continue working on all other features that we wish to have finished by our next release

What we did this week:

We were able to fix some of the bugs that we had regarding facebook and twitter so that they are now more stable. We have started working with google+ and getting feed information from them Continued working on features that make our site better looking and more functional

What we’re going to do next week:

Work on getting google+ feed on our feed page Find a way to notify users that we cannot post to google+ or perhaps redirect them to google+ Work on a FAQ page and password recovery

Issues:

Learned that we cannot post to google+ through their APIs because they do not support it for some reason. There are some hacks and workarounds but figured that it wouldn’t be worth the time to implement them.

Week of November 12th:

What we said we were going to do this week:

Work on getting google+ feed on our feed page Find a way to notify users that we cannot post to google+ or perhaps redirect them to google+ Work on a FAQ page and password recovery

What we did this week:

We were able to get a google+ feed on our feed page. We added a warning to our post message, letting the user know that we currently do not support posts to google plus. Our FAQ page has been completed. It is pretty minimal at the moment because our site is still in progress. We have worked on password recovery and logout functionality, which will hopefully be done by the time we release tomorrow.

What we’re going to do next week:

Next week will be a pretty slow week considering that it will be the Thanksgiving holiday, but we hope to at least start on some of our release three features so that we do not have a ton of work to catch up on when we get back.

Issues:

The only large issue that we dealt with this week was that our site when down on heroku for a little while. We found out later that it was due to some changes that we had made in logging functionality that didn’t work on the heroku end.

Week of November 19th:

What we said we were going to do this week:

Next week will be a pretty slow week considering that it will be the Thanksgiving holiday, but we hope to at least start on some of our release three features so that we do not have a ton of work to catch up on when we get back.

What we did this week:

Started working on some of the cron jobs that we wanted to do for scheduling and working on some bug fixes from last release

What we’re going to do next week:

Make significant progress on scheduled updates Work on getting fb likes and comments working Get retweets working

Issues:

The only real issue that we ran into this week was the lack of time due to the holiday weekend

Week of November 26th:

What we said we were going to do this week:

Make significant progress on scheduled updates Work on getting fb likes and comments working Get retweets working

What we did this week:

We were able to get support for facebook likes and comments working properly along with support for retweets for Twitter The scheduled updates feature is almost done but we still need to work out a few bugs on the backend Continued to test and close bugs

What we’re going to do next week:

Since it is our last week we will finish up work on scheduled updates and then simply close bugs and make sure all our features are working properly

Issues:

For some reason creating a datetime object works perfectly fine in the command line interface for python but when we try to make one in our views it is failing. We are continuing to debug this issue.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.