Hi all, as I promised earlier this week I bring to you a weekly update of raiden git repositories. This post will cover both raiden and microraiden repositories.

First a few disclaimers: * I invested in RDN token * I have experience in IT. My comments are mostly based upon general knowledge. I don't have a complete understanding of a raiden projects specific use cases. * Assumptions I make in this post are my personal. I will try to elaborate why I think like that. It does NOT have to be true. It is more or less an educated guess.

What is Git and Github

Okay, if you know what is git and github feel free to skip this part. But i promised a beginners crash course in git so I will try to explain git in ELI5 way.

Git is technology programmers use to make collaboration between devs on a project easier. It is pretty straight forward piece of software. Since project is basically lines of code, git tracks who added/changed/deleted what lines.

Changes in code are grouped in commits. Commit is basically a fix or a funcionallity. Commits are submitted on a branch.

Main branch is "master" branch. Sometimes when there is a bigger funcionalllity to be implemented a developer can do work on a side branch he created by "hard-forking" master branch.

Pull request is a commit developer is satisfied with and he thinks it should be accepted on master branch. If rest of developers approve this change it will be accepted and become part of master branch.

Github is online solution for git. Github makes tracking changes on git easier plus it offers possibility to plan tasks that need to be implemented (via commits and pull requests on a master branch).

Milestone is more or less a checkpoint in a software development. Sometimes a team decides that they need to implement X amount of features and once it is done that is a milestone. Usually after each milestone there will be a minor update in software version (example microraiden 0.1.0 -> 0.2.0).

A "sprint" is not related to git itself but methodology in managing tasks on a project between developers. Sprint is a limited time frame in which developer should complete tasks assigned to him. For example if sprint on a project lasts a week, a developer should have his tasks assigned on monday and he should be done by friday so he can close his sprint.

Complexity of asks in a sprint are pre evaluated. Scale used to evaluate complexity is Fibonnacy array of numbers (1, 2, 3, 5, 8, 13, 21 ...). More fibonacy points means more complexity.

In this blog posts I will cover what pull request were accepted in last week on master branch, what pull requests are waiting for approval and what tasks team planned on github for the future sprints.

PS I know all this is not 100% true but for someone who does not know what git is I think it is pretty OK explanation.

microraiden

Microraiden github was very active last week (as I am writing this post 3 more commits were accepted to a master branch).

In order to come to a currently set milestone there needs to be implemented on more thing. Issue is called "Update Documentation" and it has been the last remaining issue for last 2 weeks. One of devs commented that this change is referencing pull request #345. So, in other words, once a pull request 345 is accepted to master branch a milestone is reached. Good news is pull request 345 was APPROVED yesteday by one of devs and it is waiting to be merged. Bad news is they can wait as long as they want before they merge it or even add more changes.

Other big pull request waiting to be merged is new website for microraiden. It is not yet approved but in comments on a pull request one of devs commented that is very very close. I imagine that they will introduce new page with the release of 0.2.0. Setting up a new website once it is done should not take more than a day so I think we are pretty close to seeing it.

There are 5 more pull requests. 2 of those are approved but they want to merge them once all other for reaching milestone are done ("Bump Contract to 0.2.0, "Remove Limit")

Rest of pull requests (last 3) are pretty old and I don't think they want them in this release.

When it comes to work that was already approved and merged I will just talk what they were about. Biggest success I see is Travis implemented on project. It took them some effort but I think they are finally satisfied whit it and I guess it works (didn't try it myself). Lots of commits were tests and updates of tests. Amount of care they give to testing their software is a good sign. Rest of commits were more or less updating documentation so they can reach a milestone.

There is no information what they plan to work on once they reach current Milestone.

Good sign I see in microraiden github is amount of outside devs that got involved. In last week I saw atleast 3 new names that did some good work in microraiden project

raiden

Raiden project is currently in second plan but there was some significant work done on it nevertheless. They have 4 more features planned before new minor release (9/13 done). New big thing they did this week is switching to python 3. It was a feature one of devs worked on for more than a month but it is done (December 6 - January 15). This information can help us calculate how long till they reach next minor release. Updating to python 3 was evaluated 8 complexity points. Remaining issues until next milestones are evaluated 5, 8, 5 and unknown. Each of this issue is assigned to a different developer. So if we assume that unknown is an 8 as well we can expect that they will reach new milestone within next month and a half. Problem is they have a history of just postponing work on a feature. They like to keep some of their work hidden so I can't see are they really working on them. Other problem is I see that one of 5 complexity features is assigned to a dev that puts lots of work in microraiden so I don't think he has much time to work on it as well.

So, this is my first weekly post so please be gentle. I tried my best to bring you some news from github. I tried to be as objective as possible but there is still lots of my opinions, so if you disagree you might be right.

General feeling around how they work is positive for me and if you are too lazy to read this post I can tell you good things are happening.

PS I saw some guy saying he follows their github religiously, he might have something to add =). PPS sorry for grammar and english I didn't really put lots of effort in correcting it, and my writing is terrible even in my first language.

Enjoy!