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