The Pivotal Tracker is what we use to manage development tasks for the project. We like it because it's extremely simple to use and most of the team has previous experience working with it. It might be useful to look over the terminology to get familiar with the things you'll encounter, and I think it's helpful to understand this workflow overview to see how stories are handled from start to finish.
Ari Paul is not directly involved with the project. Are you sure you're not thinking of @AriJuels? Regardless, that's his opinion. You can follow our project tracker and get a sense of our progress. We're just going to keep on pushing code like we normally would.
There is no roadmap. Chainlink is building something brand new and exceedingly complex that needs to work more or less perfectly (and absolutely perfectly in terms of security) from the outset. Setting specific dates or benchmarks is just a way to apply unnecessary pressures that would risk causing mistakes.
What the team recommends is that you watch Chainlink's open source codebase as it develops through;
their Github: https://github.com/smartcontractkit/chainlink
and their pivotal: https://www.pivotaltracker.com/n/projects/2129823
All we know beyond that is that some aspects of the core code are currently undergoing a security audit, and that development of the Epics is well on its way, although it would be reckless to try and speculate about particular dates or timelines.
Apart from that, the closest you will get to a visual Chainlink roadmap is this.
Hi /u/NoForcer! We don't have a release date for main net, but we did open up our project tracker and Github so that the community can see our development progress as it happens.
> When it comes to software development, committing to exact dates is a fool's errand.
Use an open tracking system and let us watch the stories in progress. A tool like Pivotal Tracker (I work at Pivotal Labs, Tracker is amaaaazzzinnng) will give followers a pretty good idea of what's going on and what's coming up.
For example, we're the main contributors to the Cloud Foundry project. The whole of Cloud Foundry runs through public Tracker projects, anyone can see what's going on in any team at any time.
Right now I can see that the buildpacks team is working towards a release marker for self-built binaries, which on the current backlog will land next week.
I can see that the Diego team are working towards having all long-running process access happening through an API server, which is automatically estimated to land later this month.
Nobody makes a guess. This is all derived from actual hard data.
The pivotal tracker says the next thing on the list is 'deploy oracle contract to testnet'. If we assume it's the deadline is correct, it should be out by tomorrow.
Check the rust pivotal tracker: https://www.pivotaltracker.com/n/projects/1371850
"Pillars should block wall placement"
I'm pretty sure soon they'll be blocking the ability of placing a wall between pillars, as that's not what pillars are meant for..
Pillars are only meant to be used as a support to hold a roof/ceiling in place stronger. If a wall is already in place why would you possibly need a pillar in there too? That makes no sense.
Trello Rust Account was shut down due to millions of comments and trolling. It turned to shit as garry said.
I consider the mind map complete i dont think there really needs to be any more done to it unless they intend to do things different from what has been posted there.
They do have a new site that indicates their progress towards ideas etc.
Except for the secret stuff.
You looked at the old Ruby version. With even the most basic of research you could have avoided this embarrassing situation.
Github: https://github.com/smartcontractkit/chainlink
Pivotal Tracker: https://www.pivotaltracker.com/n/projects/2129823
I know exactly what their response would be...... "You can follow progress at Pivotal tracker"
We don't have a set date, but keep an eye on our PRs and project tracker for indicators of where we're at.
You can actually see the progress made in the pivotaltracker, but I doubt you'd know what to make of it https://www.pivotaltracker.com/n/projects/2124891
Mainnet release candidate is set for the end of July, and you can watch the team progressing with each task along the way. That will basically be a ready mainnet, though it will probably undergo some auditing and probably public testing. Nobody wants an EOS like code being pushed into use with huge issues in it.
You can follow ChainLink's progress here: https://www.pivotaltracker.com/n/projects/2129823
It looks like the testnet will be coming next month.
Also on their GitHub: https://github.com/smartcontractkit/chainlink
The ethereum address is logged when the node starts, and you can also run chainlink a
from the container's command line after logging in. We have a story here to make that easier by adding the address to the GUI. The node will only create a new address if there is no keystore file present in the $ROOT/keys
directory. Otherwise, it will use the password supplied to unlock the existing present file.
Ctrl + c
is fine if you're already viewing the active container. docker kill container_name
works the same as well. They will both gracefully stop the node.
Yes, exactly. Since every task of a run is persisted in the database, the secondary node will pick up where the primary left off. What it doesn't help for, though, is if your ethereum client goes down or stops functioning.
There is a to-do item here to be smarter about converting oz vs. fl oz by looking at the keywords in a message.
Any more keyword you can think of?
Pivotal wrote a nice blog post about using Elm in production for a new dashboard in one of their products. It's a short read, but if you're lazy: > To sum it up, our manager has mandated that all new code be written in Elm.
A crucial ingredient to make this really useful is still missing: The ability to actually access the calling contract's storage from withit a library. As soon as this is ready ( https://www.pivotaltracker.com/story/show/101774798 ) I will announce this feature more publicly.
I can't find the link for the original idea now. Someone suggested this long ago and even made up a concept icon that was essentially a bucket of scrap parts. It was pretty highly upvoted. The idea was to have the scrap tier of items made with this resource and it would be looted from radtowns and wreckage across the rust landscape. I was browsing Pivotal When I saw it was being worked on I thought I'd share the find, and that it would promote some nice discussion.
My hopes are that it would prolong the mid game and endgame of rust by requiring players to scavenge rad towns for it. It would be something that can't be obtained from the safety of a compound, forcing players to get out and about in the world. It could be used in the crafting of guns, windmills, quarries, pumps, and cars in the future maybe.
I use pivotal tracker for my project. its just me so I don't need any of the team aspects of it but it helps keep me motivated and gives a constants stream of tasks I need to do.. and an estimated time to release based on how much im doing each week
I don’t have any estimates for when Chainlink’s mainnet will be operational, but as the Chainlink team themselves will tell you to check out their Pivotal Tracker to draw your own conclusions.
Pivitol Tracker (https://www.pivotaltracker.com) is free for public projects. I don’t know if it hits all your requirements, but I found the release markers were really helpful (and accurate when I was honest with my estimates).
We are currently running a node that fulfills requests to it on the Ropsten test network. As our project tracker shows, aggregation contracts are coming soon, and that will mean multiple nodes will be able to respond to the same request (noted by the answer aggregation label). We have a few concrete examples available already in our repo that demonstrates how a smart contract can request external data from Chainlink. This includes the ability to work directly in Remix with this guide.
I cannot even view the "roadmap" on my browser. It's just a blurry image. I would hope it to be more like the Chainlink Pivotal Tracker here: https://www.pivotaltracker.com/n/projects/2129823 where we can see real progress being made, and the steps left to finish each part of the project.
Over a 20 year career managing software projects, I've tried most project management tools.
The least bad one I've found is https://www.pivotaltracker.com/. It's opinionated in all the right ways, its UI is powerful, attractive, but intuitive, and its pricing is reasonable.
It can also do cool stuff like automatically forecast what's going to get done by when, based on data - not just guesswork.
The fact you've twice mentioned .biz as a reason not to buy is laughable, I'm sure the team arn't that enthused about a chubby kid screaming about it on youtube either. The project has more depth, use, and maturity in the space than most. Ari Jules and IC3 backing the project along with SWIFT tests and SIBOS feedback provide genuine accreditation, and testnet is almost upon us...https://www.pivotaltracker.com/n/projects/2129823
I understand there's no hype going on pre release, the 'community/investors' are owed nothing if they can't do there own DD. Maybe some spurious partnerships scattered over reddit would help make it more legit? You're right though, it has under performed since mid jan 😲
Ah yeah, sorry about that. Hacktoberfest is driving an alarming number of people to the github issues page. I guess it's not the worst problem to have...
~~You can take a look at Pivotal Tracker for stories that haven't been tagged "hacktoberfest" if you want :)~~
Edit: Pivotal Tracker has been deprecated in favour of Github Issues
You are right, templates are really important if you want reusable algorithms and data structures, and we have a story for that on the backlog: https://www.pivotaltracker.com/n/projects/1189488/stories/89907258 The example in the story is a bit outdated, the code will more likely look like this: https://github.com/ethereum/dapp-bin/blob/master/future_solidity/heap.sol
Templates are not a big hindrance for formal verification, by the way, you just have to check the proofs for all template instances.
They just announced a new dev tracker that FP is using, I know triangle blocks is scheduled for a fact. I think it should be due sometime at the end of this month. :)
EDIT: Found the link for you to check it out yourself, https://www.pivotaltracker.com/n/projects/1371850
EDIT 2: It appears that the Triangle block was moved to the icebox, so that means there is no ETA on it yet.
Nope, I'm a tester. Keep an eye on these websites, they are for the Rust Developers.
https://twitter.com/RustUpdates
DEVELOPMENT TRACKER
https://www.pivotaltracker.com/n/projects/1371850
DEVELOPMENT BLOG
https://twitter.com/RustUpdates
http://playrust.com/devblog-66/
https://www.pivotaltracker.com/n/projects/1371850
Pretty much what is on the twitter generally turns up in the following update plus sometimes the previous dev blog will indicate whats coming up next and the Pivotal Tracker shows whats being worked on and when its finished. There are usually wipes once a month but not always sometimes they are delayed depending on the work done.
I'm using PivotalTracker for my project management (free for single users).
What I really like about it is that I assign "points" to tasks which represent their approximate scale. As I complete tasks, PivotalTracker calculates a rolling average, then it applies it to the remaining tasks to figure out how long it will take me to reach various milestones. I can also set a "load" for a week, e.g., 50% if I'm going away for half the week.
If a release/milestone is projected to slip based on the remaining # of points, it'll be colored red letting me know I need to be more realistic.
The point system and avg. velocity also works as a good incentive system, because I'm encouraged to start tasks and get them finished so I can keep my velocity for the week up.
There are free alternatives. I am partial to Teambox as a replacement for basecamp.
There are also other styles, like agile design. Pivotal Tracker looks promising, but I have not had much use with it.
There is a link to a page with some suggested emails for Facebook's support inbox on my site at http://www.gazerbeam.com. Go to the Resources page. You could try a few of those.
Was there anything that happened before your account was disabled that could explain Facebook's actions?
Tracking your issue here: https://www.pivotaltracker.com/story/show/178702114
The least bad project management tool I've found is Pivotal Tracker. It's more opinionated than most, but I think it's opinions are good ones.
I had trouble finding a tool that was good for prioritization so I built my own, and have used it successfully for roadmap planning a few times.
Staking with Chainlink will be nothing like with PoS networks (more info here), there is no minimum amount to run a node/stake, and the team doesn’t give timelines for development targets. You can check out the pivotal tracker to track development progress.
Here's a relevant question from the FAQ. The Pivotal Tracker is how you can track development progress.
With some project trackers, features get points and bug fixes don't. Points get rewarded. Thus, project manager and dev team do features and not bugs.
There is no public roadmap for Chainlink's development, including the price feeds, but you can use Chainlink's Pivotal Tracker to track current development.
This article might give you some insight into Chainlink's aims with respect to DeFi.
Pivotal is the parent company of Pivotal Tracker, a platform for change management and issue tracking. Figured this would be of interest to those that use the platform.
A user story is a placeholder for a conversation, and you and the author having that conversation is a good thing, IMO.
In Agile, you should never be in a situation where you can turn off your brain and only do what the "requirements" have documented.
A well written user story will describe the user, their goal, and the benefit to the user. Usually in the format of "As a [User Role], I want [Feature], so that [Benefit]" and acceptance criteria are written in Given/When/Then format. See https://www.pivotaltracker.com/blog/principles-of-effective-story-writing-the-pivotal-labs-way for a good article.
The ticket should not, for the most part, describe the "how" of the implementation. Developer implementing the story is the best person to determine "how" to implement it. The technical decisions should never be made by non-technical people.
With any new feature, there is a lot of processes that have to occur, and that is the main reason we don't give dates typically on future development. You have to research current models and examine any relevant info from academia, develop the feature, test it, get it audited, address anything in the audit, test it again, then get feedback from the teams in the ecosystem. Then you have to take into account development that may be occurring on ETH that may or may not impact what you just created. So there is a lot that goes into creating anything that goes live on mainnet. This process ensures that when something is released it works the way it was intended to, especially with something like staking where security is a must. That is why we take the "when it's ready we will release it approach".
​
We have a few ways to track our progress, like GitHub and the Pivotal Tracker. For non-developers, the community usually discusses the progress and breaks it down for non-developers on the Discord in some of our development-related channels.
I'll answer this one for you, and I'm sure you can guess the answer.
The Chainlink team typically doesn't give time frames for the completion of projects. You can check the Pivotal Tracker.
In my role as Chainlink Developer Advocate I would like to thank you for your interest in Chainlink and remind you that our Pivotal Tracker is the best way to follow the progress of the Chainlink core dev team. Also keep an eye on our blog and follow SmartContract.com on Twitter to get all the latest announcements and stuff. As much as the attention-seeker in me would LOVE to be able to give out insider information, of course I cannot. In fact, I really don't even _know_ any insider information, to be completely honest with you. I see what comes down in the blogs just like you...it's just my job to make sure as many people see it as possible!
​
Now, in my role as mod for /r/buidlrs I would like to remind you that this question is probably better suited for /r/Chainlink :wink:
Chainlink has a public issue tracker where you can follow all the development progress here.
It's good to be sceptical, especially in this space, but the guy in the interview (Sergey Nazarov) has started and ended projects (NXTdecentralized exchange) before a lot of the current teams even heard of blockchain, nevermind being aware of the oracle problem.
If you do some research you will find that they have thought this oracle problem thing through and have executed their plans with surgical precision so far. And this al with 0 overhype from the team and partnership announcements only if the other party announced first.
From the article that this post links.
> #When will staking be possible? > > In order for staking in Chainlink to be possible, two main aspects of the Chainlink software need to be complete, these are commonly referred to as the Penalty and Deposit contracts. These contracts contain the logic that allows smart contract creators to specify collateral requirements and the ability for nodes to be penalised in the event they don’t fulfill their accepted tasks. The Chainlink team do not typically work to set time frames, choosing to release the work when they feel it has met their high standard, so it is difficult to say exactly when staking will be available. However, you can track the teams progress and what they are working on here.
Hmm doesnt look like its been worked on recently and doesnt look like its ready to be released in February, mainnet not until this tasks are completed
https://www.pivotaltracker.com/n/projects/2129823/stories/157743988
https://www.pivotaltracker.com/n/projects/2129823/stories/161890399
There are a tonne of resources online to learn (https://www.pivotaltracker.com/help/articles/quick_start/ for example). A basic overview I would give is: The Left column is the currently assigned tasks: - Completed tasks for this week are colored green. - Yellow tasks mean they are currently being worked on / coding is underway. - Grey tasks have yet to be started but are scheduled to be worked on. The right column contains unassigned tasks ordered by priority.
We don't know. The team has never had a roadmap and directs the community towards the Pivotal Tracker and GitHub (https://github.com/smartcontractkit/chainlink) (both of which are very active).
Most are thinking the release will be in Q1 and I would certainly expect it by the end of the Q2 at latest.
There's a lot of factors in that answer. We need the main network to be up and running but the sooner you are answering, the better. There will be a reputation system and part of that factor is the amount of requests you've answered\time you've been online.
1/3 of the total supply is dedicated to incentivizing node operators. No details on how that will be issued but this also makes me think that that early node operators will be furthermore rewarded.
As to when the network will be ready, we are all watching the progress in pivotral tracker here: https://www.pivotaltracker.com/n/projects/2129823
While I've had this issue in the past, I am trying a new approach to keep me motivated. Small wins rather than large ones.
I track all of my work on https://www.pivotaltracker.com I break stuff down into very small chunks, small enough that I can reasonably finish one in 1-2 hours of work. I established regular working hours on my project from 6:30-8:30am every weekday. The goal being that I should be able to complete a task every day, or more if they are small enough. Then each week during sharing saturday I can post an update and feel like I am making progress.
You also need to keep in mind that projects are marathons. Every commit you make to source pushes the ball inches forward. I think its also important to reflect every month or 2 and realize just how much you have accomplished. If you can establish a set routine I think you have a better chance of sticking with it.
/r/vornth Could you please explain further what's happening if you're offline:
> Only if your node doesn't respond with what the desired endpoint gave you. LINK will be deposited in a contract, so you won't need to store them on the same address that your node uses, which will only be to pay for gas to write data to the blockchain.
https://www.pivotaltracker.com/n/projects/2129823/stories/158585548 > If the oracle does not fulfill the request, and it is forced to close without them, the money is split between the requester and the closer (50/50 for now)
what do you need to store on the node? 1) Link Tokens (to make the node thrustworthy) and 2) ETH as well? (you mentioned Gas to write data to blockchain)
what is actually lost in case your node gets unavailable. Could you pls show us a little example eg. you have 1000 Link Tokens available. How are they typically stored on the node? How much is deposited into a shared oralce contract? Are really half of the deposits lost in case of a node outage?
Thank you for your detailed reply!
> ...you'll also need an Ethereum client running...
Ok, what's the approx disk size of an ETH client? (total incl blockchain)?
Do I absolutely need to run it locally or can't I simply connect to a remote one (I mean for testing purposes and for production LINK node)
> Oracles can deposit and withdraw link into a shared oracle contract."
> https://www.pivotaltracker.com/n/projects/2129823/stories/158585548: "When a request comes into the shared oracle contract, the deposit is pulled from the oracle's available withdrawal amount. When the request is successfully fulfilled by the oracle, the deposit is made available to them. If the oracle does not fulfill the request, and it is forced to close without them, the money is split between the requester and the closer (50/50 for now)"
How much would be such a deposit be? 1 Link token? 100? 1000? - I suppose the node owner needs to pay the deposit, right?
> Only if your node doesn't respond with what the desired endpoint gave you. LINK will be deposited in a contract, so you won't need to store them on the same address that your node uses, which will only be to pay for gas to write data to the blockchain
You mean, there is a possibilty to separte between a working account for gas etc. on the node and a separted primary link account out of the node that is used to gain thrust?
Timeframe: According to your personal opinion (we all can't foresee the future) how much time do I have left? Days/months?
There will be no mainnet launch on june 21. Look at https://www.pivotaltracker.com/n/projects/2124891 It is mainnet release candidate, not mainnet launch. It means that it will start getting tested and there will be a lot of bugs that will need to be addressed + they are late on development schedule with 1.5 month or so.
The following comment by throwaway51594 was silently greylisted(for 83.2 hours).
(It was mod approved at: 2018-04-28T06:16:19.000Z UTC)
The original comment can be found at this link:
np.reddit.com/r/ BitcoinMarkets/comments/8e8qpw/-/dxwfhrk?context=4
The original comment's content was as follows:
> What the hell are you talking about? > > https://gitter.im/smartcontractkit-chainlink/Lobby > > https://www.pivotaltracker.com/n/projects/2129823
Awesome man, I actually have everything tracked on a public pivotal tracker. I'm not sure if you have used this tool before, but it's easy af to use. Here is the link for viewing what needs to be done next. Obviously everything isn't in there yet, but it's what's required to catch up and surpass the competition a bit. There are bigger goals after these features are completed:
I use pivotal tracker. It's very easy to add items, reorganize, point and set milestones. I have one list of items todo ranked first in priority then a backlog of work prioritize / plan for later. https://www.pivotaltracker.com
I'm not sure if always converting pounds to Newtons makes sense (since lbs as weight are used so much more often).
It does make sense to convert explicit mentions of "lbf" or "pound-force" into Newtons though, I'll add that to the to-do list! Thank you for your suggestion
I personally use Trello - top down for priorities and add due dates for time sensitive. Alternatives: Mingle free up to 5 users https://www.thoughtworks.com/mingle/ PivotalTracker free up to 3 users https://www.pivotaltracker.com/
If you're looking for free/cheap and light weight, these are definitely the ones I recommend (in no particular order):
I've used all of these at specific times and it can really depend on how you want to organize your work, how many people you have on the project, how detailed you want to get, etc. Feel free to PM me if you have any questions or want suggestions on how to use any of these.
FP wants to implement at least one ressource that is only obtainable through looting. It is called scrap.
source: https://www.pivotaltracker.com/n/projects/1371850
And I think they want to implement military grade weapons that you can only loot and not craft.
Here.
It was linked a day or two ago; it's what Facepunch are using to track tasks instead of Trello now. It had Exhaustion labelled as an upcoming feature and got a few people worried.
It's kind of a chain reaction thing. Someone cranks their gamma and goes out killing people in the middle of the night. People don't want to get snuck up on in the middle of the night, so they turn their gamma up, and before you know it a huge portion of the server has turned their gamma up. Facepunch is going to be attempting another fix at this, it's under Aug 14th on the Pivotal Tracker https://www.pivotaltracker.com/n/projects/1371850
Thank you guys and girls for participating in this test run. I've started a PivotalTracker to keep track of feature requests, ideas and everything else. If you have any questions or suggestions, feel free to send me a message. :)
The next release will hopefully be a public beta with working withdrawals, 2 weeks from now. That being said, ~~I'm having minor surgery this Thursday and~~ things may be delayed unexpectedly.
Edit: Now also OpenSource on Github!
Pivotal Tracker -- Our clients' product owners are expected to keep the backlog up to date at all times. As an added bonus, they have a fantastic iPhone/iPad app and it integrates nicely with Google Apps, allowing the team to easily share numerous project artifacts throughout the sprint.
As mentioned in another comment, JIRA/Greenhopper has a similar capability but in my experience of using that combo for several years with multiple teams, it's not the best tool. We found it to be a fantastic bug tracking system with a poorly written agile-like overlay. We also reported numerous bugs up to Atlassian regarding burndown calculations that were written off or ignored.
It has improved a ton since last year (I started using it around summer of 2010). They have added a ton of really cool features/improvements. Like the ability to just drag and drop screenshots into a bug. I am not sure about being able to host your own version, I'm going to guess and say no.
They have a ton of cool 3rd party integration stuff now. We use the git and campfire integration tools (and a few others, I think). I would definitely recommend it if you are trying to switch trackers again :P.
Also, if you are the correct RougeDarkJedi, thank you so much for the awesome derpy mail icon script! They are fantastic!