Progress on Eadrax
Even though me blabbering about project Eadrax doesn’t seem to interest most people (see: 0 comments on previous 2 posts) and it seems as though nobody has responded (yet) on the mailing list, I do not consider it a total failure.
I’ve decided to share just how much data you can actually gather from taking a peek at the logs behind Eadrax.
Allow you me to indulge you in a recent graph from GitHub showing some logs of the progress on Eadrax:
For those unfamiliar with version control, think of it has a log of every single change that was made. Like a save file. Each dot over there represents an edit.
Those subscribed to the mailing list and that have read the Eadrax Space will have known that I have restarted Eadrax as an open-source project. The graph up there shows two people, ukd1 and Moult (me). ukd1 (Russel) is another developer I met in the #kohana IRC room, willing to join in the project. Before continuing, you cannot see this from the image, but just as a note, every single update done up there was done by me. The little tags represent “branches”, essentially different features/sections of the site that are broken down so that people don’t get confused what belongs where (and also so somebody doesn’t screw up everybody elses work). The master branch is the overall project (well, sort of).
From this you can garner some very interesting information:
1) Only Moult has done anything on the project so far.
This is not a bad thing–at early stages of the project getting so many people to create the underlying structure of the web application can lead to some very confusing situations. I also know that the other developers have been extremely busy with other things, but hopefully this will change in the near future.
2) Russel (ukd1) apparently decided to work on the project a while back, but then just stopped. His line is quite left behind with the recent changes.
Obviously he has some catching up to do.
3) When Russel last updated his project, only two branches existed, “master” and “users”, now there are many more.
This shows that the application structure is probably mature enough to start introducing new sections of the site and thus more branches. This is a very good sign for progress.
4) The latest branch is no longer the “users” branch – in fact, it has been left behind.
Well, the users branch obviously has to do with the user system – logging in, registration, etc. This is very good proof that there is already a clear structure behind the system and now we can just build up upon it.
5) Recently the code has been splitting up and merging together.
Obviously I’ve been developing some things here, some things there, and it’s now good to start pulling things back together into a simple structure so other coders can know exactly where the code currently stands.
Summary: Well, nothing much interesting to be seen on the front end of things yet, but just a very good sign that things are moving along, and moving along quick. Expect by next week to have most of the code ported over from the previous Eadrax version.
No related posts.
p. says: (14 June 2009)
3 Comments