Status Report #1 Twitter API

Date: 28.05.2018

1.1 ApiDesign folder is created in our repository as a container for our practice application.
1.2 Almost all members directly contribute to the project.
1.3 The team tried to utilize Pull Requests in the development process
1.4 All Pull Requests were reviewed by at least one other team member
1.5 Twitter API is used to fetch some content with GET requests
1.6 Some content is created based on the Twitter API responses and used in our API
1.7 A RESTful API is created.
1.8 A frontend web site is developed with Angular Framework
1.9 Postman and frontend web site is used for testing the API endpoints.
1.10 Amazon Elastic Beanstalk is used for deployment. The link is put into the wiki page.

2.1. The team members utilized GitHub for the first time with branches and pull requests for a real project.
2.2 The notion of API is discovered
2.3 A modular design is conceptualized making the team work on the same project at the same time.
2.4 Some real up and running application is created at the end.

3.1. There were a number of things new, which should be learned.
3.2. Understanding the notion of API and the nature of GET and POST requests talking with Twitter API.
3.3. Due to asynchronous environment of Node, we had difficulties with understanding callback functions.
3.4. Testing was difficult in general. One reason can be shown as 3.2. On the other hand, we needed extra tools like Postman for checking whether our API endpoints give correct responses.
3.5 Helping each other was another challenge. We had to communicate well to deal with some problems

4.1. We did not plan the output of the project with some goals. We should have defined what is expected at the end of the project so that we can cooperate better.

5.1. Oğuz Kaan Yüksel : Prepared the main infrastructure of the code, the routing mechanism, controller-module structure.
5.2. Galip Ümit Yolcu : Account module. Endpoints to get or set the description of the account, endpoint for changing the URL associated with the account in bio part.
5.3. Kemal Tulum : Code review for all endpoints, GET api/twitter/tweets and POST api/twitter/media/upload endpoints. Also, the front end written with Angular
5.4. Serkan Özel: Learning node.js and javascript. Retweet module. Given a tweet id, actopus account will retweet that tweet.
5.5. Nazmican Çalık: Trends Module. Created an endpoint for fetching given country's trending topics. Since twitter doesn't accept country name in its apis, 2 api calls are chained to get the result.(Country woeid)
5.6. Didem Öngü: GET api/twitter/followers?screen_name=screenName endpoint
5.7. Yusuf Kalaycı: POST api/twitter/tweetWithMedia endpoint
5.8. Özgür Akaoğlu: POST api/twitter/modules/postTweet: an endpoint which enables tweeting directly from our webpage. Some texts are tweeted in order to test of the endpoint. GET /api/twitter/home endpoint which gets tweets residing in our home page. If a number is provided, that number of tweets are returned.
5.9. Gökhan Tekel: GET /api/twitter/geo/search endpoint

Provide feedback