What's TAW 3.0? This is the tag line we call our new website platform. Some of you may remember the old brown and black pages. That, in theory, was 1.0. Our current website is 2.0. The next platform is 3.0.
=
Currently working to document features of the current development version.
Client side has a base for the whole system done, but it's missing all features for user and unit management. Currently inergy is trying to finish UI designs for missing pages and we'll most likely do a small rewrite on UI layer when those designs are done. Client side development could be started before designs, it would mostly mean we'll just have to do slight rewrite later on UI components.
On the server side, we have most of the required features done for MVP version if not all. Current task for me has been to document server features properly and to test those so we would know exact state of this side but this is not finished yet, actually there is still quite a lot to document and test. I'm progressing quite slowly due to not finding a proper way to do this, and also as I'm more of a person who prefers on doing stuff instead of writing documents(yes, document are quite important but I'm overall terrible in writing anything else than code).
We have few other members in DEVOP and another member came to me few days ago asking if he could help, but I'm finding tasking this right now quite difficult. We have few members with a will to help but I can't come up with anything, mostly due to their experience with used languages/libraries are not that good. We could give them some smaller tasks when we continue development but for now it would be quite difficult for them to read code they might not understand and document it.
To summary, next on client side is creating missing UI designs, and finishing documenting on server side. After these are done, we would need to start implementing features on client side and make possible fixes on server features as those show up during documenting and/or client development.
just gonna say this again, if you ever need someone who konws mainly python but also java, hmu
Reading this, I see that we are already facing a problem to find those who know the language we are using for the code. Does this not mean maybe the language we chose is not the best to move forward with and potentially need to completely switch? Because if it is already difficult to find people who use the language now (When there is an interest of people who can help but just not in that language), then maybe we will have a TAW 2.0 problem on 3.0 due to the choice of the language later on. And the goal is to easily update it in the future and work on it right? Just thinking long term. I might have read this wrong but I just thought to ask about it.
@Nat: it should say hard to find people that know that language that will work for free....