Read and agreed upon.
Bit more transparancy couldn't hurt the project.
Like for example the 'in your face' poll of doubling the pay is quite sudden and the timing of it is, in my opinion, ill chosen after a long period of forking and way too soon: we're not sure if the update fixed it all.
The problem is we don't know that well how much effort people have put in the fixes, not everyone reads the github technicalities, I sure don't.
The thing is that the time-keeping and prior announcing of things does not work, or more correctly has never happened. If you didn't join the channel something was talked about at a certain time, you always got the surprise after the fact.
The programming stuff is a different topic, some things are just not understandable if you aren't a programmer.
But even then they need to be explained. In part that happens here on steemit, but there is no reliability.
Part of the issue here is that someone has to step up to make those announcements. Who is going to monitor the channels constantly, and release info? Do you really think it's the best use of a developer's time to have them stop coding, flush their mental buffers, and post a status update daily?
Marcos posted weekly. Play by Play, minute by minute communication takes a dedicated communications resource. All GRC has right now are random people deciding to make posts here or there. Sometimes someone makes posts for several months at a time, and then they stop.
Consider what it would take to make you personally commit to that effort, long term. It's likely, that is a starting point for making it happen. Right now operations is pinned posts in slack. Does all of that need to be on the public wiki? Does there need to be a team of communicators? How do you authenticate that they are truly communicating on behalf of GRC?
The most simple things are often the most complicated to make happen.
Lately I've been trying to communicate the dev's work to the community more effectively in my new position. Let me know how I can improve. Current plans are weekly or every other week postings about dev happenings (unless there is an update that week which takes priority).
Yes, indeed, I thought the same. There is no reliability and that is bad.
This is not the "fault" of the volunteers, it is just how things work in a crowd of volunteers with no strict goals.
Maybe something like a Report "Development of the Month" could be Interresting to inform the User(The Devs write that anyway to get the Payout of the Fundation. So it only need to make it readable for normal User)
Good idea.
We should use the voting functionality to test the waters for different ideas. For example, instead of having a poll to raise the compensation from $30 to $60 we should have had a preliminary poll asking users what their ideal compensation is for devs, with choices for $30, $40, $50, $60 etc. prior to the official poll to raise compensation.
For example, yes. Or a different model. Or...
Yes, perhaps a different model for non-core tasks. Do we have official bounties still?
Should be, I didn't retract my 30K, even if I cant remember what the 10K one was about. Or was it only 5K?
2 years ago :D