.... this is a questionnaire addressed to all authors of GUI's for
cdrecord or cdrtools or to people who maintain other software that
is related to cdrtools. As I assume that all such authors are reading
this mailing list I believe this is the right forum.
First some general questions that are not related to cdrtools at all but apply to
any OpenSource project:
1) Vitality:
- how many releases did you publish within the last 12 months?
- How many of these releases have 'only' been bug fix releases?
- how many weeks from now did you publish the most recent
release?
- Do you plan to publish a new release within the next month?
- How many hours do you spend on your project per week?
- How many hours of your free (unpaid) time do you spend on your
project(s) per week?
- Do you believe that your program is granted to be supported
and to make progress in a long term scope?
- will it survive the next year?
- will it survive the next 2 years?
- will it survive the next 5 years?
- will it survive the next 10 years?
- what will happen if you finish your study or if you
change your job?
- what will happen if you find a new friend, marry or
get children?
- Do you believe that you get enough help from other people and
users of your program for development and support?
2) Portability:
Does your project run on:
- Solaris
- Linux
- Win32 (if yes, does it need an X server?)
- HP-UX
- MacOS X (if yes, does it need an X server?)
- Is your program portable at all?
- Do you plan to increase the portability of your program?
- Which platform that is not yet supported will get support in
the near future?
3) Open Source:
- Is your project an OpenSource project?
- Does your project rely on non-OpenSource parts?
(this may be one or more libraries needed to
allow compilation ad linking)
4) Code quality:
- Do you perform code reviews?
- on a regular base
- from time to time
- never
- Do you use any source code control system?
If yes, do you:
- use SCCS
- use CVS
- check in from time to time
- check in before you publish a new release
- check in on a dayly base
- check in every time a senseful and self-contained
change has been made
- Do you allow other people to make changes on your source?
If yes, how do you control the quality of these changes?
Do you
- allow uncontrolled access to the SCCS or CVS history
- apply patches send to you from other people
- check and discuss patches before applying a reviewed
version of the patch
5) Documentation:
- Is there any written documentation?
- Do you have a troff -man version of the documentation?
- Do you have a sgml version that auto-translates into troff?
- If there is a troff or sgml manual, do you:
- have documented all features of your program in it?
- update the man page every time you change the behavior
of the program?
6) What do you believe is the status of the programs from cdrtools or
other 'Schily SING' software with respect to the above questionnaire?
/*--------------------------------------------------------------------------*/
7) Which features from cdrtools do you support?
- which features from cdrecord
- which features from mkisofs
- which features from readcd
- which features from cdda2wav
8) Which features from cdrtools do you _not_ support?
- which features from cdrecord
- which features from mkisofs
- which features from readcd
- which features from cdda2wav
9) Which features do you get requests for and you believe that you will
be able to implement them in a reasonable time but the needed low
level support is not yet present in the appropriate cdrtools program?
9a) Do you plan to enhance the portability of your program to a set of
platforms similar to cdrtools?
9b) Which platforms that are supported by cdrtools will (or may) never be
supported by your program?
- in the near future?
- really never?
J�rg
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni) If you don't have iso-8859-1
[EMAIL PROTECTED] (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
