.
FRDCSA | internal codebases | FieldGoal

FieldGoal Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

Capabilities

• fieldgoal should support group intentions.
• Could add that as a module to score/problemspace/fieldgoal or something.
• Write subsystem of audience (or maybe fieldgoal or boss) to catch up with other developers
• Maybe its getting time to get field goal working. Now obviously, fieldgoal depends on pse.
• The webpage generation can be used for job-search, for machiavelli, for fieldgoal and posi, etc.
• study/fieldgoal/EM must guarantee familiarity with various areas.
• Obviously, use FOAF for fieldgoal, etc, collaboration
• fieldgoal should have asset management readings as a reference
• Whenever a task presented by fieldgoal is rejected, a reason for this rejection should be sought in order to improve the model. also clarify whether it was a temporary refusal, permanent, etc.
• By textual analysis of what clear and now audience are storing, it should be easily possible to query the system (running the question askers for each person's data, perhaps dynamically, or somehow) what they should know and behave accordingly. Would help to have more content area specifications as per fieldgoal
• fieldgoal should determine whether the people like video games and if they do, get rid of them.
• Have fieldgoal print out a schedule of when everyone is going to get here, etc. Another thing to do is start migrating the POSIThon functionaity to programming-marathon, maybe rename this POSITHON
• Maybe an alternative name for fieldgoal is bazaar
• obviously BDI is useful for fieldgoal