Questionnaire about the Bugzilla development process

[David Miller]

I was going to just answer this, but some of the questions are throwing 
me a little (provided choices for some of the answers don't quite match 
;) So I figured I'd throw this out here for discussion, and I can mail 
it back to him when we settle on how to answer.

This is from a researcher trying to research how open source projects 
operate with emphasis on Agile and Extreme Programming.  (whatever that 
is, I'm not up on the buzzwords)

Some of the stuff in here is in the midst of change right now, too (as 
other recent threads on this list show).

> GENERAL INFORMATIONS
> 1.     Do you know Agile Methodologies, and in particular Extreme
>         Programming and its practices?
>         [ ] A. Yes    [ ] B. No
>         If so, which of XP practices does your OS project make use of
>         or benefit from?    [ ]
> 
> 2.     How many people are using your project?    [ ]
> 
> 3.     How many developers contribute to your project and how many
>         of them are allowed to commit?    [ ]
> 
>         ANALYSIS AND PLANNING
>         1.    In your OS project, how often project requirements are
>                analyzed?    [ ]
> 
>         2.    Do you apply the Simple Design XP practice, "do the simplest
>                thing that could possibly work"?
>                [ ] A. Yes    [ ] B. No
> 
>         3.    How often do you release a new version?    [ ]
> 
>         CODING
>         1.    Does your OS project adhere to coding standards?
>                [ ] A.    yes, we have an explicit set of standards
>                [ ] B.    standards are often enforced by the key developer
>                            who messages contributions in his own style
>                [ ] C.    no
> 
>         2.    In XP, the "collective code ownership" practice means that
>                anyone can modify any part of the project.  In your project:
>                [ ] A.    everyone is allowed to make and commit changes
>                            directly (e.g. via CVS)
>                [ ] B.    only a few people are allowed to make changes
>                            directly and developers changes are required
>                            to be submitted for review.
>                In the latter case, what process is required for developers
>                to submit changes?    [ ]
> 
>         3.    Do developers practice continuous integration?
>                [ ] A. Yes    [ ] B. No
>                If so, which tool or framework do they use and how often do
>                they integrate their developed code?    [ ]
> 
>         4.    How many time (average hours per week, month or year) do
>                contributors spend working at the project?     [ ]
> 
>         REFACTORING
>         1.    If contributors of your OS project practice refactoring,
>                they do this:
>                [ ] A.    all the time
>                [ ] B.    after a new functionality is added
>                [ ] C.    sometimes, when is being too difficult add new
>                            functionalities
>                [ ] D.    only when the system is going to break
>                [ ] E.    others:
> 
>         2.    Which tool or framework do developers use for refactoring?
>                [ ]
> 
>         3.    In which way does refactoring improve (or could improve)
>                the OSS development process?
>                [ ] A.    simplifies the code design level
>                [ ] B.    keep your code clean and concise, it is easier
>                            to understand, modify, and extend
>                [ ] C.    throughout the entire project life cycle saves time
>                            and increases quality
>                [ ] D.    others:
> 
>         TESTING
>         1.    If your developers community practices testing,
>                who writes tests?
>                [ ] A.    a specific team or a core member
>                [ ] B.    each contributor must test the code he develops
>                [ ] C.    there are no set rules for testing: if the
>                            developer wants he can test his code
>                [ ] D.    others:
> 
>         2.    Which tool or framework do developers use for testing?    [ ]
> 
>         3.    They have used this practice:
>                [ ] A.    since the project started
>                [ ] B.    from a certain point of the development process
>                            (in the middle, towards the end...).
> 
>         4.    Testing is carried out:
>                [ ] A.    in a systematic way: tests are provided as class
>                            methods but written after the code itself
>                [ ] B.    only to certain class methods, when needed
>                [ ] C.    tests are written  before the code itself, as XP.
>                            The community adopts the "Test Driven
>                            Development" practice (TDD).
> 
>         5.    In which way does testing improve (or could improve) the OS
>                development process?
>                [ ] A.    the code is more robust, it's simpler for
>                            developers to add a new code
>                [ ] B.    It's simpler to find and fix bugs and defects
>                [ ] C.    the project requires less oversight and review,
>                            because you know what worked
>                [ ] D.    testing encourages more people to contribute
>                            because they have immediate feedback on whether
>                            their changes worked or not
>                [ ] E.    testing allows you to release early and often
>                [ ] F.    contributors can be more confident developing
>                            because they know that the tests will catch
>                            accidental breakage
>                [ ] G.    testing improves code quality
>                [ ] H.    others:

-- 
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/