Developers Meeting 2012-01-02 (Jan 02)
Attending – Andy H., Christine E, Geir Thorud (and his clone), GeneJ, Louis Kessler, Mike Helmantoler, Neil Parker, Robert Burkhead, Roger Moffat, Tamura Jones, Tony Proctor,
Mike Helmantoler – from FS developers group /5.5.5
Andy – DTO, please remain after the meeting.
*ITEM: Further thoughts on P.R. (Tony Proctor)
Will be posting some of his advance work relative to the article.
ITEM: STEMMA file format (Tony Proctor)
If Tony is able to develop a pdf for distribution, we will have a follow up discussion in next week’s meeting.
*ITEM: RootsTech (Robert Burkhead)
We now need to know who our attendees will be.
ITEM: Personal names draft standard (Neil Parker)
The documents are accessed by links at the bottom of the Personal Name Data Standard wiki page
-Suggestion about the “User Requirements.” Find way of prioritizing this section. This is the basis of the “problem” to be solved
-What next? Write a summary, and put that summary on the BG Personal Names wiki main page; then Tweet, G+, FB, Wikispaces email notice to “all members” of this wiki; sending notice to the GEDCOM-L. BetterGEDCOM blog entry.
-Note: For Personal Names, and other topical discussions on the wiki, there are different “format” variables/syntax assumptions. We should develop way of discussing these matters that would lead to a more common approach.
-Louis wonders/suggests we might use, or at least use for now, the format/syntax/data representation grammar from the first part of GEDCOM.
-This requires follow-up.
ITEM: Status update about Source and Citations summaries (see "A Data Model for Sources and Citations")
http://bartonstreet.com/deadends/DeadEndsSources.pdf (Tom W.)
We need a renewed focus on User Requirements and how the project is to be guided by to solutions by those.
See follow up item about User Requirements. (Louis will try to update XML vs GEDCOM in the Requirements Catalog as an example.)
*ITEM: Update about "Developing the Organization"
GeneJ gave little update.
ITEM: Prioritization of activities (Geir)
Large number of activities. Two facets. (1) Any one member may be challenged to participate in all of the activities. (2) More generally, have much work that needs to be done. Priorities must reflect time conflicts.
ITEM: Length of meetings
NOTE: If members of the DTO Group could plan to remain after the end of the Developers Meeting for a short meeting it would be appreciated.
(1) User Requirements (discussions are often buried); Discussions about proposed/researched conclusions (often always buried in discussions) ….
(Louis will try to update XML vs GEDCOM in the Requirements Catalog as an example.)
(2) Definitions. End the pain, please. (Not just the definitions)
(3) Meeting Time – figure something out. (Andy-GeneJ)