The 2019 SAFE Network Roadmap / Project Plan

#23

Finally a github project board created, Maidsafe getting a bit more organized in a public manner which is good to see :slight_smile: .

Cheers to knocking out big issues and moving them to the done column. Do that enough enough times and you may just end up with a quality secure and decentralized network on your hands :+1: .

8 Likes
#24

Who wrote this? It was beautifully constructed. It more than felt the pulse of the community. It was a graceful communicatory ride. :clap: Excellent!

8 Likes
#25

Well done. I was going to say and easy to understand but I am confused by something…
The backend roadmap has test safecoin and wallet under Maxwell, yet under task level board for immediate tasks safecoin and wallet is marked as active.

Are Maxwell tasks already in progress?

Great to have this, it is done well enough to show us whats happening without setting unrealistic expectations and disappointment!
Very much appreciated, I was feeling very lost lately.

6 Likes
#26

looks great team!. Thank-you.

3 Likes
#27

great to see this road map… really appreciate it.

4 Likes
#28

Third, you can give a fork ETA without any precise date. Let’s see:

  • Fleming: Between 8 and 15 months
  • Beta: More than 20 months

Just for us to have an idea.

3 Likes
#29

8-15 months seems a bit pesimistic, thought may was the month…

#30

We have per hop secure relay, this is a faster impl of that which validates only at the destination but uses reliable message delivery instead of routes and acks. Therefore faster, no timers and no magic numbers past what PARSEC uses as assumptions. This should cover all edge cases and be faster to impl at the same time. You will see much of what is already done (in terms of we know how it works) going through this process as it gets into production.

11 Likes
#31

Yes, we have a few parallel tracks right now. There are some internal re-org of teams into project teams. This is all during the project of course, but as we now resource the plans and tasks we can get better ideas of what we can do in parallel to get a better idea of overall progress to the milestones. i.e. a live project plan, early days but we will see a lot of things happening concurrently, especially critical path items. We have the dependencies pretty accurate so next step estimates of person hours and then apply the resources we have,

9 Likes
#32

My estimate for Fleming has always been 30 June this year. I think that will be close

5 Likes
#33

Thank you for your reply :slight_smile:

3 Likes
#34

Nice work @maidsafe looking forward to cheering you guys through the long pressure filled hours ahead.

The great thing is with the amount of detail there we even get to know it a little bit in advance, can’t really ask for anymore, although some will :man_facepalming:

2 Likes
#35

I can feel a sweepstake coming on!

5 Likes
#36

This was @dugcampbell 's handy work, with some input/proof reading for other people on the team

8 Likes
#37

If I knew how to create one of those polling things I would

#38

Hey @Lisa_Brown hopefully the “30,000 foot view” roadmap will be the one for you :smiley:

12 Likes
#39

Hi @davidpbrown,

The backend and task level boards both follow the same format - the closer to the right you get the closer to completion that piece of work is (i.e. Fleming will be done sooner than Maxwell, which will be delivered sonner than the remaining pieces in to do.)

Does that help to clarify?

11 Likes
#40

Thanks for this great insight. Much appreciated!

Currently it seems that only frontend / client based tasks are assigned to projects. Will you add routing / backend tasks to projects in the task level board as well (once implementation planning is finished) or will you stick to Atlassian for those?

It seems that routing / backend is currently in full “design / implementation planning” mode, am I right?

1 Like
#41

Backend work will be moving to these projects also, to ensure we have a single place view for everything :slight_smile:

11 Likes
#42

From this I also got the impression that everything expect integration with SOLID was really ready and finalised.

This is something that I as a lay person have trouble understanding. What is the order of such things as: coded, tested, implemented…? (And also in the context of @dirvine’s reply “finalised”?)

Is it so that when something is “in code and being tested”, it is tested as a separate unit, but not as a part of bigger context, meaning not implemented?

What was finalised? The solution as an idea, but not the code?

The roadmap… a map from alien planet to me and without scale (timescale) pretty useless for me as lay person. I don’t have any idea of the difference between a molehill and a mountain. But I guess it speaks more to folks with understanding of computers and interwebs… :wink:

3 Likes