On 16 December 2012 18:53, Andreas K. Huettel <dilfri...@gentoo.org> wrote: >> 1. Even MediaWiki (wiki.gentoo.org) looks better than www.gentoo.org. >> That's impressive-bad. >> >> People still think of Gentoo as a ricer distro that's broken all >> the time, when in reality, it's one of the most stable. No one >> would suspect that anything has changed, though, since the >> homepage hasn't since before I could drink beer. >> >> It makes the entire distro look unmaintained. > > Yeah. Stable. Hehe... > > The problem with the entire webpage is that is coded in an extremely obscure > way. It is probably easier to 100% replace it from scratch than to modify and > improve it. Yes, I've tried to analyze once how e.g. the table of blog posts > or the GLSA announcements on the main page come together. > > My personal suggestion would be to code an internal replacement and > transparently port more and more pages to it (as a change mostly invisible > from outside, with two content management systems running concurrently for a > transition period). Once the transition is complete, improvements can be made > in a more sweeping way. > > How to do this, however, and what software to target should probably be > decided by people who know more than me... and in the end it all boils down to > "who has the time and motivation".
Outsource it to someone who has the knowledge and interest in doing this. The foundation has the funds to support it, and none of us actually have the time to invest in a complete webpage redesign. > > >> 2. Nowhere is it actually spelled out how to become a developer. >> Let's google "how to become a gentoo developer." This takes me >> to... >> >> > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2 >> >> which as far as I know, is complete bullshit. I should look for an >> opening in the monthly newsletter? Really? Or in #gentoo-bugs? > > That page BADLY needs an update. It should however probably also reflect > reality in the sense that you cannot really "apply to become a developer". > What you can do is help out, be useful, get noticed, and be offered the job. > (That at least is my personal impression on how it works.) Different devs got involved it totally different ways. But yes, you need to get involved in a team to get noticed and understand how things work. That a fairly good start. The fact that there are hundreds of different ways to reach a point where a recruiter picks you for interview makes it hard to document it. -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
