Recommendation for ~ubuntu-core-dev: Thierry Carrez (ttx)
mdz at ubuntu.com
Tue Jun 30 11:56:42 BST 2009
Thierry, could you perhaps attend today's Technical Board meeting at 1400
UTC to discuss your application with the TB?
On Fri, Jun 26, 2009 at 06:51:32AM +0200, Daniel Holbach wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Hello everybody,
> after an interesting discussion about Java packaging, the Server team
> and cheese the MC found out that they would very much like to see
> Thierry Carrez in ~ubuntu-core-dev. Hence our recommendation.
> [ dholbach] +1
> [ jpds] +1
> [ soren] +1 (attempted +2 though)
> [ geser] +1
> [ MootBot] Final result is 4 for, 0 against. 0 abstained. Total: 4
> Have a great day,
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
> [17:23] <dholbach> [TOPIC] Core-Dev Application: Thierry Carrez
> [17:23] <MootBot> New Topic: Core-Dev Application: Thierry Carrez
> [17:23] <dholbach> [LINK] https://wiki.ubuntu.com/ThierryCarrez/CoreDevApplication
> [17:23] <MootBot> LINK received: https://wiki.ubuntu.com/ThierryCarrez/CoreDevApplication
> [17:24] <dholbach> ttx: how's life in France?
> [17:24] <ttx> It's nice and sunny. I've a baby screaming on my lap so my answers might get delayed sometimes
> [17:24] <dholbach> :-)
> [17:24] <ttx> was kinda expecting the meeting at 1700utc
> [17:25] <dholbach> ttx: AnAnt couldn't make it later on
> [17:25] <ttx> I should be ok :)
> [17:25] <dholbach> ttx: the most pressing question I have is the following:
> [17:25] <dholbach> Mathias Gug said you should eat more cheese, what are your plans with that?
> [17:26] <ttx> dholbach: well, its a kind of phobia. But I can work around it with cooked cheese
> [17:26] <ttx> as long as it's not really raw. So I expect improvements in this area for the next cycles
> [17:26] <dholbach> :-)
> [17:27] <dholbach> ttx: how has your experience with Java packaging and integration changed in the last time?
> [17:28] <ttx> dholbach: I would say I encounter two types of actions now. One is packaging missing packages... the other is wide changes to the state of Java library packages in general
> [17:28] <ttx> Java packages don't get updated a lot so there are lots of old deps that need to be cleaned out
> [17:29] <ttx> otherwise you get unwanted dependencies, that sort of things
> [17:29] <ttx> so I look forward using core-dev powers to extend my reach to main Java library packages.
> [17:29] <dholbach> ttx: do you think we're in a better position nowadays (with a few people working on it and having skills and knowledge) to train new people to start working on them?
> [17:30] <dholbach> I'm asking because you said you'd like to do more mentoring and sponsoring :-)))
> [17:30] <ttx> dholbach: yes. And we'll restart the Java team meetings very shortly to try to build a new momentum around that
> [17:30] <dholbach> ROCK
> [17:30] <geser> ttx: what's your impression about the current status of the several java packages in the archive?
> [17:30] <dholbach> that makes me happy
> [17:31] <ttx> dholbach: same space, next week, 0900UTC
> [17:32] <ttx> geser: I'm currently working on cleaning up lots of them, as part of eucalyptus-in-main and eucalyptus-on-cd blueprints
> [17:32] <ttx> geser: so I'd say not that good, but improving.
> [17:32] <ttx> geser: main problem at that point is hard dependency on a non-headless JRE
> [17:32] <ttx> which pulls full JDKs on otherwise server-only installs.
> [17:33] <ttx> I covered like 20 of them recently... more coming :)
> [17:33] <soren> ttx: I remember there were a lot of things up in the air about how to deal with java packages some months ago. Is there a grand plan for dealing with embedded jar's and API incompatibility and all that jazz going forward?
> [17:33] <soren> ttx: Example:
> [17:34] <ttx> soren: not really. We are still at a point where if more software is added, there is a risk that the stack underneath will not support all software
> [17:34] <soren> Say there turns out to be a bug in a java library, like Bouncycastle. Is everything in the archive that uses bouncycastle already using a separately packaged Bouncycastle?
> [17:35] <ttx> there are workarounds, but the best is to convince upstream projects to have a saner approach to depends
> [17:35] <ttx> soren: they should. there are a few black sheeps, but I'm tracking them through my java-Contents files, which allow to spot code duplication in java packages
> [17:36] <ttx> I hope we can set up something more formal within the java team in the near future
> [17:36] <soren> Cool. So we have an overview of packages that need to be fixed up in case there's a security problem?
> [17:36] <ttx> Yes. Just grep for the affected class and the thing should tell you where it was unduly packaged
> [17:36] <soren> Ok.
> [17:37] <ttx> https://wiki.ubuntu.com/JavaTeam/JavaContents
> [17:37] <soren> Ah, neat. I didn't know.
> [17:37] <dholbach> soren, jpds, geser: more questions?
> [17:38] <geser> ttx: have you any ideas how to resolve this self-build-depending of some java packages?
> [17:38] <geser> I remember fighting with jboss and now maven-plugin-tools :(
> [17:39] <ttx> geser: I hit that issue with a Eucalyptus dependency. The "solution" was to push it to multiverse first and have it build from source + JAR (like Java projects like to do)
> [17:39] <ttx> then upgrade it to build-depend on itself
> [17:39] <ttx> then move to universe once it is properly bootstrapped
> [17:40] <dholbach> ttx: does that info live in JavaTeam/FAQ or something? :)
> [17:40] <ttx> It's still dirty, but it was the least dirty way I could find.
> [17:40] <ttx> dholbach: you got me. Not yet :)
> [17:40] <dholbach> :-)
> [17:41] <dholbach> I just thought "that's something that probably more than one person wondered already..." .-)
> [17:41] * dholbach is done with questions
> [17:41] <geser> I've was about to repeat the cup stunt (include the debian deb uuencoded in the .diff.gz for bootstrapping) but got stopped by an other build-dependency
> [17:41] * soren has no more questions
> [17:41] * geser neither
> [17:41] <dholbach> geser: wow
> [17:41] <dholbach> jpds?
> [17:42] <jpds> None from me.
> [17:42] <dholbach> [vote] Shall we recommend Thierry Carrez for Ubuntu Core Developer?
> [17:42] <MootBot> Please vote on: Shall we recommend Thierry Carrez for Ubuntu Core Developer?.
> [17:42] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0 to MootBot
> [17:42] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
> [17:42] <soren> +2
> [17:42] <dholbach> +1
> [17:42] <jpds> +1
> [17:42] <soren> +1
> [17:42] <MootBot> +1 received from jpds. 1 for, 0 against. 0 have abstained. Count is now 1
> [17:42] <MootBot> +1 received from dholbach. 2 for, 0 against. 0 have abstained. Count is now 2
> [17:42] <MootBot> +1 received from soren. 3 for, 0 against. 0 have abstained. Count is now 3
> [17:42] <soren> Worth a try.
> [17:42] <geser> +1
> [17:42] <MootBot> +1 received from geser. 4 for, 0 against. 0 have abstained. Count is now 4
> [17:42] <dholbach> [endvote]
> [17:42] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
> [17:42] <dholbach> well done, ttx
> [17:43] <ttx> \o/ thanks everyone :)
> [17:43] <dholbach> soren: I think that feature is only implemented for sabdfl :)
> technical-board mailing list
> technical-board at lists.ubuntu.com
More information about the Motu-council