Hey Jimmy, You can do a fork on the github project and do a pull request. On the licensing front, SLURM is released using the GPLv2 license. If it isn't too much of a problem it would be nice to be consistent with that. But it is up to you what you release your code as.
I am guessing you have flushed out the current phpext dir already in the contribs dir. In any case, this is a great contribution, thanks! Danny > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Jimmy Tang > Sent: Thursday, May 05, 2011 1:06 PM > To: [email protected] > Subject: [slurm-dev] what's the preferred way of submitting code to the > contribs/ directory > > Hi All, > > I've recently been supervising an intern with implementing a php > extension to slurm and the work is mostly complete (there is just some > documentation that needs to be done). We're planning on releasing the > code with a GPLv3 license back to the slurm community, I was wondering > what's the preferred way that the slurm project prefers for accepting > material for the contribs directory, i.e. tarballs, patches or forking > the github project? Or would it be preferable to keep the php > extension as a separate repository/project? > > Thanks, > Jimmy. > > -- > Trinity Centre for High Performance Computing, > Lloyd Building, Trinity College Dublin, Dublin 2, Ireland. > http://www.tchpc.tcd.ie/
