tag:blogger.com,1999:blog-45220773664968573922024-03-13T22:34:20.130-07:00Fogcutter DevAnonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-4522077366496857392.post-41441014012394564392013-08-25T20:19:00.002-07:002013-08-25T20:47:05.124-07:00ANN: Fogcutter Suite Synchronized Release - 418 Teapot<p />
<p>
After what seems like an eternity of development work, we are proud to announce the first ever Fogcutter Synchronized Release - "418 Teapot". Named after the (in)famous <a href="http://en.wikipedia.org/wiki/Hyper_Text_Coffee_Pot_Control_Protocol">Hyper Text Coffee Pot Control Protocol</a> as a tribute to the amount of caffeine it took to get here, this synchronized release features the simultaneous release of <a href="https://github.com/fogbeam/Quoddy/releases/tag/v0.0.0-tpr1">Quoddy v0.0.0-tpr1 (Tech Preview Release 1)</a>, <a href="https://github.com/fogbeam/Neddick/releases/tag/v0.0.0-tpr4">Neddick v0.0.0-tpr4 (Tech Preview Release 4)</a>, and <a href="https://github.com/fogbeam/Hatteras/releases/tag/v0.0.0-tpr1">Hatteras v0.0.0-tpr1 (Tech Preview Release 1)</a>.
</p>
<p>
The entire team has worked incredibly hard, and we're thrilled with the progress we've made, and happy to release the new capabilities embodied in these releases, to the public at large. We're still not finished and we have <b>tons</b> of plans for each of these projects, as well as <a href="">Heceta</a> so there will be even more awesomeness coming down the pipe in the days, weeks and months to come. But for now, here's a quick overview of what each project is, and where each is at:
</p>
<h3>Neddick</h3>
<p>
Neddick is an Open Source Information Discovery Platform, based on Groovy & Grails, and making up one component of the <a href="http://code.google.com/p/fogcutter">Fogcutter Suite</a>. Neddick shares an approach to information discovery with consumer facing websites like <a href="http://www.reddit.com">Reddit</a>, <a href="http://www.digg.com">Digg</a>, and other aggregator applications. You could call Neddick "Reddit for the Enterprise" but that would be oversimplifying a bit. Neddick is intended mainly for organizational use and therefore has features that Reddit lacks, but, in turn, lacks certain things that Reddit has. But Reddit was absolutely our inspiration for Neddick and you'll notice the commonality almost immediately.
</p>
<p>
Relative to Reddit, Neddick adds features like:
<br />
<ul>
<li> Channels can subscribe to RSS feeds - any "channel" in Neddick (roughly equivalent to a Sub-Reddit on Reddit) can link to 0 or more RSS feeds, and the channel will automatically be populated from those feeds on a scheduled basis.
</li>
<li> Tags - Neddick supports the application of arbitrary tags to entries, and provides each user a view of the tags they have used, to enable rapid access to specific content.
</li>
<li>Channel Filters - Filters allow you to filter your view of a channel based on criteria including: body keyword, title keyword, score, and tags.
</li>
<li>More powerful "sharing" capability - Neddick supports sharing content by email, XMPP, and HTTP POST.
</li>
<li>
ActivityStrea.ms support - Neddick can HTTP POST entries to remote endpoints in <a href="http://www.activitystrea.ms">ActivityStrea.ms format</a>. This is how we built our integration with <a href="http://code.google.com/p/quoddy">Quoddy</a> - the Enterprise Social Network component of the Fogcutter Suite.
</li>
<li>
Channel Triggers - Triggers allow a user to specify actions to occur when Entry related events occur which match criteria which may include: A new Entry is posted which matches a body keyword or title keyword, an Entry is voted up past a specified score threshold, or a specified tag is applied to an Entry. Trigger actions include sharing via email, XMPP and HTTP post, and in future releases will be extend to include sending JMS messages, launching workflows via BPM integration, and running user provided scripts.
</li>
</ul>
</p>
<p>
Technology Preview Relese 4 (TPR4) adds substantial new functionality, and many bug fixes, compared to the previous TPR3 release and provides the foundation for our <a href="http://code.google.com/p/neddick/wiki/Roadmap">future roadmap</a> and the forthcoming fully certified and supported <a href="http://fogbeam.com/neddick_enterprise.html">Neddick Enterprise</a> from <a href="http://www.fogbeam.com">Fogbeam Labs</a>.
</p>
<h4> New Features</h4>
<p>
<ul>
<li> Access control using Apache Shiro - Shiro provides the capability to implement fine grained, role-based access control.
</li>
<li> Private Channels
</li>
<li> Aggregate Channels
</li>
<li> Channel Filters
</li>
<li> Channel Triggers
</li>
<li> "Share to Quoddy" via HTTP POST using ActivityStrea.ms protocol
</li>
</ul>
</p>
<h4>Bug fixes & enhancements</h4>
<p>
<ul>
<li>Complete UI refresh - the entire UI has been reworked to be much cleaner, and to be consistent with Quoddy and the other components of the Fogcutter Suite.
</li>
<li>Update Grails to Grails 2 - The previous code base was built on Grails 1.3.7. We've moved to Grails 2.2.3 now.
</li>
<li>Update Groovy to Groovy 2 - along with the move to the new Grails, we've also updated to Groovy 2.1.5
</li>
<li> New "Share" dialog - the UI element for the "share entry" feature has been completely rebuilt and is cleaner and supports new functionality.
</li>
<li> Bug #94 - Edit Channel Properties page is broken
</li>
<li> Bug #51 - Problem with excessive file handles - probably a file handle leak
</li>
</ul>
</p>
<p>
To learn more about Neddick visit the Project Homepage at <a href="http://code.google.com/p/neddick">http://code.google.com/p/neddick</a>
</p>
<h3>Quoddy</h3>
<p>
Quoddy is an Open Source Enterprise Social Network, based on Groovy & Grails, and making up one component of the <a href="http://code.google.com/p/fogcutter">Fogcutter Suite</a>. Quoddy shares a common "look and feel", and substantial functionality, with consumer facing Social Networks like <a href="http://www.facebook.com">Facebook</a> or <a href="http://plus.google.com">Google+</a> as well as proprietary Enterprise Social Network products like the products from <a href="http://www.jivesoftware.com">Jive Software</a> and <a href="http://www.yammer.com">Yammer</a> among others. You could call Quoddy "Facebook for the Enterprise" but that would be oversimplifying a bit. Quoddy is intended mainly for organizational use and therefore has capabilities which make it uniquely suited to provide the social fabric to support organizational knowledge sharing, knowledge transfer, collaboration and decision support.
</p>
<p>
Relative to consumer Social Networks and other Enterprise Social Networking products, Quoddy adds features like:
<br />
<ul>
<li>Calendar Feed Subscriptions - Quoddy supports subscriptions to any calendaring server which provides an iCal feed, so you can see your upcoming events rendered in your feed alongside other important events. Future releases will support CalDAV and interactive editing of Calendar Events from right in the stream.
</li>
<li>RSS/Atom Feed Subscriptions - Quoddy supports subscriptions to any arbitrary RSS feed, so you can find crucial information in your feed. Subscribe to internal blog servers, document management systems, wikis, and any other repository which provides RSS, or subscribe to your favorite blogs, Google Alerts, and other external information sources.
</li>
<li> Business Events Subscriptions - using the <a href="https://github.com/fogbeam/Hatteras">Hatteras</a> Business Events Subscription engine, Quoddy allows users to define subscriptions to business events right off of the enterprise SOA/ESB backbone. Find out exactly what is going on in your enterprise, in real-time with Quoddy and Hatteras.
</li>
<li> BPM Integration - Quoddy supports subscribing to User Tasks from BPM / Workflow engines. We currently only support Activiti, the leading Open Source BPM offering, but support for other workflow products will be coming in future releases.
</li>
<li> Fine-grained User Stream definitions. Quoddy provides robust support for creating different "user stream" definitions, which filter content by type, source, group, or other criteria, and makes it trivially easy to quickly change the current Stream. For example, you may tke a quick peek at an enterprise-wide view of all the activity from every user, and then quickly switch back to a personalized view which includes only your BPM User Tasks. Quoddy emphasizes putting *you* in control of the content which is rendered in your stream, helping avoid information overload.
</li>
<li><a href="http://activitystrea.ms">ActivityStrea.ms protocol</a> support using REST. Quoddy exposes a HTTP interface for external systems to post ActivityStrea.ms messages. This allows our integration with <a href="http://code.google.com/p/neddick/">Neddick</a> as well as other 3rd party products.
</li>
</ul>
</p>
<p>
Technology Preview Release 1 (TPR1) is the first Quoddy release and provides a solid foundation for our <a href="http://code.google.com/p/quoddy/wiki/Roadmap">future roadmap</a> and the forthcoming fully certified and supported <a href="http://fogbeam.com/quoddy_enterprise.html">Quoddy Enterprise</a> from <a href="http://www.fogbeam.com">Fogbeam Labs</a>
</p>
<p>
To learn more about Quoddy visit the Project Homepage at <a href="http://code.google.com/p/quoddy">http://code.google.com/p/quoddy</a>.
</p>
<h3>Hatteras</h3>
<p>
Hatteras is an Open Source Business Events Subscription Engine, written in Java and making extensive use of <a href="http://camel.apache.org">Apache Camel</a>, which makes up one component of the <a href="http://code.google.com/p/fogcutter">Fogcutter Suite</a>. Hatteras works with <a href="http://code.google.com/p/quoddy/">Quoddy</a> to provide the capability for users to create Subscriptions to Business Events on the organizations ESB infrastructure. Hatteras connects to Quoddy, downloads all defined Subscriptions, and then listens for matching messages. Messages which match a Subscription are persisted to an XML database and Hatteras then sends a notification to Quoddy which creates a Subscription Item record which can be rendered in the user's stream. Quoddy and Hatteras thereby provide seamless access to important business events, alongside other import pieces of content the user has selected.
</p>
<p>
Future versions will focus on better administrative tools, and more hooks to provide interoperability in your unique environment. Over time, Quoddy, Hatteras and other Fogcutter products will add a powerful Event Stream Processing / Complex Event Processing capability to correlate events and provide deep analysis for powerful business insights. Over time, we will surface the capability to provide correlation between Events, People, and Content (Documents) and will offer the ability to quickly navigate in any direction, between the nodes in a graph of related entities which have causal, topical, or temporal relationships with each other.
</p>
<p>
To learn more about Hatteras visit the Project Homepage at <a href="https://github.com/fogbeam/Hatteras">https://github.com/fogbeam/Hatteras</a>.
</p>
<p>
Used together, the components of the Fogcutter Suite provide powerful capabilities to solve real-world business problems involving the creation, transfer, and re-use of knowledge within the organization, and enable the fingertip access to relevant contextual information needed to foster meaningful collaboration, support better and faster decision making, and provide organization-wide "situational awareness".
</p>
<p>
Of course this release by no means marks the completion of any of these projects. Our roadmap for each includes a tremendous amount of new functionality and enhancements. Follow this blog, or our <a href="http://code.google.com/p/quoddy">twitter account</a> for the latest updates and news as we continue to build a kick-ass suite of tools for managing information and knowledge.
</p>Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-86029622162182255842012-02-12T18:38:00.001-08:002012-02-12T18:39:01.984-08:00Screenshot of the new polymorphic event stream<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-JYYIP8qE6Is/Tzh3ttNCJjI/AAAAAAAAACg/cUxeJpueMts/s1600/quoddy_polymorphic.png"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 200px;" src="http://3.bp.blogspot.com/-JYYIP8qE6Is/Tzh3ttNCJjI/AAAAAAAAACg/cUxeJpueMts/s320/quoddy_polymorphic.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5708444154804184626" /></a>Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-19784500067011332192012-02-12T18:16:00.001-08:002012-02-12T18:25:37.599-08:00Quoddy is getting a polymorphic event stream!<p /><br />The big news from <a href="http://code.google.com/p/quoddy">Quoddy</a> land currently is that support for polymorphism in the event stream is largely in place. "What," you might be asking, "does that mean, exactly?" Well, simply put it means that different "kinds" of events can show up in the event stream now, and each event will render (display) differently (and appropriately) based on it's attributes. <br /><p /><br />For example, one event might be a simple text based status update from a friend. That will display the words the friend wrote, their profile avatar and the time they posted and that's about it. But the next event in the stream might be a link to a scheduled event from your <a href="http://www.meetup.com/">Meetup.com</a> iCal feed. Since it's a calendar event, it will render with a an <a href="http://en.wikipedia.org/wiki/ICalendar">iCal</a> icon, the start date/time of the event, the end date/time of the event, the location, and a hyperlink to the Meetup.com event.<br /><p /><br />Similarly an event might be a document shared from Google Docs or something, and it would, again, render seamlessly into the event stream, but with the exact details, links and controls that are appropriate for the event. This is really slick stuff, and coupled with AJAX callbacks to the server, allows us to embed any manner of interactivity right into the event stream.<br /><p /><br />Somewhere down the road we might look at incorporating <strike>Google</strike>Apache <a href="http://incubator.apache.org/wave/">Wave</a> functionality here, so you can do collaborative editing "in place" from the stream.<br /><p /><br />We'll have some screenshots of this stuff up soon.<br /><p />Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-43398525102210818132011-12-25T04:57:00.000-08:002012-08-18T22:43:24.526-07:00Just In Time For Christmas: Neddick TPR3 is Released!<a href="http://code.google.com/p/neddick/">Neddick</a> Technology Preview Release 3 (tpr3) is available, just in time for Christmas! See <a href="https://github.com/fogbeam/Neddick/tree/tpr3">https://github.com/fogbeam/Neddick/tree/tpr3</a> and enjoy!<br /><br />Merry Christmas and Happy Holidays to all, from the Fogcutter team and Fogbeam Labs.Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-51534447317136654802011-07-23T18:39:00.000-07:002011-07-23T18:41:01.599-07:00New Batch of Quoddy ScreenshotsBelieve it or not folks, progress is being made on the Quoddy project, and the progress over the last 2-3 weeks has been substantial. I've just posted a big batch of screenshots over at G+. Check 'em out here:<br /><br /><a href="https://plus.google.com/u/1/114301088526097505896/posts/3NVEkHxRVUY">https://plus.google.com/u/1/114301088526097505896/posts/3NVEkHxRVUY</a>Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-7673915426803748592011-02-24T19:33:00.001-08:002012-08-18T22:35:18.121-07:00Fogcutter Update 02-24-2011Activity around Fogcutter has been frantic since our last update. Neddick release <a href="https://github.com/fogbeam/Neddick/tree/tpr2">TPR2</a> was finally <a href="http://freshmeat.net/projects/neddick/releases/328306">released</a> and that code has been pushed to the demo server. TPR2 features UI improvements, bugfixes related to the tagging feature, the introduction of scheduled jobs, and the addition of scheduled jobs for rebuilding the entry cache and populating channels from RSS feeds<br /><br /><br />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.)<br /><br />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.<br /><br />See the <a href="http://code.google.com/p/fogcutter/wiki/Roadmap">roadmap page</a> for more on what's coming in the short-term.Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-61530767429617453372011-01-13T19:04:00.000-08:002012-08-18T22:42:53.921-07:00What's New With Fogcutter?<p /><br />Since the <a href="http://fogcutterdev.blogspot.com/2010/12/opensocial-working-sort-of.html">last post</a>, we've made a ton of commits to <a href="https://github.com/fogbeam/Quoddy">Quoddy - our Open Source Enterprise Social Networking</a> 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. <br /><p /><br />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. <br /><p /><br />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.<br /><p /><br />On that note, after cloning the repo, if you want to see the current test coverage metrics, just <pre>[user@somehost quoddy]$ grails install-plugin code-coverage</pre> and then <pre>[user@somehost quoddy]$ grails test-app unit: -coverage</pre> to generate the coverage report.<br /><p /><br />Other changes: rev'd the Grails version to 1.3.6, and switched to using Groovy 1.7.6 for development. <br /><p /><br />And that about covers it. Check the <a href="https://github.com/fogbeam/Quoddy/blob/master/TODO">TODO</a> or the <a href="http://code.google.com/p/quoddy/wiki/Roadmap">roadmap</a> for more on what's coming down the pike.<br /> <br /><p />Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-28728668744386437022010-12-23T00:48:00.000-08:002010-12-23T01:05:07.669-08:00OpenSocial working (sort of)!The first primitive bit of <a href="http://www.opensocial.org/">OpenSocial</a> support is now wired into <a href="http://code.google.com/p/quoddy/">Quoddy</a>. Don't believe me? Fine, here's the first <a href="http://imgur.com/1G9Mx">screenshot</a>:<br /><br /><p><br /><a href="http://imgur.com/1G9Mx"><img height="365" width="520" src="http://imgur.com/1G9Mx.png" /></a><br /><br /></p>Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-13824190468990706192010-12-22T17:32:00.001-08:002012-08-18T22:36:11.817-07:00Fogcutter Update 12-22-2010Since our <a href="http://fogcutterdev.blogspot.com/2010/11/screwpile-update-12-01-2010.html">last update</a>, a lot of work has gone into <a href="http://code.google.com/p/quoddy">Quoddy</a>. The latest code includes support for using LDAP for user account information, has support for creating and listing "friends" and "followers" and has some primitive <a href="http://en.wikipedia.org/wiki/Activity_stream">activity stream</a> stuff in place... and to top it all off, work has begun on adding <a href="http://www.opensocial.org/">OpenSocial</a> support using <a href="http://shindig.apache.org/">Apache Shindig</a>. The OpenSocial stuff isn't finished by any stretch of the imagination, but I hope to be able to deploy and render at least a "hello, world" <a href="http://code.google.com/apis/gadgets/">Gadget</a> sometime tonight / tomorrow morning. <br /><p /><br />To take a look at the latest changes, check the <a href="https://github.com/fogbeam/Quoddy">Quoddy repo on GitHub</a>.<br /><p />Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-1054811768722672732010-11-30T21:01:00.001-08:002012-08-18T22:37:01.230-07:00Fogcutter Update 12-01-2010Not a lot to report since last time... I (Phil) have been in more of a "research" mode than a "coding" mode lately, trying to get more up to speed on some of the theoretical stuff vis-a-vis <a href="http://en.wikipedia.org/wiki/Information_retrieval">Information Retrieval</a>, <a href="http://en.wikipedia.org/wiki/Network_science">Network Science</a> and <a href="http://en.wikipedia.org/wiki/Evolutionary_computation">Evolutionary Computation</a>. But expect some progress on Neddick - at least - in the near future. <br /><br />In the mean-time, take a gander at some of the cool stuff that's going on over at the <a href="http://www.apache.org">ASF</a>. A lot of new projects are showing up there, that may be useful for the ScrewPile projects. In particular, there's a lot fo Semantic Web related activity going on, as well as some Content Management stuff. Check out <a href="http://incubator.apache.org/stanbol/">Stanbol</a>, <a href="http://incubator.apache.org/chemistry/">Chemistry</a>, <a href="http://incubator.apache.org/clerezza/">Clerezza</a>, and note that <a href="http://wiki.apache.org/incubator/JenaProposal">Jena is becoming an Apache project</a>. Oh, and there's the little thing of <a href="http://en.wikipedia.org/wiki/Google_Wave">Google Wave</a> going down the path of <a href="http://wiki.apache.org/incubator/WaveProposal">becoming an Apache project</a> as well. Even if you were one of those people who didn't "get" Google Wave, take a minute and look at the technology (<a href="http://en.wikipedia.org/wiki/Operational_transformation">operational transformation</a>) behind it... this is some pretty cool stuff.<br /><br />So, yeah, definitely a LOT of cool stuff going on these days in Apache land, SemWeb land, and - hopefully soon - Fogcutter land.Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-84960018712612887972010-07-25T20:36:00.000-07:002012-08-18T22:38:18.365-07:00Fogcutter update for 07-25-2010So, what's new since <a href="http://fogcutterdev.blogspot.com/2010/07/whats-new-with-screwpile.html#comments">last time?</a> Well, not everything one might have hoped for, but a few Neddick bugs have been fixed at least, and progress continues on. We still hope to have Neddick TPR2 out by the end of August, and maybe a solid start on Heceta.<br /><br />Specifically regarding Neddick, since last time, the bugs that have been resolved are: <br /><br /><strike><a href="http://dev.fogbeam.org/bugzilla/show_bug.cgi?id=12">Bug #12 - Make "tag" box work when pressing ENTER]</a></strike> - FIXED<br /><br /><strike><a href="http://dev.fogbeam.org/bugzilla/show_bug.cgi?id=8">Bug #8 - Get arrows for up/down vote links</a></strike> - FIXED<br /><br /><strike><a href="http://dev.fogbeam.org/bugzilla/show_bug.cgi?id=25">Bug #25 - Create scheduler mechanism for asynchronous updates</a></strike> - FIXED<br /><br /><strike><a href="http://dev.fogbeam.org/bugzilla/show_bug.cgi?id=35">Bug #35 - Need scheduled job to rebuild entrycache on some periodic basis</a></strike> - FIXED<br /><br />The scheduled task stuff turned out to be pretty simple, thanks for the excellent Quartz Plugin for Grails. Now the EntryCache gets refreshed once a minute. Additionally, even though it wasn't in the bug list as a discrete bug, a problem with recalculating the score of an entry - after an upvote was removed - has been fixed.<br /><br />As to what's coming next... mainly work on the next Neddick TPR, so see the Roadmap for details. The bugs on the roadmap page are now sorted (more or less) by the order in which we intend to attack them, so it should be pretty easy to tell where things are going.<br /><br />And that's a wrap, for this week.Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-10231845877437709342010-07-13T18:29:00.001-07:002012-08-18T22:40:01.276-07:00What's new with Fogcutter?Since the last post, all sorts of stuff has gone on! Things are progressing nicely, especially with <a href="http://code.google.com/p/neddick">Neddick</a>. Since last time we've registered each of the Fogcutter subprojects with sited dedicated to F/OSS, such as Ohloh.net, Advogato.org, and Freshmeat.net. Source code has been pushed to GitHub and the Google Code SVN repository. We've gotten Bugzilla and IceScrum installed and configured, and we have a live Neddick demo site up and running. Additionally, documentation has been written on our development process, and some roadmap documentation has been put together. We've also put together a site at Fogbeam.org dedicated to Fogbeam's open source activities.<br /><br />Not a bad week's work, eh?<br /><br />So, for your browsing convenience, here are links to all the new hotness:<br /><br /><a href="http://spdemo.fogbeam.org:8080/neddick1">Neddick demo site</a><br /><br /><a href="http://www.fogbeam.org/">http://www.fogbeam.org/</a><br /><a href="http://dev.fogbeam.org/">http://dev.fogbeam.org/</a><br /><a href="http://dev.fogbeam.org/bugzilla/">Bugzilla</a><br /><a href="http://dev.fogbeam.org:8080/icescrum-web-R2/">IceScrum</a><br /><br /><a href="http://code.google.com/p/screwpile/wiki/DevelopmentProcess">Development Process Doc</a><br /><a href="http://code.google.com/p/neddick/wiki/Roadmap">Neddick Roadmap</a><br /><br /><br /><a href="http://github.com/fogbeam/Neddick">Neddick on GitHub</a><br /><a href="http://github.com/fogbeam/Quoddy">Quoddy on GitHub</a><br /><a href="http://github.com/fogbeam/Heceta">Heceta on GitHub</a><br /><br /><a href="http://freshmeat.net/projects/neddick">Neddick on Freshmeat</a><br /><a href="http://freshmeat.net/projects/quoddy">Quoddy on Freshmeat</a><br /><a href="http://freshmeat.net/projects/heceta">Heceta on Freshmeat</a><br /><br /><a href="http://advogato.org/proj/Neddick/">Neddick on Advogato.org</a><br /><a href="http://advogato.org/proj/Quoddy/">Quoddy on Advogato.org</a><br /><a href="http://advogato.org/proj/Heceta/">Heceta on Advogato.org</a><br /><br /><a href="https://www.ohloh.net/p/neddick">Neddick on Ohloh.net</a><br /><a href="https://www.ohloh.net/p/quoddy">Quoddy on Ohloh.net</a><br /><a href="https://www.ohloh.net/p/heceta">Heceta on Ohloh.net</a><br /><br />I think that's about it. Whew...<br /><br />Anyway, what's coming next? Well, all of the stuff from the Neddick roadmap, and we also need to get a proper Ant build setup, some tests written, and Hudson installed and configured to do continuous integration and automated testing. <br /><br />The Neddick screencast should also be forthcoming shortly, which should be fairly enlightening.<br /><br />And that's about it. Any questions, just leave a comment here, or join the fogcutter-dev or fogcutter-discuss Google Group and post there.
Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0tag:blogger.com,1999:blog-4522077366496857392.post-76804931729270124622010-07-07T20:01:00.001-07:002012-08-18T22:42:07.012-07:00Welcome to FogcutterWelcome! Some of you may have known this project under its old name <a href="https://openqabal.dev.java.net/">OpenQabal</a>. We've recently decided to rename the project amidst some other dramatic changes, and this new blog is now the home for news and updates about the project.<br /><br />If you made it here by accident, or don't know exactly what Fogcutter is, let us explain:<br /><br /><h2>What is it?</h2><br /><br />Fogcutter is an umbrella <a href="http://code.google.com/p/screwpile/">project</a>, sponsored by <a href="http://www.fogbeam.com">Fogbeam Labs</a>, which is building a suite of powerful, open-source tools for knowledge management and collaboration. ScrewPile was formerly known as <a href="https://openqabal.dev.java.net">OpenQabal</a> but has been renamed, as part of an effort to develop a consistent naming pattern for related projects.<br /><br /><h2> Why "Fogcutter?"</h2><br /><br />
Fogbeam'ers like light and things related to light... our projects are about, as we like to say, "cutting through the information fog." We like to build tools to help people find, share, reuse and create knowledge out of the raw data and unstructured information they have in their organizations. So "fogcutter" gets to the core of what we are all about. And it sounds cool to boot. <br /><br /><h2>Tell Me More</h2><br /><br />The 65,000 foot overview description would go something like this:<br /><br /><blockquote><br />"Fogcutter is an open-source suite of APIs, components and applications - driven by the principles of federation, composition, open protocols, and open standards - for building and enabling intelligent enterprise applications for collaboration, social-networking, <a href="http://en.wikipedia.org/wiki/Knowledge_management">knowledge management</a> and discovery, <a href="http://en.wikipedia.org/wiki/Organizational_learning">organizational learning</a>, <a href="http://en.wikipedia.org/wiki/Information_retrieval">Information Retrieval</a> and <a href="http://en.wikipedia.org/wiki/Decision_support_system">decision support</a>."<br /></blockquote> <br /><br />Fogcutter proper, then, is an "umbrella project" or over-arching structure for sub-projects that handle different parts of this vision. Think of how <a href="https://glassfish.dev.java.net/">Glassfish</a> has become an "umbrella" project for a series of related projects: <a href="https://mq.dev.java.net/">OpenMQ</a>, <a href="https://open-esb.dev.java.net/">OpenESB</a>, <a href="https://sailfin.dev.java.net/">SailFin</a>, <a href="https://portal.dev.java.net/">Portal Server</a>, etc.<br /> <br />With ScrewPile as the overall encompassing framework, sub-projects will deal with provide various APIs and/or applications / subsystems that are part of this overall "intelligent application" vision. <br /><br />Subprojects will deal with things like: an API / system for managing tags, recommendations engine, mechanism for dealing with voting/ranking things, something for managing a social graph and allowing queries against it, etc. <br /><br />Of course, as before, in a lot of areas existing open-source code exists to do these things. In that case, we may (within the letter and spirit of the respective licenses) just "borrow" existing code, possibly wrapping or modifying it to fit the model of what we're doing here. Other bits will have to be written entirely from scratch, and that's OK.<br /><br /><h2>Tell Me About These Subprojects</h2><br /><br />Well, here's what we think we know about them so far:<br /><ul><br /><li><br /><a href="http://code.google.com/p/neddick/">Neddick</a> - An interface that builds on the APIs for tagging, ranking and recommending items, to provide a platform for sharing and discovering useful links, documents, people, etc. What we have right now is pretty simplistic, but there's a LOT of room for growth in this.<br /></li><br /><li><br /><a href="http://code.google.com/p/quoddy/">Quoddy</a> - a sort of "mini Facebook" like social-networking interface. Builds on the APIs for <a href="http://en.wikipedia.org/wiki/Social_graph">social-graph</a> management, <a href="http://www.google.com/search?q=%22activity+stream%22">activity-stream</a>, <a href="http://en.wikipedia.org/wiki/APML">activity profiling</a>, tagging, etc. Provides the front-end for managing connections and for letting users provide information about themselves, their interests, etc. But unlike Facebook, no silly Pirates vs. Ninjas or Farmville stuff.<br /></li><br /><li><a href="http://code.google.com/p/heceta/">Heceta</a> - This may not actually come into existence as a standalone project; but the general vision is a search engine that leverages all of the various bits of information from Neddick, Quoddy, and "TBD" to provide better / deeper / more insightful search results than you can get from simple document content analysis. Intranet search in the Enterprise usually sucks, largely because page-rank type algorithms don't work well due to the lack of links between documents. But by supplementing the content analysis with scoring based on tags, social graph connections, activity-stream information, etc., it should be possible to do a much better job. This is not, by the way, a totally novel idea. It's something people are referring to as <a href="http://en.wikipedia.org/wiki/Social_search">Social Search</a>.<br /></li><br /><li>GraphEngine - as before, an API for storing and managing the "social graph stuff." Doing this on a large scale is still a problem, and I'm intrigued by the idea of using an <a href="http://en.wikipedia.org/wiki/Incremental_computing">incremental evaluation system</a> approach for this, but haven't done much on this yet.<br /></li><br /><li>ProfileEngine - name says it all, really.</li><br /><li>RecommenderEngine</li><br /><li>ActivityEngine</li><br /><li>TagEngine</li><br /><li>Etc.</li><br /></ul><br /><br />Of course since this is all intended for an enterprise setting, a big focus will be on integrating with other systems (see the point about "open protocols" and "open standards" above). <br /><br />Previous discussion of <a href="http://code.google.com/p/neddick/">Neddick</a> (formerly code-named "Project Shelley") mentions discovering documents and people, despite the screen shots only showing stuff about links so far. That's where integration comes into play... part of the vision is to integrate with, for example, a document management system like <a href="http://forge.alfresco.com/">Alfresco</a>, a forum system like <a href="https://jforum.dev.java.net/">JForum</a>, a groupware / calendar system, a HRM system like <a href="http://code.google.com/p/orangehrm/">OrangeHRM</a> and/or a social-networking application like <a href="http://code.google.com/p/quoddy/">Quoddy</a> (formerly code-named "Project Poe"). <br /><br />That, of course, also plays into the vision for Heceta, which is all about searching across all the different domains, and using the knowledge aggregated across all of them, to enhance our search capability.<br /><br />Get involved by visiting the <a href="http://code.google.com/p/fogcutter/">project page on Google Code</a>.Anonymoushttp://www.blogger.com/profile/08078684337177177862noreply@blogger.com0