World: r3wp

I think he phrased it .. something about standing on the shoulders 
of giants or something

Anyway, I agree with this as a priority because it allows greater 
concurrent contribution to R3 base code.

Great ... look forward to seeing something soon.

Henrik .. are you offering to do the ftp protocol?

Graham, no.

Carl, what the scheme system/schemes/console is used for ?

hmm... i think i got it

Is that if i map a port at system/ports/output, I can redirect all 
the output (print, probe etc...) ?

If you're working with a line oriented protcol .. do you save the 
buffer to your own buffer and work on it line by line ( deline ) 
?

Or is it enline

I don't agree on console not greatly ruining the R3 experience. R3 
sucks big way because of it. for me it degrades my experience by 
some 20-30%. Not being reboller, I would trash it. Python has own 
console too IIRC.

that "ppl can do it themselves" is rather silly. We are at it once 
again.

We never learn, and I write documents for nothing :-)

Pekr, just say "I agree with Graham"

Thank you for your cooperation.

I f*cking agree with Graham :-)

There's many ppl out there, who will want to try REBOL as a tool, 
and have ABSOLUTLY NO intention into coding some infrastructure things 
themselves. So - we can say such things as "do it yourself" in a 
community cooperative manner here, but let's not dare to present 
such opinions publicly ...

the do it yourself, is not meant for the end user, but for contributors... 
I thought that was obvious.

I hope it is obvious too ... but it surely was not obvious in R2 
days. We claimed being a glue, yet the only option to interface REBOL 
was sockets/files (free versions)

This is not a criticue, this is a raised eyebrow ... I think that 
we are on very good route - Extensions + Host ... and we will surely 
get there.

I guess there needs to be a formal limit to what RT does and what 
community should do. It can't be expected that RT would maintain 
console support on an obscure OS. OTOH you might expect HTTP to work 
as a result of RT work or someone close to RT.

Hasn't this been demarcated already?

Don't think there is anything but a task list.

I'm also unclear as to the license behind community contributed stuff. 
 Say Anton spends a couple of weeks doing an ftp scheme ... under 
what license should it be publshed as ?

Henrik - and I say I don't care how it happens. The only important 
thing is - the product and its state. If you have no answer for "who 
does it", RT is still responsible, if they want to market REBOL. 
That is why I thought bounties might help to sponsor some ppl willing 
to bring-in some usefull contributions ...

licensing was not revealed yet ....

Hmm ...

Perhaps everyone should BSD their contributions ...

As soon as people start making them of course ...

this is now declared a GPL free zone ... thanks for cooperating.

I care about how it happens, because process of knowing who does 
what will become increasingly important as R3 grows. Extensions is 
just one area where people freely can contribute under the BSD license. 
If you don't want it public, don't publish.

BSD has the best integration opportunity, yes

Now soon, GUI work will continue and there are graphics subsystem, 
OpenGL, etc. Enough work for 4-5 people there alone.

And one maintainer per OS platform.

re console: i have some patches to the linux hostkit that rip out 
the custom R3 line reader

this in itself is already an improvement on linux, as rlwrap is, 
at the moment, far superior the the line reading abilities of the 
r3 hostkit

but based on this, i have also hooked up libreadline into the r3 
hostkit, in a very basic way

Gabriele, can WeTan get posted to DevBase? There is an area for community 
projects. You could make a folder for your MD3 stuff.

Andreas, are you using LibReadLine?

that's proper line editing as well as line history

yes, sure

Nice

it's still a quite rough integration as e.g. signals (esc, C-c) are 
not yet handled properly

but it's already rather nice to use :)

Gab said wetan was in the r3 alpha file share .. where ever that 
might be ...

It is of limited availability. If we want the tool used for R2 or 
R3 source, it needs to be publically available, and that means DevBase, 
or failing that, some web site. In either case it needs the right 
licensing, but with Gabriele writing it that is unlikely to be an 
issue.

Ok, look under User/Gabriele/'wetan-test.r

there's no license attached to it.

R2/Forward is MIT - it was the least restrictive license I could 
find short of public domain or WTFPL. The FreeBSD license is comparable 
- see opensource.org for details.

Since the network protocols are asynchronous, it seems that we should 
have a common way to supply a callback to the network resource being 
requested ...