![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Jan. 19th, 2009
15 tweets for 2009-1-19
Jan. 19th, 2009 11:55 pmIn the last 24 hours, I posted the following to Twitter:
Follow me on Twitter.
- Monday, 0037: @voyagers There is a thing in my journal that is for you.
- Monday, 0236: I'm at Livermore - http://bkite.com/03R7L
- Monday, 0428: I'm at Pacifica - http://bkite.com/03RbH
- Monday, 0432: @ataniell93 OMG indeed. (re: http://tinyurl.com/6o3jf4 photo, not safe for my mom)
- Monday, 0507: jdn and Cammie are arguing in IRC. It's good to be home. Problems involve confusing jdn with @gameboyguy13 by accident. ( read the other 10 )
Follow me on Twitter.
Open Source Party
Jan. 19th, 2009 11:59 pmAnd Dreamwidth is all over certain bits of the internet, and each person supporting it has their own reasons. The thing that gets me most excited is development.
Dreamwidth volunteers are going through the back entries of LiveJournal![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif)
suggestions, mining it for all the interesting and fun ideas that LJ users have wanted for the LJ codebase over the years. Dreamwidth developers are looking at all the interesting and fun possibilities to run, to see what can be done, without having to worry about disrupting ten years of LJ and breaking things that already exist. Dreamwidth is starting from the ground up, and doesn't have to worry too much about the years upon years of data.
The thing that makes my eyes fill with tears of glee is watching the back-and-forth between people working on LJ and the people working on DW. It seems like people developing for DW are getting stuff done that's been wanted for LJ, and there are things that got developed by LJ developers that DW needed done. Not everything is going to be intercompatible, and not everything is going to be able to be shared, but the beauty of Open Source is that so very much of it will be. So much of what LJ and DW developers do is going to be for the common good of everyone using the shared codebase, no matter what clone or fork they're on.
I get excited about feature development. I get this incredible kick out of watching people come up with ideas, non-technical people flailing around in memespace looking for the words to describe what it is that they want to have happen, and then having actual features honed out of it and developed. There's this almost telepathic jolt as I try to fit my mind around what it is that they're trying to say and get it. Once the community figures out what we want and whether it would break anything physically or socially if it were implemented, in an ideal world the developers would take over and it would happen. Two teams of developers working on the same general codebase make this so much more likely.
In IRC, I watch developers collaborate and learn and make stuff happen. It's a thing of beauty. Features to the people, baby, features to the people.
Dreamwidth volunteers are going through the back entries of LiveJournal
suggestions, mining it for all the interesting and fun ideas that LJ users have wanted for the LJ codebase over the years. Dreamwidth developers are looking at all the interesting and fun possibilities to run, to see what can be done, without having to worry about disrupting ten years of LJ and breaking things that already exist. Dreamwidth is starting from the ground up, and doesn't have to worry too much about the years upon years of data. The thing that makes my eyes fill with tears of glee is watching the back-and-forth between people working on LJ and the people working on DW. It seems like people developing for DW are getting stuff done that's been wanted for LJ, and there are things that got developed by LJ developers that DW needed done. Not everything is going to be intercompatible, and not everything is going to be able to be shared, but the beauty of Open Source is that so very much of it will be. So much of what LJ and DW developers do is going to be for the common good of everyone using the shared codebase, no matter what clone or fork they're on.
I get excited about feature development. I get this incredible kick out of watching people come up with ideas, non-technical people flailing around in memespace looking for the words to describe what it is that they want to have happen, and then having actual features honed out of it and developed. There's this almost telepathic jolt as I try to fit my mind around what it is that they're trying to say and get it. Once the community figures out what we want and whether it would break anything physically or socially if it were implemented, in an ideal world the developers would take over and it would happen. Two teams of developers working on the same general codebase make this so much more likely.
In IRC, I watch developers collaborate and learn and make stuff happen. It's a thing of beauty. Features to the people, baby, features to the people.
