LSchiere is currently certified at Apprentice level.

Name: Luke Schierer
Member since: 2002-06-04 01:31:36
Last Login: N/A

FOAF RDF Share This


I'm a computer science student at George Mason University, and help out with the Gaim project.


  • Contributor on Gaim

Recent blog entries by LSchiere

Syndication: RSS 2.0
you get involved with a project by getting their source code. if you install via compiling the source you are all set, otherwise you probly have to find their home page. you then start reading the readme, and any other text files of that sort in the source code top directory, these will often explain things you may need to know at a latter point. then start looking at the source itself. at this point it might help if you know the developers, and expect this to take a significant amount of time. a project of any size will most likely not have a self-evident flow when you first look at it, the feel of the source will only come to you with time and expirience with it.

cvs helps alot. its a VERY powerful tool, and ment far more for developers than for people submitting patches, but the basic options are something you will be using. you'll need the commands cvs login cvs checkout cvs update and cvs diff

you can use cvs -H <command> ie cvs -H diff to get options on using a specific command. you will also either have to use the -d flag BEFORE the command or set the CVSROOT environment variable ie cvs -d checkout gaim will get you the copy of the gaim source code if you have previously run cvs login with the same -d flag contents.

the advantage to cvs for you, is that you are then working with the same code the developers are working with, instead of a body of code that is older, has some bugs fixed, some bugs introduced, some features removed, some features introuduced, so on. working with the same source code gives you a better chance of having your patch accepted.

you'll use the cvs diff command or the patch command to generate a patch. a patch is a list of differences between 2 versions of the same file(s). the patch command is also used to apply a patch. when you submit a patch, be it for a bug fix or a new feature, the developer(s) will read your patch to attempt to identify if its the correct fix/correct way to implement a new feature. keep in mind that some projects have style guidelines, for instance gaim does not allow gtk in some parts of the code. also keep in mind that while a given piece of code might fix your problem, it might introduce a problem for users in difference circumstances, so developers are at times very careful accepting patches, especially before they have a chance to get to know you and evaluate the quality of your work for themseleves. if two people submit the same patch, any number of things can happen, the developer might like the way one of you fixed the issue mroe than the other, or [s]he might simple use which ever was looked at first.

sometimes developers are able to get to your patch, evaluate it, and give you some feedback within a short period of time (a week or two), but that's the ideal. in real life, developers are working in their free time, are often over-worked and for good reasons or bad ones, feel under-appreciated. as a result, looking at patches sometimes gets delayed, so be patient with your developer.

for the most part you can just ignore bytesplit. at least untill he starts trying to track you down ;-) i think advogato at least knows very well the kind of responces to expect from him at this point
we have signing on with the blist loaded in its entirety pretty much working now. signing off still causes an immedate segfault. we also changed from using a GSList of persons in each group to using a GData and finding a person in a group with quarks (a glib construct, giving a 1:1 mapping between strings (ie the person name, which has to be unique in a given group), and an integer). in the process of making that conversion, we discovered quite a few things we were doing wrong, and got those fixed. the result is that while it still takes some time to load the buddy list on start, signing on happens FAST. very cool. now we just need to regain the ability to sign off ;-), and of course continue moving forward with the code to edit the list. i admit i've been procrastinating on that front; i'm not that great at coding a dialog from scratch and neither is faceprint, and i've been hoping the whole glibc issue in debian so that i could use glade-2 to write the dialog.
its nice to see that someone realizes that evolution is a theory. if you look at ID/evolution debates, you will often see evolution's supporters reference "the fact of evolution" so apparently even scientists don't understand that distinction.

we got the loading of the blist.xml at start up working now. makes it so that i can get online with oscar for the first time in a couple weeks. very nice. it takes forever and a day to see something outside of the terminal to show gaim's running now though, we'll have to change that. but loading the blist.xml only once is such an improvement, i think its worth the increased delay in startup. while i'd of course like to see that delay reduced, i'm not sure how it could be accomplished. now that i can get online again, and also now that we don't have to worry about editing only parts of a given person, we can start moving forward again. on the downside, i think i may have introduced some bugs with blist possition, and i know i introduced at least one with signing an account off.

25 older entries...


LSchiere certified others as follows:

  • LSchiere certified LSchiere as Apprentice
  • LSchiere certified seanegan as Journeyer
  • LSchiere certified chipx86 as Journeyer
  • LSchiere certified warmenhoven as Journeyer
  • LSchiere certified deryni as Apprentice
  • LSchiere certified faceprint as Apprentice

Others have certified LSchiere as follows:

  • LSchiere certified LSchiere as Apprentice
  • chipx86 certified LSchiere as Apprentice
  • deryni certified LSchiere as Apprentice
  • voltron certified LSchiere as Apprentice
  • faceprint certified LSchiere as Apprentice
  • fxn certified LSchiere as Apprentice
  • bgeiger certified LSchiere as Apprentice
  • lerdsuwa certified LSchiere as Apprentice
  • wardv certified LSchiere as Apprentice
  • jao certified LSchiere as Apprentice
  • mis certified LSchiere as Journeyer
  • seanegan certified LSchiere as Apprentice
  • mstyne certified LSchiere as Journeyer
  • technofrillco certified LSchiere as Apprentice
  • numist certified LSchiere as Apprentice

[ Certification disabled because you're not logged in. ]

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!

Share this page