Comments on: Open source design 2.0 http://factoryjoe.com/blog/2005/11/21/open-source-design-20/ This can all be made better. Ready? Begin. Tue, 18 Jan 2011 00:50:29 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Chetan http://factoryjoe.com/blog/2005/11/21/open-source-design-20/comment-page-1/#comment-1117 Chetan Wed, 23 Nov 2005 04:51:27 +0000 http://factoryjoe.com/blog/2005/11/21/open-source-design-20/#comment-1117 Robert, Chris: Well, that's a great idea, using Flickr API, I mean. Why didn't you say so? May be it's a good idea to announce it publicly that you will be using Flickr API. So, developers of software and services would start in parallel working with the available API won't lag behind. When Flock goes mature, so will all the apps, instantly transforming Flock into an all in one app of sorts. Robert, Chris: Well, that’s a great idea, using Flickr API, I mean. Why didn’t you say so?

May be it’s a good idea to announce it publicly that you will be using Flickr API. So, developers of software and services would start in parallel working with the available API won’t lag behind. When Flock goes mature, so will all the apps, instantly transforming Flock into an all in one app of sorts.

]]> By: FactoryJoe http://factoryjoe.com/blog/2005/11/21/open-source-design-20/comment-page-1/#comment-1115 FactoryJoe Tue, 22 Nov 2005 17:24:59 +0000 http://factoryjoe.com/blog/2005/11/21/open-source-design-20/#comment-1115 Robert's got it right. In fact, I <a href="http://factoryjoe.com/blog/2005/11/03/iamcaltraincom-launches-on-new-yahoo-maps-api/" rel="nofollow">put a call out</a> a short while ago asking that folks take up the task of reimplementing the Flickr API in Drupal, WordPress or other open source publishing tools. A fundamental goal with Flock is to promote choice on the web -- and we fully intend to build our tools to interoperate with as many open source systems as possible. It just so happens that Flickr is the best (and for me, most familiar) photo sharing/design tool that we have right now. And I've also got much work to do on building Flock itself, so I can't get obsessively caught up in the tools right now so long as they allow me to be more productive, efficient and open (we use Basecamp internally which is a shame -- because I would love for a lot of that content to get out!). Again, if Bugzilla had Flickr's simple but robust set of image manipulation and annotation tools built in with an API for me to use for uploading, I would be using that. But it doesn't, so for now, I want to lead by the example of what I want and need to get my work done and hope that the open source community gains something from these new workflows. Ideally we'll be moving towards cycles that are heavy on design and interface up front with engineering coming in as an the essential ingredient to make these things possible, better built, or interoperably streamlined. And yes, Daryl, this is a little new, but I'm hoping to just extend the awesome work you've done on the <a href="http://community.flock.com/pr" rel="nofollow">new PR tool</a> for this purpose! Robert’s got it right. In fact, I put a call out a short while ago asking that folks take up the task of reimplementing the Flickr API in Drupal, WordPress or other open source publishing tools. A fundamental goal with Flock is to promote choice on the web — and we fully intend to build our tools to interoperate with as many open source systems as possible. It just so happens that Flickr is the best (and for me, most familiar) photo sharing/design tool that we have right now. And I’ve also got much work to do on building Flock itself, so I can’t get obsessively caught up in the tools right now so long as they allow me to be more productive, efficient and open (we use Basecamp internally which is a shame — because I would love for a lot of that content to get out!).

Again, if Bugzilla had Flickr’s simple but robust set of image manipulation and annotation tools built in with an API for me to use for uploading, I would be using that. But it doesn’t, so for now, I want to lead by the example of what I want and need to get my work done and hope that the open source community gains something from these new workflows. Ideally we’ll be moving towards cycles that are heavy on design and interface up front with engineering coming in as an the essential ingredient to make these things possible, better built, or interoperably streamlined.

And yes, Daryl, this is a little new, but I’m hoping to just extend the awesome work you’ve done on the new PR tool for this purpose!

]]> By: Daryl http://factoryjoe.com/blog/2005/11/21/open-source-design-20/comment-page-1/#comment-1114 Daryl Tue, 22 Nov 2005 16:06:35 +0000 http://factoryjoe.com/blog/2005/11/21/open-source-design-20/#comment-1114 It's always great to learn from a blog post that you've got work entering your queue. ;) It’s always great to learn from a blog post that you’ve got work entering your queue. ;)

]]> By: Robert Douglass http://factoryjoe.com/blog/2005/11/21/open-source-design-20/comment-page-1/#comment-1113 Robert Douglass Tue, 22 Nov 2005 15:39:54 +0000 http://factoryjoe.com/blog/2005/11/21/open-source-design-20/#comment-1113 Chetan, what I like about Chris and Flock developing a Flickr uploader is that the Flickr API is published and robust. There is nothing stopping Drupal, Joomla and Wordpress from implementing the API as Flickr defines it (in fact, this should already have been done by now, imo). Once that has happened, the Flock image uploader will upload to whatever service implements the API. Designing to the interface is always a good decision, and I think this is a really good step. Sites like Ourmedia.org and NowPublic.com would benefit loads from Flock and the FlickrAPI uploader. -Robert Chetan, what I like about Chris and Flock developing a Flickr uploader is that the Flickr API is published and robust. There is nothing stopping Drupal, Joomla and WordPress from implementing the API as Flickr defines it (in fact, this should already have been done by now, imo). Once that has happened, the Flock image uploader will upload to whatever service implements the API. Designing to the interface is always a good decision, and I think this is a really good step. Sites like Ourmedia.org and NowPublic.com would benefit loads from Flock and the FlickrAPI uploader.

-Robert

]]> By: Chetan http://factoryjoe.com/blog/2005/11/21/open-source-design-20/comment-page-1/#comment-1112 Chetan Tue, 22 Nov 2005 11:49:23 +0000 http://factoryjoe.com/blog/2005/11/21/open-source-design-20/#comment-1112 Hi Chris, I understand the need to simplify web services/apps with Flock, but from what you're saying appears a lot more like Flock catering to specific services instead of enabling a general connect (to those services that are open with apis or end points of sorts to connect). In a couple of months, years down the line, there may be a lot more services that could be used via Flock. So, may be Flock should have a connecting end to begin with rather than supporting them, because browser is the first contact to the user, not the other way around. Do what I say makes any sense? Hi Chris, I understand the need to simplify web services/apps with Flock, but from what you’re saying appears a lot more like Flock catering to specific services instead of enabling a general connect (to those services that are open with apis or end points of sorts to connect). In a couple of months, years down the line, there may be a lot more services that could be used via Flock. So, may be Flock should have a connecting end to begin with rather than supporting them, because browser is the first contact to the user, not the other way around. Do what I say makes any sense?

]]>