Community Resources

From Openmoko

Revision as of 23:31, 9 February 2007 by HaraldWelte (Talk | contribs)

Jump to: navigation, search

Contents

Public Resources

All resources listed here are available to the general public. Everyone is invited to participate.

Mailing Lists

There are a number of development related mailinglsts at http://lists.openmoko.org/

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 bug squashing progress

http://lists.openmoko.org/mailman/listinfo/buglog

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.

http://lists.openmoko.org/mailman/listinfo/commitlog

community@lists.openmoko.org

This is a public mailinglist for discussion of our user + developer community out there

http://lists.openmoko.org/mailman/listinfo/community

openmoko-devel@lists.openmoko.org

This is a public mailinglist for discussion of developers who want to write code for the Neo1973

http://lists.openmoko.org/mailman/listinfo/openmoko-devel

framework-devel@lists.openmoko.org

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

http://lists.openmoko.org/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/mailman/listinfo/distro-devel

Wiki

This Wiki is our public wiki, http://wiki.openmoko.org/. You're already in it, if you're reading this.

Bugzilla

Our bug tracking system for software issues (which will become public at product release time) is available at http://bugzilla.openmoko.org/

IRC

There's a #openmoko channel on irc.freenode.net.

SVN

There is a Subversion server available at svn.openmoko.org.

Read-only access is provided via https://svn.openmoko.org/. 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.openmoko.org:2342

Web access for occasional browsing is available via http://svnweb.openmoko.org/

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
        • ...

Internal resources

There are some resources which are internal. This means that they are only available for internal developers of FIC / Openmoko Inc. The reason they are internal is either because they deal with information under NDA, or about business strategy. We kindly ask for your understanding that while we really try to be as open as possible, there are some topics which we have to discuss without public participation.

Nontheless, contrary to traditional security beliefs, we'll outline here what those resources are.

Mailing Lists

Those are for FIC / OpenMoko employees and external partners/contractors/cunsultants only.

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.

https://lists.internal.openmoko.org/mailman/listinfo/neo1973-devel

devel@lists.internal.openmoko.org

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

buglog@lists.internal.openmoko.org

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

https://lists.internal.openmoko.org/mailman/listinfo/buglog

Wiki

There is another wiki which which is for internal use only at https://wiki.internal.openmoko.org/

Bugzilla

Our internal bug tracking system, mainly for hardware issues, is available at http://bugzilla.internal.openmoko.org/

IRC

There's a #openmoko channel on irc.freenode.net.

There's also a #openmoko-devel channel, which is for OpenMoko internal developers only, sorry.

Personal tools

Public Resources

All resources listed here are available to the general public. Everyone is invited to participate.

Mailing Lists

There are a number of development related mailinglsts at http://lists.openmoko.org/

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 bug squashing progress

http://lists.openmoko.org/mailman/listinfo/buglog

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.

http://lists.openmoko.org/mailman/listinfo/commitlog

community@lists.openmoko.org

This is a public mailinglist for discussion of our user + developer community out there

http://lists.openmoko.org/mailman/listinfo/community

openmoko-devel@lists.openmoko.org

This is a public mailinglist for discussion of developers who want to write code for the Neo1973

http://lists.openmoko.org/mailman/listinfo/openmoko-devel

framework-devel@lists.openmoko.org

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

http://lists.openmoko.org/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/mailman/listinfo/distro-devel

Wiki

This Wiki is our public wiki, http://wiki.openmoko.org/. You're already in it, if you're reading this.

Bugzilla

Our bug tracking system for software issues (which will become public at product release time) is available at http://bugzilla.openmoko.org/

IRC

There's a #openmoko channel on irc.freenode.net.

SVN

There is a Subversion server available at svn.openmoko.org.

Read-only access is provided via https://svn.openmoko.org/. 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.openmoko.org:2342

Web access for occasional browsing is available via http://svnweb.openmoko.org/

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
        • ...

Internal resources

There are some resources which are internal. This means that they are only available for internal developers of FIC / Openmoko Inc. The reason they are internal is either because they deal with information under NDA, or about business strategy. We kindly ask for your understanding that while we really try to be as open as possible, there are some topics which we have to discuss without public participation.

Nontheless, contrary to traditional security beliefs, we'll outline here what those resources are.

Mailing Lists

Those are for FIC / OpenMoko employees and external partners/contractors/cunsultants only.

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.

https://lists.internal.openmoko.org/mailman/listinfo/neo1973-devel

devel@lists.internal.openmoko.org

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

buglog@lists.internal.openmoko.org

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

https://lists.internal.openmoko.org/mailman/listinfo/buglog

Wiki

There is another wiki which which is for internal use only at https://wiki.internal.openmoko.org/

Bugzilla

Our internal bug tracking system, mainly for hardware issues, is available at http://bugzilla.internal.openmoko.org/

IRC

There's a #openmoko channel on irc.freenode.net.

There's also a #openmoko-devel channel, which is for OpenMoko internal developers only, sorry.