.
FRDCSA | internal codebases | FWeb
Homepage

[Project image]
FWeb

Architecture Diagram: GIF

Jump to: Project Description | Parent Description | Capabilities

Project Description

The FRDCSA project website has unique needs and therefore we have written its own CMS, which provides users with a custom view of the FRDCSA content. Currently, it provides references to most focal areas of development: theory, projects, internal and external codebases, and packages.

Future development will include providing much more dynamic content through the use of an FLOSS CMS, or possibly Gforge. We want to compile informative reports like most complex project, etc, based on project metrics; have "public high level goals" stated clearly in front (based on output from pse, Machiavelli); put manuals in the papers sections of the project homepages; provide a neat interface to kbfs and clear; comment on the state of artifacts: rough draft, nearly complete; and generally speaking provide any actual files that are copied over should have metadata options around their links.

Capabilities

  • Rewrite fweb using catalyst, make the site dynamic.
  • Finish getting Org::FRDCSA modules out of autodia output with fweb.
  • Add to the FRDCSA.xml the dependency on autodia for fweb
  • Update fweb to include links to reasonbase's FRDCSA repo
  • Create a publications section of fweb, from coauthor.
  • Keep some database of solutions. I guess this is what architect does? But we need something more general. Example, if I can't program, and need help getting started, a good thing to do is to rebuild the fweb stuff.
  • fweb capability listings (boss too) should be organized based on importance.
  • fweb in dynamic content generation should do coloring dynamic to user.
  • diamond demos should be accessible from fweb.
  • fweb should be more differential.
  • fweb should detect archaic system names (like Predator)
  • As well as the various fweb classes.
  • Make sure fweb intropage has project statistics on it.
  • On fweb, that is.
  • Replace fweb with a ruby on rails database interface...
  • Ultimately change fweb to a dynamic web application (ruby?)
  • fweb should detect archaic system names (like Predator)
  • fweb should be more differential.
  • Why is fweb running twice?
  • Get timing information on fweb.
  • Later to make the fweb service better, we can have it realize just the words in a sentence, so that it is invariant to reformattings.
  • fweb should include links to projects like "vampire" using markup
  • When displayed with fweb.
  • Setup a version sort for fweb, or in general a function to sort software, since I notice that roadnav-0.12.0 is coming in front of roadnav-0.4.0
  • Use the template system on fweb to generate better linked documentation.
  • Fix fweb which just screwed up my webpage.
  • fweb should be more stable.
  • fweb should use a code difference metric to prevent building a digram for code that has undergone practically no change.
  • Alter fweb to display what has been accomplished.
  • Increase the fweb decay halflife.
  • fweb in dynamic content generation should do coloring dynamic to user.
  • diamond demos should be accessible from fweb.
  • Create a publications section of fweb, from coauthor.
  • fweb capability listings (boss too) should be organized based on importance.
  • /var/lib/myfrdcsa/codebases/internal/boss/scripts/stat.pl can be used in fweb.
  • Fix all the contact information in fweb and do a rebuild.
  • before fweb is rerun, must recover the information on each system.
  • Rewrite fweb using proper URL objects, so that all the conversions becomes easier.
  • It would be at least possible, perhaps not desirable, to actually use fweb project pages to display output information - for instance, pse, could display public goals through fweb.
  • Add a notes section to each fweb class
  • fweb should have the ability to rebuild specific projects only
  • To aid in debugging fweb, could add debug mode where it only does three of each project.
  • Use DrJones to extract "how old" fweb stuff
  • boss and fweb should use http://readyset.tigris.org/
  • fweb can keep a database of which sentences were entered when for which documents.
  • Add search this site with google to fweb.
  • With fweb, be sure to sort projects by case-insensitive alphabetic order, add borders to wikilike name substitutions, and add coloration based on project activity or perhaps size.
  • use the output of ls on /var/lib/myfrdcsa/sandbox and /var/lib/myfrdcsa/codebases/external and internal as an "overview" of the FRDCSA project on fweb.
  • fweb must see ontowebber


This page is part of the FWeb package.
Last updated Sat Oct 26 16:53:24 EDT 2019 .