Closed mortenengen closed 11 months ago
Another proposal for the milestones:
For this milestone we define the structure of the computer code, conventions, etc., which is illustrated for a couple of design clauses. This milestone is meant to showcase the whole idea to others and to provide clear example code for potential new team members. We expect to reach this milestone in short time.
In this milestone we realized:
For this milestone we implement all ULS and SLS code formulas (level 1) and material classes (level 2) of the fib Model Code 2020. Furthermore, we connect to the fib task group that work out different calculation examples with the new Model Code, and elaborate these examples with our computer code. We expect to reach this milestone in xxx of 2024.
In this milestone we realized:
For this milestone we implement all ULS and SLS code formulas (level 1) and material classes (level 2) of the prEN1992-1-1. Furthermore, we elaborate different calculation examples (similar as in milestone 2) using the new Eurocode 2 with our computer code. We expect to reach this milestone in xxx of 2024.
In this milestone we realized:
Hi. As a new member on this project I would like to see some text explaining the vision and motivaion for this work, what the aim currently is, and how we envision this program/code to be used for the end user (are we doing only one calculation or several millions when we run the program).
Thanks for the comment, @slobbeat. We have updated the initial comment above based on your input 😃
I have created milestones related to the package framework, and also Eurocode 2 2023 based on a brief review by @talledodiego and myself. We should do the same for fib Model Code 2020. @DanielGMorenaFhecor: could you do a brief review and suggest milestones for MC2020 similar to EC2 2023 in a comment below?
Here is my draft for the milestones for the package framework related to MC2020. As the MC2020 is extensive, we may need to add more sections in the future under demand.
@aperezcaldentey and @MestreCarlos , feel free to add or remove chapters if you consider it necessary.
* Next to all bullet points, I have written the respective chapter as of the last Draft of the Model Code 2020.
I have updated the milestones according to your comment @DanielGMorenaFhecor.
Edited June 2nd, 2023
We plan to track the progress of the project using milestones. What should these milestones be?
We suggest to use milestones for grouping issues and pull requests in related topics.
We suggest to adopt continuous integration, providing fast releases, so linking milestones to releases is perhaps not necessary. However, milestone # 0 is related to the framework of the package, and upon completion could mark the initial stable release, 0.0.1. We suggest that further releases, that should be incremental upon merging PRs, should follow semantic versioning.
We suggest that the milestone numbering could indicate the timeline, but not necessarily indicate consequentiality, i.e. milestone # 3 does not require milestone # 1 and # 2 to be completed, however, milestone # 2 requires # 1 to be completed, since # 2 is related to integrating # 1 in the package framework.
0 Framework → 0.0.1
1a EC2 2023: Properties and property development
1b EC2 2023: Ultimate limit state
1c EC2 2023: Serviceability limit state
1d EC2 2023: strut and tie and detailing
1e EC2 2023: Fatigue
1f EC2 2023: Misc
2a Integrate EC2 2023 in the framework
3 MC2020
...
4 Integrate MC2020 in the framework
...
etc. for EC2 2004 and MC2010