OpenPETRA Architecture Team

From OpenPetra Wiki
Jump to navigation Jump to search

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 originally consisted of christiank and ThiasG. They were nominated to that job by the the other OpenPetra core developers at an OpenPetra meeting in Carlisle (Nov.30th - Dec.2nd, 2010). As ThiasG has left the OpenPetra Team in the first half of 2011, christiank is currently the only person on the OpenPetra Architecture 'Team'.

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...

  • pro-actively 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. There is no particular order unless priorities got assigned by the Architecture Team.

Please keep in mind that these are discussions only and might result in one or the other decisions!

Proposals are moved to this section once they become Discussions.

  • The decision on that is to be made only by the Architecture Team!
  • 'Status','Priority' and 'Responsible' and are to be assigned only by the Architecture Team!


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 unless priorities got assigned by the Architecture Team.

Please keep in mind that these are discussions only and might result in one or the other decisions!

You can add your own topics here - 'Status' and 'Responsible' are to be assigned only by the Architecture Team, though!


Decisions Taken

  • Other Source Code Versioning System than git:
    • Decision: Moving to Bazaar after evaluation (Dec. 7th, 2010, Architecture Team meeting)
    • Status: Completed (Dec. 14th, 2010)
      • Move to a Bazaar Repository completed, after two days of intensive evaluation.
    • Responsible:
      • Evaluation: ChristianK and ThiasG
      • Implementation: ThiasG, TimotheusP
  • Data Validation Framework:
    • Decision: Go ahead with implementation (March 8th, 2011, Architecture Team telephone meeting)
    • Status: Completed (March 2012)
    • Priority: High for Phase 1; other Phases: to be determined
    • Responsible: ChristianK (with input from ThiasG)
  • New CSharp Language features 3.0 and 4.0
    • Decision: We corporately decided to use these features during an OpenPetra team meeting in November 2011
    • Status: Completed (November 2011)
    • Responsible: ChristianK and TimoP

Meeting Notes