0) Meeting Format

• Separating Science from Code?
  • Have a science meeting that is separate from 'code' meeting
  • No mention of code or 'code issue' etc… at Science meeting
  • Create tickets for 'problems' for code meetings and we can discuss tickets then
  • External users should use ticketing system as well

• Need "czars" in charge of different group activities
  • Documentation
    • Make sure documentation is complete and up to date with code
    • Delegate documentation tasks to appropriate folks
  • Code development
    • Keeps track of ongoing development projects and coordinates integration
    • Tracks progress of next release etc…
  • Grants/Proposals
    • Keep track of Teragrid proposal deadlines etc…
    • Keep track of Funding proposal deadlines etc…
    • Monitor teragrid resource usage
  • Scientific Meetings
    • Watch out for scientific meetings and application deadlines
  • Testing
    • Ensuring that regular testing is done
    • Coordinate with the development czar to oversee the development of new testing modules to test new development
  • Debugging
    • Monitor help tickets and assigning and overseeing the resolution of the tickets
  • Outreach
    • Anticipate and oversee new outreach projects
  • New Users
    • Keeping track of external users and their progress with the code.
    • Periodically reach out to external users
    • Find new avenues to increase visibility of AstroBEAR within astro community
    • Oversee publication of materials to share at conferences etc… (powerpoint slides, business cards?)
  • In-group Education
    • Organize various internal presentations

1) Science:

1. What subjects/projects are we taking on this year
2. What new capabilities will it require (Erica: subgrid model for feedback?)

Who	Project title	code devel
Erica	MHD colliding flows
Erica	outflow feedback	subgrid model for feedback

2) Code Development

1. AstroBEAR 3.0
2. Lite version etc

3) New Users/Support

1. Who do we have
2. Who do we want
3. How do we support them (ideas: no access to ticketing system?, provide a forum for extended users that we can occasionally browse and provide advice/helpful tips?)

4) Documentation

1. Moving to AB 3.0 (ideas: improved documentation on bluestreak and other pages, shortened intro material, improved overall structure of wiki?, updating our emailing/google groups lists)

5) Computing Resources/Storage

1. What do we have, what do we need

System	Procs	Memory	Storage	Used	Free	Notes ?
bamboo	16 @ 2.4 GHz	24 Gb	13 Tb	9.0 Tb	2.9 Tb	Erica
grass	8 @ 2.5 Ghz	16 Gb	5.5 Tb	3.4 Tb	1.8 Tb	Eddie
alfalfa	16 @ 2.4 Ghz	24 Gb	5.3 Tb	4.9 Tb	.13 Tb	In PAS
clover	2 @ 2.2 Ghz	16 Gb	11 Tb	9.8 Tb	.45 Tb
botwin	4 @ 2.6 Ghz	4 Gb	.89 Tb	.77 Tb	.07 Tb	hosting wiki/repos
bigdump			3.6 Tb	3.3 Tb	.11 Tb	Attached to grass - raided?
scratchdisk			.14 Tb	0.1 Tb	.13 Tb	Attached to bamboo - raided?
afrank nodes	32 @ 2.27 Ghz	13 Gb
afrank nodes	32 @ 2.33 Ghz	9 Gb
bluehive			.2 Tb/1 Tb
bluestreak			1 Tb/user
bluehive II

7) Grants

1. what do need to go after?

8) Meetings

1. Finding them/deciding which to attend

9) Office Space (4 free desks in 375 if Ruka/Erini no longer in group, 2 free computers — clover and the one on Ruka's old desk?)