K-ballo changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
<peltonp1_>
all links except the one on the first slide (previous lecture) and last slide (next slide) are broken
<hkaiser>
well, if you could be a bit more specific, or better yet, create a PR that fixes it...
<peltonp1_>
*next lecture
diehlpk_work has joined #ste||ar
<diehlpk_work>
hkaiser, mdiers[m] The latest pr worked on Fedora 35 and HPX 1.6.0 is pushed there
<hkaiser>
+1
<hkaiser>
thanks
hkaiser has quit [Quit: bye]
nanmiao11 has joined #ste||ar
<diehlpk_work>
ms[m], Would you be itnerested to apply for GSoD again this year?
<diehlpk_work>
Just received the information that organizations can apply.
<gonidelis[m]>
diehlpk_work: we need that
hkaiser has joined #ste||ar
<diehlpk_work>
gonidelis[m], yes, but we need also a nice project how to imrpove the documentation
<diehlpk_work>
and we need a mentor working with the student to improve the documentation.
<diehlpk_work>
hkaiser, GSoD application comes soon. Do we want to apply?
<diehlpk_work>
Do we have some nice project to improve the documentation?
<gonidelis[m]>
Creating a tutorial mini series is an idea
<gonidelis[m]>
Improving our API docs interface is another one
<gonidelis[m]>
Segmenting our How to build HPX docs into separated parts according to the platform and packaging the options into different tabs is a good one too
<ms[m]>
the difficulty with tutorials is that it really requires someone who both knows c++ and how to write :/
<diehlpk_work>
gonidelis[m], Assume we get one who can write technical documentation, but mostly no documentation of code and can not read/understand code
<gonidelis[m]>
I can speak for my algorithms modules part
<gonidelis[m]>
A good iteration over the algorithms docs on chasing minor doc bugs like the result types and/or clarifying their api
<gonidelis[m]>
diehlpk_work so how could one provide technical write ups without understanding the code ???
bita has joined #ste||ar
hkaiser has quit [Ping timeout: 264 seconds]
<ms[m]>
gonidelis[m]: you can't really... in 2019 we had an english major for gsod who helped clean up the language in the docs to be consistent and understandable, but it was obviously difficult for her to contribute new content