Hey, this is your lucky day - giving negative feedback is my job 😈 (as a translation reviewer).
The reason why I'm not voting for the proposal is the payout in 11 days. I don't think this makes you look unreliable, I think it makes you look contrarian. If you want to change the fundamentals of how the DHF works, you'll have to convince a significant part of the community first. I'm sure it would be convenient to receive the money up front, but I haven't seen a good reason why we would agree, setting a dangerous precedent for future proposals. Working for a DAO is never going to be like a real job.
Receiving Hive Power from the fund is also something anyone would like, but not necessary for the success of the project. I'd also remove the travel but keep a 10k marketing/communication budget. Improving structured communication between Hive devs would be useful indeed.
Throwing around the names of RedHat and Mithril is only confusing me. Is this project technically related to Mithril.js at all? Certainly not for the beem upgrade? And what makes you think that you can achieve RedHat's level of professionalism?
Why is there only one developer in a team of eight?
I don't like the packaging of very different tools. I'm interested in Nectar and yourFrontend, the badge thing is not a priority, just nice to have, and the FiscalForge would probably benefit from cooperating with other teams.
While the HiveTools website looks nice, the yourFrontend service looks ugly and barebones - worse than hive dot blog. Will you add instructions and examples of how to apply style sheets to the feed?
And finally a feature request: as a Hive blogger, the microservice I need is a way to schedule future posts, in a way that's easier than running a cron job + beem. Currently I'm using PeakD for this, but I don't want to depend on them too much, and I'm not sure how many scheduled posts they allow.
you get all the votes. its saturday now but I will be taking notes and keep on posting!