svimanet / info216 Goto Github PK

Setup maven deps file

We CANT have bloody libs pushed into the source

We will essentially be having feature branches. One issue pr branch.
The commits should fix ONE issue. If you have multiple changes: git add -p . where you stage chunks of code. Then you can git commit it with git commit -m "something"
ONE PULL-REQUEST PER FEATURE UNLESS SOMETHING ELSE IS AGREED UPON!

All Pull-Requests NEEDS to be reviewed and look by at least one other person.

// creates the new branch
git checkout -b morten/structure/refactored-files

// Do a lot of work now.

// Sync up with master branch
git checkout master
git pull origin master
git checkout <branch-name>
git rebase -i master

// Fix any merge conflicts if they occur.
// git add afterwards

git push origin <branch-name>
// Make PR from the webinteraface

Create issues and assign yourself to them if you want to solve it. Creating a Pull-Request before being ready is OK if you want opinions or suggestions to solve a problem.

Complains and/or improvements can be addressed here

Finding common interests and lift them to semantic data.

Who does what?

Project overview?
Architecture?
Keeping track of issues?
Documentation?

(I'll add more)

I'll however be the BDFL (Benevolent dictator for life!). So any disputes are resolved by my vote!

CC: @svimanet

• what do you want to make? - or: what is your application going to do? #6
• which datasets are you going to use? - or: where are you going to get your data from? are you using (only) semantic data, or will you need to lift (some of) them?
• which vocabularies are you going to use?
  • do you think you will need to create e new vocabulary/ontology, or extend existing ones?
• why is it a good idea to do this using semantic technologies? - or: what does your app do that was not possible (or at least not easy) to do before?
• what have you done so far (see below)?
• what are you planning to do in the next four weeks? #4
• have you got particular problems you need to address? See #6

Project proposal and goals.

App for planning or suggesting events based on weather. Include social media, such as friends with common interests.

Goals:

• Read weather data
• Get event feeds from Bergen
• Lift Data Into RDF/SPARQL
• Create front end
  • Create Swing interface
  • Create a phone app (Android?)
  • Create a webpage
• Do we need to write a report?

What are we going to do?

My suggestions are 2-3 hours working together, and 5 hours pr.week. I also think we should try to get a sprint BEFORE those 4 weeks are up.

I'm gone from 15th. So the weekend 4-6th or 11th-13th?
Who can have 2 guests? @svimanet? @Lillevik?

IIRC, we decided that the tabs or tiles of the app should be currentday+1 for each tile?
Then we parse the date into the current day. This could be done with SimpleDateFormat.

And stuffs needs to be generated based on the Sparql queries

Weather needs: "http://uib.no/info216/weather/" and date moved too a property.

Facebook friends needs: "http://uib.no/info216/Person" or something? Depends on the restrucutre

Event needs "http://uib.no/info216/event//"

We need to be able to ask "whats going on on monday", not just "Whats going on 2016-02-02"