Re: Moduleset Reorganization -- Take two



Hi!

> Anyway for now I'd like to concentrate on a separate point: I think
> dismantling the development tools moduleset is an error. Having a clear
> message on which are the preferred tools for development is crucial to
> attract new developers and "what should I use?" is one of the more
> frequent questions for new developers approaching gnome.

This is one of the main reasons for the Development Tools &
Documentation Hackfest happening in december[1]. We hope to be able to
provide a solid answer for this "what should I use" question there.

However, I am mixed about the development tools moduleset. Basically we
need a lot of improvements in that area and probably it is far more
useful to have a central point to start (like a revived
developer.gnome.org) that explains and shows the tools than to put them
in a moduleset. A moduleset is something pretty technical that is
unlikely to get much attention outside of people having to deal with
releases/translations.

A nice thing that happend at GUADEC though: In some talk I poke somebody
hacking because he was using anjuta and his answer was: "Yeah, I though
everybody was using that" :)

Regards,
Johannes

[1] http://live.gnome.org/Hackfests/DevDocTools

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]