ABX wrote:

> On Thu, 08 Aug 2002 09:16:00 +0200, Le Forgeron <jgr### [at] freefr> wrote:
> 
>>Yes, where is the "bounding for inside testing" patch ?
>>I can get the news message, but that's no code.
>>
> 
> There is difference text file with necessary changes attached to this message.
> I see it with my newsreader and newswebgate as well.
> 


Oh, I now see it, as a small link to an attached file.
I was expecting full inline code, just as for the other patch.


> 
>>Also, It may be worth to make patches availables as downloadable files
>> (either full file or just a file for the patch command (diff is
>>usually helpful to generate such file).
>>
> 
> In my own case I prefer description how, what and why is changed becouse it
> can help next MegaPOV coordinator and can be some kind of tutorial for
> beginners.
> 


I was just thinking about having something "easy" for
"Joe the Crazy-Patcher" (a newbie). Something like the set of 
consecutive (and ordered) patches that Joe blindly apply to its Linux 
kernel.
It may also help the nanoPov coordinators/maker, otherwise the 
understanding of the code become mandatory (Ok, it just take a few years 
of patching pov before understanding the subtilities...)


> 
>>I think there might be a need for a styleguide, if you intend to make
>>a repository. (describing what is provided to clients and what is 
>>requested from submitters; I believe the minimal requirement should be
>>a patch file and an example pov-scene. Syntax's update should also come 
>>with full documentation as text file or html (if picture are needed, 
>>they should be done with pov-script (provided), so that any 
>>resize/adjustement can be done without loss).
>>A styleguide extension for picture might be welcome too, in order to
>>specify some default/classical colour for some items.
>>(so that there is a kind of homogeneity between the documentations, such 
>>that all X-axis have the same colour (which should avoid nevertheless 
>>the shadeless red/green/blue, a more complex colour is better IMNSHO).
>>
> 
> Am I wrong or my own patches fits in your styleguide ?


You're ok, but if you open the repository to others, it would help to 
have the same kind of presentation for all the patches.


> I think I made rather patch directory instead of repository.
> 


I wish you will be successul, because otherwise, a lot of patches are 
going to wander on the internet. A one-stop site is a real good thing.


> 
>>Also, as long as patches do not interact, the repository should be easy,
>>but you may want to nevertheless organise the patches in a tree, the 
>>root being of course the official 3.5 code.
>>
> 
> I agree. It will be difficoult but since I'm mostly involved in translation
> project I have no time for any better organization at this moment.


So far, the patches do not impact each others, so no problem. Even the 
image of the tree is bogus when a new patch will require more than one 
previous independent patches.

> It would be
> graet if patch repository could be holded somehow on www.povray.org but than
> it could be mistaken that it is official. Also the Team should be twice as big
> as is then.


Well, Do it now on your pages, if successful it could always been 
transfered later.

Post a reply to this message