forked from DrkSephy/git-technetium
/
tasks.txt
277 lines (216 loc) · 11.2 KB
/
tasks.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
#####################################################################################
# Tasks / Road map (August 9th, 2014 ~ Present) #
#####################################################################################
With the initial set of data-gathering tasks finished, it is time to improve them.
The following limitatations exist:
* Github's API only returns 30 datasets at once. The rest can be retrieved by
pagination.
* How do we chain so many requests elegantly?
* We need a way to get ALL of the data for an endpoint to give proper statistics.
* Task "Number of closed issues" needs to be done asynchronously. We need an algorithm
for handling multiple requests on a resource. The current bug is that when trying to
send a request for all issue data, another request gets sent before the first is
done, leading to an error with the headers.
As such, the following tasks are now available:
Multiple Asynchronous Requests: [ Everyone ]
--------------------------------------------
The major goal here is to figure out how to loop over requests for a resource without
encountering the "headers cannot be changed once set" bug. For example, given 50
issues, we would normally like to iterate over each issue, send a request, and
gather the data. Due to the asynchronous behavior of node, multiple requests get sent
before any of them finish, throwing the "headers" error. An algorithm to solve this
is needed.
+ - - Algorithm for sending multiple requests in succession.....................[ X ]
|
+ - Patch up the issues closed task by using the asynchronous algorithm.......[ X ]
|
+ - Update express.js route for handling issues closed data...................[ X ]
Getting all Data for Resource: [ Everyone ]
-------------------------------------------
Once the above task is finished, anyone who completed a task for gathering data has
to go back and update their routes to get ALL data associated with that endpoint.
This way, our results will reflect that of the entire repository, not just a subset
of 30 datasets.
+ - - Update Commits per Contributor route to get all data......................[ X ]
|
+ - - Update Commit Comments per Contributor route to get all data..............[ X ]
|
+ - - Update Issue Comments per Contributor route to get all data...............[ X ]
|
+ - - Update Pull Requests per Contributor route to get all data................[ X ]
|
+ - - Update Lines of Code per Contributor route to get all data................[ X ]
|
+ - - Update Pull Request Comments per Contributor route to get all data........[ X ]
|
+ - - Update Number of Issues Opened per Contributor route to get all data......[ X ]
|
+ - - Update Number of Issues Assigned per Contributor route to get all data....[ X ]
|
+ - - Update Number of Issues Closed per Contributor route to get all data......[ X ]
|
+ - - Update Issues for Repository route to get all issue data..................[ X ]
#####################################################################################
# Tasks / Road map (Project Inception ~ August 9th, 2014) #
#####################################################################################
Project Setup: [ David ]
------------------------
This task involves setting up a basic full stack application.
+ - - Add package.json dependencies............................................[ X ]
|
+ - - Add bower dependencies...................................................[ X ]
|
+ - - Create base server using Express.........................................[ X ]
| |
| + - - Create basic route.................................................[ X ]
|
+ - - Create base AngularJS Application........................................[ X ]
|
+ - - Create base application controller.................................[ X ]
|
+ - - Create basic partials..............................................[ X ]
Commits per Contributor: [ David ]
----------------------------------
This task involves creating a link that the client can click which
in turn will query a repository of their choosing, returning a list
of numbers representing the number of commits that each contributor
within the requested repository has done.
+ - - Create server route for querying number of commits.........................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling commit data on client.......................[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying commit data on client........................[ X ]
Commit Comments Per Contributor: [ David ]
------------------------------------------------
This task involves creating a link that the client can click which
will return a list of the number of comments made on all commits in
the given repository for each contributor.
+ - - Create server route for querying commit comments...........................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling commit comment data on client...............[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying commit comment data on client................[ X ]
Issue Comments Per Contributor: [ Kim ]
-----------------------------------------------
This task involves creating a link that the user can click which will
return a list of the number of comments made on all issues in a given
repository for each contributor.
+ - - Create server route for querying issue comments............................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling issue comment data on client................[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying issue comment data on client.................[ X ]
Pull Requests Per Contributor: [ Kim ]
----------------------------------------------
This task involves creating a link that the user can click which will
return a list of the number of pull requests made for a given repository
for each contributor.
+ - - Create server route for querying pull requests.............................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling pull request data on client.................[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying pull request data on client..................[ X ]
Lines of Code Per Contributor: [ David ]
----------------------------------------------
This task involves creating a link that the user can click which will
return a list of the number of lines of code (addition and deletion)
that each contributor has done for a given repository.
+ - - Create server route for querying lines of code.............................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling lines of code data on client................[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying lines of code data on client.................[ X ]
Comments for Pull Requests Per Contributor: [ Kim ]
-----------------------------------------------------------
This task involves creating a link that the user can click which will
return a list of the number of comments made for all pull requests in
a given repository for all contributors.
+ - - Create server route for querying pull request comments.....................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling pull request comments data on client........[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying pull request comments data on client.........[ X ]
Number of Issues Opened Per Contributor: [ Kevin ]
--------------------------------------------------------
This task involves creating a link that the user can click which will
return a list of the number of issues opened in a repository by each
contributor.
+ - - Create server route for querying issues opened.............................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling issues opened data on client................[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying issues opened data on client.................[ X ]
Number of Issues Assigned Per Contributor: [ Kevin ]
----------------------------------------------------------
This task involves creating a link that the user can click which will
return a list of the number of issues assigned to each contributor in
a given repository.
+ - - Create server route for querying issues assigned...........................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling issues assigned data on client..............[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying issues assigned data on client...............[ X ]
Number of Issues Closed Per Contributor: [ Kevin ]
----------------------------------------------------------
This task involves creating a link that the user can click which will
return a list of the number of issues closed by each contributor in
a given repository.
+ - - Create server route for querying issues closed.............................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling issues closed data on client................[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying issues closed data on client.................[ X ]
Issues For a Repository: [ Kevin ]
----------------------------------------
This task involves creating a link which the user can click that returns
a full list of all issue titles in a given repository.
+ - - Create server route for querying getting issues............................[ X ]
| |
| + - - Parse data before sending to client..................................[ X ]
|
+ - - Create controller for handling issue data on client........................[ X ]
|
+ - - Create factory for getting data on client from server......................[ X ]
|
+ - - Create partial for displaying all issues data on client....................[ X ]
Frontend: [ David ]
-------------------
A beautiful frontend needs to be built. Anyone can take this up at the same time,
we can simply see which design fits this application the best.
+ - - - Put together front-end..................................................[ X ]