SDN survey: change-request files or manual instructions?

Hello!

Recently I made an experiment and it failed. I have posted a weblog Program Parameters vs hardcoding where I've explained the idea about an OO ABAP component, and I wanted to share the component too. I provided both downloadable change-request files (I submitted content which was linked to the weblog) and manual instructions on how to create the component. I asked a question which of these you prefered, but unfortunatelly didn't get any feedback on this dilema. I don't know why - maybe my component wasn't attractive enough, or folks simply didn't feel like answering, or both options required too much time and effort.

Actually, I'd like to know which is the best way to share objects on SDN? Now, let's see what are the options with pros and cons:

• change-request files:
  • Pros:
    • Fast 'n' easy: no doubt the fastest and easiest way for a reader to have his/her copy of a big and complicated (set of) component(s) and use it in daily work
  • Cons:
    • Potential danger: You don't have control over the change-request content and therefore can't be sure that malicious content won't get into your system. I have never heard of SAP virus or trojan or whatever, but how can we be absolutely sure?
    • BC skills: You need to have certain level of BC skills - should go into transport domain server's file system and place the two change-request files into the right folders. Then you should know what to do in STMS transport transaction to import the request.
    • BC authorisations: You should be authorised to access the server file system and use SAP's transport system (STMS)
    • BC himself: if you don't have at least one of two above mentioned, must talk to a BC and give him the files
    • Company rules: if the security in a company is very strict, you might need to pass through bureaucratic hassle to get approval just to see some sample which in the end might not be so useful. I can't blame anyone quitting at this point.
    • Mini: - the most secure is to have own personal SAP for playing around. Then you need nobody's approval - you're your own boss. But how many of us have Mini SAP (or WAS, whatever)?
• manual instructions:
  • Pros:
    • Faster for little things: well, to be honest, if the component is small and simple, for example one executable report, it's faster to copy-paste it than to download/upload change-request.
    • Security: You know exactly what's getting into your system, because you're doing it all with your hands. If you're a registered developer, you need nobody's approval (or do you?).
    • Learning: by doing it manually, you will probably learn more about the concepts than by uploading it in a request.
  • Cons:
    • Time and effort: if the component is big and complicated, or even if there are more such components, it requires a lot of effort and time to setup something. Maybe you simply don't have time, maybe you don't know if the component is really useful. All in all, bigger the effort, lower the probability that someone will actually try it.
• Both:
  • Pros: surely this would be best, everyone could choose at their preference.
  • Cons: it requires always double effort for blogger
• None: maybe at certain point the effort and time consumption is simply too big, and no method would have results. Maybe there's nothing we can do to encourage people to actually try something if it's too big (of course, it also depends on how attractive it is). It would be good to know this, because then we'll know that only small code (and idea) snippets make sense.
• What else?
  If you can think of more possibilities to share effectively, not only ideas, but real components on SDN, please speak.