Changeset a14839a in flex_extract.git for For_developers/Sphinx/source/support.rst


Ignore:
Timestamp:
May 15, 2020, 2:27:39 PM (4 years ago)
Author:
Petra Seibert <petra.seibert [at) univie.ac.at>
Branches:
master, ctbto, dev
Children:
f20342a
Parents:
b936fd3
Message:

Language corrections for the Sections Developers, Support, Changelog, and the home directory (index.html)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • For_developers/Sphinx/source/support.rst

    rba99230 ra14839a  
    1616.. _ticket system: https://www.flexpart.eu/report/1
    1717
    18 The community website http://flexpart.eu contains a
    19 `ticket system`_ which can be used to report any issue or a proposition for a new feature.
     18The community website https://flexpart.eu/ contains a
     19`ticket system`_ which can be used to report any issue or to propose new features.
    2020
    21 The tickets can be viewed by anyone, to create a ticket a registration is necessary. Since the automatic registration is unavailable, please send an email to the ``flexpart.eu[at]zamg.ac.at`` and you will receive your credentials (with some delay). 
     21The tickets can be viewed by anyone, to create a ticket a registration is necessary. Since the automatic registration is unavailable, please send an email to the ``flexpart.eu[at]zamg.ac.at`` and you will receive your credentials (possibly with some delay).  Event though a category "Support" is available, in most cases asking questions in the mailing list (see next paragraph below) will be more appropriate.
    2222
    2323
     
    2727------------
    2828
    29 The mailing list is mainly for the ``FLEXPART`` users to ask questions or share experiences regarding the whole ``FLEXPART`` process with the community. This can be a lot faster than asking only the developers for help. Since ``flex_extract`` is a preprocessor to ``FLEXPART`` this is the right place to ask for help.
     29A mailing list exists for the ``FLEXPART`` users to ask questions or share experiences with the community, regarding the whole ``FLEXPART`` process. This may be faster than asking only the developers for help through tickets. Since ``flex_extract`` is a preprocessor to ``FLEXPART`` this is the right place to ask for help.
    3030
    31 Additionally, from time to time, there will be announcements for all FLEXPART users, such as new release versions of ``FLEXPART`` or ``flex_extract``.
    32 
    33 Just write a mail to: ``flexpart[at]lists.univie.ac.at``
     31New release versions of ``FLEXPART`` or ``flex_extract`` or other important annoucements will also be made through this mailling list.
     32The subscription process is explained at the bottom of https://www.flexpart.eu/wiki/RegisteredUser. Once subscribed, write e-mail to ``flexpart[at]lists.univie.ac.at`` to post to the list.
    3433
    3534
     
    4140To properly report a problem or bug, please provide as much information as possible.
    4241This includes:
    43 
    44 * the flex_extract version
    45 * a flex_extract log file (output of submit.py script)
    46 * the CONTROL file
    47 * the commandline arguments or run(_local).sh settings and
    48 * a description of the environment you used (Unix/Linux version, library version, application mode, etc.).
     42* the ``flex_extract`` version
     43* a ``flex_extract log`` file (output of ``submit.py`` script)
     44* the ``CONTROL`` file
     45* the command-line arguments or ``run(_local).sh`` settings and
     46* a description of your environment (Unix/Linux version, library version, application mode, etc.).
    4947
    5048
Note: See TracChangeset for help on using the changeset viewer.
hosted by ZAMG