OpenPETRA Architecture Team: Difference between revisions
| Line 33: | Line 33: | ||
===Proposals for Potential Topics for Further Discussions=== | ===Proposals for Potential Topics for Further Discussions=== | ||
The list below contains proposals for discussions on topics that we might want to look at. | The list below contains proposals for discussions on topics that we might want to look at. There is no particular order. | ||
''These are discussions only and ''might'' result in one or the other decisions!'' | ''These are discussions only and ''might'' result in one or the other decisions!'' | ||
* | * [[Decimal/Rounding Calculation Definition]] | ||
* [[Validation Framework]] | |||
* [[Business Layer]] | |||
* [[Gathering of Statistics - Which Sites Use Which Functions of PETRA/openPETRA]] | |||
* [[GUI Generator: Simulator for Previewing of GUI (No Dev.Env. necessary?)]] | |||
* [[Generated Files With Manual Code Blocks]] | |||
* [[Data Spread Over Many DB Tables vs. Same Data in One DB Table - Performance]] | |||
==Decisions Taken== | ==Decisions Taken== | ||
* None so far (as of Dec. 6th, 2010). | * None so far (as of Dec. 6th, 2010). | ||
Revision as of 08:56, 7 December 2010
What is the Architecture Team?
A group of people within the openPETRA development team that looks at and improves architectural issues of various kinds.
Team Members
The openPETRA Architecture Team currently consists of christiank and MathiasG. They were nominated to that job by the the other openPETRA core developers at an openPETRA meeting in Carlisle (Nov.30th - Dec.2nd, 2010).
The members of the Architecture Team do not work full-time on architectural issues; rather they are 'normal' openPETRA developers who can be contacted about architectural issues and who are pro-actively looking for architectural issues as they go about their development work. They might work full-time on issues for a certain time as the need arises.
Purpose of the Architecture Team
The Architecture Team...
- proactively identifies issues in the architecture or development process of openPETRA and highlights them to the development team.
- investigates issues of the architecture or development process of openPETRA as identified by other development team members.
and...
- comes up with proposals on how to improve identified issues.
- implements changes to resolve or improve the identified issues themselves, or delegates the implementation of changes to another member of the development team, depending on whatever is seen as best and who/if somebody is available for that.
- creates and maintains documentation on the topics of
- openPETRA architecture
- development process of openPETRA
Discussions
Current Discussions
The list below contains discussions on current topics.
These are discussions only and might result in one or the other decisions!
- Other Source Code Versioning System than git
- Changes to the Process and Workflows of openPETRA Development
- Tools for Supporting the Process and Workflows of openPETRA Development
- DB Transaction Model, Savepoints, Locking
- DB Exception Handling
- DB Caching
Proposals for Potential Topics for Further Discussions
The list below contains proposals for discussions on topics that we might want to look at. There is no particular order.
These are discussions only and might result in one or the other decisions!
- Decimal/Rounding Calculation Definition
- Validation Framework
- Business Layer
- Gathering of Statistics - Which Sites Use Which Functions of PETRA/openPETRA
- GUI Generator: Simulator for Previewing of GUI (No Dev.Env. necessary?)
- Generated Files With Manual Code Blocks
- Data Spread Over Many DB Tables vs. Same Data in One DB Table - Performance
Decisions Taken
- None so far (as of Dec. 6th, 2010).