Agreed about clarity.. Anyone against "TAVERNA" as key?
I'll prepare loading this up in a docker image with a backup dump of T3 from today, and then we can see what it looks like. On 9 March 2015 at 15:46, Christian Brenninkmeijer <[email protected]> wrote: > Personally I would go for the whole "Taverna" > > A link like: > https://issues.apache.org/jira/browse/TAV-846 > is hard to know what it is about while > https://issues.apache.org/jira/browse/TAVERNA-846 > is much clearer. > > Christian > > ________________________________________ > From: Stian Soiland-Reyes [[email protected]] > > .... > > and will HTTP redirect (in Apache) to something like: > > https://issues.apache.org/jira/browse/TAV-846 > > > > Are we still OK with the "TAV" Jira project key? The Taverna 1 bugs > (which we'll leave behind!) use the same prefix TAV: > > http://dev.mygrid.org.uk/issues/browse/TAV-781 > > > I personally feel that "T3" is not appropriate within all of Apache - > yet Jira names tend to be short as they'll be used a lot in emails and > commit messages. > > The new key could also be "TAVERNA" -- see existing ones at Apache: > > https://issues.apache.org/jira/secure/BrowseProjects.jspa#all > -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
