Hello,
please review the pending PRs and make a new release afterwards.
We are waiting for some quite important changes.
Thank you, Mathias
Hi @m-schaeffler - I'm assuming this is in reference to @flowfuse/node-red-dashboard.
We are very overwhelmed with work at the moment, and with Steve on holiday all of those PRs fall to me, but I also have many other responsibilities at FF.
We are hiring for a full-time Dashboard developer for a reason 
4 Likes
Hey @joepavitt,
I see that you are now reviewing my pull requests. Thanks a lot for that!
But to be honest I don't expect you to do that on a friday evening, after a hard week at work. If all users in our community - except from a minority of the well known active members - decide not to contribute at all and put a pile of 330+ issues in your backlog, then the result is that they simply need to wait until you have time. It is as simple as that...
So please review my pull request afterwards when you have time, and now enjoy your weekend with your familly. Like all users of your dashboard do... No need to hurry at all!
5 Likes
If to run one hard grooming over those there's maybe hundred or so. But even that doesn't gain any speed to target.
Kind of hard for me to figure out where the focus is. But as for big thing as the dashboard is it's rather understandable.
Complicated position for third party developers is the state of supportive functionality which is not communicated out too well.
Nevermind, the thing grows and the tempo lays on us so I shut up and digg into providing some goodies for it
1 Like
Care to expand here please? What can we provide to make this easier?
We have our Activity Tracker, for which "Up Next" items are the best place to start, or if you want to go a bit more free-reign, anything from the "Must Have", "Bugs" or "Should Have" in the Planning board would also be welcome PRs.
@BartButenaers I'm not even sure checks those, he picks out some issues he thinks he can tackle and builds, we're not going to dictate what volunteers want to spend their own time building/fixing in the project, if there is something you like the look of - dive in and give it a go - we'll always be grateful for the help
Just watching the long standing pull requirest about the storage handling and input property improvement, those are standard to follow but until nothing clearly stated it is kind of arbitrary. Not good.
The layout rules also are kinda users to figure out thus the third party has nothing to rely. Simple things like should the widget take the row height into the consideration. If there's no strategy it is hard to make bullet proof things to be widely usable.
Yes absolutely correct @joepavitt. I have to admit @hotNipi that I am not really looking at Joe's priority list, because it is all about free time. I should really really start working migrating my own nodes, but I can't Joe drawning in his backlog. That is programmed in my DNA, so can't get around that unfortunately.
So when I see something arriving that I "think" fits into my free time a bit, then I try to tackle it. Although I have to admit that most of the time unexpected things happen, making it more complex as I had expected. And most of the stuff requires CSS knowledge, and I don't have time to read about CSS so I skip those ones. Or if I had a heavy day at work (which has become the standard unfortunately), I also look for issues that are at least a 'bit' amusing for me to solve.
Of course this way of working results in a weird effect: some unimported issues get solved very quickly, while other important issues need to wait a long time. But that is the way it is. It is that or nothing...
Tip of the day: don't tell me (like here) that your issue is more important than all other issues from people that are waiting polite and patiently. Because that works counter-productive for my brain: in that case I certainly won't contribute to a solution...
4 Likes
