> > We'll have to make an online Petition for HAZE to come back, but he only needs to
> > look at his Dev page to see how much people appreciated his work. We all need a
> > from things as he has been doing this for more than 10 years so when he decides to
> > come back he'll look at things from a nice & fresh perspective. He really did need
> > break & when he does come back he'll need to make sure he doesn't fall back into
> > working on MAME everyday.
> Funny how it's the users who can't seem to shut up about Haze, whereas the developers
> have more or less moved on and wish him the best, as we respect that real life takes
> precedence over free work.
> This aside, Haze stepping down will allow other developers, or potentially new
> developers, to start contributing more often. Where you see a prolific developer,
> other developers saw someone who, for various reasons, was able to take first dibs on
> quite a lot of additions that would have been the perfect fodder for new and
> inexperienced contributors to get their feet wet.
> In my opinion, it's unfortunate that he lamented the lack of anything simple for new
> developers to work on, when that situation was effectively one of his own creation.
> If you look at the list of commits to the git repository, you'll see that Scott
> "Tafoid" Stone is already dabbling in adding some of the newly-dumped clones, when
> previously he generally didn't touch the code. I wish Haze the best, and I do hope
> that he is eventually able to return to the project once he gets things in real life
> sorted out, but for now I see this as an opportunity for other people to start
> stepping up to the plate.
Yes, I'm hoping other people step up and fill in that gap.
The issue is it's not always a 'low pressure' role, there is an expectation that things get handled in a timely way, and verified to be correct etc.
Other times I've taken a step back things have either not been done, or been done badly.
When I joined the team in the first place there was a mountain of such 'low hanging fruit' that had simply been piling up with nobody even bothering to look at it.
But, as I've made quite clear, I can't go on doing this forever, so I guess it's important for others to see (and maybe find out the hard way) that things need handling in a timely fashion with a high level of aptitude.
There's a lot of basic work needs doing for some of the dumps we get to verify that they're correct, which is why I've always put many hours into creating skeletons complete with decoded graphics etc. for anything that came our way, it's easy to underestimate such work (and quite often other devs would ask me to take care of such tasks because I was more efficient at working it out than they were)
but yes, there are things there for people to work on, people need to start working on them, I hope that happens. The project makes it easier than ever to contribute with everything public facing on GitHub, and with the Dumping Union being an external entity new dumps are generally readily available; the structure of things makes for greater opportunity than it did in years gone by.
if enough users can sign up for the official forum that would help the process even more.
I don't really agree that it's unfortunate that I lamented a lack of action, I have left plenty of things in the past that I've considered 'easy' and even pointed people at them in the past, but nothing seems to happen. I actually specifically left the video slot game "fresh: Fruit Fresh (Italy)" because it's probably easy enough, and the name is fitting for a 'low hanging fruit' case ;-) There are quite a few others too tho.