Hello all,
From now on we will be using Bitbucket's Issue tracker for features, requests, bugs, etc issues.
Please from now on make any new bugs, features requests, etc only on the Bitbucket project!

I will work on it some more this weekend to get our issues transferred over. In the mean time if you wouldn't mind helping me by posting any of the issues you have, know about, or even reading over this forum for them I would appropriate it. (Lot of ground to cover, and I could use any help I can get these days)

Thanks.

(Last Updated 01/6/13)

Posted by Scrydan edit on 12/8/12

---

I changed quite a bit of things. So much the version is actually 2.6. But many of you knew that already.

I updated this list a bit to reflect changes I know I've done relating this list. We're quite on our way for 2.6!

For the full list of things I've done, stay tuned. It is a quite the list.

---

Hello Developers,

I figured I should copy-pasta my short term roadmap I have in mind for ABII's code base post 2.5.2.

So to reach 2.6, I will setup a similar situation to last time. However it's early to check often.

Criteria 1: Any remaining Legacy ABI features not currently ported and Key bugfixes/features

This will expand as we go. It will start with the unfinished ones from 2.5.1. I've also added to the list the topics that we've discussed implementing.

Legacy ABI (2/5)
*Photo Albums
*More detailed user sidebar on posts
*Favorites (@Scrydan, working on it - plans to combine it with "`thumbs`")
*Show who last edited a post/thread last. (When viewing older revisions show the person who made that edit). (@Scrydan)
*Ranks Listing page (WTF that's a staple of an AB) (@Scrydan)

New Features (2/3)

*Improved Mood Avatar/Avatar System (@Gywall) (It needs more polishing but it's done.)
*Extended Profiles system (@Scrydan, DJ Bouche)
*New/Revised Forum Editor based upon the permission system (@Scrydan)

Bug Fixes/MISC (1/5)
*Make sure announcements can't be forum ignored
*Improve 'read' system. Currently it is hit or miss. Also ew forums currently start marked unread. Have them start read
*Fix that darn Birthday message! (@Gywall, Mostly complete)
*Finish the Badges/filter/effects system.
*Expand on the sprite system to allow badges to have an effect.

Optional, but I'd like to see it... (3/9)
*Show when something has been edited "like New does but "Updated" or "Edit" "
*Show "NEW/EDITED" on Announcements (see NEW! marker for announcements)
*Implement the events system for the calendar.
*Admin Panel and setting system (@Scrydan)
*Add a field in post revisions to allow someone to put a "reason for edit". (@Scrydan)
*ABI used to have "Posts by hour/forum/etc" ABII has a bunch of PNG generated info for users that's not tied in. We could combine it to a "User Stats" Page off of user's profile.
*"Magic Firewall" (@Mega-Mario knows what this means)
*(AB1 Legacy): Avatar Library?
*Fix PoRA to work more like a post. It doesn't support filters (smiles, @Emuz etc), and implementation of a preview system is needed as well. (@Scrydan)

Total: (8/22)

Criteria 2: Functional Implementation of Acmlm's RPG Battle System

Sometime in February Acmlm provided me with the code for his SDL client that was meant to be a part of the board's RPG system. The code is in C and should compile for every major platform. I know little about it myself, but from what I gathered it has the support for a chatroom powered by the board. We'll have to make some changes board side as well. For example the RPG stats will need to track any damage member too and reflect it in the RPG stats. For the short time Kafuka would have it exclusively it would actually be something that could draw people to the board. This one is a large ticket item since we would have discuss, and we would basically have to build a game from almost scratch.

---

The goal is to reach 2.6 by very early Feb. We will preform off site testing on @Scrydan's test board. We will than migrate it over to Kafuka. After that the goals will be updated and we will work on polishing administrative features, the installer, documentation, adding important smaller features, and preparing for the public source release. 2.6.1 will be the first version on public git (github or bitbucket.. which ever we end up going with).

Please check off any of these items here and in the main TODO when you complete one... don't want to have too much more of a list-mess than we already do.

Goals have been reached for version number change, but there are a few things we can work on before moving the branch into live.

---

Hello Developers,

I figured I should post my short term roadmap I have in mind for ABII's code base. Epele has been doing a lot of little things to help out, so we're moving forward for sure.

I figure for 2.5.1 we would make the roadmap dead simple; to reach .1, one of two juxtaposed feature sets must be reached. They are juxtaposed in that one is a forward looking, and the other is legacy.

Criteria 1: Group and Permissions Manager/Editor (Mostly complete)

This is an important one. While we will be able to make due with SQL and the foundation lib/manual control system (ie: whateveritis.php?something=5&anotherthing=23) we really should implement it. This would allow us to really have a release version any time we would like. (Not saying that'll be soon but remember an underlining goal is to make ABII an open source project, once it is more user friendly) Personally I think this is a task would better tackled by DJ Bouche and knuck, but that doesn't mean we have to wait for them to work on it either.

Criteria 2: Any remaining Legacy ABI features not currently ported and Key bugfixes/features

This one is a bit easier to do as it's not one giant feature, but a bunch of little ones. I know knuck mostly built, but lose a post radar system. Hopefully he can rebuild what he had ( knuck?)

Legacy ABI (2/3)
*Photo Albums
*Post Radar (accepted by: knuck)
*Readd an All Staff sort to the member list (ABII feature)

Bug Fixes/MISC (4/6)
*Make sure announcements can't be forum ignored
*New forums currently start marked unread. Have them start read
*Using GFX Lib to show Number of new Post on index.php
*Update the FAQ from scratch. We have many more features now! (Well this is going to happen anyway)
*Fix the bug that shows forum names if they are accessed directly on forum.php via forum ID number. PRIORITY (see here)
*Fix whatever method was used by LordTrevor is post in a private forum. PRIORITY(here)

Optional, but I'd like to see it... (0/2)
*Show when something has been edited "like New does but "Updated" or "Edit" "
*Show "NEW/EDITED" on Announcements (see NEW! marker for announcements)

Total: (6/11)

If one of the two is met I will change the version number to 2.5.1, and the remaining goal list will be moved into 2.5.2's list.

This should give us a smaller, more manageable set of goals to accomplish.

Please check off any of these items here and in the main TODO when you complete one... don't want to have too much more of a list-mess than we already do.

The official development room is #abdev and it's pass is currently nopassword

Anyone who reads this message is welcome to join the room even if you are not interested in code development, but keep in mind it is not a replacement for the staff room as it will have non-staff in it.

This room is for code and feature talk only, the board discussions of members, staff, and Kafuka specific should remain in the main staff room.

Blah blah blah,

-Emuz