The return of the fix-it marathon

[yvi]

So, at the end of June, denise called for a fix-it marathon.

http://dw-dev.dreamwidth.org/11183.html

Let's have another one.

But let's make it two-fold:

First layer: blocking-launch

http://tinyurl.com/cjw9wk currently has 48 bugs: 21 assigned and 27 new. Let's try to bring that number down. A lot of these look scary, and some of them are not effort-minor, so I'm thinking of a bit of a low goal: by August 15, have the number of unassigned ones in there down to 15, which means 12 newly assigned. And by that time, have only 30 of the bugs left, which means 18 bugs fixed in 13 days.

(Edit: That's 'blocking-launch+', not 'blocking-launch??' or 'Target Milestone: Launch'. I am not sure which of these are the best indicators...)

I have two blocking-launch bugs assigned to me now. Who's with me?

Second layer: babydev

You're new to this whole thing? blocking-launch bugs are way over your head (and if you think that I am pretty much with you :)) by this point? But you're interested in tackling something, you just don't know what?

If you don't already have one, get yourself a Dreamhack.

The effort-minor keyword currently has 180 open, unassigned bugs. There are still a few left on my recent babydev bait post. If you want to do something and can't find anything in that list or don't know how to start, comment here or join #dw_kindergarten and I am sure there are people there including me who can help you find a bug to tackle and then tackling it.

And remember, this is just a suggestion. No-one is under any obligation to do any of this. I just thought it would be nice to get some of these bugs out of the way. :)

Comments

[sophie]

I don't know if I want one because I don't know exactly what's it's for...

More reasons to have a better wiki page! Okay, I'll explain.

A Dreamhack is essentially your own private installation of Dreamwidth. It's intended for development use - so you shouldn't use it to start your own journalling site, for example - but it includes everything you need to run it already in the package. In fact, after you get a Dreamhack, you can start it up just by typing one command in its SSH console: 'start-apache'. Everything else - the setup of libraries, etc - has all been done for you, leaving you able to concentrate on hacking on the code itself.

Does that help?

[foxfirefey]

But does she really need an entire Dreamhack just to work with S2? S2 changes and tests can be made on DW.org itself, or anybody else's Dreamhack one has an account on with style privileges.

She may/may not know about SSH, but I can tell you that a lot of the people wanting to work in styles with S2 or CSS won't, and trying to learn how to use a Dreamhack is the kind of thing that might only be appetizing after one is doing enough developing to make all that learning worth the investment. And it's not just learning how to use SSH, a person has to learn how to keep a Dreamhack updated, and sometimes that can run into interesting issues. (See: recent perlbal repository change.)

[ninetydegrees]

Would a Dreamhack allow me to avoid the s2id stuff to work on styles? And to easily switch from logged in/logged out view? Or from personal journal to community to other account types?

Also, I don't know if I 'just' want to work with S2. I'm willing to learn anything but I have no idea if I could be able to.