-
Notifications
You must be signed in to change notification settings - Fork 59
D> RChain Development for Bounties: VM primitives, CI integration #176
Comments
Please advise which ticket you wish to work on, and your Discord handle will be added to the ticket - so no one else will work on the ticket. |
Wow,
You're fast as light. I didn't even finish my intro email to you ;-)
…--
Cheers,
HJ
On Fri, Nov 17, 2017 at 11:26 PM, MParlikar ***@***.***> wrote:
Please advise which ticket you wish to work on, and your Discord handle
will be added to the ticket - so no one else will work on the ticket.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#176 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0x9-nBD0yThAl0rNsBbcWyljOdoeRFks5s3ggegaJpZM4QisjR>
.
|
I spent a little time orienting myself to work on ROS-271 but eventually discovered @KentShikama has done the bulk of it: PR 52 For reference: https://travis-ci.org/rchain/rchain build logs |
After discussion with @KentShikama, I put some more time in: rchain/rchain#54 time log: about 3 or 4 hrs tonight. |
Here is the wiki page for the Bounty tickets: |
@rchain-travis are you the same person as @travismorehead ?? |
No, it's the build system. https://travis-ci.org/ |
the build system made #176 (comment) ??? |
Oh, was Medha while logged into that account by accident. |
It was my bad. I was logged in there and didn't realize it until after I
made the comment.
…On Mon, Dec 4, 2017 at 8:31 AM, Mike Stay ***@***.***> wrote:
Oh, must have been Alex or Medha while logged into that account.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#176 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADcF_YUVfDhEKJ5qv7DZAIE-BrxCw9cEks5s9B5egaJpZM4QisjR>
.
|
@dckc how does it go please, want to see what contributions I can make to help resolve this issue |
@MParlikar please would likewise want to know how to engage and be assigned to a ROS please . |
@BelovedAquila which of the Jira bounties most interests you? Before you start making any changes, have you checked out the code and gotten the tests running in your development environment? |
@dckc no I haven't how do I do that |
@BelovedAquila this issue is about collaborative software development in scala (or perhaps C++). Do you have experience with that? I can't tell from your github profile whether you do. You check out the code like any other github project; see Propose changes to someone else's project. Then use sbt test in any of the subprojects under https://github.com/rchain/rchain. |
@BelovedAquila Select a ROS ticket from the list of bounty tickets and advise in Discord (DM) or you may advise here. I will assign a label to your username (hopefully your Git and Discord handles are the same) on the ticket, so others will see that you are on it. You can also look at ROS-197, which was recently completed by a member also. |
ROS-243 completed by @AbnerZheng, ROS-197 completed by @AbnerZheng. RHOL-44 and RHOL-45 in flight with @AbnerZheng. |
@dckc worked on Compiler-Web stuff |
@lapin7 let's keep this issue focussed on VM primitives, CI integration and use #185 for Compiler-Web stuff. I created #255 for the example contracts (RHOL-44, RHOL-45). @AbnerZheng 's work on VM primitives is in scope here:
Next I'll add numbers in the budget / reward spreadsheet... |
Just a short comment to become a participant on this issue. Aha |
@lapin7 @dckc @MParlikar |
Yes, $640 is good.
There was a large budget left over from previous months at the time I
entered what I did.
…On Feb 1, 2018 1:29 AM, "Abner Zheng" ***@***.***> wrote:
@lapin7 <https://github.com/lapin7> @dckc <https://github.com/dckc>
@MParlikar <https://github.com/mparlikar>
There must be something wrong for the budget and reward for this issue.
@dckc <https://github.com/dckc> vote 640$ for this issue, I guess he must
want apply all budget for work done for this month, because if the total
budget for this issue is 640$, and then the percentage of my work is 5%,
then my reward is 32$. So I vote 25000$ for this budget so that, my reward
is about 16*40 = 640$.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#176 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAJNyojizY8Wxe8W_vj04XPgV8Q2a2_rks5tQWfbgaJpZM4QisjR>
.
|
@MParlikar I'm inclined to see the big spreadsheet as a useful prototype and retire it. See #260 for a next prototype. |
@lapin7 The reward for my work is right. Thanks. |
I have made a PR for ROS-247 and ROS-314. @lapin7 @MParlikar Please assign someone to review it, thank you. |
Soon I will produce a total list of payments per person.
Before actual payments start, I can receive feedback and make adjustments
if it's needed.
The attention for the payment system has increased enormously. :-)
And I'm happy to improve the system with all your insights and suggestions.
…--
Cheers,
HJ
On Fri, Feb 2, 2018 at 9:52 AM, Dan Connolly ***@***.***> wrote:
@lapin7 <https://github.com/lapin7> in the scope of this ticket, my only
contributions in January were coordination, onboarding, and guiding.
My coding work was mostly in #185
<#185>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#176 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0x9-rJ3NQXJzQv_XrUCNo14tZ2RfR0ks5tQsy7gaJpZM4QisjR>
.
|
After i rebased dev branch, there was something wrong with this pull-request rchain/rchain#218. So i made a new pull-request here. rchain/rchain#296 |
Medha is making new issues for more recent contributions to the core development work. |
Jira Bounties
The work on these issues requires that the community engage with the core development team. @dckc has experience with this engagement. So you can ask him how that goes.
Please, ask @MParlikar how to engage and how to become assigned to a ROS.
Please put regular comments hereunder, so that it's visible for the other members that you're working.
The text was updated successfully, but these errors were encountered: