Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move from firebase to API #9

Closed
ammaratef45 opened this issue Mar 20, 2019 · 22 comments
Closed

Move from firebase to API #9

ammaratef45 opened this issue Mar 20, 2019 · 22 comments
Assignees

Comments

@ammaratef45
Copy link
Owner

use this api instead of firebase, that would require migrating a lot of functionality, use puzzles to simplify the work and divide it.

@0crat 0crat removed their assignment Mar 26, 2019
@0crat 0crat added the scope label Mar 26, 2019
@0crat
Copy link
Collaborator

0crat commented Mar 26, 2019

Job #9 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Mar 26, 2019

Bug was reported, see §29: +15 point(s) just awarded to @ammaratef45/z

@0crat
Copy link
Collaborator

0crat commented Mar 26, 2019

@ammaratef45/z everybody who has role DEV is banned at #9; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Mar 31, 2019

@ammaratef45/z everybody who has role DEV is banned at #9; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Apr 5, 2019

@ammaratef45/z everybody who has role DEV is banned at #9; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Apr 10, 2019

@ammaratef45/z everybody who has role DEV is banned at #9; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Apr 14, 2019

The job #9 assigned to @ammaratef45/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented Apr 14, 2019

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @ammaratef45/z

@0crat
Copy link
Collaborator

0crat commented Apr 14, 2019

It is strongly discouraged to assign jobs to their creators, see §19: -15 point(s) just awarded to @ammaratef45/z

@0pdd
Copy link
Collaborator

0pdd commented Apr 16, 2019

@ammaratef45 7 puzzles #45, #46, #47, #48, #49, #50, #51 are still not solved.

@0crat 0crat removed the scope label Apr 16, 2019
@0crat
Copy link
Collaborator

0crat commented Apr 16, 2019

The job #9 is now out of scope

@0crat
Copy link
Collaborator

0crat commented Apr 16, 2019

Order was finished: +30 point(s) just awarded to @ammaratef45/z

ammaratef45 pushed a commit that referenced this issue Apr 26, 2019
ammaratef45 pushed a commit that referenced this issue Apr 26, 2019
ammaratef45 pushed a commit that referenced this issue Apr 26, 2019
ammaratef45 pushed a commit that referenced this issue Apr 26, 2019
@0pdd
Copy link
Collaborator

0pdd commented Apr 27, 2019

@ammaratef45 6 puzzles #45, #47, #48, #49, #50, #51 are still not solved; solved: #46.

@0pdd
Copy link
Collaborator

0pdd commented Apr 27, 2019

@ammaratef45 8 puzzles #45, #47, #48, #49, #50, #59, #60, #61 are still not solved; solved: #46, #51.

@0pdd
Copy link
Collaborator

0pdd commented Apr 30, 2019

@ammaratef45 10 puzzles #45, #47, #49, #50, #59, #60, #61, #69, #70, #71 are still not solved; solved: #46, #48, #51.

@0pdd
Copy link
Collaborator

0pdd commented May 7, 2019

@ammaratef45 9 puzzles #45, #49, #50, #59, #60, #61, #69, #70, #71 are still not solved; solved: #46, #47, #48, #51.

@0pdd
Copy link
Collaborator

0pdd commented May 7, 2019

@ammaratef45 10 puzzles #49, #50, #59, #60, #61, #69, #70, #71, #94, #95 are still not solved; solved: #45, #46, #47, #48, #51.

@0pdd
Copy link
Collaborator

0pdd commented May 7, 2019

@ammaratef45 9 puzzles #50, #59, #60, #61, #69, #70, #71, #94, #95 are still not solved; solved: #45, #46, #47, #48, #49, #51.

@0pdd
Copy link
Collaborator

0pdd commented May 8, 2019

@ammaratef45 9 puzzles #50, #60, #61, #69, #70, #71, #94, #95, #98 are still not solved; solved: #45, #46, #47, #48, #49, #51, #59.

@0pdd
Copy link
Collaborator

0pdd commented May 8, 2019

@ammaratef45 11 puzzles #100, #101, #60, #61, #69, #70, #71, #94, #95, #98, #99 are still not solved; solved: #45, #46, #47, #48, #49, #50, #51, #59.

@0pdd
Copy link
Collaborator

0pdd commented May 13, 2019

@ammaratef45 7 puzzles #104, #105, #70, #94, #95, #98, #99 are still not solved; solved: #100, #101, #45, #46, #47, #48, #49, #50, #51, #59, #60, #61, #69, #71.

@0pdd
Copy link
Collaborator

0pdd commented May 19, 2019

@ammaratef45 6 puzzles #104, #105, #94, #95, #98, #99 are still not solved; solved: #100, #101, #45, #46, #47, #48, #49, #50, #51, #59, #60, #61, #69, #70, #71.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants