 |
| |
| META TOPICPARENT | name="MIFOS" |
|---|
High priority projects | | |
See also | |
<
< | DesiredFeatures is a list of features we want to build into the product (as distinct to this page, which is more about code improvements and other non-feature oriented improvements).
The RoadMap pages have a larger list, probably prioritized differently.
Not sure which list this should go on, but ReportsFunctionality has a todo list (in the James Daily email of 29 Nov 2006 linked at the bottom of the page). There's also the RandomTodos2007. | >
> | RoadMap is a list of features we want to build into the product (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). | | | KnownIssues (which aren't particularly separated into technical improvements versus features) |
| |
| META TOPICPARENT | name="MIFOS" |
|---|
High priority projects | | | The RoadMap pages have a larger list, probably prioritized differently. | |
<
< | Not sure which list this should go on, but ReportsFunctionality has a todo list (in the James Daily email of 29 Nov 2006 linked at the bottom of the page). | >
> | Not sure which list this should go on, but ReportsFunctionality has a todo list (in the James Daily email of 29 Nov 2006 linked at the bottom of the page). There's also the RandomTodos2007. | | | KnownIssues (which aren't particularly separated into technical improvements versus features) |
| |
| META TOPICPARENT | name="MIFOS" |
|---|
High priority projects | | | Infrastructure for cruise control, subversion, etc. Includes to-do items in this area. | |
>
> | MifosPatchQueue lists patches that have been submitted and are waiting for integration and/or feedback. |
|
<<O>> Difference Topic
TechnicalTodo
(8 - 12 Jul 2007 - Main.jkingdon)
|
| |
| META TOPICPARENT | name="MIFOS" |
|---|
High priority projects | | | | |
<
< |
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting, and gets us closer to our HtmlStandards
| >
> |
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting, and gets us closer to our HtmlStandards. See OfficeListTag for an example.
| | |
- Build a spidering tool that renders each page in MIFOS and follows links (this should find broken links, blank pages and system exceptions). It should be something which cruise control can run.
- DoubleVersusMoney
- NukeConversionJs
|
|
<<O>> Difference Topic
TechnicalTodo
(7 - 23 Jun 2007 - Main.jkingdon)
|
| |
| META TOPICPARENT | name="MIFOS" |
|---|
High priority projects | |
<
< | The following are intended to be a list of the highest priority technical projects in MIFOS, but feel free to pick something else which strikes your fancy, and/or ask on the ListServ whether a particular idea seems helpful/important. | >
> | Here are some of the larger and/or higher priority technical projects: | | | | |
>
> |
Possible volunteer projects
Some of the following are perhaps smaller than the above or easier to get started on. However, volunteers should feel free to work on one of the above, pick something else which strikes your fancy, and/or ask on the ListServ whether a particular idea seems helpful/important. | | | | |
<
< |
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
| | |
- InMemoryDatabase
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting, and gets us closer to our HtmlStandards
- Build a spidering tool that renders each page in MIFOS and follows links (this should find broken links, blank pages and system exceptions). It should be something which cruise control can run.
|
|
<<O>> Difference Topic
TechnicalTodo
(6 - 24 Apr 2007 - Main.jkingdon)
|
| |
| META TOPICPARENT | name="MIFOS" |
|---|
High priority projects
The following are intended to be a list of the highest priority technical projects in MIFOS, but feel free to pick something else which strikes your fancy, and/or ask on the ListServ whether a particular idea seems helpful/important. | |
>
> | | | |
- Run findbugs and send in fixes to those warnings via the CodeSubmissionProcess (see MifosFindbugsStatus for more details)
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
- InMemoryDatabase
|
|
<<O>> Difference Topic
TechnicalTodo
(5 - 06 Dec 2006 - Main.jkingdon)
|
| |
| META TOPICPARENT | name="MIFOS" |
|---|
| |
<
< |
- Run findbugs and send in fixes to those warnings via the CodeSubmissionProcess
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
| >
> | High priority projects
The following are intended to be a list of the highest priority technical projects in MIFOS, but feel free to pick something else which strikes your fancy, and/or ask on the ListServ whether a particular idea seems helpful/important.
- Run findbugs and send in fixes to those warnings via the CodeSubmissionProcess (see MifosFindbugsStatus for more details)
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
| | | | |
<
< |
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting.
| >
> |
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting, and gets us closer to our HtmlStandards
| | |
- Build a spidering tool that renders each page in MIFOS and follows links (this should find broken links, blank pages and system exceptions). It should be something which cruise control can run.
- DoubleVersusMoney
| |
>
> | | | | | |
<
< | Also see DesiredFeatures for a list of features we want to build into the product (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). | >
> | See also
DesiredFeatures is a list of features we want to build into the product (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). | | | The RoadMap pages have a larger list, probably prioritized differently. | |
>
> | Not sure which list this should go on, but ReportsFunctionality has a todo list (in the James Daily email of 29 Nov 2006 linked at the bottom of the page).
KnownIssues (which aren't particularly separated into technical improvements versus features)
Infrastructure for cruise control, subversion, etc. Includes to-do items in this area. |
|
<<O>> Difference Topic
TechnicalTodo
(4 - 23 Oct 2006 - Main.jkingdon)
|
| |
| META TOPICPARENT | name="MIFOS" |
|---|
- Run findbugs and send in fixes to those warnings via the CodeSubmissionProcess
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
| |
<
< |
- In-memory database. We see this as a way to speed up the tests, (eventually) reduce the ability of one test to affect another, and (someday) to make it possible to run the tests without installing MySQL. Go to the DatabaseSetup class, edit testAgainstMysql to be false, and try some of the tests. If you're lucky, you'll get a fairly comprehensible exception from within Mayfly saying basically "mayfly doesn't have this feature yet". If not, you'll get a mysterious NullPointerException or some such. If you aren't clear on what is going on here, probably best to ask on the ListServ (the description here is far from complete).
| >
> | | | |
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting.
- Build a spidering tool that renders each page in MIFOS and follows links (this should find broken links, blank pages and system exceptions). It should be something which cruise control can run.
| |
>
> | | | | Also see DesiredFeatures for a list of features we want to build into the product (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). | |
>
> | The RoadMap pages have a larger list, probably prioritized differently. |
|
<<O>> Difference Topic
TechnicalTodo
(3 - 23 Oct 2006 - Main.jkingdon)
|
| |
| META TOPICPARENT | name="MIFOS" |
|---|
- Run findbugs and send in fixes to those warnings via the CodeSubmissionProcess
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
- In-memory database. We see this as a way to speed up the tests, (eventually) reduce the ability of one test to affect another, and (someday) to make it possible to run the tests without installing MySQL. Go to the DatabaseSetup class, edit testAgainstMysql to be false, and try some of the tests. If you're lucky, you'll get a fairly comprehensible exception from within Mayfly saying basically "mayfly doesn't have this feature yet". If not, you'll get a mysterious NullPointerException or some such. If you aren't clear on what is going on here, probably best to ask on the ListServ (the description here is far from complete).
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting.
| |
<
< |
- Build a spidering tool that runs through the mifos testserver to find broken links, blank pages and system exceptions.
| >
> |
- Build a spidering tool that renders each page in MIFOS and follows links (this should find broken links, blank pages and system exceptions). It should be something which cruise control can run.
| | | Also see DesiredFeatures for a list of features we want to build into the product (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). |
|
<<O>> Difference Topic
TechnicalTodo
(2 - 20 Oct 2006 - Main.emilytucker)
|
| |
| META TOPICPARENT | name="MIFOS" |
|---|
- Run findbugs and send in fixes to those warnings via the CodeSubmissionProcess
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
- In-memory database. We see this as a way to speed up the tests, (eventually) reduce the ability of one test to affect another, and (someday) to make it possible to run the tests without installing MySQL. Go to the DatabaseSetup class, edit testAgainstMysql to be false, and try some of the tests. If you're lucky, you'll get a fairly comprehensible exception from within Mayfly saying basically "mayfly doesn't have this feature yet". If not, you'll get a mysterious NullPointerException or some such. If you aren't clear on what is going on here, probably best to ask on the ListServ (the description here is far from complete).
| |
>
> |
- Change all the HTML rendering code in the *Tag classes to call XmlBuilder. This fixes security holes with quoting.
- Build a spidering tool that runs through the mifos testserver to find broken links, blank pages and system exceptions.
| | | | |
<
< | Also see FunctionalSpecifications for desired features (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). | >
> | Also see DesiredFeatures for a list of features we want to build into the product (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). | | | |
|
<<O>> Difference Topic
TechnicalTodo
(1 - 20 Oct 2006 - Main.jkingdon)
|
|
>
> |
| META TOPICPARENT | name="MIFOS" |
|---|
- Run findbugs and send in fixes to those warnings via the CodeSubmissionProcess
- Changes to build.xml to run findbugs during the build (including Cruise Control). For this to be most useful, it would be pass/fail and currently passing, rather than a long list that someone goes through manually (findbugs filters are one way to do this). We probably don't want everyone to have to install findbugs (so can it be checked in to svn? is there another solution?)
- In-memory database. We see this as a way to speed up the tests, (eventually) reduce the ability of one test to affect another, and (someday) to make it possible to run the tests without installing MySQL. Go to the DatabaseSetup class, edit testAgainstMysql to be false, and try some of the tests. If you're lucky, you'll get a fairly comprehensible exception from within Mayfly saying basically "mayfly doesn't have this feature yet". If not, you'll get a mysterious NullPointerException or some such. If you aren't clear on what is going on here, probably best to ask on the ListServ (the description here is far from complete).
Also see FunctionalSpecifications for desired features (as distinct to this page, which is more about code improvements and other non-feature oriented improvements). |
|