yak
[Top] [All Lists]

[yak@collab] Re: Tool development: Proposed candidateInstructor/School

To: yak@xxxxxxxxxxxxxxxxxxx
From: Henry K van Eyken <vaneyken@xxxxxxxxxxxx>
Date: 09 Nov 2003 01:29:05 -0500
Message-id: <1068359345.1590.18.camel@localhost.localdomain>
Discussing a wide variety of issues is not a bad thing at all, at all.
It brings concerns to the fore and it sensitizes if nothing else.    (01)

But ultimately the idea is, in terms of Doug's talks during the
Colloquium and things he said elsewhere, to assemble ideas for
constructive purposes. This calls especially for expert input. He talked
about people manning the frontier outposts, i.e. outposts in the future
(his "C-activity"). He also talks about the forming of an encyclopedia
or handbook.    (02)

Thinking in terms of the old-fashioned (pre-macropedia, micropedia)Enc.
Britannica, it gathers fairly summarized encyclopedic knowledge written
by subject experts. With electronics, we may now do so with pretty
up-to-date references to more elaborate treatments through the magic of
hyperlinking.    (03)

I sometimes have the feeling - and I may well be wrong - that the gurus
of the digital arts think too much in terms of computers doing the
digesting or some sort of equivalent thereof. Well, some of that may
indeed be possible, but for now the main stream of digesting (editing)
has to go though human minds.    (04)

Henry    (05)

On Sat, 2003-11-08 at 20:16, John Sechrest wrote:
> I have gotten many things out of yak. And I have even worked on some 
> ideas.
> 
> However, Yak and collaborative work is a side effect of what I think
> about, not a core part of my daily work. And so it necessarily must
> take a second priority. In order for it to take a higher priority,
> it needs to have time and money behind it. 
> 
> That is the reason that I pushed out the SBIR questions earlier.
> 
> However, no-one bit on the idea. 
> 
> 
> I am running an SBIR writers workgroup in Corvallis. Our goal is to 
> improve the number of SBIR grants in our county.
> 
> If we spend some time with the tool list, and organize it a bit.
> And then chew on it a bit and break it into small SBIR size
> pieces, we might actually be able to fund specific development on
> specific ideas.
> 
> Until then, yak is a place were we all work together between other tasks,
> to gain a greater understanding. When we find a way to fund some fulltime
> attention on these issues, we will see larger steps being made.
> 
> 
> 
> 
> "Matthew A. Schneider" <matsch@sasites.com> writes:
> 
>  % Henry K van Eyken wrote:
>  % 
>  % >Not to chop things up further, I proposed a long, long time ago that we
>  % >have volunteer "thread masters" to organize and maintain thread content
>  % >in orderly (story) fashion. Alas ...
>  % >
>  % >Same idea also went into the publishing of Fleabyte: that topics be
>  % >continually "redigested" with appropriate references, so as to form a
>  % >truly dynamic DKR. Again, alas ...
>  % >
>  % >In the meantime, we are getting older and the world ticks on.
>  % >
>  % >Henry
>  % >
>  % Lots gets said here, but not much gets implemented. That's part of the 
>  % problem with this venue. Everyone waiting for everyone else to step up. 
>  % Who is going to step up and take the Yak by the horns?
>  % 
>  % Matt
>  % 
>  % -- 
>  % This message is archived at:
>  % 
>  % 
>http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=3FAD4A52.4050403@sasites.com
> 
> -----
> John Sechrest          .         Helping people use
> CTO PEAK -              .           computers and the Internet
> Public Electronic         .            more effectively
> Access to Knowledge,Inc       .                      
> 1600 SW Western, Suite 180       .            Internet: sechrest@peak.org
> Corvallis Oregon 97333               .                  (541) 754-7325
>                                             . http://www.peak.org/~sechrest
-- 
Henry K van Eyken <vaneyken@sympatico.ca>    (06)

-- 
This message is archived at:    (07)

http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=1068359345.1590.18.camel@localhost.localdomain    (08)
<Prev in Thread] Current Thread [Next in Thread>