Vahur Krouverk wrote:
> 
[Yadda/Yadda/Yadda]

Seems like there is quite interest in this proposal. To be more concrete:
1. Is out there anyone, who can provide (CVS?) server for unofficial 
POV-Ray releases?
2. Is there anyone, who agrees to be 
'buildmaster'/'maintainer'/'whatever-you-call-him/her', who has 
knowledge of version control systems (CVS?), who has development tools 
(compilers and computers to compile POVRay (for at least for Linux and 
Windows??)) and has sufficient time to build releases for POV-Ray 
patches, maintain CVS repository (merge patches with main branch), etc.
3 (probably most important?). Is there interest among POV-Ray 'hackers' 
to have such 'united' version of POV-Ray patches? '
4. Is there enough people ready to try/use/test POV-Ray versions, built 
by such approach (buildmaster can't be only person for such task!)

Post a reply to this message

Christopher James Huff wrote:
...
> From the POV-Team Status Report - September 1, 2000 in 
> povray.announce.frequently-asked-questions:
> 
> "Second, we are also hoping to use a much more open development model for
> POV 4, with public read access to our source-revision tree.
...

That's good, but it was more than two years ago, it would be nice to 
hear what the team has to say today on the matters outlined in that post.

Post a reply to this message

Vahur Krouverk wrote:

> Thomas Willhalm wrote:
>> 
>> As it comes to POV-Ray, the "stable" version is probably the official
>> release. AFAIK the POV-Team includes known bug fixes in minor updates.
> 
> I don't expect POV-Ray 4.0 anytime soon, perhaps in year 2004?

That sounds optimistic! What I meant is: As soon as there is *some* code
(which would of course barely do anything), a public cvs server -- or
a similar system - would be nice. My impression is that there are a lot of
experienced programmers around here. If they were able to look at the
code and comment on it in an early stage of development, it should 
speed it up and lead to a better result. But, as mentionend in the FAQ,
this might going to happen.

Best regards
Thomas

Post a reply to this message

Vahur Krouverk wrote:
> 
> Seems like there is quite interest in this proposal. To be more concrete:
> 1. Is out there anyone, who can provide (CVS?) server for unofficial
> POV-Ray releases?

What about sourceforge?

> 3 (probably most important?). Is there interest among POV-Ray 'hackers'
> to have such 'united' version of POV-Ray patches? '

IMO it would help. However the (more) active patch writers should answer
this question.

> 4. Is there enough people ready to try/use/test POV-Ray versions, built
> by such approach (buildmaster can't be only person for such task!)

In view of the big success of MegaPov I assume that there would be a lot
of interest, if it contains neat features. (Do you remember live without
isosurfaces and photons?)

Best regards
Thomas

Post a reply to this message

Thomas Willhalm <tho### [at] uni-konstanzde> wrote:
> If they were able to look at the
> code and comment on it in an early stage of development, it should 
> speed it up and lead to a better result.

  Although this is probably true in some cases, it might also be a burden.
Usually there are as many opinions as coders, and most people are quite
eager to express them, no matter how useful/useless the opinion is.
Trying to decipher all the text posted by people and getting the good
opinions can be a big job... Who is going to do it?

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Warp wrote:
> Thomas Willhalm <tho### [at] uni-konstanzde> wrote:
> 
>>If they were able to look at the
>>code and comment on it in an early stage of development, it should 
>>speed it up and lead to a better result.
> 
> 
>   Although this is probably true in some cases, it might also be a burden.
> Usually there are as many opinions as coders, and most people are quite
> eager to express them, no matter how useful/useless the opinion is.
> Trying to decipher all the text posted by people and getting the good
> opinions can be a big job... Who is going to do it?

Were the POV team to conduct their design discussions here, or in a 
newly created group, say, povray.developers, they would be perfectly 
able to ignore all traffic from non team members for as long as they 
liked. This would allow serious potential developers to get a feel for 
the new POVRay from the ground up and discuss it amongst themselves. 
Eventually, little by little the team members might peruse bits of the 
chatter and start to identify those people seeming to make worthwhile 
comment. From there the developer network can gradually expand. While 
not necessarily admitting more and more people to the core team itself, 
a broad base of committed developers could be established, thus allowing 
useful opinion to filter through without anyone in particular having to 
monitor all the traffic in the group full time.

Certainly, this is but one way of many that the POV Team might decide to 
go about migrating POV development more open model, but I dont see it as 
particularly problematic.

Post a reply to this message

In article <3DA### [at] alphalinkcomau> , Edward Coffey 
<eco### [at] alphalinkcomau>  wrote:

> Were the POV team to conduct their design discussions here, or in a
> newly created group, say, povray.developers, they would be perfectly
> able to ignore all traffic from non team members for as long as they
> liked.

You are kidding, right?

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> In article <3DA### [at] alphalinkcomau> , Edward Coffey 
> <eco### [at] alphalinkcomau>  wrote:
> 
> 
>>Were the POV team to conduct their design discussions here, or in a
>>newly created group, say, povray.developers, they would be perfectly
>>able to ignore all traffic from non team members for as long as they
>>liked.
> 
> 
> You are kidding, right?

Could you be more specific?

Post a reply to this message

On Fri, 11 Oct 2002 23:09:42 +0300, Vahur Krouverk <vkr### [at] starmanee>
wrote:
> Seems like there is quite interest in this proposal. To be more concrete:
> 1. Is out there anyone, who can provide (CVS?) server for unofficial 
> POV-Ray releases?

If you mean such a server for 4.0 rewrite it will be probably holded by the
team somehow. But you mean 3.5 patches, right ? I'm trying to do PoPOV as good
as I can but I'm limited with family requirements and company tasks. I can't
set up CVS in my own domain (art.pl) becouse art.pl is special domain here in
Poland and has special rules. But I can ask my friend to create some account
on the same server my abx.art.pl is located on. That's what I can do.

> 2. Is there anyone, who agrees to be 
> 'buildmaster'/'maintainer'/'whatever-you-call-him/her', who has 
> knowledge of version control systems (CVS?), who has development tools 
> (compilers and computers to compile POVRay (for at least for Linux and 
> Windows??)) and has sufficient time to build releases for POV-Ray 
> patches, maintain CVS repository (merge patches with main branch), etc.

Being maintainer on such system is a big responsibility. Such a person should
also has knowledge about povray itself and has some commercial packages as
POV-Team use. But in general being maintainer of such creation seems larger
responsibility than being POV-Team Member.

> 3 (probably most important?). Is there interest among POV-Ray 'hackers' 
> to have such 'united' version of POV-Ray patches? '

If not I hope PoPOV will be sufficent and allow quiet but effective work on
4.0.

> 4. Is there enough people ready to try/use/test POV-Ray versions, built 
> by such approach (buildmaster can't be only person for such task!)

Count me in.

ABX

Post a reply to this message

In article <3DA### [at] alphalinkcomau>,
 Edward Coffey <eco### [at] alphalinkcomau> wrote:

> That's good, but it was more than two years ago, it would be nice to 
> hear what the team has to say today on the matters outlined in that post.

The situation has not changed (other than 3.5 being out now), or that 
post would not be there any more. Don't expect it all to show up right 
after the 3.5 release, getting 3.5 out was a lot of work from people who 
don't actually have to do it, and getting 4.0 started and this kind of 
system set up would be even more work, the POV Team deserves a break.

It is pretty old info though, I'll go nag some people for an update... 
;-)

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/

Post a reply to this message