Personally I would rather not have 2016.oscedays.org at all. At the moment our activities are very strongly focused on a single annual event, but one of the ideas we have discussed a lot is that it should develop into an ongoing community, with smaller events and activities occurring throughout the year. So we shouldn’t have a website structure where the annual event dominates.
In addition, the knowledge we generate should be cumulative - last year’s event should not be separate to the current one, it should not just be archived and be forgotten about, it should feed into this year’s event. Conversations should be continued, documents should be improved, etc. And surely if we are changing the theme, but sticking with Wordpress, the structure, existing posts and links will mostly stay the same, won’t they?
I can’t really understand the utility in separate 2015. 2016. etc pages, but I think what will help bring clarity to this conversation is use cases and examples. I’ll go through how I see each section working, and then maybe you can show me where/why separation by year is necessary.
##Forum - community.oscedays.org
As far as I am aware, despite our restructuring, none of our forum links are broken, right? so we can just leave the old conversations there, they are still valuable and they will become less visible as new posts replace them. Perhaps we can add a #2015 tag to any old topics which are only relevant to that event (eg meetings, organisational stuff).
##Landing site - oscedays.org
Open Source Circular Economy Days is a diverse & globally distributed event using the collaborative Open Source methodology to build a waste-free Circular Economy.
What do we mean by OSCE? -> Mission Statement
What’s Open Source? -> OS Definition
What’s Circular economy? -> CE Definition
Get Involved -> updated README, Call for Participation etc
Latest Blogposts -> oscedays.org/blog
What happened in 2015? -> oscedays.org/documentation-2015
confirmed for 2016
active in 2015
I feel like it will be very seldom that somebody would want to click around a perfect replica of the 2015 site. Well, we can make a perfect replica of the 2015 site and put the html files etc on the GitLab for archival purposes, right?
I imagine the only relevant pages which will have changed (but will still be useful in their original state) will be the city pages.
##City Pages eg. oscedays.org/berlin
Info on OSCEdays Berlin 2016!
What happened in Berlin in 2015? -> oscedays.org/berlin-2015
We replicate the 2015 page so people can see how it looked and what was going on, and we add links to documentation.
For a city which took part in 2015 but is not taking part in 2016, we can replicate the 2015 page in this way and on the page ‘oscedays.org/kuala-lumpur’ we have a notice saying:
We currently do not have any activities planned for Kuala Lumpur during the OSCEdays 2016.
Would you like to get involved in running a local event? -> Call for Participation
Check out what happened in Kuala Lumpur in 2015! -> oscedays.org/kuala-lumpur-2015
As far as I see it I don’t need a full replica of each year on its own functioning site, I just need a single page per city. But to help me understand, can you guys provide examples for how the 2015.oscedays site would be used? I don’t think I will be available on Monday for the video call.