|
|
 |
The
sharing model is
an attempt to show how programmers across UCLA can benefit from
sharing.
1.Question - you have a technical question of some sort want
to know if anyone else on campus has any ideas about it.
2.Problem - you have a technical problem of some sort that
you may or may not have a solution for, but you'd like to see if
anyone else on campus has done something similar before you start
programming.
3.Program - you have written a program, maybe not very neatly
or well-documented, but it works for your purposes. You add it
to this category IF you are willing to demo it.
4.Clone Program - someone else has seen your demo, wants to
use or adapt it, and works with you (or interviews you) to create
docs and remove any passwords or private info. At this point the
code might need a lot of work to be used elsewhere, but it's
ready if someone wants to try.
5.Generic Program - you, or someone else, makes the program
generic so it is more easily installed and used in other parts of
UCLA.
6.Sharable Service - you, or someone else, turns this program
into a service available to all programmers on campus. The source
code might not be released in this case. A major example is ISIS.
|
|
|