[Soc-coordination] Soc-coordination Digest, Vol 88, Issue 5

Sat Jul 5 18:17:56 UTC 2014

hey!
i am a c++ coder and want to work with debian and contribute  to it. I
want to participate in the next gsoc. Please help me find the recent
bugs i can fix(being a  beginner) .

On 7/5/14, soc-coordination-request at lists.alioth.debian.org
<soc-coordination-request at lists.alioth.debian.org> wrote:
> Send Soc-coordination mailing list submissions to
> 	soc-coordination at lists.alioth.debian.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
>
> or, via email, send a message with subject or body 'help' to
> 	soc-coordination-request at lists.alioth.debian.org
>
> You can reach the person managing the list at
> 	soc-coordination-owner at lists.alioth.debian.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Soc-coordination digest..."
>
>
> Today's Topics:
>
>    1. [GSoC 2014] Improve Debian port on mips/mipsel:	Progress
>       report (Plamen Aleksandrov)
>    2. Status Report for Debian Continuous Integration,	Week 7
>       (Brandon Fairchild)
>    3. week 7 (Juliana Leal)
>    4. GSoC 2014 - Getting Muon Ready [Week7] -	FlowRiser
>       (Floris Stoica-Marcu)
>    5. [GSoC] Status Report: Java Project Dependency	Builder
>       (Andrew Schurman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 4 Jul 2014 19:48:35 +0300
> From: Plamen Aleksandrov <plamen at aomeda.com>
> To: soc-coordination at lists.alioth.debian.org
> Subject: [Soc-coordination] [GSoC 2014] Improve Debian port on
> 	mips/mipsel:	Progress report
> Message-ID: <20140704164834.GA18535 at gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> This week I have no patches ready because I'm working on several packages at
> the same time but the compilation on MIPS is too slow so I spend a lot of my
> time waiting (I use 3 QEMUs to speed up the process).
>
> I tried compiling the package quantlib-swig. I get an error at the same
> place as the error described in the auto-building log. The system I compile
> the package on is different from the one used by the auto-building system.
> Because of that I believe the reason for the problem is that the compilation
> loops infinitely. I will spend some more time on this package to make sure
> this is the reason.
>
> I am also trying to fix litecoin (I'm interested in the idea behind bitcoin
> :). The problem is that in one test does not pass on big endian because
> uint256() is only designed to work on little endian. I fixed this function
> but I have to look at some other code to make sure there are no other
> problems (note that this package does not compile on any big endian
> system).
>
> I'm working on haskell-src-exts but I'm not able to reproduce the same
> problem.
>
> I'm working on ghdl. The problem there seems to be related to 32-64-bit
> compatibility.
>
>
> Plamen
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 836 bytes
> Desc: Digital signature
> URL:
> <http://lists.alioth.debian.org/pipermail/soc-coordination/attachments/20140704/d45b2e93/attachment-0001.sig>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 04 Jul 2014 19:02:47 -0400
> From: Brandon Fairchild <csbit32 at gmail.com>
> To: soc-coordination at lists.alioth.debian.org
> Cc: autopkgtest-devel at lists.alioth.debian.org
> Subject: [Soc-coordination] Status Report for Debian Continuous
> 	Integration,	Week 7
> Message-ID: <53B73297.4080002 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Status Report for Debian Continuous Integration - Week 7
>
> This week I worked on displaying the data charts without JavaScript by
> using a Ruby library called gruff to generate the data charts.
>
> I also made a new class in the debci Ruby API (Debci::Graph) to access
> the data and generate the data charts. Debci::Graph can generate
> pass/fail and pass percentage charts for each suite/architecture.
>
> After the charts are generated, they are used in the status template if
> JavaScript is not available.
>
> Next week I plan to continue working on the data charts and any needed
> web UI improvements.
>
> Regards,
> Brandon Fairchild
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 4 Jul 2014 21:01:45 -0300
> From: Juliana Leal <juliana.m.louback at gmail.com>
> To: soc-coordination at lists.alioth.debian.org
> Subject: [Soc-coordination] week 7
> Message-ID:
> 	<CAEwDPqBQTC-yrmppZU3vYthJBSNtOKKRYfXdOucDH4UMsFB6HA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Status report - WebRTC portal for the Debian community
>
> Week 6
>
> Spent this week building the IM function for Jscommunicator.
> I used the JsSIP demo (try.jssip.net) as a guide for my development, using
> the SIP SIMPLE protocol. Currently, jscommunicator automatically starts a
> chat session when a call is made (audio or audio/video call), and allows
> creating a new chat session with the contact info entered by the user.
>
> Jscommunicator doesn't yet provide a contact list to facilitate not only
> the IMessaging, but also the calls. I plan to work on that next week. Also
> next week (Monday morning) I will be participating in a video conference
> with Yehuda Korotkin and her students to show how they can contribute to
> Debian.
>
> My best,
> Juliana
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.alioth.debian.org/pipermail/soc-coordination/attachments/20140704/8dbf3d33/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 5 Jul 2014 09:14:59 +0300
> From: Floris Stoica-Marcu <floris.sm at gmail.com>
> To: soc-coordination at lists.alioth.debian.org
> Subject: [Soc-coordination] GSoC 2014 - Getting Muon Ready [Week7] -
> 	FlowRiser
> Message-ID:
> 	<CAHEn3YUbx0Q4x7caVSAceEo3qbMCDWwXcLpQ3bD+vzzJ226JEw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello all,
>
> This week I've been focusing on integrating appstream via a lib that Sune
> created into the ApplicationBackend of Muon. Initial integration is fine
> and although appstream is a bit immature as a project; I am sure we can
> make it work, so that in the future we might be able to do a complete
> switch to appstream.
>
> To do the following weeks:
>  *Sorting by kind, project group (KDE, GNOME apps)
>  *to be unable to unninstall apps that are compulsory for the current DE
>  *figure out a way to bring icons into the appstream integration
>  *bring screens and description from appstream rather than from the
> rnr-server
>
> I'm really excited about this change,
> Floris.
>
> --
> Stoica-Marcu Floris-Andrei
> floris.sm at gmail,com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.alioth.debian.org/pipermail/soc-coordination/attachments/20140705/96515d34/attachment-0001.html>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 5 Jul 2014 00:16:01 -0700
> From: Andrew Schurman <arcticwaters at gmail.com>
> To: soc-coordination at lists.alioth.debian.org,
> 	"debian-java at lists.debian.org" <debian-java at lists.debian.org>
> Subject: [Soc-coordination] [GSoC] Status Report: Java Project
> 	Dependency	Builder
> Message-ID:
> 	<CAGs-L4sm7vLFNeXjBEkh3x+HwxWGru2K67=ONOZiNCKfgEAgPQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hey guys,
>
> This week I got to some bug fixes and continued looking into support
> for Ant based projects. It was fairly easy to add with the
> infrastructure I had using the maven-antrun-plugin as an example. When
> looking at some real Ant projects, I found they could potentially have
> jars committed in source which are used in the build. Obviously, this
> could happen with maven projects too, but with a very small chance.
> This bit of work leads into next week with a module to modify the
> source and remove non-free artifacts. I'll put a follow up question I
> have on this in another thread so it doesn't get hidden in this one.
>
> Apart from that, the next big ticket on the menu is building from a
> -sources.jar in the unlikely event that SCM information is not
> available or inaccessible.
>
> Until next week!
>
> Cheers,
> Andrew
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Soc-coordination mailing list
> Soc-coordination at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
>
> ------------------------------
>
> End of Soc-coordination Digest, Vol 88, Issue 5
> ***********************************************
>