[Rule-list] ANNOUNCE: coordinators assignments

[Marco Fioretti]

Hello,

some days ago I asked for somebody to take direct responsibility for
developing and testing the installer. Chuck Moss and Benoit Mortier
volunteered, and, after discussing it among the three of us, I am
pleased to announce that Chuck will coordinate the actual installer
development, and Benoit the many, many tests that will have to be run
to guarantee its quality and robustness.

The details are below, and will be put also on the website within a
couple of days. Of course this doesn't mean that I will wash my hands
about these issues. I will (do my best to) follow everything going on,
but, as explained previously, these two particular tasks need people
who are better programmers than me, and faster Internet connections
too.

Please help Chuck and Benoit as much as you can, and communicate them
anything they might need (what part of the installer you plan to
modify and why to Chuck, or which machines you have available for
testing to Benoit). Do it privately, if you feel it's not necessary to
send it to the list, but in that case please CC linuxdesk at inwind
dot it (not THIS address).
 
Thanks a lot again to Chuck and Benoit, and of course to everybody who
has already done a lot to get this project going

	Ciao,
	Marco Fioretti
	RULE project leader

Installer subproject

        change standard Red Hat anaconda into an installer that:

        o   will function in less than 32 MB RAM
        o   work at least from cdrom, and floppy, but also
        o   work on laptop with PCMCIA ethernet or parallel port
            connectivity and floppy, but no cdrom
        o   (not mandatory but would be nice) fit in a set of
floppies,
            able to install from standard Red Hat CDs
        o   can deal with old hardware

        What should this mean exactly? Deal with older BIOSes,
        dinosaur CDROM or disk controllers, weird peripherals, what?
        It is important to define exactly what we have to accept and
        what is unreasonable or impossible.

    Technical coordinator: Chuck Moss, cmrule at mossc dot com

        Tasks:
        
        o   choose the better development strategy
        o   distribute the work among developers,
        o   keep track of what happens....
        o   collect and maintain documentation of what has been done
        o   assign bugs founds by the testing team to the developer
            responsible for the corresponding code, or whoever is more
            available, to guarantee that the bug is not left alone
            
            
Installer testing subproject

        Tester: person who maybe doesn't know programming, or has no
        time to do it, but has one or more PCs available to:
 
        o   download any new ISO/boot image released by developers
        o   start an install with that on his PCs
        o   when it is finished, reports result, giving all info about
            any bug/trouble/etc... 

        Obviously NOTHING forbids being both a tester and a developer
        at the same time!
        
        After the developers have released something, the test team
        must, obviously, test it in all meaningful cases, and report
        the result.
        
    Technical coordinator: Benoit Mortier benoit dot mortier at
opensides dot be

        Tasks:
        
        o   defines test procedure (how to test, how to report bugs..)
        o   makes sure every tester strictly follows it
        o   figures out all the combination of tests that need to be
        done, i.e. the meaningful mixes of ( RAM / HD space / CPU /
        laptop vs desktop /ISA or other legacy HW / CDROM vs NFS
        install)
        o   knows which tester is equipped for which combo (Bill has
        a laptop with 16 MB of RAM, Joe a desktop with 32 MB but ISA
        cards...)
        o   distributes the tests as needed whenever a new release is
        available
        o   collects and filters all results, making them available to
        developer team

 


-- 
There can be no daily democracy without daily citizenship.
					      Ralph Nader

_______________________________________________
Rule-list mailing list
Rule-list at mail.freesoftware.fsf.org
http://mail.freesoftware.fsf.org/mailman/listinfo/rule-list