Initial abstract for fpm on FortranCon2021

awvwgk commented 3 years ago

Here is the first draft for the abstract of the fpm presentation in the Fortran-lang minisymposium at the FortranCon2021.

I added everybody who was active at the fpm repository in the discussion or implementation of features recently:

@certik, @milancurcic, @interkosmos, @kubajj, @lkedward, @vmagnin, @arjenmarkus, @epagone, @ivan-pi, @everythingfunctional, @rouson, @brocolis, @urbanjost, @MarkWieczorek

Here are a few thing to check:

Please confirm that you would like to be an author here. Authorship on this talk will be opt-in, therefore, please comment until the first abstract submission deadline on the 31st July here.
Please comment if I you think I have omitted any contributors from the last year!

Thematically we want to focus on:

The motivation behind fpm
Why we chose to implement fpm in Fortran
New features in fpm and the general adoption in the community
Future roadmaps (where we want to be next FortranCon?)

urbanjost commented 3 years ago

Straight from the sales department ...

Mastering a programming language is just part of the process of managing the development of software. The Fortran Package Manager (fpm) is a recent advancement introduced by and for the Fortran community that simplifies many of the complex tasks required to manage a Fortran-centric project down to a few command-line entries. fpm(1) creates a cross-platform reproducable development and production environment that simplifies the difficulties in building, running, developing, testing, sharing, and installing Fortran-centric projects. Often leveraging git(1) and github(1) it allows you to build a complex project using compilers of your choice with just a few commands. It automatically determines dependencies and build order by examining the code you place in the project, and provides mechanisms for incorporating other fpm packages; both remote and local. It abstracts common tasks, freeing the developer to concentrate on code development instead of the vagaries of the likes of compiler switches, make(1), Cmake(1), ar(1), install(1), and the multitude of other utilities often required during program development. As the number of fpm-based packages grows and populates the fpm(1) repository (searchable via fpm-search(1)) developers are easily able to incorporate other Open-Source projects, potentially drastically simplifying development time. In concert with the ever-expanding stdlib project vast amounts of time and effort can be eliminated in just a few keystrokes. fpm(1) is relatively new and still rapidly developing. Features are being added to better incorporate complex building requirements that often emerge when developing parallel applications (with OpenMP, CoArrays, MPI, GPUs ...) to integrate with GUI environments and other packaging and documentation tools (Ford, Doxygen, Jenkins, hg, Cmake, ...) and via new barely explored plugin capabilities testing frameworks, profiling and optimization tools and anything else available for leveraging in as straight-forward a manner as possible.

On 07/22/2021 9:41 AM Sebastian Ehlert ***@***.***> wrote:

Here is the first draft for the abstract of the fpm presentation in the Fortran-lang minisymposium at the FortranCon2021.

I added everybody who was active at the fpm repository in the discussion or implementation of features recently:

@certik https://github.com/certik , @milancurcic https://github.com/milancurcic , @interkosmos https://github.com/interkosmos , @kubajj https://github.com/kubajj , @LKedward https://github.com/LKedward , @vmagnin https://github.com/vmagnin , @arjenmarkus https://github.com/arjenmarkus , @epagone https://github.com/epagone , @ivan-pi https://github.com/ivan-pi , @everythingfunctional https://github.com/everythingfunctional , @rouson https://github.com/rouson , @brocolis https://github.com/brocolis , @urbanjost https://github.com/urbanjost , @MarkWieczorek https://github.com/MarkWieczorek

Here are a few thing to check:

    * Please confirm that you would like to be an author here. Authorship on this talk will be opt-in, therefore, please comment until the first abstract submission deadline on the 31st July here.
    * Please comment if I you think I have omitted any contributors from the last year!

Thematically we want to focus on:

   1. The motivation behind fpm
   2. Why we chose to implement fpm in Fortran
   3. New features in fpm and the general adoption in the community
   4. Future roadmaps (where we want to be next FortranCon?)

---------------------------------------------

You can view, comment on, or merge this pull request online at:

  https://github.com/fortran-lang/talks/pull/12

Commit Summary

    * Initial abstract for fpm on FortranCon2021

File Changes

    * A FortranCon2021-fpm/README.md https://github.com/fortran-lang/talks/pull/12/files#diff-e9dbe041a53bea08f11249fa3e9e6430def3b98e6627f5cac73355db95564279 (45)

Patch Links:

    * https://github.com/fortran-lang/talks/pull/12.patch
    * https://github.com/fortran-lang/talks/pull/12.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/fortran-lang/talks/pull/12 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDWN3JEZEPP52NK57AHTDDTZANX3ANCNFSM5A2BEYGA .

urbanjost commented 3 years ago

PS: Throw in that it is written in Fortran so if you are part of the FC (Fortran Community) or want to be if you do not see a feature you want, add it; should talk about preprocessing being in future plans, and that ironically it can be a big hurdle to learn the tools required to contribute (outside of new fpm packages themselves, which is pretty straight-forward) so ask for help with your big idea if you need it, it is available. And mention how fpm(1) is integral to not just stdlib but the new on-line discourse and the emerging learning and documentation center that is part of the new community-driven web page and other complementary resources like Modern Fortran and the Fortran WIki. I have gotten rusty, I guess.

On 07/22/2021 9:46 PM urbanjost ***@***.***> wrote:

Straight from the sales department ...

Mastering a programming language is just part of the process of managing
the development of software.
The Fortran Package Manager (fpm) is a recent advancement introduced by
and for the Fortran community that simplifies many of the complex tasks
required to manage a Fortran-centric project down to a few command-line
entries.
fpm(1) creates a cross-platform reproducable development and
production environment that simplifies the difficulties in building,
running, developing, testing, sharing, and installing Fortran-centric
projects. Often leveraging git(1) and github(1) it allows you to
build a complex project using compilers of your choice with just a few
commands. It automatically determines dependencies and build order by
examining the code you place in the project, and provides mechanisms for
incorporating other fpm packages; both remote and local. It abstracts
common tasks, freeing the developer to concentrate on code development
instead of the vagaries of the likes of compiler switches, make(1),
Cmake(1), ar(1), install(1), and the multitude of other utilities often
required during program development.
As the number of fpm-based packages grows and populates the fpm(1)
repository (searchable via fpm-search(1)) developers are easily able
to incorporate other Open-Source projects, potentially drastically
simplifying development time. In concert with the ever-expanding stdlib
project vast amounts of time and effort can be eliminated in just a
few keystrokes.
fpm(1) is relatively new and still rapidly developing. Features are being
added to better incorporate complex building requirements that often emerge
when developing parallel applications (with OpenMP, CoArrays, MPI, GPUs ...)
to integrate with GUI environments and other packaging and documentation
tools (Ford, Doxygen, Jenkins, hg, Cmake, ...) and via new barely explored
plugin capabilities testing frameworks, profiling and optimization tools and
anything else available for leveraging in as straight-forward a manner as
possible.

    > >         On 07/22/2021 9:41 AM Sebastian Ehlert ***@***.***> wrote:

    Here is the first draft for the abstract of the fpm presentation in the Fortran-lang minisymposium at the FortranCon2021.

    I added everybody who was active at the fpm repository in the discussion or implementation of features recently:

    @certik https://github.com/certik , @milancurcic https://github.com/milancurcic , @interkosmos https://github.com/interkosmos , @kubajj https://github.com/kubajj , @LKedward https://github.com/LKedward , @vmagnin https://github.com/vmagnin , @arjenmarkus https://github.com/arjenmarkus , @epagone https://github.com/epagone , @ivan-pi https://github.com/ivan-pi , @everythingfunctional https://github.com/everythingfunctional , @rouson https://github.com/rouson , @brocolis https://github.com/brocolis , @urbanjost https://github.com/urbanjost , @MarkWieczorek https://github.com/MarkWieczorek

    Here are a few thing to check:

        * Please confirm that you would like to be an author here. Authorship on this talk will be opt-in, therefore, please comment until the first abstract submission deadline on the 31st July here.
        * Please comment if I you think I have omitted any contributors from the last year!

    Thematically we want to focus on:

       1. The motivation behind fpm
       2. Why we chose to implement fpm in Fortran
       3. New features in fpm and the general adoption in the community
       4. Future roadmaps (where we want to be next FortranCon?)

    ---------------------------------------------

    You can view, comment on, or merge this pull request online at:

      https://github.com/fortran-lang/talks/pull/12

    Commit Summary

        * Initial abstract for fpm on FortranCon2021

    File Changes

        * A FortranCon2021-fpm/README.md https://github.com/fortran-lang/talks/pull/12/files#diff-e9dbe041a53bea08f11249fa3e9e6430def3b98e6627f5cac73355db95564279 (45)

    Patch Links:

        * https://github.com/fortran-lang/talks/pull/12.patch
        * https://github.com/fortran-lang/talks/pull/12.diff

    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub https://github.com/fortran-lang/talks/pull/12 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDWN3JEZEPP52NK57AHTDDTZANX3ANCNFSM5A2BEYGA .

>

epagone commented 3 years ago

I am happy to be a co-author, thanks for inviting me. Apart from the above suggestion, I think the abstract is good. Please let me know if you need more help from me.

kubajj commented 3 years ago

Hey, thanks for inviting me. I confirm that I would like to be listed as co-author.

awvwgk commented 3 years ago

Thanks John @urbanjost and Emanuele @epagone for the suggestions to the abstract.

vmagnin commented 3 years ago

Thanks Sebastian, I am interested to be a co-author. Although I just made one PR on the development side and don't have any merit there, I am trying to promote fpm in some French dev websites. I have begun writing a French fpm tutorial but had no time recently to advance on that work.

I can help in reviewing the presentation content.

awvwgk commented 3 years ago

I've submitted the abstract just now.

certik commented 3 years ago

I somehow missed this PR, but I want to be part of this too.

fortran-lang / talks

Initial abstract for fpm on FortranCon2021 #12