Low hanging fruit.

[JamieKnight]

It would be good to have a list of tasks which are somewhat newbie friendly. I want to help, but i'm not quite sure where to start.

I saw this mentioned in the meeting notes (here: https://github.com/mozilla/servo/wiki/Meeting-2013-04-15) but the suggested work there (padding, borders etc) feels like a high starting point.

I'm at first looking for trivial stuff:

• Converting tabs to spaces etc
• Renaming stuff
• Writing docs

Any suggestions? I have done a tiny amount of rust code, but happy to bash on till i get something to work.

Cheers,

Jamie + Lion

[metajack]

In terms of docs, updating the installation instructions would be good. Several people have noted that the instructions are missing a few needed components on Linux.

Another easier coding project would be to finish excising all mention of cairo from various places. I still found stuff left over (variables named cairo_x that should be freetype_x etc).

Some legacy Rust syntax is still around that needs updating. For example. ++ in front of function parameters in declarations (it can just be removed). Or fixing the build warnings in rust code, which mostly amounts to removing unused imports.

I'll keep adding as I think of more.

[JamieKnight]

Thanks @metajack will go have a poke around and see what i can do.

[metajack]

Bug triage and reproduction is always helpful too.

[burg]

There are many, many small tasks within layout but they are fairly context-deep. :-( I need to triage some of my old bugs.

[JamieKnight]

Thanks for the responses. I'm building servo now. I have made some small changes to font.rs (renaming cairo stuff), once it's built i will verify nothing has blown up and open a pull request. Planning on keeping first whirl simple.

Is there some documentation on how to build little parts of the project and running the related tests? If i understand make correctly, if i make && make check from /build it will only recompile files which have changed.

[metajack]

To build a specific subcomponent you can do make -C src/foo.

There are also lots of make targets that get defined like make rust-azure and make clean-rust-azure etc. Documenting those would be nice :)

[JamieKnight]

Will put together a list of which submodules have their own make files.

Is don't see a makefile in servo-gfx where i have been prodding, is this because all the servo stuff gets done in one go? I have been using make servo to test, i'm running make check servo now.

Next candidate seems to be unused imports in rust-layers/test.rs: its throwing a lot of warnings.

[jdm]

Note that some imports are platform-dependent and show up as unused on other platforms.

[metajack]

The contents of this bug should be a wiki page, or should turn into individual bugs labeled E-easy.

[SimonSapin]

I think this can be closed now that there is a bunch of issues marked E-easy. (I also think this is the right way to maintain that list of easy tasks.)