dw_dev | Recent Entries

Heads-up: The Dreamhack server is currently down. This was unexpected, so I'm sorry for the lack of warning! SliceHost are migrating the slice that the server is on to another datacenter. The server should have come back up by now, but it hasn't, so I'm currently trying to figure out what's wrong.

I'll edit this post with more details once I know them. :)

[edit: Back up! It seems the slice wasn't running for some reason. I'm still not entirely sure why, but after kicking it back up, it's fine now. It's actually been going for some time, but I hadn't updated this until now. Sorry! Anyway, all is good now. :)]

denise

It's been a while since I posted a "most wanted bugs" list! This is the list of bugs that I most want to see implemented, based on either our vision for the site or on what people ask for most often.

For this version I'm leaving off most of the major features that will require lots of design decisions, heavy spec work, etc, etc -- not that those aren't wanted too, but those will require a more concerted effort.

In no particular order other than the order Bugzilla listed them for me:

( Most Wanted Bugs List )

denise

Hello, all! I realized today that our code tour generator had missed a bunch of bugs being resolved, and there had been a few resolved since the last code tour, so I kicked Bugzilla until it turned up all the ones that the code tour generator wasn't picking up.

Behind the cut: 16 bugs for you to peruse. None of these will be live until the next code push.

( now with actual cut. oops. )

denise

People may have noticed that the Bugzilla form has simplifed again! i went through and disabled all the fields we aren't using that Bugzilla would let me disable, and simplified the ones that couldn't.

* Fields no longer visible: Target Milestone and QA Contact, since we aren't using them

* Flags no longer visible: blocking-launch (we've passed launch) and Upstream

* "Version" is a required field, but I removed 0.1 and 0.5 under the DW Development product, leaving only 1.0 and Unspecified. (I'd disable 1.0 and make it just be Unspecified, but that'd require a lot of bug editing, since bugs are about 50/50 split between the two. Still, don't worry about it when opening a bug.)

kareila

Every few months, I run through

changelog compiling a list of who has been contributing patches to our code repository, with the understanding that this is not a competition, or any sort of "high score" list. It's intended as a guide for casual developers, to discern not only our most prolific contributors, but also those who have contributed to the project most recently and therefore would be more likely to provide a timely, informed response to development questions. That is why the list is sorted by "Latest" instead of "Changes".

In general, one entry in

changelog equals one point in the "Changes" column, but fractional points are awarded for collaborative efforts — the most common example being a new S2 theme, where usually half credit is awarded to the theme author and the other half to the person who converts the theme into a code patch. Due to the nature of development, some changes are massive contributions of new code, and others are tiny tweaks; there is no correlation with the amount of effort involved. We are grateful to everyone who helps to improve Dreamwidth, in ways large or small.

I last compiled this list at the beginning of October. Since that time, we have welcomed six new contributors:

hope,

sevilemar,

stormy,

chagrined,

flatlanders, and

delladea. I know not all of you directly contributed code, but you have all helped make DW better. Congratulations and thank you again!

  #  User                      Changes     Latest
  1. kareila                     750.5     Wed Feb 01 07:11:19 2012 UTC
  2. mark                        410.5     Wed Feb 01 00:45:26 2012 UTC
  3. ninetydegrees              470.76     Tue Jan 31 07:30:25 2012 UTC
  4. fu                           1062     Tue Jan 31 07:04:23 2012 UTC
  5. allen                        56.5     Tue Jan 31 03:02:03 2012 UTC
  6. delladea                     2.66     Mon Jan 30 11:19:28 2012 UTC
  7. nornoriel                      10     Mon Jan 30 11:11:53 2012 UTC
  8. inoru_no_hoshi               0.58     Mon Jan 30 11:11:53 2012 UTC
  9. timeasmymeasure             11.33     Mon Jan 30 03:18:25 2012 UTC
 10. sophie                         49     Fri Jan 27 05:51:52 2012 UTC

 11. dancing_serpent              21.1     Wed Jan 25 16:22:18 2012 UTC
 12. alierak                        12     Sun Jan 22 23:53:50 2012 UTC
 13. the_wanlorn                     2     Thu Jan 19 07:46:33 2012 UTC
 14. denise                     373.08     Tue Jan 10 11:35:31 2012 UTC
 15. flatlanders                   0.5     Tue Jan 10 10:17:16 2012 UTC
 16. yvi                           145     Fri Jan 06 15:06:06 2012 UTC
 17. rising                       21.3     Wed Dec 28 07:36:38 2011 UTC
 18. laitaine                     6.75     Wed Dec 28 07:36:38 2011 UTC
 19. foxfirefey                     63     Fri Dec 23 11:39:47 2011 UTC
 20. chagrined                       1     Wed Dec 14 17:05:14 2011 UTC

( The rest of the list... (121 total) )

denise

So a while back I did an open card sort for people to help us reorganize the Account Settings tabs. The project never went anywhere, because there was zero agreement among the answers: usually when you do an open card sort, things will fall into two or three different major sets of buckets and you can work from there, but this one was all over the place and I despaired at ever doing anything with it.

The settings overrun has gotten much worse since then, though, and it's starting to be more urgent to redo them. I've taken a first stab at what I think is a logical grouping; the items inside each tab category are not organized in any way (just reorganizing the order things are listed in will make a lot of difference, I think) but this is my first pass at redoing the groupings.

The major changes (in addition to reordering the tabs themselves) are the consolidation of the Account and History tabs and the Mobile and Other Sites tabs, and the splitting of both Display and Privacy into Journal vs Site; this means we keep the number of tabs constant but there are fewer items in each tab. That, I think, will take care of 90% of the "auuugh options overload", although some of the things are very borderline as to which tab they should go on. (But it's not like it's any better now.) I've included both the label that's displayed to the user (although when I started out I was renaming some of them to be more clear) and the name of the settings package in the code.

Thoughts? Major objections? Once we go through these I'll work on reordering the settings within each tab, and put up a version on my 'hack for people to see in action.

( proposed new tabs/organization )

silverflight8

Thirty four bugs, new and old, big and small. Something for everyone!

( Watch your step! There's a lot of squished bugs round here )

And that's it for this round! Hope you enjoyed the ride, and stay tuned for the next code tour!

Current Mood: working
Current Music: Stars on 45 - disco mix

denise

I've just realized I can change the values in Bugzilla for the RESOLVED status; I've removed MOVED (which we have never used and which just takes up space) and added BYPROXY, to be used for bugs that we fixed accidentally while fixing something else or bugs that pixies spontaneously manifested a fix for by working their magic in the depths of the code while we weren't looking.

(Now why do the pixies never add new features? That's what I'd like to know.)

pauamma

Has anyone tried using the SPORE specification, Net::HTTP::Spore, or any of the other implementations (Ruby, Python, and PHP IIRC) to implement similar-but-not-identical clients for services based on LiveJournal or Dreamwidth? Any opinion of the modules themselves (if you've used them) or the spec and APIs (if you only read the docs) you'd like to share?

exor674

I have noticed certain in-journal links such as next and previous do not preserve the style= setting and really should.

Can people please look at links and compile a list of places that do not preserve this option so I can open a bug.

Thanks.

Right before my brain got refried by this stupid disease I was working on a script to turn the theme layers copied from DW itself into the right format to paste into the s2 code in the sourcecode. I was doing it as I learned how so it's only been tested on about 5 different situations at the moment and I'm quite sure it doesn't do everything so check all output please!!

And yes, my brain got fried (again) by this stupid disability so I'm on indefinite leave from developing for the mean time - and VERY disappointed about it.

At the moment you want to pipe the theme layer through STDIN to the script, so something like

$ ./newtheme.pl NewThemeName Rising "Tabula Rasa" yes < ~/file-with-theme-layer.txt

it will tell you what file it writes the output to, it will be something in $LJHOME/temp/

Script

#!/usr/bin/perl
#
#

my ( $theme_human, $author_name, $layout_human, $is_nonfree ) = @ARGV;

sub diehelp {
    warn "Syntax: newtheme ThemeName AuthorName LayoutName IsNonfree";
    exit;
}

if ( !$theme_human ) {
    warn "No theme name provided.";
    diehelp;
}
if ( !$layout_human ) {
    warn "No layout name provided.";
    diehelp;
}

( $layout_name = lc ( $layout_human ) ) =~ s/\s//g;
( $theme_name = lc ( $theme_human ) ) =~ s/\s//g;

my ( @dropped, @css, @set, $in_css );
while ( <STDIN> ) {
    my $line = $_;

if ( $in_css ) {
        if ( $line =~ m/"""; }/ ) {
            $in_css = 0;
            next;
        }
        push( @css, $line );
    } elsif ( $line =~ m/function Page::print_theme_stylesheet/ ) {
        $in_css = 1;
    } elsif ( /^\.$/ ) {
        break;
    } else {
        next unless $line;
        if ( $line =~ m/^layerinfo / ) {
            push( @dropped, $line );
            next;
        }

push( @set, $line );
    }
}

# process @set lines
my ( @unknown, @presentation, @page, @entries, @modules, @fonts );
foreach ( @set ) {
    if ( /userlite_interaction_links = / || /_management_links = / || /module.*order/ || /module.*show/ ) {
        push( @dropped, $_ ); 
    } elsif ( /font/ ) {
        push( @fonts, $_ );
    } elsif ( /module/ ) {
        push( @modules, $_ );
    } elsif ( /entry/ ) {
        push( @entries, $_ );
    } elsif ( /comment/ ) {
        push( @entries, $_ );
    } elsif ( /links/ ) {
        push( @presentation, $_ );
    } elsif ( /color/ ) {
        push( @page, $_ );
    } else {
        push( @unknown );
    }
}

my $filename = "$ENV{LJHOME}/temp/$layout_name-$theme_name.s2";
open TMP_FILE, "> $filename";

print TMP_FILE <<"EOT";
#NEWLAYER: $layout_name/$theme_name
layerinfo "type" = "theme";
layerinfo "name" = "$theme_human";
layerinfo "redist_uniq" = "$layout_name/$theme_name";
layerinfo "author_name" = "$author_name";

set layout_authors = [ { "name" => "$author_name", "type" => "user" } ];
EOT

# print @set lines
sub print_section {
    my ( $name, @lines ) = @_;

if (@lines) {
        print TMP_FILE<<"EOT";

##===============================
## $name
##===============================
EOT
        foreach ( @lines ) {
            print TMP_FILE $_;
        }
    }
}

print_section( "Presentation", @presentation );
print_section( "Page", @page );
print_section( "Entry", @entries );
print_section( "Module", @module );
print_section( "Fonts", @fonts );
if ( @css ) {
    print TMP_FILE "\n";
    print TMP_FILE 'function Page::print_theme_stylesheet() { """' . "\n";
    foreach ( @css ) {
        print TMP_FILE "    " . $_;
    }
    print TMP_FILE '"""; }' . "\n";
}
print_section( "Unknown - DELETE THIS SECTION after reclassifying lines", @unknown );
print_section( "Dropped - DELETE THIS SECTION after verifying none of it is needed", @dropped );
print TMP_FILE "\n";
close TMP_FILE;

print "Parsed theme now saved in file: $filename\n";
print "This new text needs to be put into the existing file named:\n";
print "$ENV{LJHOME}/bin/upgrading/s2layers/$theme_name/theme.s2\n\n";
print "Theme also needs a preview screenshot. Resize to 150x114px and put in:\n";
print "$ENV{LJHOME}/htdocs/img/customize/previews/$theme_name/$layout_name.png\n\n";

Feedback, cases that break it, improvements, etc. would all be great.

r

Edit: Now with super bonus functioning HTML tags!

denise

In an effort to make sure that older bugs don't get lost, I'm going through over the next few days and unassigning any bugs that have been in the ASSIGNED (now IN_PROGRESS) state for over six months with no activity on the bug, unless I know for sure that a) the assignee is still active in DW development and b) the bug is part of a larger project that the assignee is still working on.

If I accidentally hit a bug of yours that you're still working on, I apologize in advance! Just snag it back for yourself.

shadowspar

Welcome, and thank you for riding along with us today. This is regular Code Tour #92, bound for Bug 4114, making stops at Bug 1385, Bug 1220, and a total of 7 new and 1 old bugs before reaching our final destination.

( The doors are closing...be careful, please. )

Thanks to

kaberett for assembling the list of new vs duplicated bugs for this code tour, and to

john for rocketing through dozens of bugs last week, leaving little for me to steam through.

That's enough for today! Please be sure to collect all of your code snippets, thinky-thoughts, and other personal belongings before leaving the tour. Thanks again for riding with

dw_dev, and enjoy the rest of your day!

Current Mood: chipper

john

Darlings! Happy Friday, the last of the year! It's time for another code tour!

Of course, if you're in Samoa, where there is no Friday (Samoa has no Friday. Samoa needs no Friday), I suggest just popping open another bottle of bubbly and dealing with it. (On the plus side, Samoans, that's 1/52nd less of an opportunity than the rest of the world to hear Rebecca Black. Silver linings, darlings, silver linings.)

We have a wonderful 46 presents under the nondenominational Code Tour seasonal shrub today. (Ours is pohutukawa, on account of me being in New Zealand. Yes, we get New Year's first, on account of being the most awesome country ever. True facts.)

That may sound like a lot of presents! I mean fixed bugs. But many of them are related to journal styles or FAQs, so don't think that we're going all Dudley Dursley on you.

So sit back, relax, pop open a bottle of bubbly (or two! 46 bugs, remember?) and join me on this three hour (code) tour.

WARNING: Code tour may contain the occasional naughty word, naughty innuendo, and dangerous amounts of wine related puns. Do not read code tour while drinking hot beverage. Or cold beverage. Except for perfectly chilled champers.

( Keep Drinking. I mean 'Reading' )

Happy New Year, darlings. May the rest of your 2011 be filled with champagne, sugared violets and lickable people, and may your 2012 not be the end of the whole bloody world. After all, there's lots of champers to drink.

Current Location: Wellington, New Zealand
Current Mood: British
Current Music: Die Walküre, Act 3, Scene 1: "Hojotoho! Hojotoho!"

sophie

Hi all!

As the maintainer of the Dreamhacks service, I'm curious about how everybody's getting on with it and whether there's anything people would really like to have to make dev work easier.

For example, one thing I'm going to be working on is a way to make it easier to set up, start and stop the various auxiliary services that Dreamwidth uses, such as memcached, Gearman, and TheSchwartz. I'm hoping that this'll make it easier to work on bugs that need these services.

But I'd also really like to hear from people about the things they find most difficult when working on a Dreamhack. This can be anything - maybe our wiki's confusing or not quite up-to-date, or maybe you can't figure out the command you need to type to do something.

I want to make things as accessible as I can to everybody, new and experienced alike, so please let me know in the comments what you really wish was easier to do on a Dreamhack! I'll go through the comments later and see what I can do to help - for example, by programming a script for everybody to use on the server, editing the wiki, or simply answering a question if that's all that's needed!

We put out two changes to the protocol with this code push:

addcomments now has a journal parameter, a feature adopted from LiveJournal code

getreadpage is a new function that's been added, and is equivalent to getfriendspage does on LiveJournal.

getfriendspage is deprecated, and will return an error message telling you to use getreadpage instead.

If you're writing a client and there's some data you're interested in that's not currently available through the protocol, let us know!

ghoti

Two new code-bus drivers, this week, me (

ghoti) and

brainwane. Keep all appendages inside the bus, and as you exit the vehicle, please lower your head and watch your step. If you fail to do so, please lower your voice and watch your language.

( Keep reading... )

denise

Mark and I were talking tonight about "ninja releasing" little things that are heavily-asked-for features or bugfixes/UI improvements, and I thought it might be cool to do a "New Year's Resolutions" type thing in the next news post: show the link to the effort-minor Bugzilla search and let people name the one thing they most want to see, then browse the list and try to implement as many of them as we can during January.

Would anybody be interested in coding for that type of hackathon?

philkmills

This is somewhat related to someone's earlier post, but a bit more specific. I'm attempting to create a (different!) client application that would work with both LiveJournal and Dreamwidth. I'm discovering that there are modes that neither fail nor truly succeed when used with DW.

For example, 'getfriendspage' returns no error, also no information. Since DW uses a different concept around reading and subscribing, the idea that the mode doesn't work isn't too surprising.

Looking at Protocol.pm is confusing in that it appears to support getfriendspage (at least, there's code to implement it). I don't see that there is any equivalent interface for retrieving reading page events.

Since the functions of Protocol.pm call internal routines that may or may not do anything, is there a better way of discovering what things are actually supported and what they return?

(I've seen http://wiki.dwscoalition.org/notes/XML-RPC_Protocol but obviously that's not definitive either.)

denise

And with this, we are caught up to present day on code tour, finally. *G* All of these are now live. This code tour is current through 12/7.

( Code tour! )

Profile

Dreamwidth Open Source Development

February 2012

S	M	T	W	T	F	S
			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29

Syndicate

Page Summary

sophie - [resolved] Dreamhack server down
denise - Most Wanted List
denise - Code tour, 23 Jan - 1 Feb 2012
denise - more bugzilla tweaking
kareila - Current Code Contributors: February 2012
denise - first pass at redoing Account Settings tabs
silverflight8 - Code tour: January 05-26, 2012
denise - resolution field
pauamma - Net::HTTP::Spore for multiple-service clients
exor674 - Info gathering; S2 links that do not preserve style=
rb - S2 Patch Assist Script
denise - unassigning aging bugs
shadowspar - Code Tour, JR-style: 29 Dec 2011 - 05 Jan 2012
john - Code Tour (with champers!), December 23-28, 2011
sophie - What do you find difficult on a Dreamhack?
fu - ATTN: client devs: Two changes to the protocol: tweak to addcomments, added getreadpage
ghoti - Code Tour, December 8-23 2011
denise - New Year's Resolutions
philkmills - Client/Server Protocol
denise - november code tour extravaganza, part 4/4

Active Entries

Style Credit

Style:: branchandroot
Resources:: P r o l o g u e

Expand Cut Tags

No cut tags

Page generated Feb. 10th, 2012 05:43 am

Dreamwidth Development

Recent Entries

[resolved] Dreamhack server down

Most Wanted List

Code tour, 23 Jan - 1 Feb 2012

more bugzilla tweaking

Current Code Contributors: February 2012

first pass at redoing Account Settings tabs

Code tour: January 05-26, 2012

resolution field

Net::HTTP::Spore for multiple-service clients

Info gathering; S2 links that do not preserve style=

S2 Patch Assist Script

unassigning aging bugs

Code Tour, JR-style: 29 Dec 2011 - 05 Jan 2012

Code Tour (with champers!), December 23-28, 2011

What do you find difficult on a Dreamhack?

ATTN: client devs: Two changes to the protocol: tweak to addcomments, added getreadpage

Code Tour, December 8-23 2011

New Year's Resolutions

Client/Server Protocol

november code tour extravaganza, part 4/4

Profile

February 2012

Syndicate

Most Popular Tags

Page Summary

Active Entries

Style Credit

Expand Cut Tags