Wedge

Yes, it's been 'fixed' in the past, but the point of regression for the issue that it seems to be was back in RC3, not recently.

SVN would confirm that, really. The last change to it was back in January, to fix version numbering, but the last non-versioning change was a typo fix back in November that manifested as a bug (separate bug, fixed just after RC4), then a change to it back in September for an optional OpenID 1.1 parameter.

Thing is, I think there's a problem where bugs are 'fixed' but no-one's retesting it to make *sure* it's fixed.

It was originally written for them (which is why the topic/ticket move code even exists, because it was their idea), but virtually everything from after 1.0 is stuff they don't need or want, with the exception of email notifications which they even hacked in for their own site (and 2.0 does so much better anyway). All of which is fine by me, they can use it if they like, or they can ignore it. But I wrote 2.0 mostly for me and some collaborators of mine, and I'm just nice enough to release it to the community, because it was stuff that was on the roadmap anyway, and this way I get it tested by people who aren't me and it gets tested in other peoples' non production environments before I inflict it on a real production environment.


There is a rumour circulating that the second SM project will be to fork SimpleDesk and turn it into SM Helpdesk (especially since I made it very clear last summer that if they wanted to adopt SD as an official project, they'd require another CLA from me because neither the document I electronically signed in the SD team boards, nor the SM CLAs I already signed cover it, and that is just never going to happen)

Them forking it is cool with me, it's under the BSD licence, so they're free to do just that if they like. Except there is no way on hell I'm going to contribute anything to them for it, anything I've done (and anything I would go on to do) goes to the SD project itself not them, and if they want to adopt that into SM, they can have a blast because honestly, I doubt it'll be developed since in the time I wasn't working on it, it was rather sort of inactive. The whole fandango is something of an exercise in how things should be done: I write the code, sometimes it works, sometimes it's buggy, and because no-one else is code reviewing, it leans towards being a bit buggy. But it's actively tested, and when I commit a fix, the testers actually re-test the fixes as well, which means it's confirmed as fixed, or sent back to be fixed again... can you imagine what would happen if this occurred on SM? It would shake things up somewhat.

http://www.simpledesk.net/development/ will attest to that - I was slowing down and left mid July last year, and rejoined mid March this year. And I've spent longer than I ever anticipated on it. But the result is worth it.

Still, if they do fork it, maybe someone will look after it properly, but I won't get my hopes up. (Though if they asked me to take it over, I'd be on the SMHD steering committee and thus have access to some of the sekrit stuff that goes on. Like I'd ever agree to that. Probably sometime after my private key was pried from my cold dead fingers.)

You know, it looks like they're enjoying playing at being all grown up and organised, but having no idea how to actually go about it.

It has a horrible habit of crash-and-burn when it hits memory limits, seeing how it invariably attempts to get the entire SQL dump in a variable first, which on a modest sized forum is going to be unpleasant.

Yeah, it's the OpenID bug, but as I just pointed out... that ain't new, nor even a surprise - it's been broken since at least RC3 (with the same reason)

I can understand the release being delayed if there's bugs they're going to fix. I just don't see much in the way of evidence of shit happening.

It's possible, but somewhat unlikely, I think.