Hello, If we move any of the codebases with licences that need to be checked to taverna-extras does that cause problems in the future. Can we then fix them outside of the the apache repo and then move them back in when they are ready?
Out of all of these codebases what ones do we really, really, really need to part of Apache Taverna at graduation. I think it would be good to have taverna-server. I'm not fussed about workbench right now. Cheers, Ian On 24/01/17 11:01, Ian Dunlop wrote: > Hello, > > We've stalled a bit on the graduation discussion. To help a bit I > created a few sub-pages with apache rat licence/header output for > various projects - see > https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review. > Which of these source files etc needs changed? Some of them are just for > test purposes so can we just exclude them? Some of them are used by > source code to build workflow activities. I was concerned that adding > headers to them could break them - is that the case? Which things do we > need to capture in NOTICE files? > > What do we need to do for graduation? We've had a few releases. The > community has grown. What is there stopping the project from going for > graduation? > > Cheers, > > Ian > >
signature.asc
Description: OpenPGP digital signature
