Proposal “dashcore-for-redhat“ (Completed)Back

Title:Dash Core for Fedora, CentOS, and Red Hat Enterprise LInux
Owner:t0dd
Monthly amount: 33 DASH (5518 USD)
Completed payments: 2 totaling in 66 DASH (1 month remaining)
Payment start/end: 2017-01-04 / 2017-04-20 (added on 2016-12-22)
Votes: 803 Yes / 20 No / 0 Abstain

Proposal description

Dash Core software professionally packaged, tested, maintained, and delivered for the FedoraCentOS, and RHEL linux platforms.

Overview

This is a request to fund a very modest Dash patronage to help offset some of the effort associated to the development and process of building, packaging, delivery, and maintenance of Dash Core code for the premier family of linux operating systems: Red Hat -- Fedora, CentOS and RHEL. I.e., "release engineering" for this family of operating systems. I have been building packages for this line of operating systems for over 8 months now and will continue to do so, proposal accepted or not. This is a plea to assist in my efforts as I improve and expand the scope of what I am already doing. Dash Core for Fedora, CentOS, and RHEL is already the easiest to install, update, and maintain and in the next 3 to 6 months the scope of what is packaged and delivered will only expand. Thank you for your support -t0dd

For more detail, please review the full proposal description here.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
0 points,6 months ago
dnf upgrade should never install a new version of dash. Upgrading must be voluntary, with conscious effort made to do so. With autoupgrade there is a risk of pushing out undesirable binaries and hardforking without many realizing what is happening.
Reply
0 points,6 months ago
There is that risk no matter how the code is delivered. That being said, I am investigating best practice surrounding this scenario. It may be that for hard forks, it becomes a different package-set (doesn't overwrite the previous). I don't know if that is the right soution so, in the meantime, I am still digging into that.
Reply
0 points,6 months ago
Anyway... It's not a unique problem and it is solvable.
Reply
0 points,6 months ago
If you just run /dash-0.12.0/bin/dash-qt under this versions of Linux distributions, it does not work?
Reply
0 points,6 months ago
I am unsure of what you are asking. Can you please elaborate?
Reply
0 points,6 months ago
On my Debian I dowloaded latest core version from https://www.dash.org/binaries/dash-0.12.0.58-linux64.tar.gz , extracted and run dash-qt and it works fine.
Is it not the same under all Linux distribution?
Reply
0 points,6 months ago
The experience needed:
* Your software manager alerts you that a new version of Dash available, do you want to update it?
* You elect yes, and click a button.
* Done.

I want my Android app to be packaged right, with the right files landing in the right places with the right security settings delivered and updated from Google Play or F-Droid. Or from iTunes from Apple. The same standard should hold true for any desktop or server application.

Right now... you can have that experience if you run Fedora, CentOS, or RHEL. Because I built that.

If you run a masternode, it comes *close* to that experience... but is certainly the easiest masternode install and configure experience that is out there. Again, because I built that. I also fixed or enhanced packaging issues that... you don't see, but makes Dash core work better.

Some folks are just fine continuing down a path where installing and updating software is manual process involving browsing to a community webpage, downloading a a tarball or zip file and installing that. But a mature software platform needs to professionalize. This is what this is all about.

And there is much more planned (read the proposal). I hope that helps explain the effort better. Thanks for the question.
Reply
0 points,6 months ago
Example: Anyone running a dash masternode would have seen this arrive from Santa late last night... :)

https://toddwarner.keybase.pub/pub/Screenshot%20from%202016-12-23%2008-33-03.png

They don't have to browse anywhere, manually download something, then scp it to your masternode... It is simply available. Automatically and digitally signed and verified. Bliss! :)
Reply
0 points,6 months ago
Note: In case anyone is confused by the version, lemme rephrase that...
"Example: Anyone running a testnet dash masternode on Fedora would have seen this arrive from Santa late last night..."
Reply
0 points,6 months ago
I voted yes
Reply
0 points,6 months ago
Thank you, dusko!
Reply
0 points,6 months ago
Great proposal with just the right amount of information. The github link for me to view your work thus far was icing on the cake. You have my vote yes without reservation.
Reply
0 points,6 months ago
Thanks!
Reply