Takeover!
we have ...
soopy and i STILL have the passwords and keys to all the components of the system ( unless soopy has changed them without notifying me - though i highly doubt he would do such a sly thing ) ... this thread - the git - the code ...
its just that soopy is the one with the backing - where i have heard not ONE argument for support for my team and i - cwi ...
i said soopy was unreliable - NOT that he is a bad person ... soopy is one of the nicest guys i have ever met ... BUT - his reliability factor is almost ZERO ... he knows this - as he has let theteam down many times over ... which is WHY i wont work with him any longer ... NOT because of any other reason ...
soopy is still kept in high regard with me - as a person and competent dev WHEN he wants to work ... but i refuse to work with unreliable people that SAY they will do - and DONT ...
hence - this is where i stand ... and 'theteam' back my decision also ...
the community really NEEDS to remember who brought this coin back ... it wasnt soopy alone ...
ill look for the passwords and keys soon - too much on at the moment ... when i find them - ill see if they all still work ...
#crysx
So what is it that would need to be done to get you to start developing this coin? All i know this far is every attempt to resurrect this coin has ended in disaster for one reason or another. Im sure almost everyone would be happy for you to continue developing droidz.
Im not sure even if the best coder can actually currently do anything with this coin but you would know better than me.
no - i dont know any 'better' than you ...
if soopy stuck around on a REGULAR basis and kept developing and FOCUSED ( one his major weakpoints ) on the projects he assigns himself to - then it would be ok ... he is a good dev ...
BUT - as it stand - he doesnt and has let me down on our own projects many times over with granite ( grn ) ... so there is another dev - who is reliable - that is part of theteam now ...
the only catch is this ... soopy is still a part of this project - and unless he wants to remove himself from it - i will not lock him out of the thread or git or anything else without his knowledge AND request ... honor is crucial here - and i will not do that to soopy or any other person that i ( or cwi ) deal with ... its wrong to do so ...
what CAN be done is simple ...
if the consensus is that cwi take the project under its wing - then it will require a number of things to happen ... obviously this requires full authority over ALL components of the droidz system ... full control ... so that no other dev or community can interfere with it ...
IF theteam agree to take on another project on top of the ones we are currently working on - it will require a much work ond setup in the backend FIRST - before anything major is done on the wallet / daemon - just to support the current wallet and community ...
then a decision will be made whether it is a viable consideration to continue working on drz - or assimilate it into our flagship project ( granite ) ...
NONE of this can happen without community support ... simple ...
in the past pages - all i see is soopy soopy soopy ... soopy pops in for a minute - and you all lose your friggin minds ... he is here for ONE MINUTE - and then disappears for weeks and months ...
under cwi - this cannot and will not happen ... we cannot have ANYONE - let alone a core dev - disappear like that at the drop of hat ... no way ... not going to happen - not on my watch ...
so all in all - IF there is a community consensus -t hen we can have the consideration of taking the project under the wing of cwi ... only IF theteam agree that we should ... decisions will be based on the value - the use - the viability of doing such a thing ...
i can say this much though - the likely hood of furthering the coin is slim ... if anything is to be done - it will more than likely become assimilated into granite and the cwi network - which means that drz will be swapped and burned for granite ( grn ) ...
depending on what theteam decide will be the more beneficial approach - and whether the resources and time can be allocated ...
#crysx