Maybe we should continue the tradition from dikutal.dk to have blogs.

USE ALL THE FREE SERVICES!!
I've enabled the repo (https://coveralls.io/r/datalogisk-fagraad/dikultur). We just need to get travis-ci up and running and then of course a fancy badge!

https://github.com/coagulant/coveralls-python looks like the most maintained coveralls python project

http://agiliq.com/blog/2014/05/continuous-integration-with-travis-and-coverallsio/ has a walkthrough of how to integrate with travis

Currently there are events listed under Future events that happened in 2014 :(
http://dikultur.dk/events/

Having a iCal feed for events is a must!

• Proof of concept
• Events by groups

It would be nice to be able to do Event.events.future(), Event.events.past() or similar as per https://docs.djangoproject.com/en/1.7/topics/db/managers/#create-manager-with-queryset-methods and https://docs.djangoproject.com/en/1.7/releases/1.7/#calling-custom-queryset-methods-from-the-manager

Support facebook login

Make it possible to give resources a +1

It would be sweet to provide a basic REST API to get events, using django REST framework.

The project is set up (https://travis-ci.org/datalogisk-fagraad/dikultur). We need a .travis.yml file and a fancy badge in the readme.

It would be really nice to have a test suite:

Unit tests:

• iCal feeds
• Resource upvotes

Integration tests (selenium tests):

• Event creation/update
• Resource creation/update
  • File upload
  • File removal
• Resource voting

We want to be able to present different social groups.

It could be nice to be able to comment on events.
Maybe we could even integrate with facebook comments?

I CANNOT SELECT ANY GROUPS AND DATE DOESN'T LET ME CHOOSE SO I HAVE TO USE AMERICAN FORMAT BY MYSELF. THIS IS VERY BAD AND NEED FIX

Remember to update the save method on the Event model as well

If one has multiple events with the same name, occurring on different dates, their slugs will clash. So somehow there should be a way to differ between these.

There are two apparent solutions:

1. Simply put a number behind the slug and increment
2. Make all event urls rely on date (i.e. dikultur.dk/events/2014/09/17/fagrdsmde)

The user "dashboard" should have stuff like:

• created events and resources
• notifications of different sorts
• place to update profile
• other?

We should somehow try to collect email adresses on everybody - it would be nice to be able to do stuff like autosign people up for maillists when joining a group etc.

It would be nice to have a way to notify users when stuff happens. Such as (but not limited to):

• Someone joined your group
• A new comment on your event
• Your resource got upvoted, yay!

topic

This could be nice, but requires quite some groundwork.

It is, for instance, quite cumbersome to "just" get data from an event. For starters one can not just access event information using an access token from a facebook app, it has to be a user.

So in order to give Dikultur access to events, we would have to have a Dikultur facebook user, that then should be invited to that particular event.

Although it might be possible to get access using the user who wants to associate a dikultur event with a facebook one. That user would, in that case, have to be an administrator of the facebook event (as far as I can tell).

I'm not sure if that is something we want to do?

• Add group
• Edit group info
• Add users to group