Conversation

nshaffer

Hi all,

This PR is a draft of the presentation on stdlib to be given at FortranCon 2021. The presentation source is LaTeX. In there, you can see extensive presenter notes which serve as a rough script for what I intend to say along with each slide. I have also included a PDF export of the slides for easy reading.

I'm receptive to any feedback. Have I omitted something important? Dwelled on something unimportant? Need to reorganize? Anything you want to say, I will take into consideration.

@ghbrown @certik @wclodius2 @milancurcic @LKedward @awvwgk @gareth-nx @aman-godara @scivision @Jim-215-Fisher @ChetanKarwa @arjenmarkus @ivan-pi @hsnyder @jvdp1 @ejovo13

@epagone

Good presentation. As a user, I would be curious (towards the end of the presentation) to learn what are the short-terms goals of the project. What it is likely or intended to be implemented in the next 6/12 months? Of course, this goes with the caveat that, being a volunteers effort, there are no promises.

Choose a reason for hiding this comment

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

LGTM. Thank you.

@certik

Good presentation. As a user, I would be curious (towards the end of the presentation) to learn what are the short-terms goals of the project. What it is likely or intended to be implemented in the next 6/12 months? Of course, this goes with the caveat that, being a volunteers effort, there are no promises.

Right. We are looking for a team (or at least one person) to take charge of stdlib and lead the effort. Once we have that, we can have a plan like this.

@milancurcic

@epagone @certik FYI we have a maintainer team, see #484.

Everybody has a say on what should be implemented in stdlib, in the short and long term. We can certainly write out a short-term plan for stdlib now, and I plan to contribute this (among other things) to @nshaffer's talk. Thank you for suggesting it.

@epagone

I am aware of the maintainer team and I think it's a great idea. (I'm even trying to give an "unofficial", very small contribution when time allows.)

I was just trying to step in the shoes of a Fortran practitioner and thought that I would be far more "hooked" to the project by this presentation if I knew what's tentatively planned in the short or medium term.

and I plan to contribute this (among other things) to @nshaffer's talk.

Great, thanks for doing it!

Co-authored-by: Gabriel Brown <[email protected]>
@nshaffer

Good presentation. As a user, I would be curious (towards the end of the presentation) to learn what are the short-terms goals of the project. What it is likely or intended to be implemented in the next 6/12 months? Of course, this goes with the caveat that, being a volunteers effort, there are no promises.

Great suggestion! It's perfectly natural to finish a talk about "what's new in the past year" with a brief discussion of short-term goals. I am thinking for the next revision, I will rework the slide on "room for improvement" to be about short-term goals, since they are largely about the same thing, just with different framing.

@certik

Excellent. Given that you volunteered @milancurcic for the maintainer for stdlib, and given the position includes "set a project road-map and prioritize parts of stdlib development", it seems it is your job to figure out a roadmap with the community and then write it down. :) That's great. Thank you for doing that.

@hsnyder

Very well done! I agree that some discussion about future goals or at least mention of what is being done to address the issues on the second to last frame would be a good addition, but even if you don’t get around to that, it’ll still be a great presentation.

@milancurcic

@nshaffer Do you think you have room / time for one or more extra slides or you'd prefer to stay within these 10?

@nshaffer

@nshaffer Do you think you have room / time for one or more extra slides or you'd prefer to stay within these 10?

I should be able to handle another, or consolidate if need be.

@milancurcic

Thank you @nshaffer for the nice, straightforward, and to the point presentation. I think there's space for an extra slide. If you agree, I can contribute a draft of a short-term outlook / roadmap slide, as suggested by @epagone.

nshaffer and others added 2 commits September 18, 2021 22:47
Co-authored-by: Milan Curcic <[email protected]>
Co-authored-by: Milan Curcic <[email protected]>
@nshaffer

Thank you @nshaffer for the nice, straightforward, and to the point presentation. I think there's space for an extra slide. If you agree, I can contribute a draft of a short-term outlook / roadmap slide, as suggested by @epagone.

Yes, Milan, that would be great. It's important to cover this, and I will consolidate elsewhere if it feels like I'm under time pressure when rehearsing.

Thanks for your detailed feedback upthread. I'll work through it this weekend and have another draft up in a day or two.

Comment on lines +109 to +115
use stdlib_logger, only: global_logger
implicit none
call global_logger%add_log_file('log.txt')
call global_logger%log_debug('I am invisible')
call global_logger%log_information('Something informative')
call global_logger%log_error('Oopsie daisy')
end
Copy link
Member

Choose a reason for hiding this comment

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

Maybe make use of lstlisting to get some basic syntax hints in (mainly by typeface not color). For the fpm presentation I highlighted the code snippets externally and included them as pdf.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hm, I tried mimicking the example in the beamer manual and made a mess of it. In your opinion are the code listings hard to read without any styling?

@nshaffer

Thanks all, I have a next iteration of the talk, taking into consideration all the feedback so far.

https://.com/nshaffer/talks

I also invited @zoziha and @St-Maxwell to be co-authors for their contributions in the few months since I submitted the abstract.

From here, I am hoping to only fix typos (please check your name!) or make small adjustments to ensure I stay within my allotted time. But there is still time to suggest bigger changes if you think they are important. Speak now or forever hold your peace!

@milancurcic

Thank you, @nshaffer, I think it's in great shape!

@ivan-pi

Hey @nshaffer, thanks for the effort preparing this.

My only major comment would be one more example slide with a demo of sorting. Sorting, IMO, has been one of the major things missing in Fortran compared with C, C++, Python and practically every other language that all come with sorting already included.

@zoziha

Looking forward to FortranCon 2021, thank you for your presentation @nshaffer .

Co-authored-by: zoziha <[email protected]>
Co-authored-by: Ivan Pribec <[email protected]>
@nshaffer

Hey @nshaffer, thanks for the effort preparing this.

My only major comment would be one more example slide with a demo of sorting. Sorting, IMO, has been one of the major things missing in Fortran compared with C, C++, Python and practically every other language that all come with sorting already included.

Good idea. I will spin up an example tonight. I might breeze thought it if time is getting to be an issue, but it's good to have there for anyone watching the recordings or checking out the slides afterwards.

@ivan-pi

Thanks @nshaffer for the update. Looking forward to your talk 👍

@milancurcicmilancurcic merged commit 668aac3 into fortran-lang:main Nov 20, 2022
Sign up for free to join this conversation on . Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.