A Framework Becomes A Liability
When we created the Projectfork Framework, it was a conscious decision to step around the Joomla Framework. This was a very common move a couple of years ago, as many large components developed their own framework to provide what the Joomla Framework couldn't. Slowly we began to realize that we were devoting more time to framework maintenance than to Projectfork features. Bugs related to maintaining a massive framework took over the forum. Because of the framework maintenance and lack of resources, Projectfork features and extensions ground to a halt.
Moving Projectfork Back Into The Joomla Framework
With Joomla 1.7 and 2.5 soon, Joomla now offers all the features (and more) we were missing in Joomla 1.5 which prompted us to create the Projectfork Framework. If we move back into the Joomla Framework, we can focus on Projectfork again, and let Joomla do the heavy lifting.
Why We Halted 3.1
The main updates we had planned for 3.1 were centered around Projectfork permissions & ACL. These updates would require an all new learning curve. This would be totally fine if we didn't require a new learning curve in the next version, but that's exactly what would have happened. When we move back into the Joomla Framework, we'll rely on the core ACL and force everyone to relearn PF once again.
Native, Baby!
Moving back into the Joomla Framework allows Projectfork to be totally native. There are tons of benefits to this such as:
- native Projectfork menu items (link to any PF view from your regular Joomla menu)
- native Projectfork modules (place all the current "panels" in any of your module positions)
- native Joomla SEF (and 3rd party SEF)
- native Joomla install/manage/update system
- native Joomla terminology (components,modules,plugins instead of sections,panels,processes)
- easier integration with other extensions
- tons more...
We're Hoping Native Catches On
I personally hope this becomes a trend among popular Joomla components. The days of a completely different user experience in Joomla for every component need to end. Let's all stop going around Joomla and actually use it. Can you imagine a world where everything "feels" the same in Joomla? Project manager, shopping cart, social network, forum, gallery, etc. If everyone goes completely native the learning curve only occurs once! We can also share everything. One plugin for avatars across all components, one plugin for comments, etc. Native also applies to the admin site. If our administrator portion is native, the admin ux is consistent as well.
Possible Features & Extensions For Projectfork 4.0
We have much to discuss for where we're going. This list is by no means a guarantee, it's just some of the most interesting items to consider:
- PF API (to enable iOS/Android/Desktop apps & integrations w/ Gmail, Google Cal, iCal & such)
- More email notifications & settings
- Email replies to add comments
- Advanced Time Tracking Extensions
- Billing & Invoicing Extensions
- Help Desk Extensions
- Bug Tracking Extensions
- Git/SVN Integration Extensions
As I said, this list is by no means a guarantee, but you see where we can go if we're not focused on maintaining a framework.
Joomla!Platform = SaaS Projectfork (one day)
The Joomla!Platform project is split from the CMS now, and it will one day enable standalone web apps with all the power of Joomla, but without the extra overhead of the CMS. A great use of this will be a standalone Projectfork for those who just want the project management without the CMS.
The Platform is currently limited to CLI (command line interface), and is very young overall, so this isn't immediately possible. But it's definitely coming... Read more about the current status of developing on the platform over at Nicholas Dionysopoulos' blog.
We'll do a blog series to report after our planning meetings for your feedback.
