In this project we will put all the apps developed in Projects B, C and D into the website that is developed in Project F. In this project you will pull the code from each project repository, compile it with the set of dependencies and package the apps, so that they can be easily called from the web site developed in project F.
Guys, please pay attention that NO-ONE uses static endpoints in their code.
At this stage stumbling upon already two repos that have a static route to bruck's server is unacceptable:
This is definetly, definetly your responsability :D So pay close attention to these things!!! As well as not-having database configuration options in the package init for some of the projects! careful!
Bruck's gonna tier down his server at some stage because I want to test if the packages are able to stand on their own feet.
How are we gonna handle the projects B and D. There are existing two solutions for those projects.
Apparently ProjectF will only include one Project.
So we have to come up we solutions for this problem. Are there any suggestions or ideas?
Should we merge the output?
A good strategy for testing the integration of the packages is to run the API locally and see if all the various requests that need to pass, are passing.
You can run A's project very easily, you just need a config file I have to provide you. For that, send me an email to any of my addresses.
Now I want to link it to travis. Therefore I need the code climate token which is generated in the settings.
But the settings do not show up for me. I found this wiki entry, which tells reasons, why it's not shown.
Can you help me find the reason?
Is it a lack of permissions?
this is the last chance: I will turn on my computer while having my cereal tomorrow at 7 am CET, you better make sure I get:
Which projects Emilyana, Ange and Javid whill be assigned to,
What your plan is (goals, milestones, assignments) - also via github issues, I don't care. But it should be there
Jonas, Florian, Alex you are on the safer side, as I have seen already some progress from you, but don't get too relaxed. I still want them plan! :D
The other ones: brace yourselves... Christian is coming!
Hey :)
As we are getting closer to deployment: Is there a recommendation which License we should specifiy in package.json?
I know there are things, which are more important, but the question just showed up in my mind.. @sacdallago
Please make sure all projects pass their builds, if they don't, revert the pull requests (for projects != A) and signal them to make sure they pass the build PRIOR to merging into develop
(Sorry E if I use your space but this was where it made more sense to me)
Everyone @Rostlab/js_cs_sose_2016_students :
There is a discussion going on here about where scraped data (!!! ONLY) needs to be updated. The options are:
Via API.
Via MediaWiki + running the scrapers again.
The implications are respectively:
The API opens for POST requests to directly manipulate scraped data.
The API doesn't allow modifying scraped data.
I'm all in for number 2 for the following reasons:
People cloning A's repo want to have the same data as their friends who cloned the repo 2 months earlier
Updating the data via GUI is the preferred method for normal human beings
Databases can easily be rebuilt and updated by re-scraping the data off the wiki, without worrying about concurrency (someone updated the data via API call, now someone else wants to update the data via re-scraping... What is right?)
A routine can be set up that will update the database periodically by re-scraping the data.
If you are against implementing option 2 please comment here within 2 days, otherwise I take it as everyone knows what's going on and is fine with that.
NPM API key format changed recently. If your deployment fails, check your API key in ~/.npmrc. http://docs.travis-ci.com/user/deployment/npm/
~/.npmrc size: 48
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v5.8.0/bin/node" "/home/travis/.nvm/versions/node/v5.8.0/bin/npm" "publish"
npm ERR! node v5.8.0
npm ERR! npm v3.7.3
npm ERR! toString failed
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR! /home/travis/build/Rostlab/JS16_ProjectC_Group10/npm-debug.log
The problem is not in API key, but you can check it.
I think the problem with nodejs version, try to google.
Manual publishing works.
this is just a reminder that both groups will work on this project, so you are actually 6 people. I suggest you make use of issues to decide project related stuff.
Remember that your project is extremely important and it would be wise for you to follow the development in other teams to figure out how to proceed!
You can obviously also suggest other teams how they should proceed in order to also facilitate your task ;)
@jonny3576
We have a problem, at the moment our app is fully running in the client, so if we want to integrate the sentiments analysis api, we have to handle the sensitive information needed for the config.
So we have two options:
make an own api which serves your information
you make it that we don't need passwords
A implements your functionalities, or the most important ones (would be more convenient for us)
Just to reming everyone again of the feature freezes and deadlines @Rostlab/js_cs_sose_2016_students
Project
Feature Freeze
Deadline
D
28.03
01.04
B
21.03
25.03
C
21.03
25.03
A
25.03
03.04
E
03.04
F
03.04
10.04
-
-
-
C Editor
03.04
10.04
I want a short update by the E representative of each team at each deadline or FF, even the ones that have already passed, how the integration is looking and where we stand.
Doesn't have to be a poem, just something like:
Project X Team Y
Feature Freeze:
Package delivered to NPM
Integrated in A
Integrated in F
Testing in progress
Code refactoring, not expecting major implementation changes (eg. function signatures & names & number)