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

Title:Dash for Fedora, CentOS, and Red Hat Enterprise LInux (3rd month 12.1 transition refile)
Owner:t0dd
One-time payment: 38 DASH (3032 USD)
Completed payments: 1 totaling in 38 DASH (0 month remaining)
Payment start/end: 2017-02-18 / 2017-03-20 (added on 2017-02-22)
Votes: 848 Yes / 7 No / 2 Abstain

Proposal description

Hello everyone!

This is a refiling of a previously accepted proposal to cover the final 3rd month that got cut off due to the 12.1 transition. As many of you know, everyone who had proposals that spanned the network update have to refile for the remainders. There was one month to go. So here we are.

The original proposal and full writeup:
Where can I get the goods (the results of the last two+ months)?: https://github.com/taw00/dashcore-rpm

The original accepted proposal was 33 dash for each of 3 months. We are on month 3. The other two months have been honored. I tacked on 5 dash to cover this proposal fee (yup, had to cover the fee twice).The crux of the proposal was to develop Dash specific to the Red Hat family of operating systems (the largest deployed family of Linux)... and associated documentation, and whatnot. This is unique in its seamless user experience and native-feel and integration with how software is managed.

So, what has happened in last 2 months...
  • RPM packaging extensively tested on testnet and upon 12.1.0 launch and 12.1.1 refresh
  • Plugged into Fedora's (Red Hat's) community build system more directly
  • Repeatable build process, from source, that you can do at home
  • GUI is more native to GNOME and other desktops
  • systemd polish and easily adaptable to things like... email alerts and whatnot
  • General Documentation (see documentation in the link above)
  • Documentation for systemd-managed dashd (dashd as a proper service)
  • Securing your masternode
Collateral benefits, in the process of this effort...
  • Identified a number of stability issues that were addressed
  • Identified library issues that help ready Dash for the next iteration of operating system updates that are in the pipeline (I include testing against bleeding edge linux as well as current stable versions)
  • Helped a TON of people during testing, lead up, and during the transition -- I even got recognized for it, yay!

There is a ton of things still to go for the future. This bit of patronage really helps, and I thank you.

I'm asking you, the Community, to honor the 3rd month of the previously accepted proposal. Thanks and see you online!
Happy Dashing -t

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
0 points,2 months ago
No-brainer. YES.
Reply
0 points,2 months ago
Thanks guys!
Reply
0 points,2 months ago
amen
Reply
0 points,2 months ago
Voting yes. Would like to reiterate my concern from before: yum upgrade, dnf upgrade, or whatever, should NOT update dash binaries. Influential bad actors could place a messed up version into the repositories.
Reply
0 points,2 months ago
Who are these influencial bad actors?
Reply
0 points,2 months ago
It`s demo and his army ;)
Yes for me as well sir T0dd!
Reply
0 points,2 months ago
Thanks, Splawik21!
Reply
0 points,2 months ago
Regardless, thank you for your "yes"... cautious or enthusiastic. It is welcome and it is good for folks to ask questions.
Reply
0 points,2 months ago
And rolling back to an old version is trivial anyway.

As for something like 12.0 to 12.1 -- You had to actively change to a new repository. The process is solid.
Reply
0 points,2 months ago
And these are digitally signed RPMs (you will not be allowed to installed meddled with software). And you have to actively pull the trigger for an install... and... there are 8 ways to sunday to not do the wrong thing... and I eat my own dogfood, for what that is worth.

If folks get crazy paranoid, I am sure there are more steps that can be taken, but... It's a pretty darn secure process.
Reply