From owner-freebsd-doc@FreeBSD.ORG Mon Jun 17 10:12:12 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E86D7E0 for ; Mon, 17 Jun 2013 10:12:12 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog112.obsmtp.com (eu1sys200aog112.obsmtp.com [207.126.144.133]) by mx1.freebsd.org (Postfix) with ESMTP id 481E91902 for ; Mon, 17 Jun 2013 10:12:11 +0000 (UTC) Received: from mail-wi0-f181.google.com ([209.85.212.181]) (using TLSv1) by eu1sys200aob112.postini.com ([207.126.147.11]) with SMTP ID DSNKUb7g9HiMoH/YZORE0lYp7KAq/jybRcsz@postini.com; Mon, 17 Jun 2013 10:12:12 UTC Received: by mail-wi0-f181.google.com with SMTP id hq4so1993111wib.14 for ; Mon, 17 Jun 2013 03:12:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:reply-to:x-gm-message-state; bh=fXlz/uuZo4OcBCK/+11/KBK/L4B0edYwK0HDc0PHBFU=; b=ltMm7yklwEdgxpQucwp79nObBAm5ZyFV2iCwx+O75nGIek+6Vz/vtzvv3op5LT9Ulf EMsC9A3Ihc2qGUMGOmyXkLjOwtPCqfw/QQ1vbu0XioI5rF9iuPMMRLu0lEi7NAnEiUUW YjPwjhqLgFy+pSolj/IGgZGHstHv2hb6wS4UtjA29kWNrjnXLSqfeiIGQyCANHldNcxC PECV4g6uYcG+bjF5blV7+uOi8ER7n+sWznRxSVgsC99LhL1mEAKBIhFb/Bqj5Kcnd92l l1cyTPURGWKYJTgjl7LXxZpTUcJPZE3lJKUNFNnTs5mlSvWQwkhFhZQRyLWqypNRBMr7 +4WA== X-Received: by 10.195.12.133 with SMTP id eq5mr7404975wjd.27.1371463583717; Mon, 17 Jun 2013 03:06:23 -0700 (PDT) X-Received: by 10.195.12.133 with SMTP id eq5mr7404971wjd.27.1371463583641; Mon, 17 Jun 2013 03:06:23 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id fv11sm20902992wic.11.2013.06.17.03.06.21 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Jun 2013 03:06:22 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6) with ESMTP id r5HA6KxH018636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 17 Jun 2013 11:06:20 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6/Submit) id r5HA6KNV018635 for freebsd-doc@freebsd.org; Mon, 17 Jun 2013 11:06:20 +0100 (BST) (envelope-from mexas) Date: Mon, 17 Jun 2013 11:06:20 +0100 (BST) From: Anton Shterenlikht Message-Id: <201306171006.r5HA6KNV018635@mech-cluster241.men.bris.ac.uk> To: freebsd-doc@freebsd.org Subject: proposed new mailing list: FreeBSD-Fortran X-Gm-Message-State: ALoCoQkiWTu4TPHG/n8LmQspS4holNPYERhij8Bf+vAz9RtvS26qZQKYn5o7v5M/Mo7smXDBkiveQZcOPHQRN6SjqZCW8lBuJlsrl1H9E3mUB+NHcchDo5cyN32HpPGveLhib9jHiKtx0i1uE+2eAT8Kk0BB1bvuPmZWTlpr+D/d1/2exPjty+c= X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2013 10:12:13 -0000 I propose to create a dedicated FreeBSD Fortran mailing list. The list will be helpful because: 1. There are a number of ports which depend on fortran compiler or libraries in some way: $ find /usr/ports/ -name "Makefile" | xargs grep -i fortran | wc -l 361 $ 2. The FreeBSD Fortran expertise is scattered over many lists at present. This will be a single point of contact for all parties interested in Fortran on FreeBSD. 3. There are several developers/committers with Fortran expertise, e.g. bf@, gerald@, maho@, who maintain a lot of the critical fortran ports infrastructure, i.e. key libraries and compilers. The list will help Fortran users attaract the attention of all these people (hopefully they will want to subscribe). 4. Fortran is old and new, i.e. there are codes which are still in 77 standard, and there are compilers supporting 2008 standard. Accordingly, there is a great diversity of the needs of fortran users. How the fortran ports infrastructure supports these needs should be discussed. 5. There are number of fortran libraries already in ports. There are many which are not. A discussion of what would be good to have in fortran ports is needed. 6. There might be a discussion of the need for a long term strategy or plan for supporting freebsd fortran users for years ahead, including compilers, libraries and end-user code. 7. Fortran is still the most widely used language in HPC, where FreeBSD is still a minor player. This list might help formulate strategy for fortran growth in FreeBSD and thus for the promotion of FreeBSD use in HPC. Clearly this is a very ambitious and a very long term aim. 8. Discussions on this list might lead to a dedicated FreeBSD Fortran page on the freebsd.org site. The page might include the current state of fortran ports, a roadmap for the future, problems, key stumbling blocks, etc. 9. If the list will help formulate priorities for the freebsd fortran ports, then this might help attract porting volunteers. Anton