[Bioc-devel] Suggestions to improve the package 'homepages' on the Bioc site.
Kasper Daniel Hansen
kasperdanielhansen at gmail.com
Sun Apr 25 23:47:03 CEST 2010
While we are doing suggestions to the webpage
1) the links at http://wiki.fhcrc.org/bioc/DeveloperPage needs to be
updated. Specifically, the two links named 2,5 and 2.6 check report
needs to be updated to 2.6 and 2.7, and the link named "devel
packages" needs to be updated from 2.5 to 2.7 (so this was outdated
for a while).
2) On CRAN there is a link to the package NEWS/ChangeLog file as well
as a file named INSTALL. Both of these (as well as a link to a
possible README) would be extremely useful. For examples, see
On Sun, Apr 25, 2010 at 5:09 PM, Sean Davis <seandavi at gmail.com> wrote:
> On Sun, Apr 25, 2010 at 4:03 PM, Patrick Aboyoun <paboyoun at fhcrc.org> wrote:
>> On Friday we modified
>> to be more discriminatory. I'm not sure what the search engine turn around
>> time is, but let us know if you are still finding old package links coming
>> up in Google searches and the like.
> Another possibility, besides robots.txt which will simply block
> content (is this really what is desired?), is to use a sitemap.
> This would potentially allow more fine-grained control over what urls
> are crawled, how often, and most importantly, what urls are highest
> importance on the site.
>> On 4/25/10 3:23 AM, mtmorgan at fhcrc.org wrote:
>>> Hi Wolfgang --
>>> Quoting Wolfgang Huber <whuber at embl.de>:
>>>> first, a great *thank you* and congratulations to the guys in Seattle
>>>> to the new release. Fantastic job. And it seemed so smooth! (At least
>>>> from this side of the pond).
>>>> When googling a package name, one often gets the Bioc package homepage,
>>>> which is often a good first place to figure out what a package does.
>>>> E.g. http://www.bioconductor.org/packages/2.6/bioc/html/DESeq.html
>>>> is the first hit I get for "DESeq".
>>>> However, say, for "tilingArray" I get
>>> Our plan in the not-too-distant future is to add a robots.txt file that
>>> will suggest indexing the current release only, so you'll get directed to
>>> the right place as soon as the search engines pick up on the change.
>>>> So, do you reckon it would be useful that these pages, prominently, list:
>>>> - the release number (e.g. "2.6")
>>>> - the date of the release (e.g. "2009-10-26")
>>>> - if release is not the current one, a link to the current release
>>>> PS Don't forget to add the new release to the "Project News" on
>>> Thanks for the reminder!
>>>> Wolfgang Huber
>>>> Bioc-devel at stat.math.ethz.ch mailing list
>>> Bioc-devel at stat.math.ethz.ch mailing list
>> Bioc-devel at stat.math.ethz.ch mailing list
> Bioc-devel at stat.math.ethz.ch mailing list
More information about the Bioc-devel