Hello
GreyGhost,
Thank you for the prompt response and the file (sent in PM). Please find my feedback on the proposal.
Pros:
- First of all, I am really happy this proposal is created by non-core team member. It creates another DAO in Dash ecosystem - it is our ultimate goal to have many of them cooperating and working on the project development.
- Good complex description of the proposal, explaining context of the project.
- In most of the cases there are objectives and measures placed in the proposal.
- There is a basic project plan, which makes it possible to control and assess.
- Expenses plan is prepared (some parts are missed but it looks good anyway).
Cons:
- From what I read there is a strong dependency on external resources:
----- I can see an assumption on involvement of other individuals (volunteers). It will be difficult to have people available and work in the long run - the beginning is always easy when there is a lot of enthusiasm. It gets really difficult after some time (volunteers work when they want and how much they want without being paid, every one of them have private life, problems, and families, own projects etc. - this is not a criticism but a fact taken from my experience).
----- There is no budgets secured for the conferences/events (flights, accommodations, fees, presentation tailoring). There are a lot of Dash projects started and driven at the moment (and will be even more) - all of them competing for the budget. It creates a big risk and could have a strong impact on the project success.
- Core team (and the foundation) have taken seriously the community feedback after the Transform PR project and moved focus to development of the software, project infrastructure, adoptions, partnerships, better communication and organization. This proposal is a step back to the "old direction" and creates difficulties in supporting one team by another. It looks like two DAOs will work on different areas (what is good) but it will be difficult to use the same resources by them (budgets, people). Considering our very limited resources it is not a perfect solution.
- Some goals have no measures listed (it can be easy fixed).
- The proposal is submitted for 4 months and timelines cover 3 months (probably I missed one month somewhere).
- We are working on the new website. Majority of SEO efforts might be lost when the new website is created and deployed.
Neutral:
- There is a strong dependency on the external vendor (Vanabex). I do not know the company but I have checked their website and there is a very small team there and some big clients. Please make sure they will be able to book enough time for Dash.
- Goals and expected results for the vendor are pretty much the same like for the previous one.
- I am not sure why we would need strategic alliances with others in the Internet of Things industry (listed in the budget part and Manila conf) - Dash have different goals and direction than they (they will rather support projects like Ethereum in my opinion).
Summary:
I find it a good proposal and project - you have done an excellent work with this! I have dedicated more space to describe concerns just because I wanted to be understood well (and not because they are bigger than pros
). There are really strong elements in the proposal and Dash needs such activities in my opinion.
After some analysis, considering all of the above, I would recommend to execute the project but in different time frame (when we could really dedicate maximum of our resources to it - e.g. when v12.1 is finished and v12.2 in the testnet). I think it is possible to successfully start and execute it now but the results might be much better when we are done with the current activities and everyone could fully support this project. Meantime everything could be well prepared and planned in more details. This is my personal opinion and advice.