Please make "Redesign Update: Sprint 2 and 3" a front-page sticky

I agree the Redesign needs to be a sticky and priority on the front page, especially getting down the these last few rounds.

Why? The article has enough troll comments already.

There's lots of exciting news going on.

-1 to sticky.

Where you see "constructive, factual feedback" I only see a bunch of wannabees and whiners.

The front page moves rather slowly. We have <1 new article posted a day. Some articles remain on the front page well over a week, and anyone interested in news can easily page deeper into the site. Meanwhile there is a lot of good and important Drupal news out there. I've expressed my wish that we have more activity and more posts on the front page on a daily basis, which would have pushed this article down even faster. This is one of the challenges the current site presents, which is why we want to get the structures of the new design in place and start to work more than the promoted/sticky/not promoted option.

-1 to sticky this. There will be more updates. The abundance of comments suggests that plenty of interested parties are finding the news as it is, imho, and there are places where people can join in the effort.

Front page guidelines are posted here: http://drupal.org/front-page-schedule

The Drupal 6.19 announcement is sticky because a new release of Drupal core is ostensibly of interest to everyone. Other items that have had sticky or ad-block presence are large international Drupal events, which are ostensibly of interest to a vast amount of people curious about Drupal.

Beyond the basic "this week's news update" aspect of the post, it seems to me that the relevance and/or interest of this or any status update on a redesign that is 3.5 years in the making is limited to community members … who also are interested in the website's look and feel. As the post is now 10 days old, any lingering interest would be a further subset of visitors to interested community members who are also qualified to collaborate on the implementation as a coder or tester ... and who are also interested in doing that and who also have the time and energy to do that … and who are also interested in joining the sprint rather late in the game … and who are also open and interested in collaboration with the other people who have given untold amounts of hours in this endeavor already.

Repeated calls for volunteers have happened repeatedly throughout this process, with announcements on the front page of Drupal.org, in various groups on g.d.o, at events, on the Drupal Association site, on blogs aggregated on Planet Drupal…. The redesign team may opt to post more updates, or even calls for community participation on various issues, but that's up to them. The sprint is focused and gaining momentum, and while more help is generally welcome, the nature of that help is very important because, as always, the mythical man month applies — all the more so now, because we are now in a major sprint effort that includes not just front-end components but a lot of requisite back-end architecture and development and not a small amount of systems administration, all requiring enterprise expertise, all of which must dovetail together smoothly with a living site and a community that is, by the way, migrating from CVS to Git (and all the back-end work required there).

So redesign sprint updates have been and will continue to be deemed front-page material, but sticky? Likely not at this point. It just will not be of interest to the vast majority of people seeing it, especially as time moves forward. Ultimately the redesign team would have the most sway in a request for sticky placement.

With 3 site maintainers -1, and a pretty clear policy and precedent, marking this as won't fix.