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

Migrate from FindBugs to SpotBugs #884

Closed
krzyk opened this issue Apr 28, 2018 · 34 comments
Closed

Migrate from FindBugs to SpotBugs #884

krzyk opened this issue Apr 28, 2018 · 34 comments

Comments

@krzyk
Copy link
Collaborator

krzyk commented Apr 28, 2018

Findbugs project is dead, let's migrate to its successor - SpotBugs

@krzyk
Copy link
Collaborator Author

krzyk commented Apr 28, 2018

@0crat in

@0crat 0crat added the scope label Apr 28, 2018
@0crat
Copy link
Collaborator

0crat commented Apr 28, 2018

@0crat in (here)

@krzyk Job #884 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Apr 28, 2018

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

@0crat
Copy link
Collaborator

0crat commented Apr 28, 2018

@krzyk/z everybody who has role DEV are banned at this job; 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 May 3, 2018

@krzyk/z everybody who has role DEV are banned at this job; 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 May 8, 2018

@krzyk/z everybody who has role DEV are banned at this job; 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 May 14, 2018

@krzyk/z everybody who has role DEV are banned at this job; 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 May 19, 2018

@krzyk/z everybody who has role DEV are banned at #884; 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 May 24, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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 May 29, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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 Jun 3, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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 Jun 8, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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)

@ThrawnCA
Copy link

ThrawnCA commented Nov 6, 2018

@krzyk Um...I'm not exactly sure how this zerocracy is supposed to operate, but is it actually possible for someone to work on this issue, or are they going to be hunted down by a Terminator bot for stepping outside the rules?

@0crat
Copy link
Collaborator

0crat commented Nov 6, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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)

@krzyk
Copy link
Collaborator Author

krzyk commented Nov 7, 2018

@ThrawnCA I (and every architect in project) can assign tasks manually to someone. But in qulice there are no funds so the work will be for free, you can get 30 reputation points if you are registered in zerocracy.

@ThrawnCA
Copy link

ThrawnCA commented Nov 8, 2018

Doesn't manual assignment cost you reputation points, though?

(I'm not registered, no. Interesting system.)

@krzyk
Copy link
Collaborator Author

krzyk commented Nov 8, 2018

@ThrawnCA Yes it does.

@0crat
Copy link
Collaborator

0crat commented Nov 12, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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 Nov 17, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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 Nov 22, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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 Nov 27, 2018

@krzyk/z everybody who has role DEV is banned at #884; 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 Dec 4, 2018

The job #884 assigned to @paulodamaso/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

@ThrawnCA
Copy link

ThrawnCA commented Dec 4, 2018

@paulodamaso If you need any pointers on this, I'm happy to help. The new artifact is com.github.spotbugs:spotbugs, latest version is 3.1.9.

paulodamaso added a commit to paulodamaso/qulice that referenced this issue Dec 5, 2018
paulodamaso added a commit to paulodamaso/qulice that referenced this issue Dec 5, 2018
paulodamaso added a commit to paulodamaso/qulice that referenced this issue Dec 5, 2018
@0pdd
Copy link
Collaborator

0pdd commented Dec 5, 2018

@krzyk the puzzle #959 is still not solved.

@paulodamaso
Copy link
Contributor

@ThrawnCA Thanks for the tip, I implemented the skeleton and tests for SpotBugs checks.

@paulodamaso
Copy link
Contributor

@krzyk Merged, please close

@krzyk
Copy link
Collaborator Author

krzyk commented Dec 5, 2018

@paulodamaso thanks

@krzyk krzyk closed this as completed Dec 5, 2018
@0crat
Copy link
Collaborator

0crat commented Dec 5, 2018

Job was finished in 34 hours, bonus for fast delivery is possible (see §36)

@0crat
Copy link
Collaborator

0crat commented Dec 5, 2018

@ypshenychka/z please review this job completed by @paulodamaso/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat 0crat removed the scope label Dec 5, 2018
@0crat
Copy link
Collaborator

0crat commented Dec 5, 2018

The job #884 is now out of scope

@ypshenychka
Copy link

@0crat quality good

@0crat
Copy link
Collaborator

0crat commented Dec 5, 2018

@0crat quality good (here)

@ypshenychka The project doesn't have enough funds, can't make a payment

@0crat
Copy link
Collaborator

0crat commented Dec 5, 2018

Order was finished, quality is "good": +40 point(s) just awarded to @paulodamaso/z

@0crat
Copy link
Collaborator

0crat commented Dec 5, 2018

Quality review completed: +8 point(s) just awarded to @ypshenychka/z

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

6 participants