World: r3wp

And there are many parts that are sitting unfixed, because they await 
a proper solution (compiler issues), such as the many problems with 
image!.


BrianH has also done a ton of work, spoonfeeding Carl with reports 
and fixing dozens of issues with LOAD and TRANSCODE, so to say that 
things are closed, is not true.

Geomol - I have to object. Before complaining about the way the projects 
is run, please check the following:


 - do you really understand, how the project is being run at all? 
 Because quite frankly, you are not using fair arguments here imo. 
 I can agree, but only to some extent, that things are being done 
 in a chaotic way. But - being close to Carl and trying to listen 
 to him and COMMUNICATE with him, I can understand the aproach he 
 takes. 


- one of your false arguments is, that putting things into CureCode 
is not helpful - CureCode was chosen by Carl and the community as 
a streamlined channel for bug reporting. Now please don't tell me, 
that even some low level bugs are not reported? There is a changelog 
which simply proves you being wrong.


- Before some releases Carl asks BrianH to change CureCode items 
rating to fix most important stuff - so how comes that our aproach 
does not work? Please post bug reports, talk to Carl or BrianH to 
raise the importance - doesn't following section show we finally 
got our requested - release early, release often?
http://www.rebol.net/wiki/R3_Releases


- and to be honest - you are one of persons being added to the r3-gui 
world. Some time back Carl had to add even lamer like me to the list 
:-) - and you know why? Because he was not getting much of response. 
He nominated top community gurus to help with the GUI. Actually, 
the same happened during the Gab's VID3 project - only me, Henrik, 
and BrianH commented. It seems to me that some ppl prefer to chat 
about science and belief systems instead of helping to develop R3 
;-) (I am not dismissing anyone's right to come here to chat about 
anything - this place is really a rebol pub where we meet, but the 
other worlds were specialised, yet lacked the input from community, 
even if asked for help)


- in order to get more ppl involved in R3 development at native level, 
it is clear where do we need to get - we've got R3 chat to be base 
of new Altme, new BBS, new DevBase. In March plan Carl clearly outlined, 
that in order to get sources out, we need rebin, plugins. They are 
now postponed due to modules, security, but still a high priority. 
How do I know? Because I was not lazy and asked Carl the specific 
question.


- we also get improvements on other fronts - we have got new streamlined 
Docs. I suggested Carl to add community section, then also new R3 
section to rebol.com page and to produce detailed changelogs. These 
all are small steps, but steps which make a difference.


Now please tell me - how complaining here can make situation any 
better? How many bugs have you posted, how many rebdev messages you 
have asked to Carl? Why don't you talk about your concerns with Carl? 
He will respond to you, like to me or anyone else - either via chat, 
or via a Blog article.


As for me, I am quite fine with how R3 is progressing last few months. 
Yes, we are slow on the whole project, but we are still doing a good 
progress imo.

Responding to Pekr's comments:


- I've communicated with Carl privately before. Starting on the OS 
X port more than a year ago is one example. Lack of info back to 
me made me stop. It's in a group in r3-alpha, you don't have access 
to.


- About CureCode, I didn't argue, it's not helpful. I don't care, 
what bug report system is used, as long as it works. Curecode is 
one of the best such systems, I've seen. Yes, low level bugs are 
reported. That's not the problem. It doesn't make much sense to me 
to work on a building (in lack of better metaphor) at the 123 level, 
when the basement isn't stable. Question is, how long this situation 
will last, before I see a stable version across platforms. My guess 
is years, therefore my concerns.


- r3-gui. Again it doesn't make much sense to me to work on GUI, 
if the core has many bugs.


- You list many topics in monthly plan. Development is going on at 
all levels of the building. I would start by making a solid basement, 
then make my way up. Making any level finished, before going to the 
next. It's just another way of doing things. I have good experience 
doing it the way, I try to describe.


- About docs. It's about time, something is done with the docs. I 
had huge problems figuring out, even how to test R3 back in the r3-alpha 
days. Docs were confusing, lack info, etc. Some months ago I tried 
to figure out, if I could port Canvas RPaint to R3. I stopped quickly, 
when I couldn't find the docs to do even simple things.


Well, you ask, why I complain. Initially I just said, how I felt. 
Loosing faith in the project. I really hope, it'll happen one day. 
But as I see it, it'll take years. I feel like sharing this view 
with others. Then you can use it as you wish. I need to figure out, 
what I'll do with my own development.

About port to other OS, this is the info (in DocBase), I managed 
to get out of it (check history of that page):
http://www.rebol.net/wiki/Porting_Recipe

I have access to all worlds I know development went in - r3-alpha, 
r3-gui, and I of course remember your effort. It is not the time 
(yet) to do solid porting to another systems by ourselves. So far 
only Carl does some ports, bu those should be regarded being experiments.

It is not the time (yet) to do solid porting to another systems by 
ourselves.


Good info! I should have known that 1.5 years ago, when porting was 
a topic.

Question is, how long this situation will last, before I see a stable 
version across the platforms ...

 - I don't know, noone knows. The thing we need is - testing. So - 
 find a bug, file a bug, talk to Brian or Carl, make it a higher priority, 
 it will get fixed.

Do you think, the time will ever be right for people doing such ports 
to all different kinds of OSs? A situation, where the OS-dependent 
parts of R3 will be open source and documented. I have my doubts.

One thing I have learned  over the years: never care for the "new"version. 
Use what you have, and consider it as what it is... just another 
tool.

So R2 is great, often. Sometimes it is not. The longer R3 takes, 
the more often alternatives will be viable. That simple. I'd love 
to help on R3, but I have work,  kids, etc.

The way I see it (now)is R2 is just a product thatI bought that gives 
great value. But who knows.... tomorrow there might be this awesome 
language called "Zen" and after 2 years I am so good with it... you 
get the picture :-)

The goal is not R2/R3 ... the goal is to be effective. So you can 
make money. And so on.

Right.

I do remember myself panicking xy times in the past. Other panicked 
too - we all arged Carl to get back to finishing Core first, then 
move forward. But Carl thinked otherwise - that R3 is good enough 
to attract new users via GUI. You all surely know, how difficult 
it is to change Carl's mind. But OTOH Carl listens to what we say.

So the answer to your question is - yes, I really think we are months 
at max away from the source releases and real porting efforts. In 
the meantime, do what Maarten suggests - just sit and watch, and 
accept things being just an alpha, not a beta ...

Pekr, I just started my old r3-status.r from the r3-alpha world.


One of the top priority bugs in that is #60 division by zero. I went 
to Curecode and read about the bug dated 4-Jun-2007, and I tried 
it in latest R3. It's still there.


Another high priority, #115 dated 11-Jun-2007 has status waiting. 
Waiting for what?


A third is about money! datatype, #250. Currency now seem to be removed 
from R3, so it can't be tested anymore. So R3 will not have currency?

etc...


So you see, there are lots of things to put in rock at the lowest 
level. So no need to discuss all the higher level things (from my 
viewpoint), before those lower levels are fixed.


An example of backward development or bad planning or whatever. The 
issue! test, I just wrote about. It seems to be because of unicode. 
So the plan for all this wasn't made, when the issue! datatype was 
programmed? Now what? Do we have to roll all back and do heavy testing 
again at the lowest level?

If you don't watch Chat, you probably also missed Carl's info - he 
is working on a list of items, which will turn R3 into beta.

just sit and watch

No, I don't intend to. :-)

Geomol, I'm not sure why it surprises you that R3 takes a long time 
to build. It's always been difficult to determine exactly when R3 
would be considered stable. Building the GUI was a very quick way 
to expose multiple bugs of which some are solved (including some 
nasty memory related crashes).

OK, then don't sit and wait, but please try to be constructive. Or 
in other words - don't try to be a Pekr :-D

Also, why haven't people started working on protocols yet? The docs 
have been there for months and ports are ready for heavy testing.

Henrik - maybe ppl fear that low-level port system is not final yet? 
Who knows ...

:-)

That's the whole point of building protocols now, to test the port 
system.

Let's see, based on Carl's original testing hierarchy, protocols 
is level 18. No, I won't start testing protocols, when all the levels 
below that has bugs.

I would feel, I was wasting my time doing that.

How do you know there are port bugs? Are there any in Curecode?

I don't understand your aproach, Geomol. What levels are you talking 
about?

Exactly - all bug reports are supposed to be moved into CureCode. 
If there is some bug which is not there, it is an ommision, and it 
should be filled.

Geomol, the bugs I found in the port system would not have been found 
unless the HTTP protocol had been written.

The test priorities are here:
http://www.rebol.net/wiki/R3_Alpha_Test_Priorities

Geomol - give me bug tickets you want to have fixed, and we will 
see what can be done.

Written by Carl.

Yes, written by Carl. And then ignored by everyone else. No one wrote 
any tests for him.

Geomol, we're not dealing with a business system that you would potentially 
have to pay millions for (yet!). That's why it makes a lot of sense 
to write some apps now for it.

I made r3-status.r script based on that list from Carl. So no, not 
ignored.

I also worked with someone in r3-alpha to do tests, that would make 
all those low levels a green ok in r3-status.r.

Eh, there is many docs written by Carl, that are forgotten. DocBase 
became a mess, it needs serious clean up (e.g. all docs about VID3 
should be removed, it confuses ppl). When I told to Carl, that we 
need release notes, he told me he needs to think about doc structure. 
So I pointed him to one year old Doc of his (earlier alphas) and 
he told me he forgot about the doc :-)

Henrik - wasn't there some test suite with earlier alphas?

Pekr, only the framework and a few smaller tests. That was when Carl 
was talking about how huge an undertaking these tests would be.

I still regard it being a good start for further test submissions 
...

What I mean is, let's take first point in Carl's list. Scanner bugs. 
Are there any? Is
--1:23

a bug? Yes, it is. I don't have time to find all these low level 
bugs, but it seems, I easily find some of them, when I start looking. 
So problem maybe is, that people are not looking, and Carl don't 
document, how people can look for these things. It's because the 
whole thing is closed to some degree.

Geomol, again, did you post that bug to Curecode? Did BrianH see 
it so he could prioritize it for Carl?

Ah, found it - http://www.rebol.net/r3blogs/0125.html

Nope, as I see it, there are so many bugs, that I would use all my 
time posting to Curecode. I don't have that time.

Geomol, then you are not beneficial to the R3 project!

I tried to post things, and I tried to help with priority (r3-status.r), 
but it's not used.

sorry, but it upsets me, because that's plain backwards and non-productive 
to not report these bugs.

I was, I am not much these days, because I've lost faith in the project. 
:-)

Then there's no point in continuing the conversation, is there?

I'm not backward. :-) Carl started with these low level tests. We 
should have stayed there, until the thing was stable. But Carl (and 
therefore others) moved on.