Actions
Accelerate3g5 -- alteholz¶
- Table of contents
- Accelerate3g5 -- alteholz
Summary¶
Participants¶
- Thorsten Alteholz (osmocom@alteholz.de)
Details¶
Adding new features certainly is needed for a project to remain attractive to its users. On the other hand substantial QA work is needed as well to keep users satisfied with the software.
As I am not yet very familiar with all details of the cellular infrastructure, my first contributions to osmocom shall be within the latter topic. I am planning to:
- reduce number compiler warnings; the compiler knows best whether something is weird; especially CLANG is rather picky
- analyse the code with open source tools like splint or valgrind
- taking care of bugs and at least trying to reproduce them, as time goes on, I will be able to even close one or the other
A second assignement will be, probably together with Ruben Undheim, the maintenance of the Debian packages of all needed software both in unstable and backports.
In my opinion it is very important to break down barriers and allow newcomers some easy first steps into the project.
Debian packages¶
needed for 3g core network¶
libosmocore(master; 0.10.2)libosmo-abis(master; 0.4.0)- libosmo-netif (sysmocom/sctp; (master 0.1.1))
- libosmo-sccp (sysmocom/iu; (master 0.7.0))
libsmpp34(master; 1.12.0_)- asn1c (aper-prefix-onto-upstream; tbc )
libasn1c(master; 0.9.28)- osmo-iuh (master; tbc)
osmo-ggsn(master; 1.1.0)- openbsc (sysmocom/iu; tbc)
osmo-hlr(master; 0.1.0)
other packages¶
osmo-bts(master; 0.4.0)osmo-mgw(master; 1.2.0)osmo-pcu(master; 0.4.0)osmo-trx(master; 0.2.0)
other libraries¶
QA: spell checking¶
- libosmocore: 1968
QA: help with bugs¶
Journal¶
2017-03-01
start
Conclusions¶
no conclusions yet
Updated by alteholz almost 6 years ago · 4 revisions