World: r3wp

Not only that, you may replace the actors of a port at anytime.

Hey Steeve, I think my scheme is working now  :)

Looks like all R3 development work is occuring inside darknets inside 
darknets

Kinda defeats the idea of open source components

yeah, I was hoping to have a bit more feedback published from the 
daily scrums

I guess there's been more feedback than before, though

What feedback do you expect?

The thing is to concentrate and focus that we can deliver something. 
Disussions about non-priority things don't help us at the moment.

The daily scrum is not that interesting as there is nothing DONE 
until the end of a sprint. We are currently using 1 week sprints. 
This means every Friday afternoon we review what has been DONE.

Graham: I expect something to be released (open-sourced), once there 
is actually something to open-source. I mean - untill the HostKit 
isolation is done, we can't proceed. Once View is completly separated 
as module, it can, and hopefully it will be released ...

I don't know about anything why it shouldn't be released.

I'm looking forward what will be done with the host-kit. Not sure 
why it's a mandatory component for so many to use R3 but OK, maybe 
I just don't get it.

IMO it's more critical to use to get a good GUI up & running with 
a broad set of styles.

Pekr, I was just saying that all R3 development is either practically 
invisible, or, perhaps is just not happening.  r3 chat is also dead.

well, I think that if Carl's developments from the private world 
is posted on his twitter account, that should be enough.

Is the lack of developer activity just a sign of lack of interest 
in R3?

I'm not sure I understand what you mean. There is probably more developer 
activity now than in the past 2 years.

There's no unpaid activity

People are waiting for the host kit.

I'm busy again, and just chatted with Carl today about what I'm working 
on. For better or worse (mostly worse), that's unpaid.

Robert is pulling a lot of strings (namely by getting hold of all 
the right people, while they are not busy) to focus R3 development 
and I'm impressed that he was able to get Carl in on it. It's what's 
needed now to move forward at greater speed, just like any other 
serious development effort. Robert's motivation is to deliver products 
as soon as possible and there is nothing strange about that.

For the main things I was working on, I am now unblocked. Thanks, 
Robert!

ANd Pekr, who has also done a lot of behind-the-scenes work.

It's so sad that after 3-4 years there's so few people working on 
R3

Graham, I just don't get your criticism. We are MOVING. That's key.

I'm not criticising .. just making an observation

well, you can't see everything right now.

I can only observe what I see!

OK. We will weigh your observations accordingly :)

Reminds me of Get Smart

Loved that show :)

BrianH: I did nothing :-) I am just rebol politician, lobbying here 
or there :-)

Politicians are underrated. Though your role was more diplomat, messenger 
or matchmaker :)

Please don't call Pekr a politician. That would require Pekr not 
to know what he's doing and generally not really care about REBOL. 
:-)

:-) .... yes, but one aspect remains ... you work, I talk :-)

>> a: [a 1 2 b 3 4 c 5 6 d 7 8]
== [a 1 2 b 3 4 c 5 6 d 7 8]

>> head move/to/skip find copy a 'd 1 3
== [a 1 d 7 8 2 b 3 4 c 5 6]


Looks like a bug to me. [d 7 8] should be at offset 1 rather than 
3. This is also present in R2 forward.

sorry, plain R2.7.7, not R2 forward.

Nope, 2.7.7 has the R2/Forward code. I see the bug, though have a 
question: Should the index obey the skip?

When /to is not specified and /skip is, offsets are multiplied by 
the record length, so you are counting in records. This is intentional, 
to allow you to work with fixed records without messing them up. 
If we keep that behavior then the index will be the record index, 
not the series index. It's not a difficult trick, but it should be 
noted.

If you agree that this makes sense, I'll write up the CureCode entry 
and submit the fix to all three locations.

It's so sad that after 3-4 years there's so few people working on 
R3

 - I can take it if it would be "...working with R3". That's true. 
 People should use it and tell what's the most critical (that means, 
 what blocks you from making a product) thing that needs to be done 
 in R3.

It's not about x-mas and what we would like to see in R3. I have 
a very simple priority list: What do we need to get to scale R3 development 
and avoid Carl being a bottelneck? What do we need to do to use R3 
to do a commerical app?

And, yes, I'm very happy that things move on and the support from 
all helping to make it happen. The team size is good, the paces is 
good and the results are good.

What's blocking is that questions don't get answered because no one 
knows the answer

Maybe we should have our own stackoverflow for questions on R3 so 
that unanswered questions are obvious?

Or, just ask them on SO ...

For now I'll assume that Henrik's answer to my question is yes.

Graham, can you give an example question?

Sure.  If the remote server closes a connection, can you re-use the 
sub-port to re-open the port?

Have you tried it?