phpBB 3.0
31.12.2005, 10:53 Apparement l'année 2006 devrait donner le jour à une version 3 de phpBB (olympus). Cette version devrait avoir un systéme d'authentification plus poussé, un systéme de syndication RSS pré intégré, un éditeur WYSIWYH (une sorte de mini Word) et beaucoup d'autres options... Une démo du futur phpbbhttp://area51.phpbb.com/phpBB/ Citation On behalf of all the phpBB Teams, I'd like to wish everyone a happy Christmas and New Year. Like everyone else, many of the team will be taking time off over the festive season so as to spend some time with their family and friends, so it may take slightly longer than normal for someone, be it team members or your peers, to reply to your query. As always, please help us to help you by reviewing the user guide and knowledge base before posting your query as the answer to many common questions can be found here. So what of the next version of phpBB? We did say back at the end of 2003 that 2004 will be the year of phpBB2.2 yet 2004 came and went without fanfare. The start of 2005 came the announcement that phpBB2.2 will required having its version number changed to phpBB3.0 (née Olympus) due to the huge number of changes under the hood. Those of you that have kept track of development will have noticed a flurry of activity in the last few weeks as Acyd Burn not only bashed heads, but also recruited DavidMJ and naderman as trainee developers whom showed their worth via the Community Coding Project. We will soon also need help from the community (yes, that's you!) to help us climb to the top of Olympus Mons so that everyone will be able to use the long awaited next generation of phpBB, though this is all I'm willing to say for now. We look forward to seeing you again in the new year where the real fun shall begin extrait de coding project # Unified/centralised event system - A trigger based system whereby admin definable "events" are fired upon specific conditions. This will allow for a good system for adding/removing users to groups upon certain post counts, changing/allowing/disallowing avatars, sigs, etc. etc. Such a system must overridingly be sensitive to performance (this could easily eat processor time if done badly) while being comprehensive in scope and capability. Good use of the caching and cron systems should help here. A well defined/designed admin interface is also essential which re-uses code wherever applicable to reduce complexity. Let me say this is a tough project to get right and we're obviously going to be quite tough when it comes to implementation. # Syndication system - One of the most popular requests for phpBB is a method to syndicate information. This project is intended to implement such a system. We're looking for full (and valid!) support of RSS/RSS2/ATOM. It needs to be able to syndicate various feeds, e.g. given forum/s perhaps even certain topics, limit access by IP, etc. This project should be relatively straightforward. # Canned moderator responses - In phpBB3 there exists an ability to save draft messages. This allows you to save a message for later completion. We are looking to extend this functionality to include canned responses for moderators. This would allow permitted moderators to write and save messages via the MCP (Moderator Control Panel) which other moderators could then use to send to members of the community. It should be written as an MCP module (which should strictly adhere to the current module implemention to enable easy transferal to the new module setup in future). This is again a relatively straightforward project. # Authentication system - At present phpBB3 uses a simple but reasonably capable authentication system (the source used to verify your username/password, not permissions which is entirely different). However it's not good enough Smile We are looking to change this system to a proper "module system". There are difficulties involved here in that we do and wish to continue to support alternative authentication schemes (other than the user/password stored in the users table) such as LDAP, Apache auth, other CMS/board/etc (Gallery, Wordpress, etc.). systems. This project should also examine and where possible introduce or propose the introduction of changes to the UCP system to allow "two-way" communication between the UCP and auth module. For example changing details in the UCP should offer (via the auth module) a way of altering those details in the source authentication system (if you get my drift!). This later area may require significant thought in terms of altering what already exists in the UCP without requiring a complete rewrite. Also I'd suggest you be or find someone with a good level of LDAP expertise. # Karma - This is a bane for us Very Happy Firstly what is Karma? Well karma for this implementation is a method of rewarding helpful members of the community. Such a system could allow for automatic (perhaps via the event system above) group addition for useful members, ability to use avatars/sigs/etc., ability to post in certain fora, etc. Some have suggested an ability to tag posts ala Slashdot may be useful too (in addition/instead of this pure "numerial system" . There is an ongoing sujet on this to be found here, you may want to look at modularising the system too to allow multiple algorithms to suit the many varied uses to which phpBB is put. This is a complex project that will require significant thought in implementation. Like events performance is king here. # Backup/restore with modular file transfer system - The current backup system deployed in phpBB3 is a step beyond what phpBB2 offered. However it would be nice to take it further still with support for all databases phpBB itself supports, further options ala phpMyAdmin (but without resorting to canabalising phpMyAdmin!). It would also be nice to allow users to upload/download backups via methods other than http. For example, ftp, scp, etc. Going further still a modularised system for file upload/download could be examined and utilised elsewhere within phpBB. Of prime concern here is security and compatability. # WYSIWYG editor - We are often asked for this funtionality but we've shied away. There are several issues with a WYSIWYG editor the two greatest of which are; wide cross-browser support (not just the top two but all the majors) and parsing of the submitted post text. The former is a very important issue which is now being addressed by various implementations but still problems remain. The second issue is important in terms of XSS and even just basic implementation. You'd be expected to find solutions to both problems here and ones in which performance (server and client side) doesn't suffer. Simply supplying one of the existing opensource standalone WYSIWYG solutions won't be enough to fulfill this mini-project! # Security and performance test suite - Although we do code with performance and security in mind (no matter what some may say!) it would be nice to have a suite of scripts which could test phpBB3 in an automated manner. This project is entirely external to phpBB3 itself (although coding standards must still be followed) and is intended purely for internal useage. Therefore it has the widest scope in terms of implementation. Personally I suggest only those familiar with security and/or performance testing look at this project. mumuri forum.ashots.org mumuri Messages : 13 307 27.03.2006, 12:49 Une version béta de olympus sortira bientôt, le but étant d'identifier les éventuelle bugs de la version 3.Citation Hi everyone, phpBB "Olympus", otherwise known as phpBB 3.0.0 is nearing its initial beta release and we decided to open our bug tracker for reporting issues with CVS now. The aim of the opening of the bug tracker is so that advanced users already having a current CVS copy working or those able to cope with installing and maintianing a CVS copy, may now report problems they encountered. We want to identify problems with "Olympus" now, before we release a public beta. This has the advantage of us being able to change the code without providing an update path and in turn then hopefully being able to provide an update path during the betas. For all of you not wanting to install a half-finished product (it is actually pre-alpha code still), we have compiled a list of features "Olympus" is having currently. We also strongly discourage the use of "Olympus" in live environments. Who should report bugs Everyone comfortable with manual database work, editing of PHP files and willing to help spot the most obvious bugs. What happens to reports about unfinished features Reports about unfinished features are most likely to be tagged as "Review Later" which means that we will revisit the bug report at a later stage. The same tag will be used for reports we are not able to handle "immediately" and need to revisit after having finished or cleaned up other parts of the code. Are there any items being more important? Since we develop with MySQL primarily, it would be nice if there are people competent with other DBMS than MySQL. For example a person testing "Olympus" with Oracle would help us greatly to identify SQL layout and syntax problems. The currently supported DBMS are: * Firebird (firebird) - Firebird 1.5+/Interbase 7.1+ * MSSQL (mssql) - MSSQL 2000+ * MSSQL through ODBC (mssql_odbc) - MSSQL 2000+ * MySQL (mysql) - MySQL 3.23+/4.0+/4.1+ * MySQL4 (mysql4) - MySQL 4.0+/4.1+/5.0+ * MySQLi (mysqli) - MySQL 4.1+/5.0+ * Oracle (oracle) * PostgreSQL (postgres) - PostgreSQL 7.3+ * SQLite (sqlite) If you are working with one of those DB's daily and also being competent in PHP, you are invited to contact me by PM too. We want to work close with these DB Experts to make Olympus a pleasure experience on every DB. Smile Are we able to report security related problems? Yes, we even ask for those reports - though please use our security tracker for reporting security related issues with "Olympus". Links * Olympus Bug Tracker * Security Tracker * Area51 - phpBB Development * Daily Snapshots/CVS Information * KB Article on how to use CVS * Non-exhaustive Olympus Feature List And when do we get the beta now? We hope the bug tracking phase to last at least a few weeks, since we need to finish some areas and features before we are able to release a public beta. Depending on the issues arising due to the reportings we may expand this further. Thanks everyone and happy reporting. mumuri forum.ashots.org mumuri Messages : 13 307