Proposal “dash-nexus-accelerated-development“ (Active)Back

Title:Dash Nexus: Accelerated Development
Monthly amount: 166 DASH (15052 USD)
Completed payments: no payments occurred yet (4 month remaining)
Payment start/end: 2019-08-18 / 2019-12-13 (added on 2019-08-18)
Final voting deadline: in passed
Votes: 350 Yes / 146 No / 43 Abstain
Will be funded: No. This proposal needs additional 292 Yes votes to become funded.
External information:
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many 905a84e817d2f6d5b1fc5392c639ab257f8bb342bb82af4651b2d42ec983e54d funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

Our primary proposal (Ongoing Development) covers the basics necessary to keep Nexus fully operational and provides the resources to make gradual improvements to the platform. However, it alone is insufficient to make significant advancements in the platform's functionality.Funding this proposal will allow us to expand our development team and optimize our work flow without increasing overhead. By having additional developers on the project, we will be able to tackle more complex features, have dedicated resources to address bugs (without interrupting new feature development), and increase the overall synergy between designers, developers, testers, and project managers.

What does this proposal funding request cover?
The entirety of the funds requested in this proposal will be used to hire developers. As mentioned in the primary proposal, these will be in-house developers, rather than agency contractors. We will not need to spend any additional funds on project management, since this will already be covered by the primary proposal. Having a larger team also means that developers will be able to focus on areas that they specialize in, rather than spreading themselves thin across a number of frontend and backend tasks.With the additional manpower, we will be able to to begin working on more complex tasks, such as overhauling the discussion area to encourage more engagement. This would include adding the ability to tag users in comments, generating push notifications to alert users even when they don't have a tab open, unifying MNO-only and community 'channels' into one and creating permissions/filters to allow users to see the content that's relevant to them. Tasks like these require extensive development and testing and are only feasible with multiple devs working in sync.

Looking Forward
We believe that now is the perfect time to build out an in-house development team for Dash Nexus. Not only will it allow us to amplify the momentum that we have been building over the last few months, but it will also perfectly position us to take full advantage of the DAPI when it is released.

Thank you for your support!!

- Dash Nexus Team

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
1 point,17 days ago
Last minute shout out. Two hours to go, and this proposal to accelerate DashNexus still fits very nicely in the un-allocated Dash. 300 YES votes is a lot of ground to cover in two hours, but I have seen miracles happen before. Building more sophisticated infrastructure to submit props, vote and do governance seems like a much better use of the Dash than burning it.

However you vote, thanks for participating!

0 points,19 days ago
Voting yes, we can pick between the Nexus proposals, no?
0 points,18 days ago
Looks like this can still fit into our budget, can we have both Dash Nexus props passed this cycle?
1 point,25 days ago
I note that there is only a week left for voting, and in general, voting levels are pretty low. I would encourage everyone to get some voting done.

Another thing I noted which may cause some bad decisions is that DashNexus has two props going this month. One is to keep the lights on and keep the same current level/pace of development. Slow and steady, etc. They have a second prop that would allow them to hire some more Dev horsepower and speed things up. It would appear that the second prop won't fit since it falls below the yellow "Budget Limit" line (on app.dashnexus dot org). But Eugenia's "Transaction Turbocharge in VZ" is unlikely to pass (whole other conversation) and if that is true, the 2nd prop for DashNexus fits fine.

Yuri says that site traffic to DashNexus has really picked up the last few months, and now the vast majority of props are submitting using their (far easier) method. So, woo hoooooo, it's getting traction and working, but there are a bunch of features they would like to add, and the current skimpy budget just feels too slow.

I know everybody feels a bit depressed in Dash and the larger crypto space because of failure to moon. But we will get another bull run sooner or later. We need to get the easy infrastructure in place now to be able to accommodate a bunch of fomo newbies.