phpBB Weekly

Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

Download AAC Episode (26 MB) | Download MP3 Episode (50.9 MB)
Download Episode Chat Log

Episode Duration: 52:58
Panel Moderators: Steve Atkinson (stevemaury / Support Team) and Douglas Bell (webmacster87)
Panel Members: David Colón (DavidIQ / MOD Team), Will Hough (will_hough / Moderator Team), Raimon Meuldijk (Raimon / Styles Team), Yuriy Rusko (Marshalrusty / Management Team & Support Team), and Josh Woody (A_Jelly_Doughnut / Developer Team)

This special episode of phpBB Weekly is the recording of the phpBB Team Discussion Panel session which took place during Libertyvasion 2010 in New York City on Saturday, August 21. Support Team member Steve Atkinson moderated the panel, while Douglas Bell coordinated the questions asked from the audience and from phpBB Weekly’s special Libertyvasion channel (#phpbb-libertyvasion on irc.freenode.net) to make this an incredibly informative session covering a wide range of topics.

All six teams were represented on this panel, and the members weighed their input topics including how quick reply made it into phpBB3, how phpBB “competes” with other bulletin boards and social media, what it’s like to work with such a wide age-range of team members, how plans for phpBB4 will affect phpBB, how each of the members got involved in the first place, and much more.

Enjoy this great discussion panel, and plan to join us for our final live phpBB Weekly episode this Saturday for a complete Libertyvasion 2010 recap!

Session: Building Your Community by Libertyvasion 2010. The post has not been proof-read for spelling, grammar, or accuracy.

This presentation is more focused on your community, though it’s not a be-all end-all, there’ll be a Q&A discussion at the end.

It’s important to know why you are creating your forum. What services and benefits is it going to provide? What will people get out of your forum? Just saying “I WANT A FORUM!” is the wrong answer. How will your site be different? Who do you want to attract? Why would they come to you? How will people find your site? (Google will not magically drive people to your site.)

Don’t spam your site! People will ignore it and delete it, except for spambots, who will immediately come to your site.
Use signatures and website fields to promote your site. Buy ads (if appropriate) to drive people to your site. However, note that targeted campaigns will go much farther than blanket ones. Bringing new users to your site is the hardest part of getting your new community off the ground.

How will your board be organized? Don’t start with dozens and dozens of forums. Are there any legal issues with your site? How many people do you expect? How do you plan on expanding?

Most importantly: Why are people going to stay? Your site needs to have content and a reason for people to stay, or people will drift away to other sites. Your site will be a failure unless you can answer all of these questions.

Once you’ve established your site, some tips:
* Moderation — There is no one-size fits all approach to moderation. You do need to prepare rules, but be flexible in how you enforce them. Don’t hide what you expect out of users. (On phpBB.com, every page links to the rules page.) Make sure that your users know the rules. Know how to handle various situations; you will encounter all kinds of situations on your board, including: spam, competitor advertisements, profanity, flame wars, forum games, obnoxious avatars/signatures, banned users coming back, criticism of your site, escalating complaints (& chain of command for dealing with appeals), legal threats/action, and plenty of others.
The phpBB.com Moderator Team has an internal 24-page guide for handling situations, and a private forum for communicating on how to handle situations and ensure problems are being handled fairly or consistently.

Open mic offering suggestions of other issues to be aware of. Mentioned were the “holy trinity of flame topics”: politics, religion, and web browsers. Be aware of local laws that apply to your board, i.e. the COPPA in the United States.
Question asked — isn’t it all just common sense? It is, but there are lots of people that don’t do the right thing for what’s best for the community.

When you’re building your site, think about what your community wants, what it needs, and what can help it grow. Don’t install 55 MODs on a site that has only 5 members, where’s the value there?

Session: Titania: The Customization Database by Nathan Guse and Tom Catullo
Date/Time: Saturday 8/21 at 4:30-4:55 PM

This post contains my rough crib-notes from this presentation at Libertyvasion 2010. The post has not been proof-read for spelling, grammar, or accuracy.

The Customization Database is an application that has been in use since the retirement of Ariel (the previous MODs/Styles Database), and Titania now handles more than just MODs and Styles and has many more features.

Titania improved searching contributions greatly over Ariel, makes category listings more prominent, easier to access and navigate. Now offers screenshots and demo links more prominently, and for non-styles as well. Titania also makes previous revisions available to the public for download. Much more prominent Download button.

For authors, contributions can now contain more information (screenshots, co-authors, demo URL, etc.) and allows for updating/editing this information for the contributions. Each contribution now has its own Support and FAQ sections, and support topics are propagated to a single location for authors. No longer necessary to cram all support into a single topic within the MODs or Styles Releases forum.

Titania also brings automation to the MOD revision process, including automatic checks by the MPV (MOD pre-validator) and AutoMOD. Author can immediately see the result and make fixes immediately without waiting for validation.

Titania is very maintainable. The code is object-oriented and generally contained in classes, and is built to integrate seamlessly with a phpBB installation. Titania makes use of a similar hooks system that phpBB has. Requires no edits in phpBB to install it, despite its size.

Unlike Ariel, Titania’s code is not directly integrated with phpBB.com but is its own application. It has been released on Code Forge so that International Support Teams can use it on their own websites rather than having to build their own.

Q&A
Titania uses its own system to provide the individual support forums for contributions, and is completely standalone, although it does take advantage of phpBB APIs where necessary.

Session: Automatic MOD Installation: Then and Now by Josh Woody
Date/Time: Saturday 8/21 at 2:20-2:50 PM

This post contains my rough crib-notes from this presentation at Libertyvasion 2010. The post has not been proof-read for spelling, grammar, or accuracy.

Josh will be talking about the history of automatic MOD installation (not just pertaining to phpBB), up to what’s coming in 3.1.

GNU diff/patch is “older than a wild Yuriy (1970s)” and powers the automatic updater. Diff/patch is well-supported in the *nix world, but not-so-well supported in the Win32 world.
In phpBB, GNU diff/patch is completely functional, but misses several items that MODs use, such as metadata, new file copies are more difficult, and “do it yourself” non-file change instructions. It’s not easy to process by hand.

EasyMOD was 2002-03, the granddaddy of this for phpBB3. Originally written by Nuttzy99, later picked up by Jim (TerraFrost). Performed MOD file changes well, but that’s about it. Couldn’t handle custom styles or translations. Josh steps us through a sample MOD install of Nils’ April Fools MOD for phpBB2 using EasyMOD 0.4.0 beta.
No options to speak of in EasyMOD, most support questions revolved around initial setup, especially permissions.

The MODX transition began because the Text Template limited what EasyMOD could do. It was a verbose patch with some metadata, didn’t work well with translations and multiple styles, etc. MODX allowed the new AutoMOD features to exist (just not always in an obvious or friendly fashion, or equitably). Now Josh steps through a sample MOD installation with AutoMOD 1.0.0 — noxwizard’s EasyPortal for phpBB3. Still has some issues that are not intuitive.

The Ascraeus MOD installer has the following priorities: Fix the user interface, address the inequities (things you can’t do with AutoMOD though supported by MODX), and make the code more flexible. No screenshots yet because the UI isn’t available yet, so far only backend work has been done.
The new MOD installer will move closer to a wizard interface, and give the user all relevant prompts before installing the MOD. Demonstrates the process of installing “RMcGirr83′s Beer MOD”. First get to tell AutoMOD how to process styles, how to process languages, if this is an upgrade to an existing MOD or not, and then start the install.

Question: Will phpBB 3.1 will be supporting a language fallback? For example, if new English strings are added that don’t exist in German, will phpBB fall back to showing the English strings by itself? Answer is no, not feasible at this time because of how the language files are implemented. Not feasible to calculate whether or not to fallback on a string-by-string basis.

Will phpBB interface with phpBB.com and the customization database? Answer is maybe, but only if the feature can be completed in time for the Ascraeus release.

Session: phpBB “Ascraeus” 3.1: News for MOD Authors by Henry Sudhof
Date/Time: Saturday 8/21 at 1:30-2:10 PM

This post contains my rough crib-notes from this presentation at Libertyvasion 2010. The post has not been proof-read for spelling, grammar, or accuracy.

The phpBB3 code-base looks like a bunch of spaghetti code. (Showing a picture of spaghetti on the screen.)

phpBB 3.0 introduced modules (plug-and-play), but were limited to adding pages to the control panels, and is not well understood. There are also plugins, which work for the search, CAPTCHA, auth, and cache. However, the functionality of these varies, there are different non-uniform APIs, and it’s not well adopted. And there are also hooks which alter phpBB’s behavior, but these are mainly intended for wrapping phpBB within other applications. They are rather limited, and by-and-large have not been adopted. Instead, we are using MODs, which are glorified patchfiles, but have excellent adoption.

MODs aren’t necessarily bad. They provide unlimited expressive power, are simple to understand, have a shallow learning curve, have been adopted very well, are a well-documented format, offer good performance, and benefit from MOD Team audits. However, there is a non-uniform codebase, creating difficulties with maintenance, it impedes updating phpBB, can cause conflicts and side-effects, and are difficult to install, among other issues. (Yet another picture of spaghetti on the screen.)

phpBB 3.1 introduces hooks into the system, meaning that the phpBB code will call and run all functions hooked into particular places of execution in the code

In order to do this, the old hook system is going to have to be rewritten. “Hooks have to be fun.” They need to be able to resolve conflicts (within limits), allow for easy placement, and make it easier to implement hooks.

phpBB 3.1 will have “automagic” hooks, using PHP OOP methods. Examples of the under-the-hood code that enables these to work being shown.

Flavors: Injection, Validation, Callback registration, Event, System, Altering, Cron, and many others.
phpBB needs ideas of where to place hooks, help with the MOD installer in hooks, community support for this implementation, and lots of testing of these hooks.

Thanks that won’t happen in phpBB 3.1: Forms not built by any form API, nor will there be pretty URLs (URL rewriting).

Q&A
Douglas comments that hooks are a big step for making more pluggable MODs, and it’s the main reason why WordPress Plugins are as successful and as plentiful as they are. However, in order for the hooks system to be successful, MOD authors really need to share feedback on where hooks should be added within the phpBB 3.1 core.
Stefan asks about why phpBB isn’t deciding to adopt Symfony’s hooking system within 3.1 to help reduce the spaghetti code and make future transition easier: the main issue is that phpBB 3.1 still needs to support PHP 5.2.x.