User:Eerik Wissenz/Proposed organic architecture - Revision history

Anthonyrepetto: /* Response? */

2011-07-21T17:29:52Z

Response?

← Older revision		Revision as of 17:29, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated with it, and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? ...As a self-organizing clearing house for OS hardware and project collaboration of all stripes, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options? <- and this is a 'request' type, as opposed to an 'info question' like "who is in charge of CADing this design?")		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated with it, and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? ...As a self-organizing clearing house for OS hardware and project collaboration of all stripes, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options? <- and this is a 'request' type, as opposed to an 'info question' like "who is in charge of CADing this design?" ... searching for all the 'current requests' would be a quick way to sort tasks.)

	- Anthony, 'the little black bird' :)		- Anthony, 'the little black bird' :)

Anthonyrepetto: /* Response? */

2011-07-21T17:28:44Z

Response?

← Older revision		Revision as of 17:28, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated with it, and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? ...As a self-organizing clearing house for OS hardware and project collaboration of all stripes, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated with it, and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? ...As a self-organizing clearing house for OS hardware and project collaboration of all stripes, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options? <- and this is a 'request' type, as opposed to an 'info question' like "who is in charge of CADing this design?")

	- Anthony, 'the little black bird' :)		- Anthony, 'the little black bird' :)

Anthonyrepetto: /* Response? */

2011-07-21T08:32:06Z

Response?

← Older revision		Revision as of 08:32, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated with it, and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated with it, and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? ...As a self-organizing clearing house for OS hardware and project collaboration of all stripes, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)

	- Anthony, 'the little black bird' :)		- Anthony, 'the little black bird' :)

Anthonyrepetto: /* Response? */

2011-07-21T08:31:01Z

Response?

← Older revision		Revision as of 08:31, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated with it, and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)

	- Anthony, 'the little black bird' :)		- Anthony, 'the little black bird' :)

Anthonyrepetto: /* Response? */

2011-07-21T08:30:31Z

Response?

← Older revision		Revision as of 08:30, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm, affiliated and maintained by the distant crowd, instead of Marcin; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)

	- Anthony, 'the little black bird' :)		- Anthony, 'the little black bird' :)

Anthonyrepetto: /* Response? */

2011-07-21T08:27:44Z

Response?

← Older revision		Revision as of 08:27, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., ~~are never going to~~ be searched for as a group - you don't want to ~~read~~ every resource link to every topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. The nature of their relationship to the topic is what defines 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., and it's unlikely these will be searched for as a group - you don't want to search for ''every'' resource link to ''every'' topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)

	- Anthony, 'the little black bird' :)		- Anthony, 'the little black bird' :)

Anthonyrepetto: /* Response? */

2011-07-21T08:23:53Z

Response?

← Older revision		Revision as of 08:23, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., are never going to be searched for as a group - you don't want to read every resource link to every topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?) - Anthony, 'the little black bird' :)		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., are never going to be searched for as a group - you don't want to read every resource link to every topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?)

			- Anthony, 'the little black bird' :)

Anthonyrepetto: /* Response? */

2011-07-21T08:23:33Z

Response?

← Older revision		Revision as of 08:23, 21 July 2011
Line 83:		Line 83:
	== Response? ==		== Response? ==

	I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., are never going to be searched for as a group - you don't want to read every resource link to every topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?) - Anthony, 'the little black bird' :)		I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., are never going to be searched for as a group - you don't want to read every resource link to every topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' text according to its relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?) - Anthony, 'the little black bird' :)

Anthonyrepetto: /* Wiki vs Framework */

2011-07-21T08:21:33Z

Wiki vs Framework

← Older revision		Revision as of 08:21, 21 July 2011
Line 80:		Line 80:

	Now, a wiki is open source so in theory could be augmented to act as a framework, but in my experience it's a lot easier to use the tool designed for what you want to do rather than adapt another tool.		Now, a wiki is open source so in theory could be augmented to act as a framework, but in my experience it's a lot easier to use the tool designed for what you want to do rather than adapt another tool.

			== Response? ==

			I hope I'm not stubbing your wiki toes! I'm straddling that exact hurdle, at the moment, and you're outlining my dream interface. :) I like the way you think. Labels are far more flexible than folders, assigning labels a priority scale creates those lovely layers of relevance you mentioned, and label hierarchies allow that 'zoom' that'll become so critical as we do more detailed prototypes and input/output accounting. It sounds like the framework could easily morph into an attached 'library' to OSE and Factor e Farm; perhaps, that could be the initial step? As a self-organizing clearing house for OS hardware and project collaboration, a blog/discussion board for personal connections (so important, for maintaining motivation!), and a more private, technical layer devoted to Marcin's 50 tools, and Factor e Farm activities, in particular. We've got a blog, a forum, and a wiki, currently - they'd all collapse into one archive. One point that might be relevant: when you diagram flow, you don't just label the objects - you label their connections, too. 'Moderator Notices', 'Final Drafts', 'Resource Links', 'Tangents & Points of Interest', etc., are never going to be searched for as a group - you don't want to read every resource link to every topic. Just filter within that topic, by 'Resources'. The other side of this: we forget a lot. A single index is invaluable for the task of orienting yourself within the context, and accurately directing your energy. I'd love to have a 'Complete OSE Index' that I could filter by object label, as well as the labels of its posts' relationships, and allow full zoom & cross-linkages along all paths. I dunno how to do that fancy computer stuff, but if it were here, I'd be happy to help organize the data on it. :) (I addressed a few things in this post: opinions, summary, concerns, options, offers... how would we tag each of these aspects, separately? 'Color-code' relationship labels, for folks to self-moderate? We'd have to keep the number of relationship labels low, or it'd become unwieldy. Other options?) - Anthony, 'the little black bird' :)

Eerik Wissenz at 12:23, 10 June 2011

2011-06-10T12:23:08Z

← Older revision		Revision as of 12:23, 10 June 2011
Line 70:		Line 70:

	Whether Spip is chosen or not, the framework approach I think is the correct way to go, since they're the most flexible. A non-coder oriented CMS, like Drubal, Joomla or Wordpress, are great if you don't want to code, however, what happens if you can code is that modifying complex configurable plugins becomes more work (and a lot riskier) than simply writing exactly the script you want from scratch. This latter approach is what a frame work is there to simply facilitate (for instance providing a back-end for interacting with the database, that has been tried and tested security wise, so you don't have to code one yourself).		Whether Spip is chosen or not, the framework approach I think is the correct way to go, since they're the most flexible. A non-coder oriented CMS, like Drubal, Joomla or Wordpress, are great if you don't want to code, however, what happens if you can code is that modifying complex configurable plugins becomes more work (and a lot riskier) than simply writing exactly the script you want from scratch. This latter approach is what a frame work is there to simply facilitate (for instance providing a back-end for interacting with the database, that has been tried and tested security wise, so you don't have to code one yourself).

			== Wiki vs Framework ==
			Obviously a wiki is also meant for organic content creation. The differences would be:

			#One of feel, people would feel they're "blogging" rather than contributing to a wiki, and in my opinion would be more comfortable to start out, and more comfortable blogging whatever their thoughts are rather than auto-criticizing before even posting (and so never posting anything).
			#The content can be made to flow in a way far more relevant. A wiki is designed to snippets of independent subjects and is hard to break out of this model. For development, there's not a lot of independent posts but rather a huge volume of posts around a specific subject;so in a framework, all the content can flow around the subjects (each tech could have a sort of control room control room, with all the latest posts, comments etc.) Also, meta key-words such as "important", "to-do" etc. can also be added to posts to further organize them. Likewise, in a framework you can have "key-word groups" so that a page can associated with a component of the CEB for instance, and automatically appear in the latest on the CEB, but appear only with other posts on that component when one "zoom's" in on that component (i.e. each component would have it's own "control room", and indeed the whole project could have a "control room" ... maybe "situation room" is better); so it becomes easy to follow the whole project, a specific technology, or a sub component by zooming in and out of the content flow.
			#In a framework the design is put into the content and not the content into the design, so things would in general be a lot sexier and could easily be augmented indefinitely.
			#Lastly, in a framework all the services currently orbiting around the wiki could be coded into the same system, which reduces management considerably and allows far greater possibilities of leveraging content.

			Now, a wiki is open source so in theory could be augmented to act as a framework, but in my experience it's a lot easier to use the tool designed for what you want to do rather than adapt another tool.