Meeting:2009/06/22

From Post-Apocalyptic RPG wiki

Revision as of 14:11, 22 June 2009 by MvBarracuda (Talk | contribs)
Jump to: navigation, search

This article contains a list of topics for as well as the results of the July developer IRC meeting.

Contents

Date

Monday, 22th of June, 5-7PM GMT. If you're unsure the time difference between the timezone you're residing in and GMT, check out this useful website: http://wwp.greenwichmeantime.com/

Type of meeting

First official developer meeting at the IRC channel. Developers from all departments and interested community members are encouraged to take part in the meeting. As it's hard to find a common for all interested developers, we should try to establish department-specific meetings to ensure that all departments meet at least twice a month at IRC. This might not be needed for departments that already have informal semi-meetings on the IRC channel on a quite regular basis (e.g. the programming department).

List of topics

The basic idea is to have a speaker for every subject who introduces the topic and also leads the discussion for this specific point.

Meeting workflow

  • Introduction by: mvBarracuda
  • Proposal: stick to the usual FIFE developer meeting workflow for the first meeting to get to the topics right away instead of lenghty discussions about the general rules of the meeting
  • Alternative workflow for future meetings is possible; change the workflow of future meetings based on feedback after the first meeting
  • Different departments can agree on different workflows for their specific meetings; choose an approach that suits your needs
  • For the first meeting the following workflow - derived from the experience of numerous FIFE meetings - is proposed:
    • There is a "speaker" for every topic who introduces it; preferably the speaker has prepared some notes so he can give his presentation right away without needing to make up his mind as he writes
    • While there is no formal speakers list, we should try to find the right balance between imidiate inquiries while the topic is still introduced and questions that are better to be asked once the introduction is done and we've moved into feedback mode
    • Feedback mode starts as soon as the speaker has ended his introduction; (s)he should point out that his / her introduction is over with some kind of tag, e.g. <end>, _end_, END, done, or something along these lines; this way we avoid extra waiting time
    • Discussion on each topic should not exceed 15 minutes; this is a rule of thumb that depends on the total number of topics; meetings that take longer than 90-120 minutes tend to become more and more exhausting than productive
    • The person who introduced the topic should act as moderator in case the topic exceeds the time limit; in this case he should summarize the different point of views introduce by the developers and propose how to continue (shift discussion to the forums, the next meeting or to the time after the official part of the meeting has ended)
    • The results of the discussion and how to continue need to be written down under the results paragraph, preferably by the developer who introduced the topic; it does not apply to cases when a developer introduces two topics after each other; in this case another developer of the department will hopefully volunteer for the task or propose to juggle topics to avoid these kind of problems
    • Once the meeting is over the project management department is responsible for adding a link to the meeting log at the specific paragraph; in case the IRC logging bot is down, the meeting logs need to be uploaded to the wiki instead and a link to the specific file is added at the log paragraph instead

Programming

Splitting up of tasks for the tech demo.

  • How to make the GUI better.
  • Are we happy with the current framework?
  • Suggestions for the dialog code.
  • Object-Orientation in the code
  • Interfaces to separate work to reduce merging/conflict solving overhead

Audio

Graphics

Game mechanics

  • Recent progress, current state
  • Are there possible ways to implement abstract structures on the programming side, at this point?

Writing

  • Where are we at with the writing department - are there any (secretly) active writers at this point and what is fixed story-wise if at all; speaker: Gaspard (doing one's best to try and attend)
  • Finding a starting point. NineOfHearts' and Dave's story idea?
  • How to get things moving

Project management

  • Introducing department specific IRC meetings?
    • Topic introduced by: mvBarracuda
    • How do the different departments feel about having department meetings about twice a month?
    • Does it address the problems of assymmetric IRC attendance (some departments are underrepresented at the IRC channel)?
  • Restructuring the wiki starting page
    • Topic introduced by: mvBarracuda
    • Focusing on the wiki pages that are shared by all development departments
    • The department-specific pages should be structured according to the preferences of the developers of the department, though help by the project management department is possible if wanted
    • Plan: work out a proposal for a new wiki starting page structuring, post link to the forums, discuss it, apply changes based on feedback, replace old starting page with new one

Results

The agreed upon decisions are listed here. This way it's easier for developers and community members who missed the meeting to get an idea of the general results. Wording of the results for a specific topic should be taken care of by the speaker who introduces the topic.

Programming

Audio

Graphics

Game mechanics

Writing

Project management

Log

Link to the full meeting log.

Personal tools