Move content over from Blogspot

[ElDragonRojo]

We put a lot of information at Blogspot including descriptions of all the events we had thought of up to that point.

I moved one piece over as an example.

When someone has the chance, they should move the rest over.

Then, someone should also look through it to see what is useful, what is outdated, and what should be discarded.

[matteom]

This is the first time I see this. I was not aware of its existence. Do we have other stuff like that? Should we open an issue to list them?

[ElDragonRojo]

I suppose we should open an issue for each known or discovered resource in need of being moved over and gone over.

Collect all these under the "On the GitHub" milestone.

Sent from my iPhone

On 17 jul. 2013, at 20:54, matteom [email protected] wrote:

This is the first time I see this. I was not aware of its existence. Do we have other stuff like that? Should we open an issue to list them?

—
Reply to this email directly or view it on GitHub.

[ElDragonRojo]

The biggest problem with this information is that much of it is out of date.

This was a forward-looking dump of everything the organization had thought of when planning 2012. It might be more interesting than useful. This heavily depends on whether there is a living body of work that has superseded it, or whether it should be the basis for such a body to be created.

The options are:

• Put it in a deadend archive folder with a name like Appsterdam2012 and copy from it piecemeal as necessary. This is the only option that makes sense if there is a superseding body.
• Fork the repo, add all these to the events folder, then issue a pull request, so @judykitteh and whoever else is actually running operations can decide what is useful and what is not.
• Put it all in the wiki so that people can start bringing it up to speed organically, with parts being selectively added to the canon later.

[ElDragonRojo]

It looks like this information had been migrated into the current wiki and can be considered superseded.

Migrating the wiki to the new wiki should happen first, the organic option from my comment above, but with the superseding body.

The blogspot documents can at least be looked over to see if there's anything useful not contained in the wiki. It may or may not be interesting to dump them into a historical archive.

It's confusing that there's multiple sets of information in multiple places, as @matteom's comment shows. We should take the opportunity in the migration to delete superseded bodies of work upon migration.