From Navit's Wiki
Jump to: navigation, search

Navit dev process.svg


If you look at user:Usul/Disburden cp15, it's recommend to modularize our dev workflow as well. Please keep in mind, that this will be a process of months/years and not weeks!

  • be indipendend from providers ->self hosted
  • be able to replace single components without needing to switch everything -> single components
    • is currently exactly the opposite (people expect we use the internal bugtracker, mailinglist, ... there, even if we currently use only the SVN)
  • but portals enable the components to work closely together
  • Components should offer PostgreSQL backend, SSO via custom OpenID (our wiki)


  • use a DVCS -> offline commits, support staging, allow sharing unstable code
  • GIT very popular, widely supported
  • git-flow enables easy seperation into 5 streams (stable, dev, feature, hotfix)


  • is it only on translating, or does I18n cover here further resources?
  • Translatewiki has already some OSM context

code review[edit]

We need to review code before submitting it to our mainline dev branch. This ensures that formating, coding style and docs relect our standards and that it will be possible to build the branch

  • normalize code quality before merging to mainline
  • minimize load for the reviewer (make it confortable, fast communication, ...)
  • Gerrit
  • GITlab
  • Phabricator

issue tracking[edit]

  • our trac is spammend and unamanage
  • trac itself isn't very intuitive, focused
    • roadmap planing isn't well embedded

build server[edit]

Currently we use our own solution

  • package building
  • no support for multiple dev flows
  • no triggering for post actions (tests, benchmarking, ...)
    • ctest