Plan to archive DrupalCon/event and GSOC/GCI content from drupal.org [#1243274]

We have events and sessions going back to pre-DrupalCon sites.

http://drupal.org/node/86537
and GSOC
http://drupal.org/google-summer-of-code/2005

They're an interesting historical record, but that's about it. Problems I see:

1. Pages aren't maintained, and usually contain dead links.
2. They sometimes have forum posts mixed in.. is anyone going to read http://drupal.org/node/28645 ?
3. They comprise a lot of nodes, which can then pollute search results. First three matches are from 2005, 2008 and 2007: http://drupal.org/search/apachesolr_multisitesearch/Google%20Summer%20of...
4. It's all organized by date. This assumes that people want to browse by year/know they year that contains the content they want to find.

WE CAN DO BETTER.

The plan:

1. First of all, this date-sensitive content should be from the current year and a future year. Two years of detailed content, tops.
2. The old content gets repurposed into an 'overview page' so we preserve who was involved and their project (tell me what to preserve in comments below).
3. Move content you want to keep to an appropriate place.
4. Then we delete the old detailed nodes beginning September 2011.

I've started a DrupalCon landing page: http://drupal.org/drupalcon

For DrupalCons without a dedicated site, it's probably worth keeping just an overview (dates, presenters etc).

Thoughts?

Comments

Comment #0.0

lisarex CreditAttribution: lisarex commented 8 August 2011 at 21:49

Issue summary:

View changes

clarify

Comment #1

LeeHunter CreditAttribution: LeeHunter commented 9 August 2011 at 14:42

Information about past events - even from the current year - is stale content and should be removed.

We only need to point people to archive.org where they can find the video from past Drupalcons and an archive of drupal.org.

Comment #2

lisarex CreditAttribution: lisarex commented 9 August 2011 at 20:37

Title:	What to do with old DrupalCon/event and GSOC/GCI content?	» Plan to delete DrupalCon/event and GSOC/GCI content from drupal.org
Status:	Active	» Needs work

I had some feedback in IRC from jhodgdon and arianek but were also unclear. Similar content also exists on groups.drupal.org, and many of the nodes point to g.d.o anyway, e.g. http://drupal.org/node/740326

If you care about preserving the Drupalcon/event & GSOC content from last year on back, please archive it on groups.drupal.org or somewhere else before September 10 2011.

After that date, I will begin deleting these nodes (but preserving what is deemed worthwhile). I am relying on the community to tell me what is 'worthwhile' or I'll just use my best judgement :)

Comment #3

lisarex CreditAttribution: lisarex commented 9 August 2011 at 20:41

@LeeHunter, thanks for the input. I agree, it should be gone. In terms of "an archive of drupal.org" what do you recommend?

Comment #3.0

lisarex CreditAttribution: lisarex commented 9 August 2011 at 20:41

Issue summary:

View changes

complete sentence!

Comment #4

greggles

he/him

English

Denver, Colorado, USA

CreditAttribution: greggles commented 11 August 2011 at 15:46

I agree with getting rid of outdated content, but would love to keep around the detail as much as possible. I often find myself digging through content from more than 2 years ago to understand why something was done in a particular way.

is anyone going to read http://drupal.org/node/28645

Yes, 10 people in the last year before August 9th. 2011 :)

The Mozilla project has a digital memory bank dedicated for historic information. If we need to create one of those to get these things out of the centralized search results I would be willing to help make that happen (i.e. create the site [presumably on d.o infrastructure], create a way to transfer content that created redirects).

Comment #5

lisarex CreditAttribution: lisarex commented 11 August 2011 at 18:07

Title:

Plan to delete DrupalCon/event and GSOC/GCI content from drupal.org

» Plan to archive DrupalCon/event and GSOC/GCI content from drupal.org

I've been speaking to other long-time contributors in person, and they would prefer to see the information marked/tagged/identifed as 'archived', and removed from the search results (we could have the archived content searched as an opt-in). Archived content / nodes would also have a different appearance to regular nodes. Sounds *great*, however, I don't know how much work that would take and who would want to do make it happen.

@greggles, the Mozilla idea seems interesting.

Ideally, the archiving approach we take can benefit other content on d.o. e.g. deprecated project issue queues, archived forums, archived documentation that folks are hesitant to delele completely....