Make persistent "predictions" page for yearly follow-ups

i was searching for the predictions post and didn't see it, did you write it?

Yeah! :) We need one!

Also, I don't have time to drive this myself, but in case anyone else is so-inclined, here are the past prediction posts that you could cull from. ;)

2004:
http://drupal.org/node/4877

2005:
http://drupal.org/node/14784

2006;
http://drupal.org/node/41966

2007:
http://drupal.org/node/105423

2008:
http://drupal.org/node/204454

2009:
http://drupal.org/node/356251

2010:
http://drupal.org/node/671566

2011:
http://drupal.org/node/1028810

Thanks, Angie!

We don't need to make the predictions themselves. A basic outline might be:

- A quick look at the outcomes of the previous year's prediction's accuracy. What happened or didn't of the things people suggested?

- A general statement about the direction of Drupal, including aspects of hopes and fears to make it exciting.

- A call for people to participate in the conversation to invite predictions.

But I don't want to even touch this, as Bert might have something planned? He says above "I'll write it". So he might just be on holiday :)

LOL, I couldn't really understand "the task" there.

I made a few corrections only to grammar or wording for the first few paragraphs. I don't quite get the last few.

---

January. After the fireworks have stopped, distant relations have gone home and the last champagne bottle has been found. After all that, it is time for those other two traditions that we Drupalistas have.

Come up with the predictions for the year ahead for Drupal, be it for the code, the community or the license. And the second tradition, draft this post a little late.

So this last tradition has been been fulfilled by this posting. Now it is up to you to come up with the predictions for 2012. And this year, we are double-teaming these predictions. We make the predictions for the last two years!

// not sure i understand this part though!

So what you have to do is think it is the end of December 2012 and look back at the year "ahead" as well as 2010. So from a point of view of nearly one year in the future, descibe what were the highlights of 2011 as well as some of the worse things that have been happening in 2011. And then, in the past tense, write what you thought were the best predictions for 2012.

For example, one of the highlights in 2011 was the proposal during a session of DrupalCon London and for 2012, the best prediction was that actually happened, was the unexpected release of Drupal 8.... And now it is your turn....

The last two and a half paragraphs make no sense to me. I propose we delete them and publish this before January is over.

I deleted them - anyone +1?

There were still a few grammar and spelling typos which I cannot fix, but are fixed in the text here below. I also think we could link to the previous year's predictions for the curious.

If you change the typos, then I'll +1!

START COPY

January. After the fireworks have stopped, distant relations have gone home and the last champagne bottle has been found. After all that, it is time for those other two traditions that we Drupalistas have.

First, come up with the predictions for the year ahead for Drupal, be it for the code, the community or the license. And the second tradition, draft this post a little late.

So this last tradition has been been fulfilled by this posting. Now it is up to you to come up with the predictions for 2012.

You might also like to see our predictions from 2011 to see how we did.

END COPY

OK, updated with your copy.

Cool, looking forward to the comments people have.

Something tells me (perhaps it's my calendar) that it's a bit too late for this. :(

#sadpony

So we don't let this happen next time, I created #1675098: 2012 Drupal Milestones

And here is this year's link:
"Predictions for 2013":
http://drupal.org/node/1881074

I have 2 suggestions:
(re-opening/re-using this post as it is both related/relevant and we have webchick's list of all the previous posts here already).

1. turn "Predictions" this into a permanent book page overview where we can hook in next+next++ year Prediction threads, summarise, "analyse"/evaluate (development/trends), etc. Make that page easy to find, and perhaps as part of a collection of other reference link/pages suitable for promoting Drupal and tempting more people to join.

2. Start a discussion about how we can use voting etc. to measure the support of individual predictions and perhaps compare years/stages/etc. There are a lot of insights to gain from a more structured approach to using this information. I imagine it would be useful with standardising on posting each prediction on its own for such things to be possible.

I think it is possible to turn this yearly "event" into something useful, beyond interesting and inspiring.
This would be practical even just to gather all related links and guidelines in one place. The very list of links itself is reason enough to "keep open" in a more prominent place than in the issue queue.

@Leeteq - nice suggestions! @bertboerland wrote one for 2014 too https://drupal.org/node/2173123

Would be nice if this were an automated feature.

Given that no progress has been done in 7 years, I am closing this issue.