WG211/M6TeachinDisc
Ralf Laemmel
Many of us are giving courses at various levels with relevance for program generation, or the broader subjects of software transformation, automated software engineering, and programming languages. There is an obvious question: Doesn't it make sense to set up a repository so that we can share some of the material that we develop in different places? There are a few more questions. Only if we can answer them it may be possible to create such a repository.
1. Is it perhaps not worth the effort because we could use existing textbooks and wait for a few more textbooks, and be done with the problem of material on the subject?
2. Are there any good examples out there where other disciplines, perhaps other areas of computer science have successfully set up a repository?
3. Do we have some critical mass in mind that we can pump into the repository soon so that it becomes a reality?
4. How would one go about the copyright matter so that it is easy to release things to the repository, easy to reuse things from the repository, but still all interests of copyright holders and credits are observed?
5. Can such a repository work as a plain team effort, or would we rely on individuals to invest extra time into it (more than just releasing stuff, while hoping that such release effort is payed back immediately when adopting other material for their benefit)?
6. Are their funding options that could be leveraged here?
7. How could we add assignments (and perhaps even solutions) to the repository? That is, is it at all practical to reuse assignments somewhat over several years and in several places?
