Wonderful; too bad nobody will care, either. Why, instead of making these
changes, don't we revert back to the way things were and then look at
how we
can make all these news coexist without encroaching on each other? That
seems like a level-headed approach to solving the problem.
<goodoldirc>
[16:31] <bjori> Chocula: as I said yesterday, scoates (or anyone with
karma) is totally free to revert it for all I care
</goodoldirc>
Does anyone actually object to reverting this until we can talk about a
good solution to the problem?
In the same vein, does anyone actually disagree that we should talk
about these things on-list before doing them?
I'd be happy to help implement a solution that at least attempts to make
everyone happy (that means I'll volunteer to help write the code).
IMO, we also need to set a soft policy on what is and isn't allowed on
the main page (in a collective manner).
Sean/Marco-
You both know I've got nothing but love for php|architect, and I do agree with the principle that this could have had some list discussion before being implemented. That said, I don't think moving these is unreasonable. They are PHP-community news items, but not actual PHP news. I also don't think it's unreasonable for PHP to give-back to those who organize conferences (which in turn allow a lot of us to travel and meet-up in person) by displaying some advertising (yes, I'm calling these how I see them).
So we need a compromise.
My proposal would be to bifurcate the homepage with actual PHP news going on top (release announcements, security advisories, etc...), and PHP-Community news going on the bottom (Conference announcements, PUGs, etc...). I would also recommend splitting the RSS feed in twain so that these topics are covered independently. This satisfies the need to "unclutter" PHP news, while granting reasonable affordances to conference organizers and other driving forces of the PHP community.
-Sara