Hello,

Paul Morelle (madprog), Guillaume Bouchard (guibou) and me talk about moving
soya to a Decentralized VCS hosting. We are suggesting moving to mercurial[1]
dvcs on a http://bitbucket.org account.

This suggestion is included in a bigger plan. Paul Morelle is working on the
testing and documentation side:
    - Way to test SDL base process without opening any window,
    - Moving the documentation to sphinx,
    - Turning tutorial into online documentation,
    - Turning tutorial into test.
Guillaume Bouchard is working on a migration from Pyrex to Cython and in
particular in a way to avoid generating recompiling 200 000 line of C every
time a single comma is altered in pyx source.

The move will probably motivate the following reorganisation:


1. split the huge soya repo into multiple one:

    :soya3d:      to hold the current content of soya/ and soya-contrib 
directories
    :cerealizer:  to hold the current content of cerealizer/ directory
    :tofu:        to hold the current content of tofu/ tofu_enet/ tofu_udp/ 
directories

    the osx_stuff/ directory is probably deprecated

    the ebuild/ directory will be split in associated repo

2. Relayout source and non-source.

    I'm very fond of this convention but current python packaging tool pretty
    much enforce the setup.{py,cfg} file to be at root of a directory that
    contains root directory of the python package.

    If you did not understand the above sentence:
    $ cd soya
    $ mv setup.* ..
    $ mv docs ..
    $ mv tutorials ..
    $ mv tests ..


Unless some opposition raise, I'll move forward and create a soya-project
account on bitbucket.


-- 
Pierre-Yves <marmoute> David


[1] this suggestion include a free introduction to mercurial for jiba

_______________________________________________
Soya-user mailing list
[email protected]
https://mail.gna.org/listinfo/soya-user

Reply via email to