View source for Community Resources

From Openmoko

Jump to: navigation, search

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Administrators.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Template used on this page:

Return to Community Resources.

Retrieved from "http://wiki.openmoko.org/wiki/Community_Resources"
Personal tools

Mailing lists

There are a number of development related mailinglsts at both lists.internal.openmoko.org and lists.openmoko.org.

coreteam@lists.internal.openmoko.org

Product Management and Consulting only, for strategic discussions. Better known under its alias coreteam@openmoko.org

neo1973-devel@lists.internal.openmoko.org

This is the main internal development list about anything regarding the Neo1973 hardware, the software development for it, etc.

http://lists.internal.openmoko.org/cgi-bin/mailman/listinfo/neo1973-devel

framework-devel@lists.openmoko.org

This is a (soon completely public) mailinglist on the OpenMoko Framework

http://lists.openmoko.org/cgi-bin/mailman/listinfo/framework-devel

distro-devel@lists.openmoko.org

This is a (soon completely public) mailinglist on the OpenMoko Distribution. Here issues such as ipk packaging related and root fs image related topics should be discussed. Also, questions regarding the OpenEmbedded based build process go here.

http://lists.openmoko.org/cgi-bin/mailman/listinfo/distro-devel

devel@lists.internal.openmoko.org

Old developer list, became an alias for neo1973-devel.

buglog@lists.openmoko.org

A read-only list where every status update to a bug (bugzilla entry) will get posted. Nice to keep updated on the bugsquashing progress

commitlog@lists.openmoko.org

A read-only list where every source code change (commit to the subversion server) gets posted. Nice to keep posted on development progress.

Wiki

This Wiki. You're already in it, if you're reading this.

Bugzilla

Our bug tracking system, available at bugzilla.gta01.

SVN

There is a Subversion server available at svn.gta01.hmw-consulting.de.

Read-only access is provided via http://svn.gta01.hmw-consulting.de/. You should not normally use this URL, it's mainly for later public access after product release.

Read-write access for developers is provided via https://svn.gta01.hmw-consulting.de:2342

Web access for occasional browsing is available via SvnWeb

If you need help, please read more about Using Subversion.

SVN Tree Layout

The Subversion (svn) tree is laid out as follows:

  • trunk (main branch, similar to CVS "HEAD")
    • src (program source code)
      • host (programs that work on the host PC)
        • sjf2410-linux
        • ...
      • target (programs that work on the target device)
        • dialer
        • package_manager
        • ...
    • doc (Documentation)
      • ...
  • branches (branches, created by lead developers if required)
    • src
      • host
        • ...
      • target
        • ...
  • developers (private/experimental branches, created by individual developers)
    • laforge
      • ...
    • sean
    • mickey
      • ...
    • ...
  • releases (official 'releases' of code in 'trunk' or 'branches')
    • src
      • host
        • ...
      • target
        • ...