As an academic, I think that's a great first step. But there are many structural issues beyond this: advisors and students both under pressure to do whatever i

As an academic, I think that's a great first step. But there are many structural issues beyond this: advisors and students both under pressure to do whatever it takes to get the paper out and move on to the next project, students needing / wanting to just graduate and move on, usual yard sticks of academic achievement behind in recognizing software as legitimate product of research, etc (). On top of which, lots of different kinds of software is developed in research institutions, most of which are just rapid prototypes but some do get used by many people everyday, and it's not clear one process fits all. If anyone out there has suggestions of useful resources, I'm all ears! () Those of us who care about software do try to work on all these issues, but progress is slow.