-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add October 2021 news #19174
Add October 2021 news #19174
Conversation
- Also adds November 2021 template - Adds Casey to codeowners for the newsletter
@lindsayad functor material property and 3D mortar content please @eshemon it would be great to have someone add some content (a summary) about the new reactor meshing capability - what all is in it and what all is to come. Would you mind delegating to someone? |
Hi @loganharbour , happy to provide info - how exactly do we add content and in what format? |
@eshemon You can add content to the |
Apologies - forgot to mention that all content should be in markdown style, like the other MOOSE documentation. We can help you get it in the right format after pushing it up, if tweaks are needed. |
@miaoyinb and I will work on getting a summary together. |
@miaoyinb and I will work on getting a summary together. |
Thank you! When your addition is ready, you can point me to your (or @miaoyinb's) branch and I can add the commit to this directly. |
Job Documentation on 333352f wanted to post the following: View the site here This comment will be updated on new commits. |
Job Generate and verify coverage on 333352f wanted to post the following: Framework coverageCoverage did not change Modules coverageCoverage did not change Full coverage reportsReportsThis comment will be updated on new commits. |
@cticenhour - my update on the reactor module is at https://github.com/eshemon/moose/tree/reactor_newsletter_update. Let me know if this is ok. |
The content on this looks good! I will add some automatic linking to the documentation of the objects you mention here when I pull this commit over. Also, if you have an image of an interesting mesh you would like to share, I would be more than happy to add it to your description here. Is there something already existing in the documentation I could link to? |
@loganharbour This is ready for another review. |
I do have something to add for Oct |
Is it in an open PR? We are merging now so that folks who have PRs open can add content alongside their work without us having to rebase. That being said - if you have already merged your work, then feel free to add an entry. |
@fdkong get it in by the end of the day? |
@jbadger95 do you have any time to write-up a 3D mortar announcement? |
@lindsayad I’m a bit busy today (trying to get some jobs in), when does it need to be done? |
@jbadger95 You can submit it later this week in a new PR if you don't have time today. Make your changes in @fdkong @lindsayad Merging this PR today doesn't mean the October newsletter is finalized. We have through the end of the month to record things. Just trying something new in the monthly workflow for these so that we don't have to catch up half a month later. |
@fdkong Did you still want to add content to this PR, or make a new PR? |
I could do that now. If you want to merge it, I am fine with that as well |
Well, it looks like we have a Python failure stopping merges from next. @loganharbour do we want to wait again on this? |
python failure should go away when #19214 is merged |
I thought @dschwen then said it wasn't just that one line change? Since I'm seeing a pyparsing error in that output as well. |
@idaholab/moose-ccb Now that September 2021 is merged into next, I'm opening October early so that people can be pinged for updates. Please add your contributions for October 2021.
Refs #11447