Wedge

It's a matter of fine tuning, right now, my version works as:

• If it's the same day, it shows time stamps like "one hour ago", "five hours ago" and so on
• If it's yesterday, it shows "Yesterday, xx:xx
• If it's before yesterday, but less or equal than 7 days old, it shows the week day (e.g. Tuesday, 12:33).
• If it's older than that - well, it shows things like "three weeks ago"..

There is still room for improvement, for example, if the date is not from the same month but less than a year old, show something like "March, 27th, 18:00"

As for performance - modern JS engines are insanely fast, they can be used to implement a virtual i386 machine and run a Linux kernel in a browser :) - with decent performance, so converting a couple of time stamps shouldn't be much of an issue. I've tried hard by setting the refresh interval to one second (by default it's one minute and that's obviously enough) and opera.exe was still sitting at 0% cpu in task manager.

And of course, there is a profile setting to disable them completely. Some people simply don't like them, no matter how fine-tuned they are.

I'm going to do this as well in mine and it has little to do with copying, just with agreeing on the fact that it wasn't a very bright idea to include it in the first place. Seriously, how well are the PGSQL and SQLite layers tested in a real-world scenario?

PostgreSQL is, without doubt, a fine database, in some areas much better than MySQL, but its importance for forum installations is close to zero and I'm unsure about SQLite, which is also a very nice piece of software just not very important as a database for web applications.

I'll also kill support for PHP4, caching support for eAccelerator (doesn't make sense, because eAccel has been stripped from the required functionality) and Turk MMCache (doesn't make sense to support it when you're PHP5+). Furthermore, APC, XCache, memcached and the fallback method with disc caching should be enough options to cover the vast majority of installations.

I'm also considering wiping MySQL fulltext search, because it's pretty much useless when you have custom index (sufficient for most installations) and sphinx (for the big guys).

I hate legacy code that just sits there, making the code harder to read and maintain while doing absolutely nothing for 99% of all installations.

Really? They don't even allow anonymous checkouts?

I can understand the commit limitations as one should be very careful in handing out these privileges, but making anonymous read-only access limited just doesn't make ANY sense to me for an open source project. A strategy never heard of before in the open source world.That's just.... hm, better to say nothing...

Nah, really. It seems weird to me. I've been on a number of other open source projects and never really seen one where patches from community members were not welcome or in other words, where people didn't have access to the head branch or trunk code or whatever you name it.

If you're good enough, you can even get a patch into FreeBSD and this project is ruled by people who will reject anything that does not 100% fit their expectations and they have very high expectations and quality standards.

In most OSS projects, you can at least get a patch into review stage unless it fails the very basic checks/coding standards and looks broken at a first glance :)Regarding bugs...

Is there anywhere a comprehensive list of bugs in the 2.0 release code base?Well, makes sense. If you want to be closed or "semi-open" - fine, do so, nothing wrong with it as long as you don't tell anyone "we're an open source project".

Well, I'm afraid this is now dead forever. It was a nice theme while it lasted, but way, way, way too old and outdated by today's standards.

Short story: first of all, I'm here because Nao invited me to join.

Long story:

Many, many years ago, I was semi-active in the SMF community and released a theme for SMF 1.0 (yes, one point zero :) ) Later, I became occupied with other open source projects and basically stopped doing stuff for SMF, but my own forum was always running with SMF - many years with 1.0.x and I never bothered upgrading to 1.1, mainly because I had no time and 1.0 was working fine. When 2.0 became apparent, I decided to port the SMF AQUA theme I'd released years before for 1.0 but quickly lost interest after seeing all the bad things happening over at the SMF community. At this time, SMF's future didn't exactly look bright, so I stopped my work on the theme - nobody really wants to invest lots of time into a project threatened by extinction :)

About a year and a half later...

About 2 weeks ago, I started to play around with the 2.0 code base, realizing that it's now BSD licensed and there is no longer the risk of a dying project. Code is out, open sourced and this will never change, so it's safe to use it as a base.

I started with some work on the curve theme which I plan to rewrite completely, aiming for modern browsers (= HTML 5, jQuery, CSS3, IE8 minimum) adding a few Ajax features and a couple of relatively minor features.

Right now, I cannot exactly say which direction it will take. For the first part, it will stay closer to the SMF code base than Wedge, simply because I fear I don't have enough time for major changes in the core. Maybe later...

I plan to concentrate mostly on the end-user experience and adding a few (small) features of which I believe should be part of the core.

For the curios: Forum is here and it always runs on the current code, so it may change and break on a daily base and sometimes it may not even work at all. Since the forum is not very active (most of the old support boards for my other open source project(s) are now read only for quite some time and only there for reference), I can break it whenever I want :)

So yes, this is another project that qualifies as a SMF fork and it was only a couple of days ago, when I became aware of Wedge after Nao joined my site. We quickly figured that neither myself nor him knew about each other's project and I was a bit surprised for how long yours already exists.