question_export, question_import and results_export has now been separated out of quiz. We have created a separate project for these modules here:
http://drupal.org/project/quiz_ei
The reasons for having a separate project is mainly to reduce the size of each project and give them separate release cycles.
The EI modules are included in Quiz 4 Beta 6. With releases after beta 6 the import and export modules will be gone, and you'll have to download and install the quiz_ei project to continue using those modules.
Pros
Separate release cycles
- Bugs in one of the projects doesn't have to affect the other.
- Spend less time testing each release
- Updates can be rolled out faster
Smaller projects
- The Quiz project is huge. Making the code base a little bit smaller might help attract more maintainers, and makes quiz easier and faster to maintain. The same is even more true for a possible new Import/Export project.
- Separate issue lists
- I believe that the majority of users uses Quiz without import and export features.
Cons
Dependencies
- The import and export modules are closely tied to Quiz. Changes in quiz can make the Import and Export modules fail. This means that our users have to keep track of what versions of their Import and Export modules is compatible with what versions of Quiz. (This can be minimized by keeping/making the interface between Quiz and Import/Export modules clear)

Comments
Should create a QQ-API (Quiz Questions API)
I favor the separation of export/import of quizzes/questions and the main quiz itself. We can address the "Cons" by making an API.
CORE: It should manage the quizzes and questions (their creation and retrieval) - and store users performance on them. Also, it should provide an API to let other modules access and modify these values. So, it can contain the following modules: quiz, quiz_question, truefalse, multichoice, short_answer, long_answer, scale, matching, quiz_directions, QQAPI.
QUIZ-EI: It should contain all helper tools for creating and conducting a quiz and should exclusively use the QQAPI for interacting with CORE.