I believe that the SDN-community has an enormous creative potential. We use to discuss our ideas online and scetch programming techniques in weblogs. Unfortunately, a consequence of ABAP software logistics is that it is quite difficult to contribute the results of our work to other ABAP developers like we could do at sourceforge.net for example.
But indeed it would be possible to start Open Source projects in ABAP. Ideally, from a technical point of view we would need
- a central Web Application Server,
- an administrator,
- an own namespace (perhaps /SDN/),
- programming rules concerning package dependencies.
Of course, we would also need rules for joint work: what has to be done before starting a new software project, for example.
A more minimalist approach would call for a repository to store transport requests. Although distributed development would be impossible, interested parties could at least import the requests into their own systems, thus obviating the need to manually recreate lots of development objects. A dedicated namespace and rules concerning the naming and allowed dependencies of packages provided via this service would be necessary nevertheless.
However, at first we should answer the question whether there is a need for Open Source software based on SAP and whether this community can manage it.
Or do think this is this too ambitious? But perhaps this suggestion could lead to platform that allows SDN members to present their prototypes/solutions to other SDN members?
What do you think?