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

Make ListEnvelope public #996

Closed
Shryne opened this issue Jan 6, 2019 · 18 comments
Closed

Make ListEnvelope public #996

Shryne opened this issue Jan 6, 2019 · 18 comments

Comments

@Shryne
Copy link

Shryne commented Jan 6, 2019

As the title says, make ListEnvelope public so that I, as a user, can use it. I would prefer that instead of creating my own version of it. Similar classes (like MapEnvelope or CollectionEnvelope) are public so I don't see why ListEnvelope should be different.

@0crat
Copy link
Collaborator

0crat commented Jan 6, 2019

@llorllale/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Jan 6, 2019

@Shryne/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

@llorllale
Copy link
Contributor

@0crat in

@0crat 0crat added the scope label Jan 10, 2019
@0crat
Copy link
Collaborator

0crat commented Jan 10, 2019

@0crat in (here)

@llorllale Job #996 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Jan 10, 2019

@0crat in (here)

@llorllale Thanks for your contribution, @Shryne/z! If you would be a member of the project, you would now earn +15 reputation points, as explained in §29. You can join and apply to it, see §2.

@piotrkot
Copy link

@llorllale Anyone working on it? Can I make a PR?

@piotrkot
Copy link

@llorllale PR #1073 is waiting to be reviewed (and merged).

piotrkot added a commit to piotrkot/cactoos that referenced this issue Mar 5, 2019
@0crat
Copy link
Collaborator

0crat commented Apr 2, 2019

The job #996 assigned to @victornoel/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

@victornoel
Copy link
Collaborator

@0crat wait for #1096 to be merged

@0crat 0crat added the waiting label Apr 6, 2019
@0crat
Copy link
Collaborator

0crat commented Apr 6, 2019

@0crat wait for #1096 to be merged (here)

@victornoel The impediment for #996 was registered successfully by @victornoel/z

@0pdd
Copy link
Collaborator

0pdd commented Apr 21, 2019

@Shryne the puzzle #1109 is still not solved.

@victornoel
Copy link
Collaborator

@Shryne the PR was merged, this issue can be closed now :)

@0crat
Copy link
Collaborator

0crat commented Apr 23, 2019

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

@0crat
Copy link
Collaborator

0crat commented Apr 23, 2019

The job #996 is now out of scope

@sereshqua
Copy link

@0crat quality good

@0crat
Copy link
Collaborator

0crat commented Apr 23, 2019

Quality review completed: +4 point(s) just awarded to @sereshqua/z

@0crat
Copy link
Collaborator

0crat commented Apr 23, 2019

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

@0pdd
Copy link
Collaborator

0pdd commented Jun 7, 2019

@Shryne the only puzzle #1109 is solved here.

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

7 participants