Dekko && Decko2 - a sad story
-
But, you missed to answer my question: Why Dekko wasn't just developed further? Why these fundamental issues which let me think it was rewritten?
Dekko was just developed further. I don't know why it was called Dekko2. It's not a total rewrite of everything, as I understand it.
-
@guru Short version. I believe at the time Dan Chapman creator of Dekko was unable to carry on with it's development. The team behind dekko2 then carried on with the work and development.
-
@dobey
With the announced deprecation of click packages development on the original Dekko was halted, and all effort was poured into de snap version of Dekko for Ubuntu Personal, which would have included mobile devices.
When UBPorts took over the Ubuntu Touch project, Dan was persuaded by popular demand to release a new version for the platform. So he released Dekko2 which was based on the work done for the snap version, but was in very early stages. The rest of the story went as @Lakotaubp states. -
@arubislander Yes, but the code packaged in the snap was not entirely new code different from what was in the click. It was an evolution of the same initial code as I understand.
But really it doesn't matter. Dekko 2 is Dekko and that's it. It's a newer iteration, and if there are bugs they should be reported on the GitLab project for it.
-
@dobey Are they dekko2 bugs or issues with OTA5 now fixed in later OTA's ?. Wouldn't it be best to go OTA7 first and see if their reproduced.
-
@lakotaubp said in Dekko && Decko2 - a sad story:
@dobey Are they dekko2 bugs or issues with OTA5 now fixed in later OTA's ?. Wouldn't it be best to go OTA7 first and see if their reproduced.
Most of the things listed in the original post seem like issues in Dekko that have nothing to do with the rest of the system.
-
So this isn't my work - only a very very very small part of it - but I would be very proud if it was mine and even reading the title of the thread doesn't feel right for me...
The only thing I can feel when holding dekko2 in my hands is deep gratefulness. Thank you Dan, for being with us, for continuing Dekko, making teleports possible and teaching and guiding us! Also thanks to all the other experienced developers as well as the not so experienced devolpers and also the non tech guys dedicating their time. And ofc thanks for all the donations. I especially like the way how the experienced people are guiding the unexperienced in the ubports community. Thats great! You're great!
@guru sry for hijacking your thread -
@dobey said
Dekko was just developed further. I don't know why it was called Dekko2. It's not a total rewrite of everything, as I understand it.
Dekko2 is an important rewrite because Dan has been obliged to abandon the Trojita library he was using in Dekko.
@guru Dekko2 is a new software so this time again no regression
-
Dekko isn't a sad story i think !
Thank you for the work done by Dan Chapman and the community.
But indeed, maybe for various reasons, a very long story, with yet normal user expectations of a good mail client.
-
I'm very thankful to Dan and all the UBports community for the work they have done and do, and where I can I help I do so, with my knowledge and with tests, for example for Dekko.
Do not get my message wrong. I'm and old software developer with more than 30 years of background in UNIX, etc. And I'm an user of UT since the beginning (when the 1st devices were sold), a beta tester for BQ.com for the tablet. The BQ E4.5 is my daily driver and my work (and social contacts) depend on a functional MUA on this device. The (old) Dekko worked fine for me. When I moved from UT to UBports, I have had to move to Dekko2, and got no new features, but many issues. That's why for me as an user, this is clearly a step back, a regression.
-
@guru
Dan stopped the development of Dekko because it was no longer possible for him to maintain and evolve the code by continuing to use the trojita library. He was at a dead end.He therefore launched the development of a new Dekko2 application with new code to replace the basic messaging features provided by trojita.
As long as UBports UT was in version 15.04, it was possible to use either version, dekko or dekko2.
Then UBports started the migration to 16.04. with OTA-4 and OTA-5.
At the same time Dan suspended all his contributions to UBports and dekko2 for personal reasons and there was no version 16.04 of dekko2 available.
So, some brave people from the community rolled up their sleeves to bring a Dekko2 Community Edition compatible with UBports UT 16.04.At the end of 2018, we had the pleasure of witnessing Dan's gradual return and he was able to take care again of Dekko2.
Since it is not the same application, the same basic code, I do not find it entirely accurate to use the term regression (with regard to the usual use in software development), although I understand that for some use cases and some users it may look that way.
Anyway, I hope I have clarified the situation a little.
It's not a sad story but a heroic story.
-
@guru IMO, as you're a veteran software developer, you should know that you can set forth the issues you're experiencing without using such a negative tone.
Thank you for all the work you're doing btw, and I hope you understand what we're trying to explain you
-
My initial words have no "negative tone", they are just the truth about what I'm facing as an user of Dekko2; and I stay with them even if you delete all 100 points of my score. I learned in many years of sw development that at the beginning of an improvement the first step is a clear picture of the actual situation. You (and others), do you use Dekko2 in production (i.e. to read and answer company or customer mails)? If so, you should understand my open words.
My last word in this thread. The rest will be filed as issues.
-
The negative tone starts at your post title ("a sad story") and then continues. What it's "a clear picture" for you, maybe other people see it just as a grumbling because you're using some adjectives that are not really necessary to describe a technical problem.
Anyway, it's way better to fill an issue, that's true.
