Hi Dave, I will be at HUPO and look forward to chatting with you about it then!
Regards, Eric > -----Original Message----- > From: [email protected] [mailto:spctools- > [email protected]] On Behalf Of dctrud > Sent: Monday, September 14, 2009 5:53 AM > To: spctools-discuss > Subject: [spctools-discuss] Re: Alternative interfaces, licensing etc... > > > Just a quick update and thanks again to Greg and Eric for their > comments. I've received permission to release our pipeline software > under the CDDL license... so it'll be Open Source, but unfortunately > not under a GPL compatible license. The CDDL is being used as it's > what the University are happy with, and we are keen to release > something to the community as soon as possible. I hope that some of > the code we release might be of use to others. It should be available > mid-October, when I've had time to get everything checked through. > We'll have a poster at HUPO 2009, so I look forward to meeting anyone > else who is there! > > DT > > > > On Aug 4, 4:28 pm, dctrud <[email protected]> wrote: > > Dear All, > > > > Firstly, apologies that this is going to be a bit of a rambling post. > > > > Over the past 12 months I've been working on what is effectively an > > alternative interface to the TPP vs Petunia, tailored towards giving a > > very simple front-end for users of our central proteomics facilities, > > fully automating submission to multiple search engines, and > > distributing jobs over a GridEngine cluster. There's a simple MySQL DB > > backend that tracks data submissions, searches, and results. The web > > app is written in Perl using the catalyst framework, and then there > > are a bunch of perl pipeline scripts which invoke the TPP tools etc. > > > > Lots of similar functionality is present in other packages such as > > CPAS, and in Petunia itself as it is continuously improved, but for > > various reasons we decided to re-invent the wheel, and have come up > > with something that works very nicely for us. I'm now starting the > > process of requesting clearance from the University to release the > > software. There's a new open source release procedure here and I > > really want to make sure anything useful our software contains can be > > contributed to the TPP project. > > > > Given that the open source release procedures here are very new, and > > that in the past software has been released under relatively strict > > non-commercial licenses that wouldn't allow us to give back to the TPP > > project I wondered whether anyone had any tips for arguing the case > > for a LGPL/GPL license? Are other people developing custom interfaces/ > > pipelines for the TPP tools, particularly if targetted at core > > facility usage? I'd like to be able to convincingly argue that others > > would benefit from our work, but moreover that we could benefit from > > people being interested in and potentially collaborating. > > > > Thanks, and thanks to the TPP developers for all their freely > > available work! I hope to be able to give something back soon! > > > > Dave Trudgian > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/spctools-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
