Name: Andrei Barbu Physical location: Toronto, CA Email: teval@myrealbox.com Areas of responsibility: lisp Mentor: george
My nick everywhere is teval, just so everyone knows who they are talking to. Same over irc, bugzilla, and the forums.
*** Bug 36876 has been marked as a duplicate of this bug. ***
Apparently mkennedy will also be assisting with mentoring. Or you two can duel over it 8)
Replying here to easily keep everybody in focus. On Wednesday 31 December 2003 09:46, Andrei Barbu wrote: > I spoke to Kevin (the guy who manages lisp in Gentoo), and I proposed we I guess (from further context) you meant Debian here? > make a central CVS of the packages that have no upstream maintainers > anymore. This will not only help everyone keep track of the packages, and > make sure there is no > reinventing the wheel between the two distros, it'll also attract more > developers and patches. A lot of people probably don't know who to go > for patches. > > The list would be hosted on the sourceforge acct, and be for both > distors (debian-gentoo-lisp) would be a nice name. I'm thinking > sourceforge because it's neutral and neither distro will have to do more > than the other. If there are problems in the end, we won't end up with > one person keeping everything (it's happened to be before with > developers which slacked off, and decided not to give others access > anymore). Giving them a place on the web (right now only the gentoo and > debian package listings list these very important packages) might even > get other distros to include them, and they might eventually find their > own maintainers. That would be awesome! On Wednesday 31 December 2003 09:47, Andrei Barbu wrote: > How could I get an teval@gentoo.org acct? and access to the gentoo-dev? > It's kind of awkward to contact new people about lisp and say I'm on > gentoo and have a myrealbox acct :p It would also be useful if I could > talk on gentoo-dev :) Post to this bug, well, I just did already :). So, avenj, seemant: when teval is supposed to get @gentoo.org email and voice on -dev (irc)? IIRC irc privs are usually handled right away, while email gets assigned with the rest of access privs, but may be we can do an exception (for email at least, he can get cvs access in two weeks) in such situation? George
He already has autovoice on #-dev; I set that up yesterday evening, I believe. Everything'll get added at the end of two weeks (and reception of copyright assignment forms and so on, but we'll deal with that when the time comes). Frankly, he's _not_ with Gentoo yet; he hasn't completed the two week mentoring period. We've had to terminate mentoring periods in the past (which is the value of the mentoring period)
update: Andrei has sent his response to the quiz to the relevant folks
Yes he did. And I am going through his bugs (looking good so far). But doing training of another prospective dev and being somewhat tied with other gentoo and nongentoo stuff this does not go as fast as I would like. Matthew: so, considering that he is about to take on lisp stuff, some help would be appreciated ;). Actually on closer look at many of his bugs I see that a big portion of them is really common-lisp specific ;) (for the most part trivial version bumps) plus they depend on #36621. In short I am not feeling comfortable touching many of them and would ratjer leave them to you ;). Here is the list that he sent me: ------------- 36621 is trivial, but it's very important. The upgrade fixes an important part of the lisp system (the common-lisp-controller, which due to inetd updates has stopped working) 36732 Isn't trivial, along with 36691 and 36670 36670 is mostly the same ebuild, but I fixed the diff files. I'll add more tonight :) Other trivial bugs are: 36733, 36745, 36778, 36779, 36780, 36690, 36688, 36678, 36671, 36664, 36654, 36620 ------------- I've gone through some of them and will go through some more, but please feel free to assign common-lisp specific stuff to yourself ;), as I think I am no too good a candidate to take care of them. Another thing, what should we do about herding? Andrei expressed interest in doing Lisp stuff in general. Do we need to create another herd, I would think that's gotta be "lisp", or would it be better to bundle it all under the same herd, possibly renaming common-lisp => lisp? In the latter case you or him can put appropriate comment in a <role> filed for example... but this is pretty much up to you. Now that there is also a Scheme dev onboard I am not really sure what is the best way to organize. George
George, At the moment, we have a common lisp herd (common-lisp). This herd uses lisp@gentoo.org as a general assignee. I added teval@gentoo.org to the common-lisp herd. (assuming his username doesn't change). I've reassigned the common lisp bugs you had to lisp@gentoo.org. We can feast from there. A few days ago I created a scheme herd, since this class of software is quite significant in portage. I am sponsoring another developer currenty (Blake Matheny, jake on IRC, bug #37864). He has a keen interest in improving the scheme situation amongst other things. I am also in the scheme herd with a minor role description (I maintain scsh, since I use that). George, you might like to add yourself to that herd since you seem to have a lot of scheme bugs. In reply to your last paragraph, since scheme and common lisp are pretty different, lisp@gentoo.org is really only meant for common lisp specific stuff. This includes: dev-lisp/sbcl, dev-lisp/cmucl, dev-lisp/clisp, app-emacs/ilisp, dev-lisp/common-lisp-controller, and all of dev-lisp/cl-*. There are some languages which are more similar to common lisp than scheme, these include dev-lisp/xlispstat, and dev-lisp/lush. It is okay to use lisp@gentoo.org for those. As things get rolling with the scheme herd, we'll need to get the assignee: scheme@gentoo.org too.
Andrei, Keep doing what you're currently working on (updating stuff and adding missing bits to dev-lisp). This is really great atm, since I'm refactoring the controller and each impl for a more robust compilation system (based on regenerating an ASDF def. for *all* thats installed). This means I've got a lot hacked up in my tree for the impls and controller, and your current work isn't likely to conflict.
recruiters (avenj/seement/etc.): I have sent CVS/SSH access information etc. to this developer in preparation for when they finally get their account.
Help!!! This guy is submitting and assigning hordes of high-quality ebuilds and bug fixes to me. Give the man an account! Arrrrhhhg... Seriously, its been a month.
Andrei, We need an e-mail to recruiters@gentoo.org with: 1) responses to http://dev.gentoo.org/~avenj/quiz 2) SSH DSA public key attached 3) GPG key ID (not the key itself) 4) birthdate including year
quiz done, needs copyright, and he's good to go
fixed in cvs, nice catch
