[Savannah-register-public] [task #4242] Submission of ruQueue

[John Fulton]

Follow-up Comment #2, task #4242 (project administration):


I've made your suggested changes.  Please see the updated source:

http://ruqueue.rutgers.edu/savannah/ruQueue.tar.gz

There are two files that I did not author:  

1.  countdown.js

> countdown.js is released under the GNU GPL version 2 only.
> Licensing under the "GNU GPL v2 only" is problematic. Would 
> you agree to license your project under the "GNU GPL v2 or 
> later"? 

countdown.js was written by someone else (outside of Rutgers).  
Since it was GPL I thought it would be OK, but now I see the 
v2 only issue.   Since I'm not the author I don't think I can 
change it.  I would be happy to release ruQueue so that it can 
easily advance to GPL v3.  Can we just let the countdown.js file 
be GPL v2 only and the rest of the system be GPL with ability to 
advance?  It's a such a simple clock that it would be easy to 
write my own.  Would writing my own (even after seeing the code) 
would count as fair-use since it's so simple?  I'm open to your 
suggestions for getting around this.  At the moment the COPYING 
file simply explains that this file is GPL v2 only.  

2.  base64.pl

This file came from MHonArc:   

 http://www.mhonarc.org/MHonArc/lib/base64.pl

which is standard GPL:

 http://www.mhonarc.org/MHonArc/COPYING

Are there any issues with using this file?

You had asked:  

> What motivated you to create a system similar to RT, instead of > using RT?


Originally our Help Desk was using RT but we decided to write
our own ticket system.  We're mainly a PHP shop and we felt it
would be easier (and educational) to write our own smaller
system (containing only what we need) which we would then know
in and out for easier modification in the long run.  It was also
designed to help our staff follow our Help Desk policies.  It
contains an integrated scheduling system which is linked to our
ResNet operation.  For example, ResNet Consultants enter their
schedules via the system.  The system then schedules an appointment as a part
of ticket creation and the system then notifies the consultant and end user. 
Our system also integrates with our University LDAP directory to keep track of
users and for
authentication.

Since our staff were already familiar with RT we "black boxed" a
lot of its external design.  So the HTML layout of our system
looks similar to way that RT did at that time (2001).  However,
we designed the DB and wrote the PHP scripts from scratch.  We
used Perl only for a simple mail interface that we added later.
We're not Perl experts but the CPAN Sendmail module made it easy
to do this part in Perl.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?func=detailitem&item_id=4242>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/