[arch-dev-public] Please provide Info for my talk!
Hi, I am giving an hour long talk at the end of next week about Arch, how it works and why we are successful. I will focus on stuff I am involved with (i.e. pacman...), but will give examples of things like how we decided on systemd, the new installer, etc. (other suggestions welcome) One thing I would like to talk about is our interaction with upstream. I know a few of us have commit access to various upstream projects, or have regularly contributed patches, or have upstream bug tracker privileges etc. Could people let me know about these things so I can make a summary. Something else I was specifically asked to cover is future plans for Arch. Does anyone have things beyond updating packages they want to do? Finally, if you are in Lisbon on the 1st of March, come see me! Search for "SINFO XX" for details. Allan P.S. Please reply off list to avoid irrelevant noise and we don't want to spoil my talk! I believe the talk will be posted on youtube and I will make my slides available too.
On Tue, Feb 19, 2013 at 3:15 PM, Allan McRae <allan@archlinux.org> wrote:
I am giving an hour long talk at the end of next week about Arch, how it works and why we are successful. I will focus on stuff I am involved with (i.e. pacman...), but will give examples of things like how we decided on systemd, the new installer, etc. (other suggestions welcome)
I'm doing a similar thing in Paris at the beginning of April, so I'll be asking Allan for whatever off-list feedback you give so I can steal it :)
Finally, if you are in Lisbon on the 1st of March, come see me! Search for "SINFO XX" for details.
Also, if anyone are in Paris on the fourth and fifth of April, please come say hi (I'll post a link once the conference is announced). Cheers, Tom
On 20/02/13 00:34, Tom Gundersen wrote:
On Tue, Feb 19, 2013 at 3:15 PM, Allan McRae <allan@archlinux.org> wrote:
I am giving an hour long talk at the end of next week about Arch, how it works and why we are successful. I will focus on stuff I am involved with (i.e. pacman...), but will give examples of things like how we decided on systemd, the new installer, etc. (other suggestions welcome)
I'm doing a similar thing in Paris at the beginning of April, so I'll be asking Allan for whatever off-list feedback you give so I can steal it :)
@Tom: I will ping you with what I got... In fact, you can also have a copy of my talk! Disappointingly, I only have responses from 4 devs, 2 TU and 2 users.
On 25 February 2013 10:26, Tom Gundersen <teg@jklm.no> wrote:
On Mon, Feb 25, 2013 at 12:17 AM, Allan McRae <allan@archlinux.org> wrote:
@Tom: I will ping you with what I got... In fact, you can also have a copy of my talk!
Thanks!
Disappointingly, I only have responses from 4 devs, 2 TU and 2 users.
:(
Disappointingly, I only have responses from 4 devs, 2 TU and 2 users. Do you mean you think some people have some commit access but did not (take the time to) answer or do you mean you thought more people had commit access?
I'm sorry but as Guillaume suggested sadly I don't have anything related worth mentioning. On Mon, Feb 25, 2013 at 5:03 PM, Guillaume Alaux <guillaume@alaux.net>wrote:
On 25 February 2013 10:26, Tom Gundersen <teg@jklm.no> wrote:
On Mon, Feb 25, 2013 at 12:17 AM, Allan McRae <allan@archlinux.org> wrote:
@Tom: I will ping you with what I got... In fact, you can also have a copy of my talk!
Thanks!
Disappointingly, I only have responses from 4 devs, 2 TU and 2 users.
:(
Disappointingly, I only have responses from 4 devs, 2 TU and 2 users. Do you mean you think some people have some commit access but did not (take the time to) answer or do you mean you thought more people had commit access?
On 26/02/13 02:03, Guillaume Alaux wrote:
Do you mean you think some people have some commit access but did not (take the time to) answer or do you mean you thought more people had commit access?
Commit access was not the only thing I asked. There was also: On 20/02/13 00:15, Allan McRae wrote:> Something else I was specifically asked to cover is future plans for
Arch. Does anyone have things beyond updating packages they want to do?
[2013-02-20 00:15:40 +1000] Allan McRae:
One thing I would like to talk about is our interaction with upstream. I know a few of us have commit access to various upstream projects, or have regularly contributed patches, or have upstream bug tracker privileges etc. Could people let me know about these things so I can make a summary.
I've sent quite a few patches upstream; probably half of them are of the type "porting foo to libbar-2's API" - we aren't on the bleeding edge for nothing. I haven't done a lot besides that, and try more and more to get users to interact with upstream themselves. In fact, I see KISS packaging as a way of cutting the middle man (me): make packages so straightforward and minimalistic that all user complaints can be forwarded as-is upstream. A package for which this has been taken to the next level is audacious: upstream follows our bug tracker and, usually, by the time I get assigned a new bug report, they have already worked out what the problem is (sometimes with the help of the reporter) and released a new version fixing it. So I'm just closing bug reports and packaging new versions... I'm sure that also applies to tons of other packages in our repos.
Something else I was specifically asked to cover is future plans for Arch. Does anyone have things beyond updating packages they want to do?
Only what I've mentioned on the mailing list in the past - but unfortunately haven't had enough time to bring further since: - merge with Arch ARM. - build packages in VM (works like a charm for i686/x86_64, that's how I've been building stuff [instead of chroots] for the past many months, but I haven't gotten around adapting it to allow ARM VMs yet). Cheers and enjoy the trip/conference! -- Gaetan
On Wednesday, February 20, 2013 00:15:40 Allan McRae wrote:
Hi,
I am giving an hour long talk at the end of next week about Arch, how it works and why we are successful. I will focus on stuff I am involved with (i.e. pacman...), but will give examples of things like how we decided on systemd, the new installer, etc. (other suggestions welcome)
One thing I would like to talk about is our interaction with upstream. I know a few of us have commit access to various upstream projects, or have regularly contributed patches, or have upstream bug tracker privileges etc. Could people let me know about these things so I can make a summary. I am always helping Chinese and Taiwanese upstream follow the bugs on our tracker (librime, fcitx, etc), but not so much patches yet (got some pull-requests accepted on pidgin-lwqq upstream during these months), but wrote some (really) small tools like ydcv, fcitx-tsundere, etc.
I am also admin of Archlinux CN community (archlinuxcn.org), and active on #archlinux-cn IRC and Baidu Tieba (a large active Chinese community of Baidu Inc.), always posting there some newly introduced sweets in our repos and getting some user feedbacks (or sometimes bug reports). Since Chinese users sometimes getting trouble in language when trying to report bugs upstream, sometimes I did it for them (though my English is poor too :P). That's all I could say about interaction with upstream =)
Something else I was specifically asked to cover is future plans for Arch. Does anyone have things beyond updating packages they want to do?
In my dreams: * Kernel versioning, to make Arch the best server os. * Splitted packages support in AUR. Oh wait, forget those trivial things. Let's say: * Official ARM support * Drop i686 support (yes!) Enjoy the trip :) Felix Yan Twitter: @felixonmars Wiki: http://felixc.at
On 20/02/13 00:15, Allan McRae wrote:
Hi,
I am giving an hour long talk at the end of next week about Arch, how it works and why we are successful. I will focus on stuff I am involved with (i.e. pacman...), but will give examples of things like how we decided on systemd, the new installer, etc. (other suggestions welcome)
One thing I would like to talk about is our interaction with upstream. I know a few of us have commit access to various upstream projects, or have regularly contributed patches, or have upstream bug tracker privileges etc. Could people let me know about these things so I can make a summary.
Something else I was specifically asked to cover is future plans for Arch. Does anyone have things beyond updating packages they want to do?
Finally, if you are in Lisbon on the 1st of March, come see me! Search for "SINFO XX" for details.
Allan
P.S. Please reply off list to avoid irrelevant noise and we don't want to spoil my talk! I believe the talk will be posted on youtube and I will make my slides available too.
Any further responses to this? I had (maybe not so...) surprisingly few so far. Allan
On 22 February 2013 07:14, Allan McRae <allan@archlinux.org> wrote:
On 20/02/13 00:15, Allan McRae wrote:
Any further responses to this? I had (maybe not so...) surprisingly few so far.
Allan
Hi Allan, while I do have commit access to hugin and enblend, I don't know if it's worth mentioning, because I didn't do any development for these projects lately. I still watch closely the development though. I also have a few projects of mine, like eilin (driver for EIZO monitors), minidlna-transcode (fork of minidlna that adds full transcoding support) and most importantly FotoSHOCK, which is a bitmap editor mostly aimed at photo editing that supports many bit depths (from 1bit to 64bits), colorspaces and has quite inovative UI, but I don't advertise this project very much yet. Lukas
participants (7)
-
Allan McRae
-
Felix Yan
-
Gaetan Bisson
-
Guillaume Alaux
-
Lukas Jirkovsky
-
Massimiliano Torromeo
-
Tom Gundersen