Home       Goals       Download       Documentation       Support Us       Development       Job Openings       Webstore       Patrons       Contact us / Enlist      

 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

summary_meeting_march_30_2005 [2012/03/30 01:33] (current)
Line 1: Line 1:
 +====== Summary of meeting march 30 - 2005 ======
 +
 +a) Approval of last weeks writeup - each participant gives his / her say and is allowed to comment if he / she feels there are misenterpretations or other discreppancies in the writeup, or if something is amiss.
 +
 +b) Follow Up - We look at the assignments undertaken at the last meeting. Have goals been met? If not then why. Goals not met are moved to e) on the assignment list for the upcoming week.
 +
 +On the agenda last week - the source for Little-T is it ready, is it online? If No then why not?
 +
 +The Roadmap is discussed on the regular agenda as it is a work in progress.
 +
 +c) Agenda - The agenda consists of points that participants want to discuss and have an opinion about which can be expressed in the collaboration wiki and discussed there so that the actual processing of the particular subject goes as smoothly as possible during the meeting itself.
 +
 +Our roadmap - what is the status
 +
 +Our site - what is the status
 +
 +Our todo and done lists - what is the status and how are they being maintained/used.
 +
 +The work process are we proceeding in the correct manner?
 +
 + Chief programmer:
 + we are in trouble with for example the roadmap, for it to work I
 + think we must imagin that the roadmap is not only future plans,
 + but also a table of contens to what is going on, and have been done
 + to put it short we need to bind the wiki together in a more struktured
 + way, lets say:
 +
 + the Team no 1. page is like an index of pages
 + the Roadmap is like a past/present/future table of contens
 + the meeting pages, are sort of the place to put new ideas.
 +     unlike the todo list, after a meeting something get transfered
 +     there (unless exeptions are made on the basis of phone, email,
 +     etc.)
 +
 +PM: I disagree with your assertions on the todo list - the todo list must be freely accessible to team members as needed. Something may arise unforseen and waiting a week for something to be added to the list is not adviseable, it will slow down the development process.
 +
 +The way to go IMHO is to implement a subdivision of the todo list as well as a priority system as mentioned further below. That way it will be easy to see what needs to be done and what doesn't. I believe the wiki has a system for adding color etc to text so that it is clear to see what is what. Possibly in the long run we should simply have an extra headline in color in case we work with people with colorblindness etc.
 +
 +
 +Put it like this: the meeting pages are the free forum to raise
 +new idea and discussions, rest of the pages must be in total
 +sync and interconnected or else there is no use for it, unless
 +to store oposing views & ideas.
 +
 +PM: About the RoadMap I think you are correctly stating that it is a mesh of present and future, past I wouldn't say as the roadmap should only envision the present and next steps. The done list presents the completed steps.
 +
 +With regard to the roadmaps I'd like to propose we install the following reasoning in our list.
 +
 +
 +1=A$=RED items are targetted for the next release. 
 +input funktión
 +2=B$=GREEN items are stuff
 +that needs to be done, but aren't urgent. 
 +USB support
 +3=C$=BLUE items are things that
 +would be nice to have, er, someday. 
 +Input frá dataglove
 +D$=WHITE is where items that have been done
 +are put - this section is cleared when we release.
 +
 +We could do this on our todo list as well.
 +
 +Skriva tal definitión á fyrstu sidu i wiki
 +
 +Furthermore the todo list has to be subdivided into sections.
 +I propose the following sections:
 +
 +General: - The place we put stuff not fitting a particular category Assorted/Miscellaneous V
 +Site: - The place for all things related to site development
 +Programming: - The place for all things related to software development - undirdeilt The XebLibrary og div progs V
 +PR: - The place for things related to increased exposure
 +Financial: - The place for things related to economics and ways to increase income.
 +
 +
 +Sponsorship offers:
 +When we approach an equipment vendor for a hardware sponsorship - how about offering a minimum of one year exposure to the sponsor but extending the exposure for as long as the equipment is in use for development work - We could mention that the - 80686 of yours is still in use. meaning there's value for money. 
 +
 +We could then on our pages indicate the following:
 +Development Equipment donated by... and then a list of sponsors discretely placed on all pages with links to the sponsors. V + vit eru equip sponsorar. Telefon Andy - Broadband VoIP - Eg Broadband telephony - Porto/Office supplies. E.Petersen B.Petersen + Lond. Takk fyri support til Johnsen International + Sølystgade Kiosk. One4Charity.Com
 +
 +The more sponsors more credibility.
 +
 +Chief programmer:
 +The more sponsors more credibility. Yes...but the more sponsors lesser space for the big fish, this idea is not new...only this time its just called equipment sponsors instead of small sponsors, Im not dead against it, just very skeptical becuase it feels like we wil break coherency in price policies between big and small sponsors
 +Dunno if we could do something like..this piece of software was produced on/with blabla software/hardware platform?
 +
 +
 +d) Miscellaneous - When we have reached a consensus on points a to c we proceed to discussing miscellaneous matters. Anything project related goes here and matters need no be posted beforehand.
 +
 +just and extent of some todo list comment:
 +------------------------------------------
 + 1) hevdi tad ikki veri snildast at
 + default radio but var Other
 +
 +      Chief P: Absolutly Should be other - V
 +------------------------------------------
 +PDF's
 +Ger studio/voice pdf til DK - FO - UK - NL - F - S - D - Is - I - Porto, upload Gjøgnumgang og censurera contact info frá endorsements upload og 
 +lacera appropriate links í do006.html T-Board the Virtual Keyboard manual Ger image compilation til photographer og voiceartist pdf's  Ger photographers pdf upload validate links.
 +
 +Chief P: WHY?...we used a lot of time making our own viewer
 +It is fine to have tings in pdf, but just at good to
 +alongside also distrbute in our own format, that is more powerfuld
 +as we control features.
 +------------------------------------------
 +While on the point of our own viewer etc. I need more info on the Linux "Click & Play Installer" well I looked at autopackager, its from a users point of view kind of ok, and might work for our programs if we just can confirm that they are linked staticaly as you running linux program compiled on my machine indicates, but we dont know if XBasic calls some general linux libs.
 +
 +Evt. heldur gera tad í HTML
 +
 +http://zero-install.sourceforge.net/ is another VERY! alternativ installer, take a peek.
 +
 +Is there a manual on using the viewer? Does the viewer display images - how is it possible to format pages. 
 +
 +PRO for using the PDF is that it is platform independant and people need not install anything - hence the fear of viruses etc is gone. *I have personally refrained from reading hundreds of e-books etc. because they were in exe format and hence made me uncertain if they contained potential malware etc.
 +
 +e) Assignments - This is a list of assignments for each team member. The assignments are handed out during the discussion of points a - d and once they are written up, each team member verifies the assignments he / she has received.
 +
 +Senda bugreport til B
 +
 +f) Should the next meeting follow the standard structure or do we need to impose an alternative meeting structure.
 +
  
summary_meeting_march_30_2005.txt · Last modified: 2012/03/30 01:33 (external edit)
 
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki



The contents of this site, i.e. texts, programs and images, but not limited to these, belongs to their respective owners and are protected under international copyright treaties according to individual licensing.

Please make sure you familiarize yourself with the appropriate permissions / licenses and follow these individually before using anything you find on this site.

The Global Ability Initiative is a Non Profit venture dedicated to the development of gratis, open source software for the disabled, the sick and the needy - We aim to provide assistive software to a wide variety of people, suffering for example from Aphasia, MS, ALS, Cerebral Palsy and other disabilities as well as pushing initiatives in the field of ECG monitoring.

With reservation for changes and errors.