On Tue, Jun 17, 2008 at 4:08 AM, Firmicus wrote:

Aaron Griffin wrote:

...

Hey guys, We discussed this a few and things went a little by the wayside due to me not having internet at home. So I'd like to take this opportunity to welcome Francois and Allan aboard as new fancy developers.

Hello everyone and thanks to Aaron for these warm welcoming words!

As you surely know, my main job will be to take care of the TeXLive packages (a big task in itself!). I may well help with some Perl packages too.

I intend to put new TeXLive packages in testing soon after the official release of TL 2008 (to occur in the "rather near future"). Among other changes, they will go to /usr instead of /opt/texlive (as is currently the case with my community pkgs).

...

I think I covered everything. If anyone else has something to add, go ahead.

Cheers, and welcome guys!

Glad to be on board :)

Speaking of things developers do, has anyone written up a brief thing on signoffs? Like what signing off actually entails, how many are needed for core packages, whether you can do it for extra, etc. If anyone still has those old arch-dev emails tagged and can do this, that would probably be really helpful for any new guys like these two. -Dan

On Tue, Jun 17, 2008 at 6:43 AM, Dan McGee wrote:

On Tue, Jun 17, 2008 at 4:08 AM, Firmicus wrote:

...

Aaron Griffin wrote:

...

Hey guys, We discussed this a few and things went a little by the wayside due to me not having internet at home. So I'd like to take this opportunity to welcome Francois and Allan aboard as new fancy developers.

Hello everyone and thanks to Aaron for these warm welcoming words!

As you surely know, my main job will be to take care of the TeXLive packages (a big task in itself!). I may well help with some Perl packages too.

I intend to put new TeXLive packages in testing soon after the official release of TL 2008 (to occur in the "rather near future"). Among other changes, they will go to /usr instead of /opt/texlive (as is currently the case with my community pkgs).

...

I think I covered everything. If anyone else has something to add, go ahead.

Cheers, and welcome guys!

Glad to be on board :)

Speaking of things developers do, has anyone written up a brief thing on signoffs? Like what signing off actually entails, how many are needed for core packages, whether you can do it for extra, etc. If anyone still has those old arch-dev emails tagged and can do this, that would probably be really helpful for any new guys like these two.

I'll wikify it today, and post a link in this thread

Aaron Griffin wrote:

And another "Welcome Aboard" to Dusty. He's going to be taking over the django development.

Thanks for the welcome and sorry for the late reply... I've been busy fixing bugs and stuff. (Just not on this project. :P) Hello everyone, and thanks Jason for the welcome back... are you the only one old enough to remember I've been here before? What happened to Damir? And Tobias? And old what's his name... Judd, I think it was...

Dusty, the above text applies to you as well, as you may want to learn the process a bit so you know how we work.

I might also maintain a package or two.. django, python related, you know me. I wouldn't mind seeing a subversion django in unstable, for example...

To the other people who said they wanted to help out with django development, I'd suggest you get in contact with Dusty, as I'd like him to help spear-head the development here, but I don't think he's averse to team members 8)

Oh yes, then I can take credit for multiple levels of accomplishment! That would be lovely. XHTML and CSS, especially, are things that I would be much less grumpy about if somebody else was doing them. But more python coders would be great too. Especially since I daydream about writing an entire Arch framework in django with unified login for forum, flyspray, wiki, aur, and satellite launchers. But I don't feel like writing that alone so I'd need to see a lot of enthusiastic coders first. -- I have a few things to report. I've gotten used to this code and fixed a couple of the simple bugs that were hanging around, nothing major. Mostly I've been working with the archweb_pub; I'm still not certain what the highest priority tasks on archweb_dev are right now. Bug reports that get assigned to me will probably get addressed first. At Aaron's request, I've merged the newmodel branch into master and deleted newmodel; anyone who happens to be running git clones of archweb_(pub|dev) should switch to the master branch. You can delete the remote references to the old branch using: git remote prune origin git branch -d newmodel Aaron: I've already changed the git repos in the sites home directory over to the master branch. Perhaps we should test and restart httpd sometime soon to complete the transfer. Aaron also mentioned that he wants to have an opportunity for testing before rolling out changes. I don't have my own public webserver for testing so I put some test sites on archlinux.org: archweb_dev: http://www.archlinux.org:1982/ archweb_pub: http://www.archlinux.org:1983/ You'll need to contact me privately for a password to test the archweb_dev of course, if you're interested. These are both django development servers which means they could be slow (single threaded and communicating with sqlite) but I don't expect them to get much load. If you forget the port, check the arch developers page for your overlord's year of birth. Finally, since I'm taking over cactus' noble work, I should probably mention that I'm not an accomplished consumer of tacos and you should continue to forward taco-related queries to him at his home phone number. (1-800-eat-taco). His are a huge pair of boots to fill and I am honoured to be chosen to do so. Dusty