IFC 4.3.x Change Process
- [new] Change proposed by anyone via new issue creation. This type of issue has no label assigned.
- [allocated] Change is allocated to one or more review teams. An "allocated" label will be assigned. In addition, an "allocated-x" will be assigned, where the "x" corresponds to the review team. This "allocated-x" label will persist throughout the workflow, so at any future point, it is known which team is responsible.
- [proposal] Proposal is clearly articulated into exactly what should be changed (documentation, data types, names, descriptions, etc) so it can be debated. It may now be further refined or decided upon. This distinguishes vague questions or ambiguous suggestions from clearly defined proposals that can be objectively analysed.
- [decided] Review teams approve decision on proposal.
- [implemented] The necessary changes in documentation / UML / code have been made ...
- [rejected] Proposal is rejected, or ...
- [invalid] No proposal is valid, a duplicate of an existing issue, or does not make sense
- [onhold] The review teams lack the time and resources, or cannot prioritise a continued constructive discussion on this issue. It will be temporarily ignored and resumed later.
Decisions are to be made with respect to the ten principles for a future IFC.
Review teams:
The core team handles generic schema changes that affect multiple domains or potentially have far-reaching impacts on software implementations.
- @TLiebich Thomas Liebich
- @berlotti Leon van Berlo
- @aothms Thomas Krijnen
- @Moult Dion Moult
- @NickNisbet Nick Nisbet
- @peterrdf Peter Bonsma
- Andreas Pinzenöhler
- Evandro Alfieri
- @TLiebich
- @hlg
- @Moult
- @yorik
- @aothms?
- @jmirtsch Jon Mirtschin
- @Jesusbill Ioannis Christovasilis
- @krande
- @CyrilWaechter
- @CyrilWaechter
- @Moult
- ?
- @billeast Bill East
- Shawn O'Keeffe
- @LeeGregory12d
- Jon Mitchell
- Robin D.
- @czapplitec
- @SergejMuhic
- @TLiebich
- @Moult
- @SigmaDimensions
- @TLiebich
- @Moult
- @SigmaDimensions
- JanK