Sunday, December 25, 2011
Just In Time For Christmas: Neddick TPR3 is Released!
Merry Christmas and Happy Holidays to all, from the Fogcutter team and Fogbeam Labs.
Saturday, July 23, 2011
New Batch of Quoddy Screenshots
https://plus.google.com/u/1/114301088526097505896/posts/3NVEkHxRVUY
Thursday, February 24, 2011
Fogcutter Update 02-24-2011
On the Quoddy front, the user-profile support has been radically improved and the UI for editing profiles has been cleaned up considerably. A preliminary preview release should be out soon. The main feature that we want to get in for a TPR1 release of Quoddy is basic "activity stream" support (think the "Wall" feature on Facebook.)
We've also started digging into the Mahout clustering code, and are starting to look into implementing some of the neat stuff that you can do with Machine Learning and Text Mining. An "auto tagging" feature and a better "related links" feature for Neddick are on the drawing board.
See the roadmap page for more on what's coming in the short-term.
Thursday, January 13, 2011
What's New With Fogcutter?
Since the last post, we've made a ton of commits to Quoddy - our Open Source Enterprise Social Networking platform (which is receiving most of the attention right now.) The most recent batch of changes have been focused on LDAP integration and User Profile editing.
Specifically, we've made all use of LDAP optional (the first pass at adding LDAP support actually assumed LDAP would always be present) by finishing up the "Local Accounts" support. We also added LDAP User Import, and we now fully support a mixed authentication mode where both "Local Account" users and (optionally) external LDAP users may log in. We've also started adding some (very) primitive support for editing User Profiles, and we added the very first UNIT TEST! Yes, the intent is to have a comprehensive test suite, but we'd been neglecting that stuff while doing a lot of exploratory programming earlier.
Yeah, it's considered bad form to write the code first and retrofit the tests, but in this case we think it's going to be OK. There isn't *that* much code to test.
On that note, after cloning the repo, if you want to see the current test coverage metrics, just
[user@somehost quoddy]$ grails install-plugin code-coverageand then
[user@somehost quoddy]$ grails test-app unit: -coverageto generate the coverage report.
Other changes: rev'd the Grails version to 1.3.6, and switched to using Groovy 1.7.6 for development.
And that about covers it. Check the TODO or the roadmap for more on what's coming down the pike.