Obey Arthur Liu | 3 Jun 12:00 2009
Picon

Progress meeting 1

Hi all,

First meeting this Saturday around 6pm UTC.

Please fill this form with your mentor to tell me if you can be in the
Saturday 6pm group. If you need another time, select it on the Doodle
here. If none of these times fit, mail back.
<http://www.doodle.com/wekp3e46ifiev882>

I'll send you your precise individual time slot once I get everyone in.

Also, get your written progress reports on the mailing list, preferably
at least a few hours in advance of the meeting so we can read it :).

Cheers

Arthur

--

-- 
Obey Arthur Liu
<http://www.milliways.fr>

_______________________________________________
Soc-coordination mailing list
Soc-coordination@...
http://lists.alioth.debian.org/mailman/listinfo/soc-coordination
Obey Arthur Liu | 5 Jun 08:26 2009
Picon

Re: Progress meeting 1

Obey Arthur Liu a écrit :
> Hi all,
> 
> First meeting this Saturday around 6pm UTC.
> 
> Please fill this form with your mentor to tell me if you can be in the
> Saturday 6pm group. If you need another time, select it on the Doodle
> here. If none of these times fit, mail back.
> <http://www.doodle.com/wekp3e46ifiev882>
> 
> I'll send you your precise individual time slot once I get everyone in.
> 
> Also, get your written progress reports on the mailing list, preferably
> at least a few hours in advance of the meeting so we can read it :).

(all times expressed UTC)

Slots:
Saturday 2:00pm : Jonathan Yu/Dominique Dumont/perl-qt4
Saturday 2:20pm : Stephan Peijnik/Michael Vogt/update-manager
Saturday 2:40pm : Emilio Pozuelo Monfort/Josselin Mouette/debug
Saturday 3:00pm : Cristian Porras/Daniel Burrows/aptitude
Saturday 3:20pm : Diego Escalante Urrelo/Margarita Manterola/amancay
Saturday 3:40pm : Philipp Kern/Luk Claes/autobuilding
Saturday 4:00pm : Sha Liu/Anthony Fok/mips
Saturday 4:20pm : David Wendt Jr/Steffen Moeller/ec2
Monday 7:00pm : Per Andersson/Wookey/mtd

Please arrange a common time in the week:
Luca Favatella/Aurelien Jarno/kbfreebsd
(Continue reading)

Obey Arthur Liu | 5 Jun 11:07 2009
Picon

Re: Progress meeting 1

Obey Arthur Liu a écrit :
> Obey Arthur Liu a écrit :
>> Hi all,
>>
Friday 7:30pm: Luca Favatella/Aurelien Jarno/kbfreebsd

--

-- 
Obey Arthur Liu
<http://www.milliways.fr>

_______________________________________________
Soc-coordination mailing list
Soc-coordination@...
http://lists.alioth.debian.org/mailman/listinfo/soc-coordination
Obey Arthur Liu | 5 Jun 12:56 2009
Picon

Re: Progress meeting 1

Obey Arthur Liu a écrit :
> Hi all,
>
> First meeting this Saturday around 6pm UTC.
>
> Please fill this form with your mentor to tell me if you can be in the
> Saturday 6pm group. If you need another time, select it on the Doodle
> here. If none of these times fit, mail back.
> <http://www.doodle.com/wekp3e46ifiev882>
>
> I'll send you your precise individual time slot once I get everyone in.
>
> Also, get your written progress reports on the mailing list, preferably
> at least a few hours in advance of the meeting so we can read it :).
By the way, if you can, try to include something that other DDs could
try out to see what your project is about. This might take the form of a
.deb package, livecd, qemu image, demo webapp, screencast, whatever.
Just don't force people to spend a week reproducing your dev environment
to be able to try your stuff :)

Cheers

Arthur

--

-- 
Obey Arthur Liu
<http://www.milliways.fr>

(Continue reading)

Luca Favatella | 5 Jun 14:09 2009
Picon

kFreeBSD progress report week 2

During the "Community Bonding Period", I played a bit with the boot
sequence on GNU/kFreeBSD by updating [ging].
I didn't manage to make it completing the boot sequence, but it was useful.
Then I evaluated the work to do on debian-installer; i.e. I
-tracked previous attempts to port it to GNU/kFreeBSD (see [cbp0])
-played a bit with the its image creation process on GNU/Linux
-looked at which udebs were missing on GNU/kFreeBSD (see [cbp1])
Then I started to port BusyBox udeb, producing some patches and
getting some of them merged upstream (see [cbp2]).

Since coding period start, I have worked on porting BusyBox udeb on
GNU/kFreeBSD.
Now BusyBox should have enough features to work in debian-installer,
except for networking.

I tried to test BusyBox init in a Debian GNU/kFreeBSD virtual machine,
substituting /sbin/init.
I had no success because "BusyBox init doesn't support multiple
runlevels" (from busybox man page).
See the first part of [cp0].

I gradually enabled more and more useful BusyBox config options.

Some of them built without patches needed (probably I had disabled
them to have no problems).
See the second part of [cp0] and the "updates" of [cp1].

The config options that needed some work are
-CONFIG_SWAPONOFF
-CONFIG_MOUNT
(Continue reading)

Aurelien Jarno | 5 Jun 14:10 2009
Picon

Re: kFreeBSD progress report week 2

Note: Luca did all the work writing this report, so I didn't feel like
      adding my note at the bottom. I have however reviewed it and I 
      agree with it. Hope this is ok.

On Fri, Jun 05, 2009 at 02:09:03PM +0200, Luca Favatella wrote:
> During the "Community Bonding Period", I played a bit with the boot
> sequence on GNU/kFreeBSD by updating [ging].
> I didn't manage to make it completing the boot sequence, but it was useful.
> Then I evaluated the work to do on debian-installer; i.e. I
> -tracked previous attempts to port it to GNU/kFreeBSD (see [cbp0])
> -played a bit with the its image creation process on GNU/Linux
> -looked at which udebs were missing on GNU/kFreeBSD (see [cbp1])
> Then I started to port BusyBox udeb, producing some patches and
> getting some of them merged upstream (see [cbp2]).
> 
> 
> 
> Since coding period start, I have worked on porting BusyBox udeb on
> GNU/kFreeBSD.
> Now BusyBox should have enough features to work in debian-installer,
> except for networking.
> 
> 
> I tried to test BusyBox init in a Debian GNU/kFreeBSD virtual machine,
> substituting /sbin/init.
> I had no success because "BusyBox init doesn't support multiple
> runlevels" (from busybox man page).
> See the first part of [cp0].
> 
> I gradually enabled more and more useful BusyBox config options.
(Continue reading)

Stephan Peijnik | 5 Jun 19:57 2009
Picon

update-manager progress report week 2

I started working on my project early during the community bonding
period. After a few chats with Michael we decided that it would probably
be the best option to rip apart update-manager completely and then put
everything together again, using a modular approach [0].

update-manager has gotten 3 plus 1 modules now, being the backend, the
frontend, the distribution specific module plus some glue code, tying
the other three modules together.

I also decided to ditch the old synaptics-based backend altogether and
started writing a new python-apt based backend.

Additionally I started documenting all code I either wrote myself or
that I started using again in the modular version. The reason for doing
so was that update-manager was hardly documented at all. All
documentation I wrote so far is based on docstrings and a few
restructured text files. 
Combined the rst files and docstrings make up the update-manager API
documentation [1].

During the last week I was able to finish all three tasks I came up with
[2]. This means that update-manager's home is now on
alioth.debian.org/bzr.debian.org [3][4], the API documentation has been
generated and uploaded [1] and that the Debian-specific module is able
to fetch changelogs and the Gtk UI is able to display that information.

Additionally I created an update-manager-devel mailing list over at
alioth [5], which can be used for development discussion and is open to
everyone.

(Continue reading)

Diego Escalante Urrelo | 6 Jun 01:17 2009
Picon

Re: Progress meeting 1

On Fri, 2009-06-05 at 08:26 +0200, Obey Arthur Liu wrote:
> 
> Slots:
> Saturday 2:00pm : Jonathan Yu/Dominique Dumont/perl-qt4
> Saturday 2:20pm : Stephan Peijnik/Michael Vogt/update-manager
> Saturday 2:40pm : Emilio Pozuelo Monfort/Josselin Mouette/debug
> Saturday 3:00pm : Cristian Porras/Daniel Burrows/aptitude
> Saturday 3:20pm : Diego Escalante Urrelo/Margarita Manterola/amancay
> Saturday 3:40pm : Philipp Kern/Luk Claes/autobuilding
> Saturday 4:00pm : Sha Liu/Anthony Fok/mips
> Saturday 4:20pm : David Wendt Jr/Steffen Moeller/ec2
> Monday 7:00pm : Per Andersson/Wookey/mtd
> 

Hey Arthur, I can't make it before 6pm UTC on Saturday (I would arrive a
few minutes late even), I have to be at university, I have classes on
saturday mornings. Would that be ok?
Cristian Porras | 6 Jun 01:17 2009
Picon

Aptitude History Tracking progress report, Week 2

The first important task when one wants to carry out a historical
study of the behavior of a system is to determine what information you
want to store and how this is going to be saved, thinking of providing
an easy way to access information when needed.

In our case, we need to store the information of the packages status
and the actions that have been made to them. For now I have confronted
the aptitude state and the dpkg state.

We use the state of dpkg to see the changes that other applications
(Apt, Synaptic, Adept, etc..) can perform on the packets.
To see the changes we rely on the pkgstates file (which contains some
information about the last state that was seen by aptitude) and the
routine build_selection_list, comparing what is in the apt cache and
what is stored in pkgstates.

So the first task was to create routines to save in each member of the
history the information that can be collected from pkgstates and the
cache, which really is not much. This process is accompanied by the
function to write in the text log and the binary database. I believe
that work it's around 70-75%, missing optimization and definitions of
some values.

I have been working this week on the aptitude state , creating a
vector of entries which is storing the information collected from the
state's changes through the functions cleanup_after_change,
apply_solution and build_selection_list from aptitudeDepCache, calling
on the last function to the routine that writes the whole vector of
changes made so far in the text log and the database, I think this
work is located at 50%.
(Continue reading)

sha liu | 6 Jun 08:05 2009
Picon

Create a N32 MIPS Port for Debian, week 2

    There're not really any progress in my the last two weeks since my only laptop was down and I had some TA stuff to finish. I spent the other time installing and studing the multi-lib tool chain on my Fuloong 2f box.
    I started working on the project early at the community bonding period, by building a LFS[0] and a CLFS[1] system. This process teach me how to build a native or a cross-complile tool-chain and how to use this tool-chain to build your own linux system. Then by finishing the book LPI linux Certification in a Nutshell ,I got familiar with Unix-like environment admistrative skills and some basic network administration. And by reading the book See MIPS Run Linux I got some basic idea of MIPS ISA and O32, N32 ABI.
    I also tried to run the mipsel port of Debian under qemu[2] before I got the fuloong box. Since the performance is not very good, I didn't build any package on it.
    After I received the fuloong box, I installed lenny on it by simply extracting the whole system from a tar ball to a empty partition[3]. Very sadly, a Gdium Liberty 1000 netbook, also a Loongson2f based machine which is kindly donated by Dexxon/Emtec and BLUG[4], is lost by the local courier :-(
    I plan to first build the binutils and then kernel, gcc and glibc on my fuloong box in the next week. I've already discussed with Fai Wong about the this and all these packages with necessary patches is ready on my laptop which I could get back this afternoon.
    There is another link may be helpful If some of you are insterested in installing debian on a loongson2f based system[5].
 

--
Best,
Sha Liu
_______________________________________________
Soc-coordination mailing list
Soc-coordination@...
http://lists.alioth.debian.org/mailman/listinfo/soc-coordination

Gmane