Loading ...
Sorry, an error occurred while loading the content.

BoD Log 4/7/2008

Expand Messages
  • Andrew Maitland
    [19:00] [Chair]Eddy: Greetings everyone, I ve got 10pm EDT, let s begin. [19:00] [Admin]Andrew: yeah, your four clones [19:00] [PR_SB]Maredudd: ER, maybe not .
    Message 1 of 1 , Apr 7, 2008
    • 0 Attachment
      [19:00] [Chair]Eddy: Greetings everyone, I've got 10pm EDT, let's begin.
      [19:00] [Admin]Andrew: yeah, your four clones
      [19:00] [PR_SB]Maredudd: ER, maybe not . . .
      [19:00] [PR_SB]Maredudd: :-)
      [19:00] [Chair]Eddy: Tonights agenda items following status reports:
      [19:00] [Chair]Eddy: 1.) 5.14 status
      [19:00] [Chair]Eddy: 2.) Gencon plans
      [19:00] [Chair]Eddy: 3.) Yahoo file status (when should old files be
      [19:00] [Chair]Eddy: I'll start with the content report
      [19:00] [Chair]Eddy: Documentation
      [19:00] [Chair]Eddy: Doc Bugs: 4 for 5.12 (5 total, unchanged since last
      [19:00] [Chair]Eddy: Doc FREQs: 6 for 5.14 (30 total, +1 since last meeting)
      [19:01] [Chair]Eddy: Doc status: good to go, issues are being delt with
      as they are posted
      [19:01] [Chair]Eddy: Output Sheets
      [19:01] [Chair]Eddy: OS Bugs: 3 for 5.14 (4 total, unchanged since last
      [19:01] [Chair]Eddy: OS FREQs: 17 for 5.14 (39 total, -1 since last meeting)
      [19:01] [Chair]Eddy: If no one objects I'm going to bump most of these
      trackers to 6.0, there's no one to work on them and most of them I
      consider non-essencial for 5.14.
      [19:01] [Chair]Eddy: We will need to find someone to implement new
      blocks for ability objects in the PDF's next cycle or they will fall
      behind, currently we still use SAB for output.
      [19:01] [Chair]Eddy: Data
      [19:01] [Chair]Eddy: Data Bugs: 1 for 5.14 (28 Total, +1 since last meeting)
      [19:01] [Chair]Eddy: Data FREQs: 3 for 5.14 (52 Total, -1 since last
      [19:01] [Chair]Eddy: Data status:
      [19:01] [Chair]Eddy: All major FREQs are complete, what's left will
      either be done shortly or is not required and can be bumped to the next
      cycle if is doesn't make it in before we hit RC.
      [19:02] [Chair]Eddy: The only bug we have needs to be resolved by the
      publisher, it's years old so if it's not resolved it will be bumped as well.
      [19:02] [Chair]Eddy: Other bugs are being addressed as they are opened.
      [19:02] [Chair]Eddy: In short data is ready for release!!!
      [19:02] [Admin]Andrew: Yay!
      [19:02] [Chair]Eddy: New Data Development:
      [19:02] [Chair]Eddy: We have two left in the pipeline for 5.14:
      [19:02] [Chair]Eddy: [1914042] [RPG Objects] Darwin's World 2 -Terrors
      of Twisted Earth
      [19:02] [Chair]Eddy: [1843819] [AEG]Gods
      [19:02] [Chair]Eddy: Both need to be reviewed for OGL complience
      [19:02] [Chair]Eddy: Questions?
      [19:02] [OGL]Nylanfs: I'm almost finished with TTE
      [19:03] [Chair]Eddy: Excellent, thanks Paul
      [19:03] [Admin]Andrew: None from me.
      [19:03] [PR_SB]Maredudd: None from me . . .
      [19:03] [Admin]Andrew: Can I go next?
      [19:03] [Chair]Eddy: OK, Andrew, while we still have you go for it
      [19:03] [Admin]Andrew: Thanks, Eddy
      [19:04] [Admin]Andrew: Okay. Website - Kar has been made a few progress
      steps, but won't get anything solid till after the 5.14 cycle
      [19:04] [Admin]Andrew: We plan on adding trackers for volunteers to hit,
      also slated for post 5.14
      [19:05] [Admin]Andrew: Trackers - Kar, Eddy, Tom and Eric. Great job for
      creating and tackling those trackers. Things seem to be on a roll.
      [19:05] [Admin]Andrew: Release - James has already submitted the
      releasenotes for 5.13.13 (I think .13)
      [19:05] [Admin]Andrew: James anything to add?
      [19:06] [Chair]Eddy: Is this the last beta?
      [19:06] [Code_SB]james: 5.13.13 will be in under 12 hours now - just
      sent out the notification
      [19:06] [Code_SB]james: Lets save that question for the status :)
      [19:06] [Chair]Eddy: no prob
      [19:06] [Admin]Andrew: Cool.
      [19:07] [Admin]Andrew: Questions for Admin?
      [19:07] [Chair]Eddy: not from me
      [19:07] [Admin]Andrew: Okay... Over to you Eddy...
      [19:07] [Admin]Andrew: Thanks...
      [19:07] [Chair]Eddy: Thank you
      [19:07] [Chair]Eddy: Eric, can we hear from PL next?
      [19:07] [PR_SB]Maredudd: I have a quetin for admin . . .
      [19:07] [Admin]Andrew: Ok
      [19:08] [PR_SB]Maredudd: The Roadmap hasn't been updated in awhile. I
      was trying to do it, but the wiki gets wacked way to often . . . do we
      need to maintain it?
      [19:08] [PR_SB]Maredudd: Or, as we havn't really been using it, can we
      drop it al together?
      [19:09] [Admin]Andrew: I think we should keep the Road map current -
      although this last period we kinda made a few exceptions considering CMP.
      [19:09] [PR_SB]Maredudd: \Hmmm, I'm talking about the roadmap on the
      wiki with all of the trackers listed . . .
      [19:09] [Admin]Andrew: But the road map sets our goals for each cycle.
      I've been lax in keeping it up, but if the Wiki is giving you issues...
      [19:09] [Code_SB]james: We aren't using it for the release notes, so
      maybe if it just tracked major things - freqs and high priority bugs it
      might be simpler
      [19:10] [Chair]Eddy: The roadmap has it's most utility at the start, it
      loses relevance the closer the goal gets
      [19:10] [Admin]Andrew: Ah, trackers. Yes, James that's a good point. - I
      say keep it. We can discuss what to do with it post reports... Is that
      ok Eric?
      [19:10] [PR_SB]Maredudd: Yep!
      [19:11] [Admin]Andrew: OKay... AFK.
      [19:11] [Chair]Eddy: it's a good tool to use at the start nut I don't
      see the need to maintain it religiously to the end
      [19:11] [Chair]Eddy: Erik, you up next
      [19:11] [PR_SB]Maredudd: Set the baseline for a cycle . . .
      [19:12] [PR_SB]Maredudd: Ok. PL next:
      [19:12] [PR_SB]Maredudd: Publisher Liaison Team Report:
      [19:12] [PR_SB]Maredudd: Artwork, logos, and hyperlink Permissions Request
      [19:12] [PR_SB]Maredudd: 32 Letters sent/14 Responses to date
      [19:12] [PR_SB]Maredudd: 11 Pubs Agree/3 Pubs Denied Permissions (2 for now)
      [19:12] [PR_SB]Maredudd: No new publishers added to our list since
      Paizo, though I do have a letter out to them for PathfinderRPG.
      [19:13] [PR_SB]Maredudd: Any question on PL? PaulK . . . any additional
      [19:14] [Code_SB]james: Great to see the publishers talking up our new
      [19:14] [Chair]Eddy: Not from me
      [19:14] [PR_SB]Maredudd: For the record, letters have only been sent to
      publishers for whom we distribute datasets . . .
      [19:14] [Code_SB]james: Makes sense
      [19:14] [Chair]Eddy: ditto
      [19:14] [PR_SB]Maredudd: The other publisghers will be hit up after 5.14
      gets out .. .
      [19:14] [Chair]Eddy: hopefully we can talk this capability up at Gencon
      [19:14] [PR_SB]Maredudd: I plan on it!
      [19:15] [PR_SB]Maredudd: On to the OGL Team
      [19:15] [PR_SB]Maredudd: OGL Team Report:
      [19:15] [PR_SB]Maredudd: A number of folks have signed NDAs with WotC to
      take a look at the GSL. Â Unfortunately, WotC hasn't released the GSL
      for review as yet. Â When they do, We'll get a look at it.
      [19:16] [PR_SB]Maredudd: As noted earlier, only two set require review
      in support of 5.14.
      [19:16] [PR_SB]Maredudd: PaulG, any additions?
      [19:17] [PR_SB]Maredudd: If there are no questions, I'll move to
      Advertising . . .
      [19:17] [OGL]Nylanfs: Nope, I should have TTE finished tonight and try
      and take a look at GODS
      [19:17] [PL_2nd]Paul: sorry. no i have nothing else to say
      [19:17] [PL_2nd]Paul: been rather busy recently
      [19:17] [PR_SB]Maredudd: Advertising Team Report:
      [19:17] [PR_SB]Maredudd: Press Releases went out for the last beta as
      well as a "PCGen Goes to Gen Con" press release. All the standard site
      were hit. Â There are a few others that I will be hitting in the next
      round, which will be when we get the booth information from Gen Con.
      [19:17] [PR_SB]Maredudd: A "PCGen Goes to Gen Con" wiki page is up here
      [19:17] [PR_SB]Maredudd:
      [19:18] [PR_SB]Maredudd: Any questions?
      [19:20] [Chair]Eddy: Not from me, shall we move on to ARCH?
      [19:20] [Arch_SB]thpr: been working on getting more complete testing for
      the tokens - only a handful left to go to get to 100% for stand alone tests
      [19:21] [Code_SB]james: Nice
      [19:21] [Arch_SB]thpr: (stand alone means no .MOD behavior, no .CLEAR
      behavior, assumes only one on a line)
      [19:21] [Arch_SB]thpr: Integration tests are also progressing well,
      though those aren't yet nearly that high
      [19:21] [Arch_SB]thpr: as no ADD, AUTO or global tokens are yet being
      integration tested
      [19:22] [Arch_SB]thpr: Have received feedback based on compatibiltiy
      testing that has driven some corrections into the 6.x branch (generally
      I had a few issues with separators or late 5.13 additions that I hadn't
      [19:22] [Arch_SB]thpr: Some more of those to go, but nothing that's major
      [19:23] [Arch_SB]thpr: Have been trading emails with Connor - he's been
      a great help in looking at the architecture of 6.x
      [19:24] [Arch_SB]thpr: Some good ideas, and I think he's still pondering
      if/how we can work those in and not have issues
      [19:24] cpmeister: i've been wanting to IM you for a while...
      [19:24] [Arch_SB]thpr: Yea, sorry, I should be on much of this week,
      except Wed
      [19:24] [Arch_SB]thpr: so we should be able to catch up
      [19:25] cpmeister: :)
      [19:25] [Arch_SB]thpr: I think that's probably it for now
      [19:25] [Arch_SB]thpr: questions?
      [19:27] [Code_SB]james: A few weeks ago you mentioned a potential change
      of approach for 6.0 - is it worth discussing that now?
      [19:27] [Code_SB]james: or as an item for a later meeting?
      [19:27] [Arch_SB]thpr: I think we want to discuss that as a code team
      and then come back and make sure no one has major objections
      [19:28] [Code_SB]james: Sounds good
      [19:28] [Chair]Eddy: OK, James, you're up next
      [19:28] [Code_SB]james: Right-o
      [19:28] [Code_SB]james: Code Report 20080408 (pre 5.13.13)
      [19:28] [Code_SB]james: Bugs: Last meeting 39 open. This fortnight: 15
      new opened, 16 fixed, 2 pending/deleted, 36 open for 5.14
      [19:28] [Code_SB]james: Feature requests: Last meeting 2 open. This
      fortnight: 2 closed, 2 open for 5.14
      [19:28] [Code_SB]james: Plugin bugs: Last meeting: 7 open. This
      fortnight: 2 new opened, 0 fixed, 9 open for 5.14
      [19:28] [Code_SB]james: Plugin feature requests: No further work
      scheduled for 5.14
      [19:28] [Code_SB]james: So, code is keeping up but not really closing
      the gap.
      [19:29] [Code_SB]james: BTW: 18 of our bugs are assigned, but 5 or so of
      those are to people who haven't been active in the code for a while.
      [19:30] [Code_SB]james: The 2 open features I believe need to be either
      completed by the next release or rescheduled back to 6.0
      [19:31] [Arch_SB]thpr: Is there any specific help the rest of us can
      provide on those two?
      [19:32] [Code_SB]james: Both are with Joe - he would be best placed to
      [19:32] [Arch_SB]thpr: ok, I'll hound him to answer later since he's not
      speaking up now :)
      [19:32] jfrazierjr: nah.. I am good... I had expected to get them done
      this weekend.. but then I came down with a virus and it laid me up
      [19:32] [Arch_SB]thpr: ok
      [19:32] jfrazierjr: I have both in the works
      [19:33] [Code_SB]james: The best thing that could be done is the code
      arena is for a few people to get in to the bugs and give me a hand there
      [19:34] [Arch_SB]thpr: Well, skiing here is pretty much done, so I have
      more weekend morning free time to invest. Hopefully that will help
      close that gap
      [19:34] [Code_SB]james: Thanks Tom, that'd be great
      [19:34] [Code_SB]james: ok, any questions on the code report?
      [19:35] [PR_SB]Maredudd: I have a quick one . . .
      [19:35] jfrazierjr: I have several items for substitutionlevel broken...
      so that will probably keep me busy for a while... Tom/James... I may
      need to tap you guys for questions on the particulars of one or two of them
      [19:35] [Code_SB]james: No problems Joe
      [19:36] [PR_SB]Maredudd: Tom had suggested some time ago that we move
      the Tag Dictionary (my term for it) to xml. Is that still an option and
      if so, what do we need to do to get there?
      [19:36] [Arch_SB]thpr: I never got a development volunteer to develop
      the necessary code
      [19:36] [PR_SB]Maredudd: I recall that some script work hadto be done to
      facilitate that . . .
      [19:36] [Arch_SB]thpr: so we're gated by that - and thus probably gated
      for some time
      [19:37] [Arch_SB]thpr: script is secondary - the primary issue is in the
      [19:37] [PR_SB]Maredudd: OK . . . I'll talk to you more about it later
      Tom . . .
      [19:37] [Arch_SB]thpr: I would consider that a post 6.0 project at this
      [19:37] [Arch_SB]thpr: ok
      [19:38] [PR_SB]Maredudd: Thats all I had . . .
      [19:38] [Chair]Eddy: Shall we move on to agenda item 1, 5.14 status?
      [19:38] [Code_SB]james: For sure
      [19:38] [Chair]Eddy: As I said earlier content is in good shape
      [19:38] [Chair]Eddy: what's the release schedule at this point?\
      [19:39] [Code_SB]james: As you might of guessed from my report I can't
      say the same about code.
      [19:39] [Code_SB]james: 5.13.13 beta - 7th April
      [19:39] [Code_SB]james: 5.14.0 RC 1 - 21st April
      [19:39] [Code_SB]james: 5.14.0 RC 2 - 28th April
      [19:39] [Code_SB]james: 5.14.0 prod release - 4th May
      [19:39] [Code_SB]james: is what we had previosuly discussed.
      [19:40] [Code_SB]james: I think we might have to add another beta in
      there now for code to catch up. That could be a one or a two week delay
      [19:40] [Chair]Eddy: what do we do when we go from beta to RC? I recall
      the RC was branched, when does that happen?
      [19:41] [Code_SB]james: Bets idea is probably to branch from the source
      used to do RC1
      [19:41] [Chair]Eddy: so release RC1 and cut a branch?
      [19:41] [Arch_SB]thpr: So now we expect 5.13.14 on Apr 21
      [19:42] [Code_SB]james: Yes that's my recommendation
      [19:42] [Chair]Eddy: I'm OK with that
      [19:43] [Code_SB]james: We might then do a single week cycle for RC1 (so
      28 Apr for RC1 and 4 May for RC 2 )
      [19:43] [Code_SB]james: so the prod release on 11th May
      [19:44] [Chair]Eddy: unless issues are found of coarse
      [19:44] [Code_SB]james: Absolutely
      [19:44] [Chair]Eddy: sounds good to me
      [19:44] [Code_SB]james: We need to be comfortable with the issues
      remaining before we do the prod release
      [19:45] [Admin]Andrew: I have a related question
      [19:46] [Admin]Andrew: After we do the production release of 5.14 when
      will the core code switch to CDOM take place?
      [19:46] [Code_SB]james: Short answer - when it is ready
      [19:47] [Admin]Andrew: Fait enough. :)
      [19:47] [Admin]Andrew: fair
      [19:47] [Code_SB]james: Longer answer - we will need to have a code
      meeting to discuss that one - its a big step and we need all involved to
      be aware of what is changing and what will need to be worked on
      [19:49] [Chair]Eddy: Is there any objections to the recommendation of an
      additional beta?
      [19:49] [Code_SB]james: not here
      [19:49] [Arch_SB]thpr: not from me
      [19:49] [Admin]Andrew: none from me
      [19:49] [PR_SB]Maredudd: Not from me . . .
      [19:50] [PR_SB]Maredudd: Gives me two more weeks to work on GODs
      [19:50] [Code_SB]james: A May 11th release will still give us plenty of
      time before Gencon won't it?
      [19:50] [Chair]Eddy: OK, we'll aim for 5.13.14 on the 14th and we'll see
      if we can go RC next meeting
      [19:50] [Code_SB]james: Sounds good
      [19:50] [Chair]Eddy: Yeah, that should be more than enough
      [19:50] [PR_SB]Maredudd: Yes it will James. All of the CD production
      companies I reviewed had quick turna around as a standard feature . . .
      [19:50] [Code_SB]james: Nice
      [19:51] [PR_SB]Maredudd: Lomgest time was 13 days . . .
      [19:51] [Chair]Eddy: which is a nice segway to the next item: Gencon
      [19:52] [Code_SB]james: :)
      [19:52] [PR_SB]Maredudd: So, you want me to start?
      [19:53] [Chair]Eddy: looks like we won't have a partner
      [19:53] [PR_SB]Maredudd: Thats what it looks like.
      [19:53] [PR_SB]Maredudd: Booth registration is in. Now we wait to hear
      back from Gen Con on our booth number . . .
      [19:53] [Chair]Eddy: Anything specific we need to discuss? I don't think
      we need a full report of everything tonight
      [19:54] [PR_SB]Maredudd: Two items . . .
      [19:54] [PR_SB]Maredudd: Business Card vs Flyer . . .
      [19:54] [PR_SB]Maredudd: Tom recommended using a generic BCard and it
      was seconded by someone . . .
      [19:55] [PR_SB]Maredudd: Any thoughts?
      [19:55] [Arch_SB]thpr: Do we need to make that decision
      [19:55] [Arch_SB]thpr: ?
      [19:55] [Chair]Eddy: me :-)
      [19:55] [Chair]Eddy: no we do both
      [19:55] [Arch_SB]thpr: Yea - wait a month
      [19:55] [Arch_SB]thpr: let's have more time to figure out what our budget is
      [19:55] [Chair]Eddy: meantime we'll design both
      [19:55] [PR_SB]Maredudd: Right now our budget is $1655
      [19:55] [Arch_SB]thpr: yea
      [19:55] [Arch_SB]thpr: well, take out the booth
      [19:56] [Arch_SB]thpr: since we kinda did that already ;)
      [19:56] Fitzs: DO you want the watchers to chime in or wait till later
      [19:56] [PR_SB]Maredudd: With Booth and badges, it leaves just over $200
      [19:56] [Chair]Eddy: chime in Terry :-)
      [19:57] Fitzs: Do you want me to open the booth or close?
      [19:57] [PR_SB]Maredudd: er, just under $300 . . .
      [19:57] Fitzs: or just be there
      [19:57] [PR_SB]Maredudd: For now, just be there . . .:-)
      [19:57] [Chair]Eddy: we can probably work out the schedule closer to the
      show date
      [19:57] [PR_SB]Maredudd: Right.
      [19:58] Fitzs: My problem is the open/close requires a Exhibitor badge,
      and I have a DM's
      [19:58] Fitzs: Need to get that replaced
      [19:58] [OGL]Nylanfs: It will probably end up being covering lunchs and
      filling in for Eric when he's schmoozing publishers
      [19:59] [PR_SB]Maredudd: You can get it replaced when you show up to the
      con . . . The cost is the same . . .
      [19:59] Fitzs: Yes, but I'm demoing for Ad Astera
      [19:59] [PR_SB]Maredudd: As Eddy said, we'll work out the schedule as we
      get closer to the show.
      [19:59] [OGL]Nylanfs: Actually you have to pay for another badge and
      then get the original one reimbursed at least I did last year
      [20:00] [PR_SB]Maredudd: Thats what Gen Con told me, but you can do it
      right there.
      [20:00] Fitzs: Gen Con's getting back to me about that as their system
      apparently does like to issue two badges
      [20:00] [Chair]Eddy: Sounds good, I would not mind having an exhibitor badge
      [20:02] Fitzs: One comes with the table, additional at $65.00 trying to
      findout if its limited
      [20:03] [Arch_SB]thpr: Sounds to me like we should deal with that offline
      [20:03] [Chair]Eddy: agreed
      [20:03] jfrazierjr: unless anyone has any questions for me... I am out....
      [20:04] [Chair]Eddy: Thanks Joe,
      [20:04] [PR_SB]Maredudd: I've nothing else for now on Gen Con.
      [20:04] [Chair]Eddy: Thanks Eric
      [20:04] [Chair]Eddy: Things look very well in hand, I'm psyched
      [20:04] Fitzs: See ya Joe
      [20:05] [Chair]Eddy: OK the last agenda item was 3.) Yahoo file status
      (when should old files be purged)
      [20:05] *** jfrazierjr has signed off IRC ("Do fish get thirsty?").
      [20:06] [Code_SB]james: I'd start from a standard expiry period unless
      there was a specific need
      [20:06] [Admin]Andrew: Agreed
      [20:06] [Chair]Eddy: I guess we got some old files hanging around?
      [20:06] [Code_SB]james: However if we aren't running out of room it may
      not be too much of an issue
      [20:06] [Admin]Andrew: Yes
      [20:07] [Chair]Eddy: Yeah, I don't think we are (out of space that is)
      [20:07] [Admin]Andrew: July 7th 2002 old enough for you?
      [20:07] [Code_SB]james: :)
      [20:07] [Chair]Eddy: Once 5.14 is out we should probably do a good
      review of the status of what we've got in those file sections
      [20:08] [Admin]Andrew: And that was just a quick look....
      [20:08] [Chair]Eddy: he he, that's pretty old
      [20:08] [Admin]Andrew: It's an Armies of the Abyss, something we should
      probably pull due to Green Ronin's Permission status.
      [20:09] [Chair]Eddy: agreed
      [20:09] [Admin]Andrew: I have several 2002 - 2006 stuff as well...
      [20:09] [Arch_SB]thpr: Sounds to me like someone from, say, the Admin
      team, need to run through the list and make recommendations
      [20:10] [Chair]Eddy: good idea
      [20:10] [Admin]Andrew: Yeah, I can handle it... But I was looking for
      input from the Board for a general guideline on time frame... and should
      we try and add this into the data stuff?
      [20:10] [Arch_SB]thpr: "add this into the data stuff"?
      [20:11] [Code_SB]james: I'd say we should assess anything over two years old
      [20:11] [Admin]Andrew: Sorry wife is trying to talk to me....
      [20:12] [Admin]Andrew: Anything that is a partial set; or usable, should
      be evaluated for future inclusion into the PCGen repository. Granting we
      have the appropriate permissions from the publisher and it meets are
      Quality standards
      [20:14] [Code_SB]james: Yes that would be a worthwhile move - too easy
      to lose things in the file area
      [20:15] [Admin]Andrew: Another guideline... if a lst monkey corrects a
      work, should we delete the original piece to keep the extras to a minimum?
      [20:16] [Arch_SB]thpr: with data is there a reason we're using files
      rather than a branch in svn?
      [20:16] [Arch_SB]thpr: we wouldn't have discussions over changes &
      originals because we'd have the whole thing
      [20:16] [Admin]Andrew: The concern that a file once in svn cannot be
      deleted permanently
      [20:16] [Chair]Eddy: many data monkeys don't know SVN
      [20:17] [PR_SB]Maredudd: And it is only vary recent that we have used
      the notfordistribution folder on svn . . .
      [20:17] [Chair]Eddy: I like to move stuff into SVN whenever possible but
      it needs to be OK'd by PL first
      [20:17] [Chair]Eddy: Yeah, hopefully more folks can start using that
      [20:18] [OGL]Nylanfs: I've deleted files in the exp when I've done the
      OGLness and made corrections
      [20:18] [Chair]Eddy: That's fine Paul, since you know the new file has
      all the old one does
      [20:19] [Chair]Eddy: we need to be careful if we are not the person who
      created the new file
      [20:19] [Chair]Eddy: you need to verify the the two file are what you
      think they are
      [20:20] [Arch_SB]thpr: Sounds to me like we just need to go through
      everything regardless of date
      [20:20] [Arch_SB]thpr: maybe we need to do that over time if there are a
      lot of files
      [20:20] [Chair]Eddy: At any rate I'm not seeing a major problem here,
      just maintenance.
      [20:20] [Admin]Andrew: Yeah, I was, which is what brought up this topic...
      [20:21] [Admin]Andrew: OKay, well unless anything else is needed... I'd
      say that wraps up the topic for me... :)
      [20:21] Fitzs: Maybe post a warning on PcGen so the data monkeys that
      are interested can pull a copy for future work
      [20:22] [PR_SB]Maredudd: Thats a reasonable approch. A two week warning
      of impending doom for the file . . .
      [20:22] [Admin]Andrew: Sounds good... Remember I'm hitting all three
      [20:23] [Admin]Andrew: Exp though is a little different.
      [20:23] [Chair]Eddy: Yeah, that group is fairly well maintained
      [20:23] [Admin]Andrew: It's the staging ground for new data sets... but
      lst help and pcgen have
      [20:23] [Admin]Andrew: lots of old data
      [20:23] [Chair]Eddy: the other groups I can see how they would need to
      be cleaned out
      [20:24] [Chair]Eddy: OK, does anyone have any topics for open discussion?
      [20:24] [PR_SB]Maredudd: Not me . . .
      [20:24] [Arch_SB]thpr: nope
      [20:24] [Code_SB]james: no
      [20:25] [PR_SB]Maredudd: Except to say that the cheese finally came out
      right . . . :-)
      [20:25] [OGL]Nylanfs: Nope
      [20:25] [Admin]Andrew: Eric volunteered for job posting... :) otherwise
      I'm done
      [20:25] [OGL]Nylanfs: Yea! Bringing some to GenCon?
      [20:25] [PR_SB]Maredudd: I most certainly can . . . If they'll let me
      carry it on the ariplane . . .
      [20:25] [PR_SB]Maredudd: "Excuse me sir, but your Roqufort is ticking .
      . . "
      [20:26] [Admin]Andrew: Eddy I'd say that's a wrap!!!
      [20:26] Fitzs: FedX it to me and I'll drive it down
      [20:26] [Chair]Eddy: Sounds like it
      [20:26] [OGL]Nylanfs: BTW If anyone is interested in the Player's Guide
      to Oathbound I was finally able to snag a copy, email me if you want one
      [20:26] [PR_SB]Maredudd: Can do!
      [20:26] [Chair]Eddy: Thanks everyone *bangs gavel*

      ~ Andrew Maitland (LegacyKing)
      ~ Admin Silverback, PCGen Board of Directors
      ~ Data Gibbon, Tracker Gibbon, Docs Lemur
      "Quick-Silverback Tracker Monkey"
    Your message has been successfully submitted and would be delivered to recipients shortly.