You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Stian Soiland-Reyes <st...@apache.org> on 2016/05/09 16:48:41 UTC
Draft download pages
Hi,
I have drafted download pages for the upcoming release:
http://taverna.staging.apache.org/download/engine/
http://taverna.staging.apache.org/download/common-activities/
http://taverna.staging.apache.org/download/commandline/
And listed them on
http://taverna.staging.apache.org/download/
(Please, don't push the CMS publish button now!)
Please review and edit!
While the first two are new, and basically clones of the
/download/osgi/ page, the third page include links to Taverna Command
Line 2.5, as I think 'normal' users should still generally download
2.5 before we know how well 3.1.0 works on 'real' workflows.
For 2.5, should we keep the links to the legacy site's
http://www.taverna.org.uk/download/command-line-tool/2-5/
(Alan - what happened about those legacy banners?)
or just send them to the big list on
https://bitbucket.org/taverna/taverna-commandline-product/downloads/
?
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
Re: News pages was Re: Draft download pages
Posted by alaninmcr <al...@googlemail.com>.
On 10/05/2016 14:09, Ian Dunlop wrote:
> Hello,
>
> I guess its the G+ feed that needs updated. Who controls it? Looks like
> some GSoC 2016 news/tweets are needed. No point having the social media
> feeds if they are not used :(
It's strange as some posts have been made e.g. BioVeL = SEEK and Taverna
addressing climate change.
> Cheers,
>
> Ian
Alan
Re: News pages was Re: Draft download pages
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
I guess its the G+ feed that needs updated. Who controls it? Looks like
some GSoC 2016 news/tweets are needed. No point having the social media
feeds if they are not used :(
Cheers,
Ian
On 10 May 2016 at 13:10, alaninmcr <al...@googlemail.com> wrote:
> Hello everyone,
>
> I noticed the News https://taverna.incubator.apache.org/community/news is
> very out of date compared with the Tweets.
>
> I think it would be better to hide out of date "News". Any ideas /
> comments?
>
> Alan
>
News pages was Re: Draft download pages
Posted by alaninmcr <al...@googlemail.com>.
Hello everyone,
I noticed the News https://taverna.incubator.apache.org/community/news
is very out of date compared with the Tweets.
I think it would be better to hide out of date "News". Any ideas / comments?
Alan
Re: Draft download pages
Posted by alaninmcr <al...@googlemail.com>.
On 09/05/2016 18:58, Stian Soiland-Reyes wrote:
> OK, great if you could put it live!
>
> I think now with the Command Line relesse is a good time to force old users
> through the Apache Taverna pages, even if it might mean they go back to the
> archive page to download the 2.5 Workbench.
It should be live now.
Alan
Re: Draft download pages
Posted by Stian Soiland-Reyes <st...@apache.org>.
OK, great if you could put it live!
I think now with the Command Line relesse is a good time to force old users
through the Apache Taverna pages, even if it might mean they go back to the
archive page to download the 2.5 Workbench.
On 9 May 2016 6:22 p.m., "Alan Williams" <al...@googlemail.com> wrote:
> On 09-May-16 17:48, Stian Soiland-Reyes wrote:
>
>> Hi,
>>
>> I have drafted download pages for the upcoming release:
>>
>> http://taverna.staging.apache.org/download/engine/
>> http://taverna.staging.apache.org/download/common-activities/
>> http://taverna.staging.apache.org/download/commandline/
>>
>>
>> And listed them on
>> http://taverna.staging.apache.org/download/
>>
>> (Please, don't push the CMS publish button now!)
>>
>>
>> Please review and edit!
>>
>>
>> While the first two are new, and basically clones of the
>> /download/osgi/ page, the third page include links to Taverna Command
>> Line 2.5, as I think 'normal' users should still generally download
>> 2.5 before we know how well 3.1.0 works on 'real' workflows.
>>
>>
>> For 2.5, should we keep the links to the legacy site's
>> http://www.taverna.org.uk/download/command-line-tool/2-5/
>>
>> (Alan - what happened about those legacy banners?)
>>
>
> I wondered that as well! They are still on prototype.taverna.org.uk
> though so I will do another copy tomorrow.
>
> or just send them to the big list on
>> https://bitbucket.org/taverna/taverna-commandline-product/downloads/
>> ?
>>
>
> I think it's OK to go to the legacy pages.
>
> Alan
>
>
Re: Draft download pages
Posted by Gale Naylor <Ga...@noventussolutions.com>.
Thanks for the blast-from-your-past, Stian. Too bad I can't read Norwegian!
I speak a little German, so I'm familiar with compound-word-isms. ;-)
Deciding how to hyphenate and capitalize Command-line Tool turns out not to
be a trivial issue. I spent some time today looking into this. (If you're
really interested, I wrote a blog post, too: http://bit.ly/1TS7YXi)
------------------------------------
Documentation
------------------------------------
As Stian noted, both command line and command-line can be found. After some
thinking, this is what I propose for the documentation (README files and
website).
Use Taverna Command-line Tool when talking about the tool and in titles.
For example, Taverna Command-line Tool (as a title)
or “The Taverna Command-line Tool relies upon …” (in a sentence).
Use all lower case (command-line tool) when talking about generic
command-line tools.
For example, “The Taverna Command-line Tool is one of two command-line
tools…”
Other acceptable ways of referring to the Taverna Command-line Tool (and
variations) would be:
Command-line Tool
Apache Taverna Command-line Tool
Apache Taverna Command-line product
Avoid:
Taverna Command-line (always use “Tool”)
Taverna Command line Tool (always hyphenate)
Taverna Command Line Tool (always hyphenate and use lower case “l”)
------------------------------------
Changes to git repo/groupId?
------------------------------------
As far as the GIt repo and groupId names for the Command-line Tool are
concerned,
I agree that keeping "commandline" as one word in the repo, groupId, and
artifacts looks cleaner.
In looking at the repo names and pom.xml files, I wonder if it is
reasonable to change the following:
incubator-taverna-common-activities
--> groupId to org.apache.taverna.common.activities
incubator-taverna-commandline
--> name to Apache Taverna Command-line
incubator-taverna-workbench-common-activities
--> groupId to org.apache.workbench.common.activities
--> artifact to apache-workbench-common-activity
I don't know how difficult it is to manage all the relationships, but it
would be nice if these were consistent.
------------------------------------
Question
------------------------------------
incubator-taverna-workbench-product has the same groupId as
incubator-taverna-workbench. Is this correct?
To quote Ian, Cheers!
Gale
On Thu, May 12, 2016 at 3:18 AM Stian Soiland-Reyes <st...@apache.org>
wrote:
> On 10 May 2016 at 01:03, Gale Naylor <Ga...@noventussolutions.com> wrote:
> > Is there a difference between "Taverna Command Line Tool" and "Taverna
> > Command Line"? It seems sometimes on the download page we use one term
> and
> > sometimes we use the other term. For example,
>
> No difference - just my Norwegian compound-word-ism sneaking in! We
> would say "Taverna Kommandolinjeverktøy" - rolls off the tongue..
>
> { https://wiki.ucl.ac.uk/display/ScanStuds/Norwegian+Compounds
> And in fact in my teenage years I was an active campaigner to remind
> Norwegians to write compound words correctly and not pretend it's
> English - from a 1997 newspaper:
> http://soiland-reyes.com/stian/scrap/lausslept.png
> (Sorry, we didn't have perma-urls back then..)
> }
>
>
> Notice that the git repository is "incubator-taverna-commandline", our
> groupID is "org.apache.taverna.commandline", artifactIds are
> "taverna-commandline-api" etc, and the download would be called
> apache-taverna-commandline-3.1.0-incubating.tar.gz -- I thought it
> would be nice if those "code names" had consistent hyphenization --
> and for me this is good to avoid the hierarchically more confusing
> "taverna-command-line-api".
>
> However we also have "incubator-taverna-common-activities" with
> groupId org.apache.taverna.commonactivities!
>
> Changing git repo names I think CAN be done at this point - probably a
> bit of a hazzle for Infra to keep the GitHub link ; if we want to
> change group/artifactIds we should decide on now before we do the
> first release.
>
>
>
> However the English title we can be more liberal with (but yes,
> consistent) - just like
> https://taverna.incubator.apache.org/download/osgi/ describes the
> "Apache Taverna OSGi plugin system " rather than the misleading
> "Apache Taverna OSGi".
>
> https://en.wikipedia.org/wiki/Command-line_interface uses the spelling
> "command-line interface", but the spelling "Command line" is also ver
> common - but in my view does not read very well in further
> combinations, after all we don't provide a "Line tool".
>
>
> Which English title one should it have? Perhaps "Taverna Command-Line
> Tool" ? Weird?
>
> We've got several native English speakers here from 3 different
> continents - what are your views?
>
>
>
> > I made some minor edits to the three download pages. I changed the title
> of
> > the command line page to say "Download" and match the other two pages.
>
> Thanks!
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>
Re: Draft download pages
Posted by Stian Soiland-Reyes <st...@apache.org>.
On 10 May 2016 at 01:03, Gale Naylor <Ga...@noventussolutions.com> wrote:
> Is there a difference between "Taverna Command Line Tool" and "Taverna
> Command Line"? It seems sometimes on the download page we use one term and
> sometimes we use the other term. For example,
No difference - just my Norwegian compound-word-ism sneaking in! We
would say "Taverna Kommandolinjeverktøy" - rolls off the tongue..
{ https://wiki.ucl.ac.uk/display/ScanStuds/Norwegian+Compounds
And in fact in my teenage years I was an active campaigner to remind
Norwegians to write compound words correctly and not pretend it's
English - from a 1997 newspaper:
http://soiland-reyes.com/stian/scrap/lausslept.png
(Sorry, we didn't have perma-urls back then..)
}
Notice that the git repository is "incubator-taverna-commandline", our
groupID is "org.apache.taverna.commandline", artifactIds are
"taverna-commandline-api" etc, and the download would be called
apache-taverna-commandline-3.1.0-incubating.tar.gz -- I thought it
would be nice if those "code names" had consistent hyphenization --
and for me this is good to avoid the hierarchically more confusing
"taverna-command-line-api".
However we also have "incubator-taverna-common-activities" with
groupId org.apache.taverna.commonactivities!
Changing git repo names I think CAN be done at this point - probably a
bit of a hazzle for Infra to keep the GitHub link ; if we want to
change group/artifactIds we should decide on now before we do the
first release.
However the English title we can be more liberal with (but yes,
consistent) - just like
https://taverna.incubator.apache.org/download/osgi/ describes the
"Apache Taverna OSGi plugin system " rather than the misleading
"Apache Taverna OSGi".
https://en.wikipedia.org/wiki/Command-line_interface uses the spelling
"command-line interface", but the spelling "Command line" is also ver
common - but in my view does not read very well in further
combinations, after all we don't provide a "Line tool".
Which English title one should it have? Perhaps "Taverna Command-Line
Tool" ? Weird?
We've got several native English speakers here from 3 different
continents - what are your views?
> I made some minor edits to the three download pages. I changed the title of
> the command line page to say "Download" and match the other two pages.
Thanks!
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
Re: Draft download pages
Posted by Gale Naylor <Ga...@noventussolutions.com>.
Is there a difference between "Taverna Command Line Tool" and "Taverna
Command Line"? It seems sometimes on the download page we use one term and
sometimes we use the other term. For example,
>Taverna Command Line Tool
<http://taverna.staging.apache.org/documentation/command-line> enables you
to run workflows from a command prompt.
>Taverna Command Line Tool is basically the Taverna Workbench stripped of
its GUI so you can run workflows from a command prompt headlessly (i.e.
without the graphical environment).
>Apache Taverna Command Line can run workflows ...
I made some minor edits to the three download pages. I changed the title of
the command line page to say "Download" and match the other two pages.
On Mon, May 9, 2016 at 2:59 PM Gale Naylor <Ga...@noventussolutions.com>
wrote:
> Right! I forgot about that. Thanks for the reminder!
>
> On Mon, May 9, 2016 at 2:38 PM Stian Soiland-Reyes <st...@apache.org>
> wrote:
>
>> You need to click the "[Update this directory]" button from
>> /trunk/content/
>>
>> The CMS is a bit confusing.. it has a personal SVN checkout for you -
>> and so if you come back 3 weeks later it will stay at the version it
>> had at your last edit!
>>
>> On 9 May 2016 at 19:02, Gale Naylor <Ga...@noventussolutions.com> wrote:
>> > I am having trouble editing the staged versions of the engine,
>> > common-activities, and commandline download pages. I can't find them in
>> the
>> > download directory:
>> >
>> https://cms.apache.org/taverna/wc/browse/gnaylor-C4CSQm/trunk/content/download/
>> >
>> > Is there something I'm missing, or something special I need to do?
>> Thanks.
>> >
>> > On Mon, May 9, 2016 at 10:22 AM Alan Williams <alaninmcr@googlemail.com
>> >
>> > wrote:
>> >
>> >> On 09-May-16 17:48, Stian Soiland-Reyes wrote:
>> >> > Hi,
>> >> >
>> >> > I have drafted download pages for the upcoming release:
>> >> >
>> >> > http://taverna.staging.apache.org/download/engine/
>> >> > http://taverna.staging.apache.org/download/common-activities/
>> >> > http://taverna.staging.apache.org/download/commandline/
>> >> >
>> >> >
>> >> > And listed them on
>> >> > http://taverna.staging.apache.org/download/
>> >> >
>> >> > (Please, don't push the CMS publish button now!)
>> >> >
>> >> >
>> >> > Please review and edit!
>> >> >
>> >> >
>> >> > While the first two are new, and basically clones of the
>> >> > /download/osgi/ page, the third page include links to Taverna
>> Command
>> >> > Line 2.5, as I think 'normal' users should still generally download
>> >> > 2.5 before we know how well 3.1.0 works on 'real' workflows.
>> >> >
>> >> >
>> >> > For 2.5, should we keep the links to the legacy site's
>> >> > http://www.taverna.org.uk/download/command-line-tool/2-5/
>> >> >
>> >> > (Alan - what happened about those legacy banners?)
>> >>
>> >> I wondered that as well! They are still on prototype.taverna.org.uk
>> >> though so I will do another copy tomorrow.
>> >>
>> >> > or just send them to the big list on
>> >> > https://bitbucket.org/taverna/taverna-commandline-product/downloads/
>> >> > ?
>> >>
>> >> I think it's OK to go to the legacy pages.
>> >>
>> >> Alan
>> >>
>> >>
>>
>>
>>
>> --
>> Stian Soiland-Reyes
>> Apache Taverna (incubating), Apache Commons RDF (incubating)
>> http://orcid.org/0000-0001-9842-9718
>>
>
Re: Draft download pages
Posted by Gale Naylor <Ga...@noventussolutions.com>.
Right! I forgot about that. Thanks for the reminder!
On Mon, May 9, 2016 at 2:38 PM Stian Soiland-Reyes <st...@apache.org> wrote:
> You need to click the "[Update this directory]" button from /trunk/content/
>
> The CMS is a bit confusing.. it has a personal SVN checkout for you -
> and so if you come back 3 weeks later it will stay at the version it
> had at your last edit!
>
> On 9 May 2016 at 19:02, Gale Naylor <Ga...@noventussolutions.com> wrote:
> > I am having trouble editing the staged versions of the engine,
> > common-activities, and commandline download pages. I can't find them in
> the
> > download directory:
> >
> https://cms.apache.org/taverna/wc/browse/gnaylor-C4CSQm/trunk/content/download/
> >
> > Is there something I'm missing, or something special I need to do?
> Thanks.
> >
> > On Mon, May 9, 2016 at 10:22 AM Alan Williams <al...@googlemail.com>
> > wrote:
> >
> >> On 09-May-16 17:48, Stian Soiland-Reyes wrote:
> >> > Hi,
> >> >
> >> > I have drafted download pages for the upcoming release:
> >> >
> >> > http://taverna.staging.apache.org/download/engine/
> >> > http://taverna.staging.apache.org/download/common-activities/
> >> > http://taverna.staging.apache.org/download/commandline/
> >> >
> >> >
> >> > And listed them on
> >> > http://taverna.staging.apache.org/download/
> >> >
> >> > (Please, don't push the CMS publish button now!)
> >> >
> >> >
> >> > Please review and edit!
> >> >
> >> >
> >> > While the first two are new, and basically clones of the
> >> > /download/osgi/ page, the third page include links to Taverna Command
> >> > Line 2.5, as I think 'normal' users should still generally download
> >> > 2.5 before we know how well 3.1.0 works on 'real' workflows.
> >> >
> >> >
> >> > For 2.5, should we keep the links to the legacy site's
> >> > http://www.taverna.org.uk/download/command-line-tool/2-5/
> >> >
> >> > (Alan - what happened about those legacy banners?)
> >>
> >> I wondered that as well! They are still on prototype.taverna.org.uk
> >> though so I will do another copy tomorrow.
> >>
> >> > or just send them to the big list on
> >> > https://bitbucket.org/taverna/taverna-commandline-product/downloads/
> >> > ?
> >>
> >> I think it's OK to go to the legacy pages.
> >>
> >> Alan
> >>
> >>
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>
Re: Draft download pages
Posted by Stian Soiland-Reyes <st...@apache.org>.
You need to click the "[Update this directory]" button from /trunk/content/
The CMS is a bit confusing.. it has a personal SVN checkout for you -
and so if you come back 3 weeks later it will stay at the version it
had at your last edit!
On 9 May 2016 at 19:02, Gale Naylor <Ga...@noventussolutions.com> wrote:
> I am having trouble editing the staged versions of the engine,
> common-activities, and commandline download pages. I can't find them in the
> download directory:
> https://cms.apache.org/taverna/wc/browse/gnaylor-C4CSQm/trunk/content/download/
>
> Is there something I'm missing, or something special I need to do? Thanks.
>
> On Mon, May 9, 2016 at 10:22 AM Alan Williams <al...@googlemail.com>
> wrote:
>
>> On 09-May-16 17:48, Stian Soiland-Reyes wrote:
>> > Hi,
>> >
>> > I have drafted download pages for the upcoming release:
>> >
>> > http://taverna.staging.apache.org/download/engine/
>> > http://taverna.staging.apache.org/download/common-activities/
>> > http://taverna.staging.apache.org/download/commandline/
>> >
>> >
>> > And listed them on
>> > http://taverna.staging.apache.org/download/
>> >
>> > (Please, don't push the CMS publish button now!)
>> >
>> >
>> > Please review and edit!
>> >
>> >
>> > While the first two are new, and basically clones of the
>> > /download/osgi/ page, the third page include links to Taverna Command
>> > Line 2.5, as I think 'normal' users should still generally download
>> > 2.5 before we know how well 3.1.0 works on 'real' workflows.
>> >
>> >
>> > For 2.5, should we keep the links to the legacy site's
>> > http://www.taverna.org.uk/download/command-line-tool/2-5/
>> >
>> > (Alan - what happened about those legacy banners?)
>>
>> I wondered that as well! They are still on prototype.taverna.org.uk
>> though so I will do another copy tomorrow.
>>
>> > or just send them to the big list on
>> > https://bitbucket.org/taverna/taverna-commandline-product/downloads/
>> > ?
>>
>> I think it's OK to go to the legacy pages.
>>
>> Alan
>>
>>
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
Re: Draft download pages
Posted by Gale Naylor <Ga...@noventussolutions.com>.
I am having trouble editing the staged versions of the engine,
common-activities, and commandline download pages. I can't find them in the
download directory:
https://cms.apache.org/taverna/wc/browse/gnaylor-C4CSQm/trunk/content/download/
Is there something I'm missing, or something special I need to do? Thanks.
On Mon, May 9, 2016 at 10:22 AM Alan Williams <al...@googlemail.com>
wrote:
> On 09-May-16 17:48, Stian Soiland-Reyes wrote:
> > Hi,
> >
> > I have drafted download pages for the upcoming release:
> >
> > http://taverna.staging.apache.org/download/engine/
> > http://taverna.staging.apache.org/download/common-activities/
> > http://taverna.staging.apache.org/download/commandline/
> >
> >
> > And listed them on
> > http://taverna.staging.apache.org/download/
> >
> > (Please, don't push the CMS publish button now!)
> >
> >
> > Please review and edit!
> >
> >
> > While the first two are new, and basically clones of the
> > /download/osgi/ page, the third page include links to Taverna Command
> > Line 2.5, as I think 'normal' users should still generally download
> > 2.5 before we know how well 3.1.0 works on 'real' workflows.
> >
> >
> > For 2.5, should we keep the links to the legacy site's
> > http://www.taverna.org.uk/download/command-line-tool/2-5/
> >
> > (Alan - what happened about those legacy banners?)
>
> I wondered that as well! They are still on prototype.taverna.org.uk
> though so I will do another copy tomorrow.
>
> > or just send them to the big list on
> > https://bitbucket.org/taverna/taverna-commandline-product/downloads/
> > ?
>
> I think it's OK to go to the legacy pages.
>
> Alan
>
>
Re: Draft download pages
Posted by Alan Williams <al...@googlemail.com>.
On 09-May-16 17:48, Stian Soiland-Reyes wrote:
> Hi,
>
> I have drafted download pages for the upcoming release:
>
> http://taverna.staging.apache.org/download/engine/
> http://taverna.staging.apache.org/download/common-activities/
> http://taverna.staging.apache.org/download/commandline/
>
>
> And listed them on
> http://taverna.staging.apache.org/download/
>
> (Please, don't push the CMS publish button now!)
>
>
> Please review and edit!
>
>
> While the first two are new, and basically clones of the
> /download/osgi/ page, the third page include links to Taverna Command
> Line 2.5, as I think 'normal' users should still generally download
> 2.5 before we know how well 3.1.0 works on 'real' workflows.
>
>
> For 2.5, should we keep the links to the legacy site's
> http://www.taverna.org.uk/download/command-line-tool/2-5/
>
> (Alan - what happened about those legacy banners?)
I wondered that as well! They are still on prototype.taverna.org.uk
though so I will do another copy tomorrow.
> or just send them to the big list on
> https://bitbucket.org/taverna/taverna-commandline-product/downloads/
> ?
I think it's OK to go to the legacy pages.
Alan