Advertisement
Guest User

all-hands Kokua meeting

a guest
Jan 29th, 2012
88
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.18 KB | None | 0 0
  1. # Irregardless of anything else, do we as a team want to continue work and are there enough of us with enough time available to work on a viewer?
  2. ## If the answer is no, do we want to work on something else, such as a TPV code repository like Boroondas suggested?
  3. ## Assuming the answer is yes, do we want to start fresh or continue on the old code base?
  4. # Firestorm: How closely do we want to work with them, or even for them etc?
  5. # Git or Hg: Let's pick one and stick with it. So which shall it be? (Git is familiar to many, but Hg is used by LL and it's easier to import LL patches to Hg)?
  6. # Any new client will use the Kokua name. Should the project name change to Kokua as well or stay Imprudence?
  7. # Should a fresh start for the project mean a fresh start for the site as well? Perhaps an integration of the Blog and Forum using the new BBPress plugin. Do we want to stick with MediaWiki and Redmine or switch to something else? Further do we need to keep all the ancillary sites like the Q&A site or focus on simplifying our web presence?
  8. # What focus should the project take, features or stability? Second Life first and foremost or OpenSim/Aurora?
  9. # What should the first thing people see when they load up the viewer be? An explanation of the various alternative grids and how to access them (Many TPV users never connect to an OpenSim grid). The site blog, or a simple tutorial section on the blog? What about a grid picker, and should there be a default grid and thus it's landing page showing upon first launching the program (And changed to last used upon subsequent launchings)?
  10. # What platforms do we want to support? There is no longer a Mac developer, and 64 bit is becoming more mainstream. Should we support Linux and Windows 32bit initially, or try to do 32bit and 64bit on some of the platforms?
  11. # User statistics: Are there any we can get from LL? If not, can we create an opt-in within the client for sending hardware stats such as CPU, RAM, OS etc? Would this help us in better developing the client for our audience?
  12. # Future weekly meetings: Do we wish to reschedule them or is Wednesday's at 20:00 working out for everyone?
  13. # How do we inform the public about what we have decided here today?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement