John Todd originally posted this message to the asterisk-dev mailing list. I will be attending, and would love to see you there!
[Note: Please pass this note along to European developers who you may know are not actively scanning the -dev list!]
The European Asterisk development community may be the largest number of active participants on a per-continent basis, depending on how the measurement is done. There have been a few meetings of Asterisk developers in Europe over the last ten years, but recently there has not been a planned get-together of developers like has been arranged at AstriDevCon (following Astricon) in North America. It is too infrequent that Digium engineering members get to see some of those participants, and also we’d like to encourage the development community by getting everyone together once in a while to meet and talk in a way that is more personable than email, IRC, or by voice alone. Therefore, I’d like to announce that there will be an Asterisk Developer European Meet-Up held in Rostock, Germany on May 2nd and 3rd for the purposes of meeting old friends, introductions to new coders, and getting some good work done towards furthering Asterisk open-source development.
The meeting will be held immediately before AMOOCON on the Saturday/Sunday before the conference. We’ve been given a room and Internet connectivity for the purposes of having the meet-up, and I suspect there are some good restaurants and bars in the area which might be suitable for post-coding discussion as well.
There is a small group who I’ve already been in touch with on this, and in order to get a good quorum of developers we’d like to open up the session to a wider audience of development participants. This is really for people who write core Asterisk code – the subjects covered will not be applicable to “user” portions of Asterisk, so please respond only if you’re actively writing code within the Asterisk project. If you’d like more general topics, the AMOOCON conference will cover a broader range of VoIP areas. You are encouraged to sign up for the AMOOCON (http://www.amoocon.de/) event which is happening right after the meet-up and is a paid event, but keep in mind the Asterisk Developer European Meet-Up is free to participants. There will be a good handful of attendees from Digium – Kevin, Russell, and perhaps other as-yet-undecided engineering staff, but it’s your participation that is what is going to make the meeting productive – we look forward to hearing from you!
Please send your interest to me and I’ll add you to the list of attendees.
What: Asterisk Developer European Meet-Up
When: May 2-3, 2009
Where: Rostock, Germany
Why: Coding, discussion, testing, bugfixing, drinking, etc.
Who: Replies to jtodd at digium.com
As originally reported on the asterisk-dev list, the Asterisk project’s application for participation in the Google Summer of Code 2009 has been accepted. Hooray!
For potential students interested in working with us, our ideas list is here, and feel free to contact me directly at russell (AT) digium (DOT) com if you have any questions.
Yesterday, official support for MFC/R2 signaling in chan_dahdi was merged, and will be included in Asterisk 1.6.2. Here is the commit.
To get a head start on testing Asterisk 1.6.2 with R2 support, check out the code from the 1.6.2 branch:
$ svn co http://svn.digium.com/svn/asterisk/branches/1.6.2 asterisk-1.6.2
Before compiling Asterisk, you will need to compile and install LibOpenR2.
Thank you very much to Moises Silva (Moy), who worked very hard to write LibOpenR2 and bring this functionality to Asterisk!
The Asterisk Development Team is proud to announce release of Asterisk 1.4.24, and is available for immediate download at http://downloads.digium.com/
In addition to other bug fixes, this release candidate fixes several crash issues, and resolved some remaining issues related to call pickup and call
parking that were discovered after the release of Asterisk 1.4.23. In addition, issues related to chan_iax2, and regressions introduced to the ‘h’ extension have been resolved.
This release marks the first inclusion of the release summary files which will be included in all future releases. The purpose is to give a clearer overview of the changes that have taken place between the current and previous release, which issues have been closed, and which community members were involved with issue submission, code commits, and issue testing. Additionally, a diffstat at the end of the file shows at a brief glance the number of changes made to files between the previous and current releases.
For a summary of the changes in this release, please see the release summary:
For a full list of changes in this release, please see the ChangeLog:
The following list of bugs were resolved with the participation of the community, and this release would not have been possible without your help!
* Paging application crashes asterisk
- Closes issue #14308. Submitted by bluefox. Tested by kc0bvu. Patched by seanbright.
* Crash in VoiceMailMain if hangup occurs before a valid mailbox number is entered (IMAP only)
- Closes issue #14473. Submitted by, and patch provided by dwpaul.
* Incoming Gtalk calls fail
- Closes issue #13984. Submitted by, tested, and patched by jcovert.
* Realtime peers are never qualified after ‘sip reload’
- Closes issue #14196. Submitted by, tested, and patched by pdf.
* SIP Attended Transfer fails
- Closes issue 14611. Submitted by, tested, and patched by klaus3000.
Thank you for your continued support of Asterisk!
The Asterisk project participated in the Google Summer of Code program in 2005, but has not since then. I would like to apply again this year. I think it is an amazing opportunity to reach out to new developers and get some code written that we all want done, but have not had a chance to get to.
If we want to make this happen, we have a couple of things that we need to come up with as soon as possible. Mentoring organizations must complete their application for the program this week.
1) We need to determine who is willing to serve as a mentor from the Asterisk project. Mentors will be paired up with a student and will provide guidance to help the student bring their project to completion. Without commitments from mentors, we can not participate in the program.
Obviously, an appropriate pairing of a mentor to a student is important. It’s acceptable to say, “I am willing to be a mentor, provided that it is for a student working on a project in my area of expertise.”
If you think you would be interested, please let me know! Feel free to respond on this list, or to me directly.
2) We must build a suggested project list. When students apply for the program, they can submit a proposal for implementing one of our suggested projects, or another project of their choosing. Projects for this list should be appropriate in scope for a college student not yet familiar with the code base to implement in a Summer.
I’m going to create a file in svn to maintain our project ideas list:
To kick of the list of ideas, here are a couple of high level thoughts:
a) I think we could break up the “PineMango” project into multiple suggested projects.
b) John Todd and others had some great ideas regarding security in Asterisk at the last developer conference that could be turned into suggested projects.
If you have some thoughts about other projects to add to the list, again, please let me know, and I’ll add them to our ideas list.