Skip to content

Abstract for FortranCon 2020 about stdlib #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
May 29, 2020

Conversation

jvdp1
Copy link
Member

@jvdp1 jvdp1 commented May 22, 2020

Edited after comments:

Authors:
Jeremie Vandenplas, [email protected], Wageningen University & Research
Bálint Aradi, [email protected], University of Bremen
Izaak Beekman, [email protected], ParaTools Inc.
Ondrej Certik, [email protected], Los Alamos National Laboratory
Milan Curcic, [email protected], University of Miami
Pierre de Buyl, [email protected], KU Leuven
Juan Fiol,,
Michael Hirsch, [email protected], SciVision, Inc.
Ivan Pribec, [email protected], Technical University of Munich
Nathaniel Shaffer, [email protected], Los Alamos National Laboratory

To be acknowledged in the presentation (following comments):
Neil Carlson
Pedro Costa
???
Yuichiro Sakamoto
Ashwin Vishnu

Track: Junior presentations (15 + 5 minutes discussion)

Presenter: Jeremie Vandenplas

Title: Fortran Standard Library

Alternative title: Fortran Standard Library - a community project

Deadline: June 1

@jvdp1 jvdp1 marked this pull request as draft May 22, 2020 18:23
@jvdp1 jvdp1 marked this pull request as ready for review May 22, 2020 18:23
Copy link
Member

@certik certik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks great. Thanks for writing it! I left some minor comments.

Copy link
Member

@milancurcic milancurcic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @jvdp1! Looks good to me, pending @certik's suggestions which I agree with.

@pdebuyl
Copy link

pdebuyl commented May 22, 2020

Hi @jvdp1 thank you for the initiative!

@jvdp1
Copy link
Member Author

jvdp1 commented May 23, 2020

Thank you @certik @milancurcic @pdebuyl for the comments. They are now integrated.

@milancurcic
Copy link
Member

Thanks Jeremie. You can merge yourself when you're ready.

@jvdp1
Copy link
Member Author

jvdp1 commented May 23, 2020

Thanks Jeremie. You can merge yourself when you're ready.

I will let it here a few more days, such that other contributors have a chance to read it.

Regarding co-authors, I don't have full names, affiliations or/and email addresses of some of those listed. what is the plan for that?

@milancurcic
Copy link
Member

Sounds good. Ultimately, it will be up to you, but here's what I think makes most sense. You invited all contributors to be co-authors and that's what matters. Those who want to be co-authors and contribute to the talk, they'll write here and provide the needed information. Everybody else, you can acknowledge in the talk. This is how I plan to do it for the community talk.

@ashwinvis
Copy link

Thanks to @fortran-lang developers for being inclusive and welcoming. I appreciate the gesture, but I do not consider my small patch worthy to be counted amongst co-authors. Feel free to exclude my name.

+1 on @milancurcic 's point

@p-costa
Copy link

p-costa commented May 23, 2020

I also think that my very, very minor contributions are not enough to deserve co-authorship (or even acknowledgment), so please feel free to exclude my name.

@sakamoti
Copy link

Thank you for inviting me to be one of a co-authors. I only tested the library and fixed the specific issue, so I don't think it's enough to participate as a co-author now.
I'm very interested in this project, so if it's as an acknowledgement, I'm glad to be included my name.
(I've added my name to my profile on github.)

Copy link
Member

@aradi aradi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot to include me on the author list! I think, it is a very good idea to present the stdlib on the FortranCon 2020!

@JHenneberg
Copy link

I also think that my very, very minor contributions are not enough to deserve co-authorship (or even acknowledgment), so please feel free to exclude my name.

Same for me.

Copy link
Collaborator

@nshaffer nshaffer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great initiative on getting an abstract up. I think FortranCon is a perfect place to publicize stdlib. Just filled in my name and had some minor suggestions. Take them or leave them.

Started a few months ago, no less than 15 people already contributed to the development of the Fortran Standard Library and its documentation.
Currently the library includes procedures for catching and handling errors, handling optional arguments, facilitating I/O operations, linear algebra, numerical integration, and descriptive statistics.
Many other programmers are also involved in active discussions about the development of the Fortran Standard Library through GitHub issues.
The development of this library is part of the Fortran-lang project and aims to collaborate with the Fortran Standards Committee.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to be more specific? My understanding is that stdlib is to be the reference implementation for compiler vendors if is eventually adopted by the standards committee.

Copy link
Member Author

@jvdp1 jvdp1 May 28, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I keep your suggestion for the presentation. I can't integrate this in the abstract due to word limits

@nncarlson
Copy link

I also think that my very, very minor contributions are not enough to deserve co-authorship (or even acknowledgment), so please feel free to exclude my name.

And same for me as well. But your gesture to be inclusive is appreciated. Hopefully sometime in the not so distant future I'll have the time to contribute in a more significant way to this important effort.

@jvdp1
Copy link
Member Author

jvdp1 commented May 28, 2020

Thank you all for your comments. I will submit the abstract tomorrow afternoon.

@jvdp1
Copy link
Member Author

jvdp1 commented May 29, 2020

I submitted the manuscript. Thank you all for your comments and input.

@jvdp1 jvdp1 merged commit 24a6824 into fortran-lang:master May 29, 2020
@jvdp1 jvdp1 deleted the fortrancon-stdlib branch May 29, 2020 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.