Profile cover photo
Profile photo
Michael Babker
664 followers -
Army vet, IT geek, Open Source aficionado, posts are typically angrier than intended
Army vet, IT geek, Open Source aficionado, posts are typically angrier than intended

664 followers
About
Michael's posts

Post has attachment
For those who haven't had the opportunity, the slides from my #JWC13  session are posted.  Video was taken but isn't up just yet.

Post has attachment
The CMS is better than this application in an area!?  Not possible!  LOL
Photo

They haven't shared the schedule yet, but my session for the Joomla World Conference about this little project got accepted.  Since timelines and availability keep slipping to the right (and my burnout level keeps rising because of it), my hope is that we could be either beta or RC ready by then (November 8 for those not tracking) then I might let that announcement slip into my slide deck.

So where does everyone think we stand in terms of a v1.0 at this point?  In looking through the GitHub tracker, there are to me two items that block a 1.0 stable release: filter/sort capabilities (https://github.com/joomla/jissues/issues/1) and data validation (https://github.com/joomla/jissues/issues/48).  There's also the rehashed discussion on file uploads (https://github.com/joomla/jissues/issues/18) to sort out (be it for v1 or later down the road).  I'd like to aim for a beta tag in the next few weeks which means these last few items need to be addressed.

Post has attachment
Something we need to look at as we aim to finalize v1 is the DB schema.  What's here right now that's still relevant and what's leftover from the Platform architecture?
Photo

Post has attachment
So, what about a basic services API?

On the developer site, the stats pages scrape data out of Joomlacode to build those graphs for everyone to brag about how much they've done.  With bringing life back into the patch tester component, Brian made a good suggestion for the UI (see http://ux.joomla.org/forum/Miscellaneous-improvements---open-area/1671-patch-tester-ui#1698) about reporting statuses.  The component could do it theoretically, but this would need some sort of API to check in with.

Thoughts?

So we're currently using two ways to log stuff.  There's the code in \App\Debug\TrackerDebugger for error states and some debug stuff and \Joomla\Log being used by the hooks.  Quite honestly, I think the code +El KuKu wrote for the debug app produces a much more user friendly product than \Joomla\Log both in the raw file and viewing the logs via the site.  So, I vote we cut ties to \Joomla\Log and just use our debugger.  Thoughts?
Wait while more posts are being loaded