From FusionForge Wiki
Revision as of 16:15, 19 May 2009 by Livewire74 (talk | contribs) (Topic list update)

Jump to: navigation, search


Install without DNS & vhosts (David Partain)

I work in an environment where I cannot change DNS in any way. As such, virtual hosts with project.company.com are not an option. I'd like there to be a way to decide during installation whether you'll use subdomains or not. If not, the installation will then configure things appropriately. That means, as an example, that sys_default_domain, sys_scm_host, sys_ldap_host, etc in local.inc will all be the same, that "Project Home Page" will have to be something other than project.company.com (e.g., company.com/projects/project).

→ This is the "URL relocation" mentioned in the roadmap; the goal is to be able to run your forge as www.company.com/tools/forge/ and have non-web tools working too.

Web pages hosting (David Partain)

I'd really like to see a plain ol' Web area that is under the same access control as the rest of the project information, requires login if the site does, etc. Of course, a good wiki plugin will help here.

→ A solution that I use is to provide webdav directory, so projects have their own web space and can work on documents.

Plugin manager improvements (Alain Peyrat)

  • The 'Run Init Script' is confusing users. If the init is needed, then why this option ?
  • Add a description to explain the plugin, a version number for upgrading.
  • Add a dependency (example: to enable only svn2tracker if scmsvn is active).
  • Add a 'enabled by default' option.

Plugin to display a banner on the whole site (Alain Peyrat)

To display a maintenance banner when an operation will be performed.

Roadmap/Timeline tool (Alain Peyrat)

To have a simple view of pending bugs, tasks, features. An example is: http://trac.edgewall.org/roadmap

Logging Framework (Muris Ahmovic)

The needs to use or develop a logging framework for fusionforge would help during development and users could easier report bugs

It should be well described and used by the plugins.

Another good convention (from my expirience) would be to have Entry/Leaving DEBUG log entries for EVERY function.

Example: "Entering - doSomeMagic($staff)"

The following features are needed:

  • Log Levels (ERROR, WARN, INFO, DEBUG, etc.)
  • Writing to stream/file (append)
  • Log Rotation
  • Setting the log level global (For example: During DEV the log level should remain debug/trace and for the production use erorr)

The only usable framework is Zend Framework -> Zend_Log: http://framework.zend.com/manual/en/zend.log.html

There is unfortunately no release yet for log4php http://incubator.apache.org/log4php/qsg.html

→ To get fine logging (like entry/leaving), xdebug can be used quite easily.

IDE integration (Olivier Meunier)

  • Provide a connector to use fusionforge from Eclipse via Mylyn, using the SOAP interface. The Web Templates Connector is not easily (?) usable.
  • Provide a Visual Studio plugin to access tasks in fusionforge projects from the task view in Visual Studio.

I noticed one of our subscribers is linked with [1] see also [2], maybe useful for Mylyn (Note de Christian Bayle)

=> Interested in Mylyn integration, checkout the dedicated project Mylyn connector

Separate contents from presentation

It would make life much easier for graphic designers looking to customise the appearance of their forge if the display stuff were not so tightly bound with the code. Ideally, that would mean switching to a template system (Smarty or Flexy maybe?).

Separate translations files could be necessary too: one for the fusionForge functionalities, one for the rest of the purpose. the use of widgets (like projects list...) could be useful too (related translation could help to separate functionnalities and purpose translations)

More RSS feeds

  • Trackers
  • Project managers
  • Also an aggregated feed for everything related to one project

Processors list update

it could be useful to update processor classes list by default:

  • AMD64
  • ARM Families
  • ...

Topic list update

it could be useful to update topic items list by default:

  • Control Version::GIT
  • Operating System::Windows::Vista, Seven, 2008...

New categories could be added like:

  • Terminal Classes::Laptop, Desktop, Embedded::Mobile, Smartphone, Pdas...
  • Mobile standards::GSM, GPRS, UMTS with sub standards...

And so on...

Organising their translations with the inner DB (not with po files) could be interresting too

Back to FusionForge