You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Christian Brenninkmeijer <br...@cs.man.ac.uk> on 2015/01/12 16:42:19 UTC
Website Migration
Hi All,
I have taken on the job of migration the old Taverna Website:
http://www.taverna.org.uk/ to http://taverna.incubator.apache.org/
To record progress and choices I make I have added
http://taverna.incubator.apache.org/websiteMigration/
(This directory is not linked of the main page and should be removed
once the migration is finished.)
First step was to create a sitemap of the old site:
http://taverna.incubator.apache.org/websiteMigration/sitemap.txt
Next step is to go through the sitemap and record which pages should be
1. Migrated
a. Changing links
b. Changing some Mygrid references to Apache incubator
2. Migrated as above but with serious editting after migration
3. Replaced with completly new pages.
4. Left as links to the old site only
5. Deleted.
Farther updates to this project will be recorded at:
http://taverna.incubator.apache.org/websiteMigration/
With only major milestones reported to this mailing list.
Feel free to contact me with any comments or suggested or add them
directly to http://taverna.incubator.apache.org/websiteMigration/
Christian
Re: Website Migration
Posted by alaninmcr <al...@googlemail.com>.
On 22/01/2015 11:31, Christian Brenninkmeijer wrote:
> Stain and Andy raise a critical question.
>
> Do we keep it as 2 competely seperate sites one for Taverna 2 and
> previous and one for Taverna Apachee?
> Or have one site with both but with different styles for the Non Taverna
> stuff?
>
> In the case of the two seperate sites only stuff that correctly applies
> to the Apache version should go on the new site.
> So for now only server and command line and only those plugins we know
> will be included in the first Apache release.
> With just a few link back always via the old site to make it clear.
I would go for the two separate sites.
> I would high discourage anything in between these two options as that
> would lead to duplication.
Indeed
> Christian
Alan
Re: Website Migration
Posted by Stian Soiland-Reyes <st...@apache.org>.
+1 to two separate sites as you say - limit what Apache Taverna site
covers until it is true for Apache Taverna.
On 22 January 2015 at 11:31, Christian Brenninkmeijer
<br...@cs.man.ac.uk> wrote:
> Stain and Andy raise a critical question.
>
> Do we keep it as 2 competely seperate sites one for Taverna 2 and previous
> and one for Taverna Apachee?
> Or have one site with both but with different styles for the Non Taverna
> stuff?
>
> In the case of the two seperate sites only stuff that correctly applies to
> the Apache version should go on the new site.
> So for now only server and command line and only those plugins we know will
> be included in the first Apache release.
> With just a few link back always via the old site to make it clear.
>
> I would high discourage anything in between these two options as that would
> lead to duplication.
>
> Christian
>
>
> On 21/01/2015 22:48, Stian Soiland-Reyes wrote:
>>
>> Can't we keep the old site at say archive.taverna.org.uk ?
>>
>> I think to start with for taverna.org.uk we would just redirect front
>> page,
>> contact, download (?) to the apache site. The old Taverna 2 pages, e.g.
>> its
>> plugin listing or description of projects that use(d) non-Apache Taverna
>> we
>> should be reluctant to move.
>>
>> The most portable T2 pages are the documentation, which is in the wiki.
>> Many things might need updates, but the principle structure of using
>> Taverna 3 is not different from 2.
>>
>> The current site has a big overlap with the wiki on the intro-level
>> documentation, but often failing to link into the deeper documentation in
>> the wiki.
>>
>> about the pre-apache download page, I agree with Andy to be careful. We
>> don't want to be promoting those, but keep them mainly for transitional
>> purposes for real and existing users who want to stay on 2.x.
>>
>> Say I a years time, and Apache Taverna 3 workbench (or at least server and
>> cmd line) are production releases, then you should need to go to the
>> pre-apache page and then be explained in the warnings. Taverna.org.UK
>> would
>> take you to Apache Taverna, where download somewhere would mention the
>> pre-apache downloads.
>>
>> We can from there link to archive.taverna.org.uk/download/2.5 or even
>> straight to the flat bitbucket folder listing. That the 2.5 downloads *by
>> then* look less official or polished than Apache Taverna 3 would be a good
>> thing.
>> On 21 Jan 2015 13:44, "Christian Brenninkmeijer" <br...@cs.man.ac.uk>
>> wrote:
>>
>>> Hi All,
>>>
>>> I have add a look at the old site http://taverna.incubator.
>>> apache.org/download/pre-apache.html and found over 400 pages.
>>>
>>> Before I migrate the website we have to make a few choices.
>>>
>>> 1. Move Taverna 2 material?
>>> Much of the current material is heavily Taverna 2 base. This incudes
>>> descriptions of things like the workbench and some plugins that are
>>> likely
>>> not to be part of the first Apachee release.
>>> My proposal is that we migrate this material anyway, possibly with a
>>> warning that is is Taverna 2/ Not Apache
>>> I also suggest merging many of the smaller pages into single larger pages
>>> Otherwise we have to come up with a different strategy of where to store
>>> this material especially if we plan on pointing
>>> http://www.taverna.org.uk/
>>> to the offical Apache website
>>> Not moving some material also means that 2 websites have to be fixed and
>>> kept up to date.
>>>
>>> 2. Taverna 1/2 download links.
>>> The proposal is to keep http://taverna.incubator.apache.org/download/pre-
>>> apache.html and make sure it contains all the download links found under:
>>> http://www.taverna.org.uk/
>>>
>>> 3. News
>>> http://www.taverna.org.uk/ is wordpress based and so automatically picks
>>> up news posts and creates a new page for each.
>>> http://taverna.incubator.apache.org is not wordpress based so needs a
>>> different strategy,
>>> Having looked at several Apache projects there is no clear pattern for
>>> news items. (if there is any at all)
>>> Some just use a blog such as OpenOffice <https://blogs.apache.org/OOo/>
>>> Some use a single manually editted page such as Lucene <
>>> http://lucene.apache.org/mainnews>
>>> The proposal is to create a single archive news page including all the
>>> news posts at: http://www.taverna.org.uk/
>>> I would suggest keeping this seperate from Apache incubator news. The
>>> choice how to do Apache news can be made later but again I suggest a
>>> singke
>>> page.
>>>
>>> 4. Wiki.
>>> I propose keeping all links to http://dev.mygrid.org.uk/wiki until we
>>> consider what to do about the wiki.
>>>
>>> 5. Wide page vs fixed width,
>>> Bootstrap offer the choice between a wide page or keeping a fixed width.
>>> I would propose using the wide page as many developers have wide screens
>>> and this allow us to get as much information as possible on a single
>>> screen.
>>> While at the same time of course making sure it still look good medium
>>> and
>>> small screens but not worring about mobiles.
>>>
>>> 6. top bar
>>> As already started I suggest we keep a single navbar for all pages on th
>>> apache website.
>>>
>>> 7. Side bar
>>> For large pages longer than two screens even on a very wide screen.
>>> Have a page specific menubar on the right. Possibly hiding it on small
>>> screens.
>>> This would only be used to point to subjection on that page.
>>>
>>> Please see http://taverna.incubator.apache.org/websiteMigration/ for a
>>> summary of these questions which I will update if any suggests are made
>>> based on this email.
>>> There is also
>>> http://taverna.incubator.apache.org/websiteMigration/sitemap
>>> which list the pages I am currently planning on merging.
>>>
>>> Christian
>>>
>>> On 12/01/2015 15:42, Christian Brenninkmeijer wrote:
>>>
>>>> Hi All,
>>>>
>>>> I have taken on the job of migration the old Taverna Website:
>>>> http://www.taverna.org.uk/ to http://taverna.incubator.apache.org/
>>>>
>>>> To record progress and choices I make I have added
>>>> http://taverna.incubator.apache.org/websiteMigration/
>>>> (This directory is not linked of the main page and should be removed
>>>> once
>>>> the migration is finished.)
>>>>
>>>> First step was to create a sitemap of the old site:
>>>> http://taverna.incubator.apache.org/websiteMigration/sitemap.txt
>>>>
>>>> Next step is to go through the sitemap and record which pages should be
>>>>
>>>> 1. Migrated
>>>> a. Changing links
>>>> b. Changing some Mygrid references to Apache incubator
>>>>
>>>> 2. Migrated as above but with serious editting after migration
>>>>
>>>> 3. Replaced with completly new pages.
>>>>
>>>> 4. Left as links to the old site only
>>>>
>>>> 5. Deleted.
>>>>
>>>> Farther updates to this project will be recorded at:
>>>> http://taverna.incubator.apache.org/websiteMigration/
>>>>
>>>> With only major milestones reported to this mailing list.
>>>>
>>>> Feel free to contact me with any comments or suggested or add them
>>>> directly to http://taverna.incubator.apache.org/websiteMigration/
>>>>
>>>> Christian
>>>>
>>>
>
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/0000-0001-9842-9718
Re: Website Migration
Posted by Marlon Pierce <ma...@iu.edu>.
+1 for linking to slideshare or something similar. Also remember you
have access to a Confluence wiki. I suggest reserving the website for
"evergreen" content and use the wiki for things that will be more dynamic.
Marlon
On 1/28/15 9:13 AM, Stian Soiland-Reyes wrote:
> On 28 January 2015 at 11:54, Christian Brenninkmeijer
> <br...@cs.man.ac.uk> wrote:
>
>> 3. Place any presentation ect into a /presentation folder
>> Similar if other direct links are found
> No - there could be many license problems and would not be covered by
> Apache license (which also applies to our website - see the footer).
>
> Most of those slides would have copy-and-pasted stuff from all over.
> Some of them are made by non-Manchester staff and would not be covered
> by the IP grant. Some of them are however Creative Commons - which
> you can use with the right notice - but it sounds painful to try to
> maintain that here.
>
> Maintaining such a slides archive also sounds daunting - and slides
> are generally not a software project thing, but a research project
> thing. (except your tutorials, which I think we SHOULD host)
>
> We already have http://www.slideshare.net/myGrid -- perhaps just make
> http://www.slideshare.net/ApacheTaverna and use it in a similar way,
> starring other people's slides on slideshare, and only self-uploading
> Apache Taverna-produced slides like tutorials?
>
>
>> 4. Create a community page
>> Make sure this includes the inforamtion from http://www.taverna.org.uk/about/
> No - almost all of this will now be misleading as it says things like
> we are lead by Prof Goble - she's not a committer on Apache Taverna,
> and Apache projects are not "lead".
>
> See instead the comments from Marlon which I think describes nicely
> what the community pages should cover:
>
> http://mail-archives.apache.org/mod_mbox/taverna-dev/201501.mbox/%3C54C7BFD0.9030208%40iu.edu%3E
>
> Mailing lists are already on
> http://taverna.incubator.apache.org/contact/ but needs details like
> "How to ask a good question" - see
> http://jena.apache.org/help_and_support/index.html
>
>
> What the community pages need is to bring together those things like
> who the developers are, how you can contribute, how to contact us, how
> to report a bug, how to find the source code.
>
>
> The "Referencing Taverna" citation should probably go somewhere under
> 'about', though.
>
> A brief history that covers us through the incubation will also be nice.
>
>
> I tried to cover this last night when updating:
>
> http://en.wikipedia.org/wiki/Apache_Taverna#Open_source_community
>
> (comments?)
>
>
>> 5. Create a community/collaborations page
>> Ask people to add themselves/ their project here
>> Link to http://www.taverna.org.uk/collaborate/collaborations/
> I don't think we can have that kind of collaboration listing - those
> institutions are not working with Apache
> Taverna - if anything it would be individual people from there who do.
>
> If some of them in any way contribute to Apache Taverna, then
> (specially now in the incubatyor), we should vote them in as
> committers. Remember that "contribute" doesn't have to be "write
> code" - helping out with documentation, user questions, and even
> promoting Taverna elsewhere (as Steffen Moller does in DebianMed) also
> count.
>
>
> We are not a research project of institutions anymore, we're an open
> development software project of individual developers.
>
>
> We should however have a neutral "Taverna in use" page somewhere - but
> that would have to be kind of self-reported thing (wiki page?) and
> should only describe other projects/software using Apache Taverna 3.x,
> not Taverna 2.x or 1.x.
>
> As of today, such a list is presumably empty if we exclude committers
> (but why should we?) - we know Matías Fernández is using SCUFL2 [1] so
> once taverna-language is out and they use that (which is the first
> module we are preparing), then we can ask if they want to be listed.
> :)
>
> [1] http://mail-archives.apache.org/mod_mbox/taverna-dev/201412.mbox/%3C54A2DF32.80604%40gmail.com%3E
>
>
>> 6. Add Developers page
>> Mainly as link to http://www.taverna.org.uk/developers/
> No - we already have this at
>
> http://taverna.incubator.apache.org/about/
>
> (which could be fleshed out with details on how to join etc)
>
> and these kind of community things should NOT link to taverna.org.uk
> as they are essential to the Apache project.
>
>
>
>> 7. Check dowload page covers (maybe indirectly) all links under
>> http://www.taverna.org.uk/download/
> We agreed we must keep those indirectly - but the indirection could be
> to the bitbucket folder.
>
>
>> 8. Create news page
>> With link to http://www.taverna.org.uk/news/
>> Copy over only relevant Apache news
> I thought you said to not have a news page? :) More maintenance..
>
> Perhaps just a Twitter link? We should register @ApacheTaverna (this
> was encouraged at the ApacheCon Marketing talk) and put a
> iframe/javascript thing like on:
>
> http://mesos.apache.org/community/
>
> Using Twitter retweets (which could be from a committer's personal
> accounts) also makes it more neutral and not look like Apache
> promoting a third-party, say if someone wrote a paper about using
> Taverna.
>
>
> Sadly we would have to simply share that Twitter account password as
> Twitter hasn't got a delegation concept - but we can register with
> private@taverna.. and email it there.
>
Re: Website Migration
Posted by Stian Soiland-Reyes <st...@apache.org>.
On 28 January 2015 at 11:54, Christian Brenninkmeijer
<br...@cs.man.ac.uk> wrote:
> 3. Place any presentation ect into a /presentation folder
> Similar if other direct links are found
No - there could be many license problems and would not be covered by
Apache license (which also applies to our website - see the footer).
Most of those slides would have copy-and-pasted stuff from all over.
Some of them are made by non-Manchester staff and would not be covered
by the IP grant. Some of them are however Creative Commons - which
you can use with the right notice - but it sounds painful to try to
maintain that here.
Maintaining such a slides archive also sounds daunting - and slides
are generally not a software project thing, but a research project
thing. (except your tutorials, which I think we SHOULD host)
We already have http://www.slideshare.net/myGrid -- perhaps just make
http://www.slideshare.net/ApacheTaverna and use it in a similar way,
starring other people's slides on slideshare, and only self-uploading
Apache Taverna-produced slides like tutorials?
> 4. Create a community page
> Make sure this includes the inforamtion from http://www.taverna.org.uk/about/
No - almost all of this will now be misleading as it says things like
we are lead by Prof Goble - she's not a committer on Apache Taverna,
and Apache projects are not "lead".
See instead the comments from Marlon which I think describes nicely
what the community pages should cover:
http://mail-archives.apache.org/mod_mbox/taverna-dev/201501.mbox/%3C54C7BFD0.9030208%40iu.edu%3E
Mailing lists are already on
http://taverna.incubator.apache.org/contact/ but needs details like
"How to ask a good question" - see
http://jena.apache.org/help_and_support/index.html
What the community pages need is to bring together those things like
who the developers are, how you can contribute, how to contact us, how
to report a bug, how to find the source code.
The "Referencing Taverna" citation should probably go somewhere under
'about', though.
A brief history that covers us through the incubation will also be nice.
I tried to cover this last night when updating:
http://en.wikipedia.org/wiki/Apache_Taverna#Open_source_community
(comments?)
> 5. Create a community/collaborations page
> Ask people to add themselves/ their project here
> Link to http://www.taverna.org.uk/collaborate/collaborations/
I don't think we can have that kind of collaboration listing - those
institutions are not working with Apache
Taverna - if anything it would be individual people from there who do.
If some of them in any way contribute to Apache Taverna, then
(specially now in the incubatyor), we should vote them in as
committers. Remember that "contribute" doesn't have to be "write
code" - helping out with documentation, user questions, and even
promoting Taverna elsewhere (as Steffen Moller does in DebianMed) also
count.
We are not a research project of institutions anymore, we're an open
development software project of individual developers.
We should however have a neutral "Taverna in use" page somewhere - but
that would have to be kind of self-reported thing (wiki page?) and
should only describe other projects/software using Apache Taverna 3.x,
not Taverna 2.x or 1.x.
As of today, such a list is presumably empty if we exclude committers
(but why should we?) - we know Matías Fernández is using SCUFL2 [1] so
once taverna-language is out and they use that (which is the first
module we are preparing), then we can ask if they want to be listed.
:)
[1] http://mail-archives.apache.org/mod_mbox/taverna-dev/201412.mbox/%3C54A2DF32.80604%40gmail.com%3E
> 6. Add Developers page
> Mainly as link to http://www.taverna.org.uk/developers/
No - we already have this at
http://taverna.incubator.apache.org/about/
(which could be fleshed out with details on how to join etc)
and these kind of community things should NOT link to taverna.org.uk
as they are essential to the Apache project.
> 7. Check dowload page covers (maybe indirectly) all links under
> http://www.taverna.org.uk/download/
We agreed we must keep those indirectly - but the indirection could be
to the bitbucket folder.
> 8. Create news page
> With link to http://www.taverna.org.uk/news/
> Copy over only relevant Apache news
I thought you said to not have a news page? :) More maintenance..
Perhaps just a Twitter link? We should register @ApacheTaverna (this
was encouraged at the ApacheCon Marketing talk) and put a
iframe/javascript thing like on:
http://mesos.apache.org/community/
Using Twitter retweets (which could be from a committer's personal
accounts) also makes it more neutral and not look like Apache
promoting a third-party, say if someone wrote a paper about using
Taverna.
Sadly we would have to simply share that Twitter account password as
Twitter hasn't got a delegation concept - but we can register with
private@taverna.. and email it there.
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/0000-0001-9842-9718
Re: Website Migration
Posted by Christian Brenninkmeijer <br...@cs.man.ac.uk>.
Hi All,
It is now clear that the community wants to keep two seperate sites.
1. taverna.incubator.apache.org for any that is or could become Apache
2. What is currently http://www.taverna.org.uk/ for Taverna up to
including all Taverna 2 releases
So my current plan is to
1. Copy the sections
Introduction, Documentation as they are.
2. Place all images in the /img folder
3. Place any presentation ect into a /presentation folder
Similar if other direct links are found
4. Create a community page
Make sure this includes the inforamtion from
http://www.taverna.org.uk/about/
5. Create a community/collaborations page
Ask people to add themselves/ their project here
Link to http://www.taverna.org.uk/collaborate/collaborations/
6. Add Developers page
Mainly as link to http://www.taverna.org.uk/developers/
7. Check dowload page covers (maybe indirectly) all links under
http://www.taverna.org.uk/download/
8. Create news page
With link to http://www.taverna.org.uk/news/
Copy over only relevant Apache news
9. Create cite page
adding taverna.incubator.apache.org
Christian
On 22/01/2015 11:31, Christian Brenninkmeijer wrote:
> Stain and Andy raise a critical question.
>
> Do we keep it as 2 competely seperate sites one for Taverna 2 and
> previous and one for Taverna Apachee?
> Or have one site with both but with different styles for the Non
> Taverna stuff?
>
> In the case of the two seperate sites only stuff that correctly
> applies to the Apache version should go on the new site.
> So for now only server and command line and only those plugins we know
> will be included in the first Apache release.
> With just a few link back always via the old site to make it clear.
>
> I would high discourage anything in between these two options as that
> would lead to duplication.
>
> Christian
>
> On 21/01/2015 22:48, Stian Soiland-Reyes wrote:
>> Can't we keep the old site at say archive.taverna.org.uk ?
>>
>> I think to start with for taverna.org.uk we would just redirect front
>> page,
>> contact, download (?) to the apache site. The old Taverna 2 pages,
>> e.g. its
>> plugin listing or description of projects that use(d) non-Apache
>> Taverna we
>> should be reluctant to move.
>>
>> The most portable T2 pages are the documentation, which is in the wiki.
>> Many things might need updates, but the principle structure of using
>> Taverna 3 is not different from 2.
>>
>> The current site has a big overlap with the wiki on the intro-level
>> documentation, but often failing to link into the deeper
>> documentation in
>> the wiki.
>>
>> about the pre-apache download page, I agree with Andy to be careful. We
>> don't want to be promoting those, but keep them mainly for transitional
>> purposes for real and existing users who want to stay on 2.x.
>>
>> Say I a years time, and Apache Taverna 3 workbench (or at least
>> server and
>> cmd line) are production releases, then you should need to go to the
>> pre-apache page and then be explained in the warnings. Taverna.org.UK
>> would
>> take you to Apache Taverna, where download somewhere would mention the
>> pre-apache downloads.
>>
>> We can from there link to archive.taverna.org.uk/download/2.5 or even
>> straight to the flat bitbucket folder listing. That the 2.5 downloads
>> *by
>> then* look less official or polished than Apache Taverna 3 would be a
>> good
>> thing.
>> On 21 Jan 2015 13:44, "Christian Brenninkmeijer" <br...@cs.man.ac.uk>
>> wrote:
>>
>>> Hi All,
>>>
>>> I have add a look at the old site http://taverna.incubator.
>>> apache.org/download/pre-apache.html and found over 400 pages.
>>>
>>> Before I migrate the website we have to make a few choices.
>>>
>>> 1. Move Taverna 2 material?
>>> Much of the current material is heavily Taverna 2 base. This incudes
>>> descriptions of things like the workbench and some plugins that are
>>> likely
>>> not to be part of the first Apachee release.
>>> My proposal is that we migrate this material anyway, possibly with a
>>> warning that is is Taverna 2/ Not Apache
>>> I also suggest merging many of the smaller pages into single larger
>>> pages
>>> Otherwise we have to come up with a different strategy of where to
>>> store
>>> this material especially if we plan on pointing
>>> http://www.taverna.org.uk/
>>> to the offical Apache website
>>> Not moving some material also means that 2 websites have to be fixed
>>> and
>>> kept up to date.
>>>
>>> 2. Taverna 1/2 download links.
>>> The proposal is to keep
>>> http://taverna.incubator.apache.org/download/pre-
>>> apache.html and make sure it contains all the download links found
>>> under:
>>> http://www.taverna.org.uk/
>>>
>>> 3. News
>>> http://www.taverna.org.uk/ is wordpress based and so automatically
>>> picks
>>> up news posts and creates a new page for each.
>>> http://taverna.incubator.apache.org is not wordpress based so needs a
>>> different strategy,
>>> Having looked at several Apache projects there is no clear pattern for
>>> news items. (if there is any at all)
>>> Some just use a blog such as OpenOffice <https://blogs.apache.org/OOo/>
>>> Some use a single manually editted page such as Lucene <
>>> http://lucene.apache.org/mainnews>
>>> The proposal is to create a single archive news page including all the
>>> news posts at: http://www.taverna.org.uk/
>>> I would suggest keeping this seperate from Apache incubator news. The
>>> choice how to do Apache news can be made later but again I suggest a
>>> singke
>>> page.
>>>
>>> 4. Wiki.
>>> I propose keeping all links to http://dev.mygrid.org.uk/wiki until we
>>> consider what to do about the wiki.
>>>
>>> 5. Wide page vs fixed width,
>>> Bootstrap offer the choice between a wide page or keeping a fixed
>>> width.
>>> I would propose using the wide page as many developers have wide
>>> screens
>>> and this allow us to get as much information as possible on a single
>>> screen.
>>> While at the same time of course making sure it still look good
>>> medium and
>>> small screens but not worring about mobiles.
>>>
>>> 6. top bar
>>> As already started I suggest we keep a single navbar for all pages
>>> on th
>>> apache website.
>>>
>>> 7. Side bar
>>> For large pages longer than two screens even on a very wide screen.
>>> Have a page specific menubar on the right. Possibly hiding it on small
>>> screens.
>>> This would only be used to point to subjection on that page.
>>>
>>> Please see http://taverna.incubator.apache.org/websiteMigration/ for a
>>> summary of these questions which I will update if any suggests are made
>>> based on this email.
>>> There is also
>>> http://taverna.incubator.apache.org/websiteMigration/sitemap
>>> which list the pages I am currently planning on merging.
>>>
>>> Christian
>>>
>>> On 12/01/2015 15:42, Christian Brenninkmeijer wrote:
>>>
>>>> Hi All,
>>>>
>>>> I have taken on the job of migration the old Taverna Website:
>>>> http://www.taverna.org.uk/ to http://taverna.incubator.apache.org/
>>>>
>>>> To record progress and choices I make I have added
>>>> http://taverna.incubator.apache.org/websiteMigration/
>>>> (This directory is not linked of the main page and should be
>>>> removed once
>>>> the migration is finished.)
>>>>
>>>> First step was to create a sitemap of the old site:
>>>> http://taverna.incubator.apache.org/websiteMigration/sitemap.txt
>>>>
>>>> Next step is to go through the sitemap and record which pages
>>>> should be
>>>>
>>>> 1. Migrated
>>>> a. Changing links
>>>> b. Changing some Mygrid references to Apache incubator
>>>>
>>>> 2. Migrated as above but with serious editting after migration
>>>>
>>>> 3. Replaced with completly new pages.
>>>>
>>>> 4. Left as links to the old site only
>>>>
>>>> 5. Deleted.
>>>>
>>>> Farther updates to this project will be recorded at:
>>>> http://taverna.incubator.apache.org/websiteMigration/
>>>>
>>>> With only major milestones reported to this mailing list.
>>>>
>>>> Feel free to contact me with any comments or suggested or add them
>>>> directly to http://taverna.incubator.apache.org/websiteMigration/
>>>>
>>>> Christian
>>>>
>>>
>
Re: Website Migration
Posted by Christian Brenninkmeijer <br...@cs.man.ac.uk>.
Stain and Andy raise a critical question.
Do we keep it as 2 competely seperate sites one for Taverna 2 and
previous and one for Taverna Apachee?
Or have one site with both but with different styles for the Non Taverna
stuff?
In the case of the two seperate sites only stuff that correctly applies
to the Apache version should go on the new site.
So for now only server and command line and only those plugins we know
will be included in the first Apache release.
With just a few link back always via the old site to make it clear.
I would high discourage anything in between these two options as that
would lead to duplication.
Christian
On 21/01/2015 22:48, Stian Soiland-Reyes wrote:
> Can't we keep the old site at say archive.taverna.org.uk ?
>
> I think to start with for taverna.org.uk we would just redirect front page,
> contact, download (?) to the apache site. The old Taverna 2 pages, e.g. its
> plugin listing or description of projects that use(d) non-Apache Taverna we
> should be reluctant to move.
>
> The most portable T2 pages are the documentation, which is in the wiki.
> Many things might need updates, but the principle structure of using
> Taverna 3 is not different from 2.
>
> The current site has a big overlap with the wiki on the intro-level
> documentation, but often failing to link into the deeper documentation in
> the wiki.
>
> about the pre-apache download page, I agree with Andy to be careful. We
> don't want to be promoting those, but keep them mainly for transitional
> purposes for real and existing users who want to stay on 2.x.
>
> Say I a years time, and Apache Taverna 3 workbench (or at least server and
> cmd line) are production releases, then you should need to go to the
> pre-apache page and then be explained in the warnings. Taverna.org.UK would
> take you to Apache Taverna, where download somewhere would mention the
> pre-apache downloads.
>
> We can from there link to archive.taverna.org.uk/download/2.5 or even
> straight to the flat bitbucket folder listing. That the 2.5 downloads *by
> then* look less official or polished than Apache Taverna 3 would be a good
> thing.
> On 21 Jan 2015 13:44, "Christian Brenninkmeijer" <br...@cs.man.ac.uk>
> wrote:
>
>> Hi All,
>>
>> I have add a look at the old site http://taverna.incubator.
>> apache.org/download/pre-apache.html and found over 400 pages.
>>
>> Before I migrate the website we have to make a few choices.
>>
>> 1. Move Taverna 2 material?
>> Much of the current material is heavily Taverna 2 base. This incudes
>> descriptions of things like the workbench and some plugins that are likely
>> not to be part of the first Apachee release.
>> My proposal is that we migrate this material anyway, possibly with a
>> warning that is is Taverna 2/ Not Apache
>> I also suggest merging many of the smaller pages into single larger pages
>> Otherwise we have to come up with a different strategy of where to store
>> this material especially if we plan on pointing http://www.taverna.org.uk/
>> to the offical Apache website
>> Not moving some material also means that 2 websites have to be fixed and
>> kept up to date.
>>
>> 2. Taverna 1/2 download links.
>> The proposal is to keep http://taverna.incubator.apache.org/download/pre-
>> apache.html and make sure it contains all the download links found under:
>> http://www.taverna.org.uk/
>>
>> 3. News
>> http://www.taverna.org.uk/ is wordpress based and so automatically picks
>> up news posts and creates a new page for each.
>> http://taverna.incubator.apache.org is not wordpress based so needs a
>> different strategy,
>> Having looked at several Apache projects there is no clear pattern for
>> news items. (if there is any at all)
>> Some just use a blog such as OpenOffice <https://blogs.apache.org/OOo/>
>> Some use a single manually editted page such as Lucene <
>> http://lucene.apache.org/mainnews>
>> The proposal is to create a single archive news page including all the
>> news posts at: http://www.taverna.org.uk/
>> I would suggest keeping this seperate from Apache incubator news. The
>> choice how to do Apache news can be made later but again I suggest a singke
>> page.
>>
>> 4. Wiki.
>> I propose keeping all links to http://dev.mygrid.org.uk/wiki until we
>> consider what to do about the wiki.
>>
>> 5. Wide page vs fixed width,
>> Bootstrap offer the choice between a wide page or keeping a fixed width.
>> I would propose using the wide page as many developers have wide screens
>> and this allow us to get as much information as possible on a single screen.
>> While at the same time of course making sure it still look good medium and
>> small screens but not worring about mobiles.
>>
>> 6. top bar
>> As already started I suggest we keep a single navbar for all pages on th
>> apache website.
>>
>> 7. Side bar
>> For large pages longer than two screens even on a very wide screen.
>> Have a page specific menubar on the right. Possibly hiding it on small
>> screens.
>> This would only be used to point to subjection on that page.
>>
>> Please see http://taverna.incubator.apache.org/websiteMigration/ for a
>> summary of these questions which I will update if any suggests are made
>> based on this email.
>> There is also http://taverna.incubator.apache.org/websiteMigration/sitemap
>> which list the pages I am currently planning on merging.
>>
>> Christian
>>
>> On 12/01/2015 15:42, Christian Brenninkmeijer wrote:
>>
>>> Hi All,
>>>
>>> I have taken on the job of migration the old Taverna Website:
>>> http://www.taverna.org.uk/ to http://taverna.incubator.apache.org/
>>>
>>> To record progress and choices I make I have added
>>> http://taverna.incubator.apache.org/websiteMigration/
>>> (This directory is not linked of the main page and should be removed once
>>> the migration is finished.)
>>>
>>> First step was to create a sitemap of the old site:
>>> http://taverna.incubator.apache.org/websiteMigration/sitemap.txt
>>>
>>> Next step is to go through the sitemap and record which pages should be
>>>
>>> 1. Migrated
>>> a. Changing links
>>> b. Changing some Mygrid references to Apache incubator
>>>
>>> 2. Migrated as above but with serious editting after migration
>>>
>>> 3. Replaced with completly new pages.
>>>
>>> 4. Left as links to the old site only
>>>
>>> 5. Deleted.
>>>
>>> Farther updates to this project will be recorded at:
>>> http://taverna.incubator.apache.org/websiteMigration/
>>>
>>> With only major milestones reported to this mailing list.
>>>
>>> Feel free to contact me with any comments or suggested or add them
>>> directly to http://taverna.incubator.apache.org/websiteMigration/
>>>
>>> Christian
>>>
>>
Re: Website Migration
Posted by Stian Soiland-Reyes <st...@apache.org>.
Can't we keep the old site at say archive.taverna.org.uk ?
I think to start with for taverna.org.uk we would just redirect front page,
contact, download (?) to the apache site. The old Taverna 2 pages, e.g. its
plugin listing or description of projects that use(d) non-Apache Taverna we
should be reluctant to move.
The most portable T2 pages are the documentation, which is in the wiki.
Many things might need updates, but the principle structure of using
Taverna 3 is not different from 2.
The current site has a big overlap with the wiki on the intro-level
documentation, but often failing to link into the deeper documentation in
the wiki.
about the pre-apache download page, I agree with Andy to be careful. We
don't want to be promoting those, but keep them mainly for transitional
purposes for real and existing users who want to stay on 2.x.
Say I a years time, and Apache Taverna 3 workbench (or at least server and
cmd line) are production releases, then you should need to go to the
pre-apache page and then be explained in the warnings. Taverna.org.UK would
take you to Apache Taverna, where download somewhere would mention the
pre-apache downloads.
We can from there link to archive.taverna.org.uk/download/2.5 or even
straight to the flat bitbucket folder listing. That the 2.5 downloads *by
then* look less official or polished than Apache Taverna 3 would be a good
thing.
On 21 Jan 2015 13:44, "Christian Brenninkmeijer" <br...@cs.man.ac.uk>
wrote:
> Hi All,
>
> I have add a look at the old site http://taverna.incubator.
> apache.org/download/pre-apache.html and found over 400 pages.
>
> Before I migrate the website we have to make a few choices.
>
> 1. Move Taverna 2 material?
> Much of the current material is heavily Taverna 2 base. This incudes
> descriptions of things like the workbench and some plugins that are likely
> not to be part of the first Apachee release.
> My proposal is that we migrate this material anyway, possibly with a
> warning that is is Taverna 2/ Not Apache
> I also suggest merging many of the smaller pages into single larger pages
> Otherwise we have to come up with a different strategy of where to store
> this material especially if we plan on pointing http://www.taverna.org.uk/
> to the offical Apache website
> Not moving some material also means that 2 websites have to be fixed and
> kept up to date.
>
> 2. Taverna 1/2 download links.
> The proposal is to keep http://taverna.incubator.apache.org/download/pre-
> apache.html and make sure it contains all the download links found under:
> http://www.taverna.org.uk/
>
> 3. News
> http://www.taverna.org.uk/ is wordpress based and so automatically picks
> up news posts and creates a new page for each.
> http://taverna.incubator.apache.org is not wordpress based so needs a
> different strategy,
> Having looked at several Apache projects there is no clear pattern for
> news items. (if there is any at all)
> Some just use a blog such as OpenOffice <https://blogs.apache.org/OOo/>
> Some use a single manually editted page such as Lucene <
> http://lucene.apache.org/mainnews>
> The proposal is to create a single archive news page including all the
> news posts at: http://www.taverna.org.uk/
> I would suggest keeping this seperate from Apache incubator news. The
> choice how to do Apache news can be made later but again I suggest a singke
> page.
>
> 4. Wiki.
> I propose keeping all links to http://dev.mygrid.org.uk/wiki until we
> consider what to do about the wiki.
>
> 5. Wide page vs fixed width,
> Bootstrap offer the choice between a wide page or keeping a fixed width.
> I would propose using the wide page as many developers have wide screens
> and this allow us to get as much information as possible on a single screen.
> While at the same time of course making sure it still look good medium and
> small screens but not worring about mobiles.
>
> 6. top bar
> As already started I suggest we keep a single navbar for all pages on th
> apache website.
>
> 7. Side bar
> For large pages longer than two screens even on a very wide screen.
> Have a page specific menubar on the right. Possibly hiding it on small
> screens.
> This would only be used to point to subjection on that page.
>
> Please see http://taverna.incubator.apache.org/websiteMigration/ for a
> summary of these questions which I will update if any suggests are made
> based on this email.
> There is also http://taverna.incubator.apache.org/websiteMigration/sitemap
> which list the pages I am currently planning on merging.
>
> Christian
>
> On 12/01/2015 15:42, Christian Brenninkmeijer wrote:
>
>> Hi All,
>>
>> I have taken on the job of migration the old Taverna Website:
>> http://www.taverna.org.uk/ to http://taverna.incubator.apache.org/
>>
>> To record progress and choices I make I have added
>> http://taverna.incubator.apache.org/websiteMigration/
>> (This directory is not linked of the main page and should be removed once
>> the migration is finished.)
>>
>> First step was to create a sitemap of the old site:
>> http://taverna.incubator.apache.org/websiteMigration/sitemap.txt
>>
>> Next step is to go through the sitemap and record which pages should be
>>
>> 1. Migrated
>> a. Changing links
>> b. Changing some Mygrid references to Apache incubator
>>
>> 2. Migrated as above but with serious editting after migration
>>
>> 3. Replaced with completly new pages.
>>
>> 4. Left as links to the old site only
>>
>> 5. Deleted.
>>
>> Farther updates to this project will be recorded at:
>> http://taverna.incubator.apache.org/websiteMigration/
>>
>> With only major milestones reported to this mailing list.
>>
>> Feel free to contact me with any comments or suggested or add them
>> directly to http://taverna.incubator.apache.org/websiteMigration/
>>
>> Christian
>>
>
>
Re: Website Migration
Posted by Andy Seaborne <an...@apache.org>.
On 21/01/15 12:43, Christian Brenninkmeijer wrote:
> Hi All,
>
> I have add a look at the old site
> http://taverna.incubator.apache.org/download/pre-apache.html and found
> over 400 pages.
>
> Before I migrate the website we have to make a few choices.
>
> 1. Move Taverna 2 material?
> Much of the current material is heavily Taverna 2 base. This incudes
> descriptions of things like the workbench and some plugins that are
> likely not to be part of the first Apachee release.
> My proposal is that we migrate this material anyway, possibly with a
> warning that is is Taverna 2/ Not Apache
The warning would be a very good idea. Even to the point of distinct
page style. The current setup that the links go off ASF to
http://www.taverna.org.uk works for me. Other mentors?
The Apache site can talk about anything but it must be absolutely clear
what is Apache and what is not. "don't confuse/mislead users"
A general comment, more mentor-hat-off: identify what MUST be done. All
us developers have a tendency to make ToDo list longer!
So this is also a chance to downplay older stuff.
"Older Versions of Taverna may be found at ..."
> I also suggest merging many of the smaller pages into single larger pages
> Otherwise we have to come up with a different strategy of where to store
> this material especially if we plan on pointing
> http://www.taverna.org.uk/ to the offical Apache website
> Not moving some material also means that 2 websites have to be fixed and
> kept up to date.
>
> 2. Taverna 1/2 download links.
> The proposal is to keep
> http://taverna.incubator.apache.org/download/pre-apache.html and make
> sure it contains all the download links found under:
> http://www.taverna.org.uk/
To reinforce :
This must be very clear that it is not an Apache release with all its
legal implications (IP, copyright ... and a formal release passes the
legal liability from the release manager to the foundation).
Even saying "Taverna Downloads" needs careful qualification.
One way is to point to the old site so the user goes to a different
place (and style) and then finds downloads.
Is the old site in danger of going away sometime soon?
Andy
Re: Website Migration
Posted by Christian Brenninkmeijer <br...@cs.man.ac.uk>.
Hi All,
I have add a look at the old site
http://taverna.incubator.apache.org/download/pre-apache.html and found
over 400 pages.
Before I migrate the website we have to make a few choices.
1. Move Taverna 2 material?
Much of the current material is heavily Taverna 2 base. This incudes
descriptions of things like the workbench and some plugins that are
likely not to be part of the first Apachee release.
My proposal is that we migrate this material anyway, possibly with a
warning that is is Taverna 2/ Not Apache
I also suggest merging many of the smaller pages into single larger pages
Otherwise we have to come up with a different strategy of where to store
this material especially if we plan on pointing
http://www.taverna.org.uk/ to the offical Apache website
Not moving some material also means that 2 websites have to be fixed and
kept up to date.
2. Taverna 1/2 download links.
The proposal is to keep
http://taverna.incubator.apache.org/download/pre-apache.html and make
sure it contains all the download links found under:
http://www.taverna.org.uk/
3. News
http://www.taverna.org.uk/ is wordpress based and so automatically picks
up news posts and creates a new page for each.
http://taverna.incubator.apache.org is not wordpress based so needs a
different strategy,
Having looked at several Apache projects there is no clear pattern for
news items. (if there is any at all)
Some just use a blog such as OpenOffice <https://blogs.apache.org/OOo/>
Some use a single manually editted page such as Lucene
<http://lucene.apache.org/mainnews>
The proposal is to create a single archive news page including all the
news posts at: http://www.taverna.org.uk/
I would suggest keeping this seperate from Apache incubator news. The
choice how to do Apache news can be made later but again I suggest a
singke page.
4. Wiki.
I propose keeping all links to http://dev.mygrid.org.uk/wiki until we
consider what to do about the wiki.
5. Wide page vs fixed width,
Bootstrap offer the choice between a wide page or keeping a fixed width.
I would propose using the wide page as many developers have wide screens
and this allow us to get as much information as possible on a single screen.
While at the same time of course making sure it still look good medium
and small screens but not worring about mobiles.
6. top bar
As already started I suggest we keep a single navbar for all pages on th
apache website.
7. Side bar
For large pages longer than two screens even on a very wide screen.
Have a page specific menubar on the right. Possibly hiding it on small
screens.
This would only be used to point to subjection on that page.
Please see http://taverna.incubator.apache.org/websiteMigration/ for a
summary of these questions which I will update if any suggests are made
based on this email.
There is also
http://taverna.incubator.apache.org/websiteMigration/sitemap which list
the pages I am currently planning on merging.
Christian
On 12/01/2015 15:42, Christian Brenninkmeijer wrote:
> Hi All,
>
> I have taken on the job of migration the old Taverna Website:
> http://www.taverna.org.uk/ to http://taverna.incubator.apache.org/
>
> To record progress and choices I make I have added
> http://taverna.incubator.apache.org/websiteMigration/
> (This directory is not linked of the main page and should be removed
> once the migration is finished.)
>
> First step was to create a sitemap of the old site:
> http://taverna.incubator.apache.org/websiteMigration/sitemap.txt
>
> Next step is to go through the sitemap and record which pages should be
>
> 1. Migrated
> a. Changing links
> b. Changing some Mygrid references to Apache incubator
>
> 2. Migrated as above but with serious editting after migration
>
> 3. Replaced with completly new pages.
>
> 4. Left as links to the old site only
>
> 5. Deleted.
>
> Farther updates to this project will be recorded at:
> http://taverna.incubator.apache.org/websiteMigration/
>
> With only major milestones reported to this mailing list.
>
> Feel free to contact me with any comments or suggested or add them
> directly to http://taverna.incubator.apache.org/websiteMigration/
>
> Christian