[sip-comm-dev] GSoC Project Requirements


#1

Hello all, and especially all you GSoC students, :slight_smile:

As most of you are probably aware the GSoC coding period will start in
some ten days, so time to roll your sleeves! I would like to wish all of
you good luck and give you a few pointers.

In order to be able to better organize your work, we have prepared a
list of issues that you need to address in order for your project to be
considered successful. We call these "requirements lists". They contain
the minimum set of tasks that we expect you to complete during this
summer, so check them out now:

http://sip-communicator.org/gsoc

Once you have a look now, please let us know if you see any flagrant
mistakes (Student/Mentor name or project content) that could have
occurred while filling in the details.

All lists are separated in two sections: First and Second term (and some
come with an "Optional" section), so that it would be easier for your to
plan your work. We'll be tick-ing the tasks in these lists as you move
forward and report your progress to this list.

Note that in addition to the tasks in the requirements lists we expect
_all_ students to also:

1. Communicate regularly on the dev mailing list with (at least)
frequent progress updates. Once or twice every two weeks should be a
minimum. Learning the ways of open source is an essential part of this
program and communication is probably the most important FOSS dev
characteristic.

2. All the code you submit should respect our code conventions:
http://www.sip-communicator.org/index.php/Documentation/CodeConvention

3. All your code should be well commented and there shouldn't even be a
single method without javadocs (... don't worry, writing these is
definitely more fun than what it sounds :wink: )

If you are now thinking: "Oh my God/Spirit/Force/Nothing/Whatever, how
on earth am I going to get all this done?!?", then keep in mind that we
are in this together! You have a group of very dedicated mentors and,
above all, an extremely friendly community that will be accompanying you
every step of the way. This doesn't mean that it's going to be easy ...
After all, easy is not what you signed for. The one thing we could
promise however is that this summer you are definitely in for one
unforgettable learning experience!

Well I believe we are all set. Good luck to you all!

Cheers
Emil

路路路

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Everything ok with our project (OTR). Only a little something: I am
working in/for Estonia, even if I am German, so maybe, we should add
this.

Ok, let's get busy (even more than we all are at the moment)!!!

Cheers,
Uli

路路路

On Mon, May 11, 2009 at 3:51 PM, Emil Ivov <emcho@sip-communicator.org> wrote:

Hello all, and especially all you GSoC students, :slight_smile:

As most of you are probably aware the GSoC coding period will start in
some ten days, so time to roll your sleeves! I would like to wish all of
you good luck and give you a few pointers.

In order to be able to better organize your work, we have prepared a
list of issues that you need to address in order for your project to be
considered successful. We call these "requirements lists". They contain
the minimum set of tasks that we expect you to complete during this
summer, so check them out now:

http://sip-communicator.org/gsoc

Once you have a look now, please let us know if you see any flagrant
mistakes (Student/Mentor name or project content) that could have
occurred while filling in the details.

All lists are separated in two sections: First and Second term (and some
come with an "Optional" section), so that it would be easier for your to
plan your work. We'll be tick-ing the tasks in these lists as you move
forward and report your progress to this list.

Note that in addition to the tasks in the requirements lists we expect
_all_ students to also:

1. Communicate regularly on the dev mailing list with (at least)
frequent progress updates. Once or twice every two weeks should be a
minimum. Learning the ways of open source is an essential part of this
program and communication is probably the most important FOSS dev
characteristic.

2. All the code you submit should respect our code conventions:
http://www.sip-communicator.org/index.php/Documentation/CodeConvention

3. All your code should be well commented and there shouldn't even be a
single method without javadocs (... don't worry, writing these is
definitely more fun than what it sounds :wink: )

If you are now thinking: "Oh my God/Spirit/Force/Nothing/Whatever, how
on earth am I going to get all this done?!?", then keep in mind that we
are in this together! You have a group of very dedicated mentors and,
above all, an extremely friendly community that will be accompanying you
every step of the way. This doesn't mean that it's going to be easy ...
After all, easy is not what you signed for. The one thing we could
promise however is that this summer you are definitely in for one
unforgettable learning experience!

Well I believe we are all set. Good luck to you all!

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
title+name: Dr. Ulrich Norbisrath
web: http://ulno.net; address+phone+fax: http://ulno.net/contact
google:unorbisrath@gmail.com; icq:46786247
mailto:ulno@ulno.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi,

I have just checked my project requirements (Java interface for Mac OS X's Growl). All the requirements are clear to me except the last one - "Make the Mac OS X sparkle updater work with java 1.6". Could someone explain me why sparkle updater is not working with java 1.6? I am currently using a 32-bit intel mac, so I can't use java 1.6 and see the problem myself.

Cheers,
Egis

路路路

On 11 May 2009, at 23:51, Emil Ivov wrote:

Hello all, and especially all you GSoC students, :slight_smile:

As most of you are probably aware the GSoC coding period will start in
some ten days, so time to roll your sleeves! I would like to wish all of
you good luck and give you a few pointers.

In order to be able to better organize your work, we have prepared a
list of issues that you need to address in order for your project to be
considered successful. We call these "requirements lists". They contain
the minimum set of tasks that we expect you to complete during this
summer, so check them out now:

http://sip-communicator.org/gsoc

Once you have a look now, please let us know if you see any flagrant
mistakes (Student/Mentor name or project content) that could have
occurred while filling in the details.

All lists are separated in two sections: First and Second term (and some
come with an "Optional" section), so that it would be easier for your to
plan your work. We'll be tick-ing the tasks in these lists as you move
forward and report your progress to this list.

Note that in addition to the tasks in the requirements lists we expect
_all_ students to also:

1. Communicate regularly on the dev mailing list with (at least)
frequent progress updates. Once or twice every two weeks should be a
minimum. Learning the ways of open source is an essential part of this
program and communication is probably the most important FOSS dev
characteristic.

2. All the code you submit should respect our code conventions:
http://www.sip-communicator.org/index.php/Documentation/CodeConvention

3. All your code should be well commented and there shouldn't even be a
single method without javadocs (... don't worry, writing these is
definitely more fun than what it sounds :wink: )

If you are now thinking: "Oh my God/Spirit/Force/Nothing/Whatever, how
on earth am I going to get all this done?!?", then keep in mind that we
are in this together! You have a group of very dedicated mentors and,
above all, an extremely friendly community that will be accompanying you
every step of the way. This doesn't mean that it's going to be easy ...
After all, easy is not what you signed for. The one thing we could
promise however is that this summer you are definitely in for one
unforgettable learning experience!

Well I believe we are all set. Good luck to you all!

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Noted and fixed.

Cheers
Emil

Ulrich Norbisrath wrote:

路路路

Everything ok with our project (OTR). Only a little something: I am
working in/for Estonia, even if I am German, so maybe, we should add
this.

Ok, let's get busy (even more than we all are at the moment)!!!

Cheers,
Uli

On Mon, May 11, 2009 at 3:51 PM, Emil Ivov <emcho@sip-communicator.org> wrote:

Hello all, and especially all you GSoC students, :slight_smile:

As most of you are probably aware the GSoC coding period will start in
some ten days, so time to roll your sleeves! I would like to wish all of
you good luck and give you a few pointers.

In order to be able to better organize your work, we have prepared a
list of issues that you need to address in order for your project to be
considered successful. We call these "requirements lists". They contain
the minimum set of tasks that we expect you to complete during this
summer, so check them out now:

http://sip-communicator.org/gsoc

Once you have a look now, please let us know if you see any flagrant
mistakes (Student/Mentor name or project content) that could have
occurred while filling in the details.

All lists are separated in two sections: First and Second term (and some
come with an "Optional" section), so that it would be easier for your to
plan your work. We'll be tick-ing the tasks in these lists as you move
forward and report your progress to this list.

Note that in addition to the tasks in the requirements lists we expect
_all_ students to also:

1. Communicate regularly on the dev mailing list with (at least)
frequent progress updates. Once or twice every two weeks should be a
minimum. Learning the ways of open source is an essential part of this
program and communication is probably the most important FOSS dev
characteristic.

2. All the code you submit should respect our code conventions:
http://www.sip-communicator.org/index.php/Documentation/CodeConvention

3. All your code should be well commented and there shouldn't even be a
single method without javadocs (... don't worry, writing these is
definitely more fun than what it sounds :wink: )

If you are now thinking: "Oh my God/Spirit/Force/Nothing/Whatever, how
on earth am I going to get all this done?!?", then keep in mind that we
are in this together! You have a group of very dedicated mentors and,
above all, an extremely friendly community that will be accompanying you
every step of the way. This doesn't mean that it's going to be easy ...
After all, easy is not what you signed for. The one thing we could
promise however is that this summer you are definitely in for one
unforgettable learning experience!

Well I believe we are all set. Good luck to you all!

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Founder and Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hi Egis,

I have just checked my project requirements (Java interface for Mac OS X's Growl). All the requirements are clear to me except the last one - "Make the Mac OS X sparkle updater work with java 1.6".

You may have wondered why this item was in the list. We thought you may finish the growl project ahead on schedule, and that the experience you'll gain during the project would certainly help us a lot to deal with this issue (it also uses a JNI in objective-C that I wrote).

Could someone explain me why sparkle updater is not working with java 1.6?

An issue with some debug logs is available in our tracker:
https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=597

I am currently using a 32-bit intel mac, so I can't use java 1.6 and see the problem myself.

That's something we can work on together. Anyway, there's still a long road before reaching this point, so let's first concentrate on the growl part, we'll further discuss the sparkle one when it'll be time.

Cheers,
romain

路路路

On 2009/05/12, at 13:02, Egidijus Jankauskas wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Hi Egis,

I am currently using a 32-bit intel mac, so I can't use java 1.6 and see the problem myself.

That's something we can work on together. Anyway, there's still a long road before reaching this point, so let's first concentrate on the growl part, we'll further discuss the sparkle one when it'll be time.

By the way, OpenJDK has just released a first beta for Java6 which works also on 32-bit intel mac. It is available here:
http://landonf.bikemonkey.org/code/java/OpenJDK6_MacPorts.20090516.html

It might be a bit early to give it a try, but it was just to let you know that some alternatives exist.

Cheers,
romain

路路路

On 2009/05/12, at 23:50, Romain KUNTZ wrote: