rostlab / js16_projecte Goto Github PK

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:

• https://github.com/Rostlab/JS16_ProjectB_Group6/blob/b0b138d72c513fca2526b7a3d31b2f8914fc7867/api-handler/dataAccess.js#L11
• https://github.com/Rostlab/JS16_ProjectD_Group5/blob/2a48bb68d63f4b3214e7b0c063bfb9dc254bdc8d/db/dbA.js#L36

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.

C10 did an excellent job in making their module... modular! https://github.com/Rostlab/JS16_ProjectC_Group10/wiki/Init-New-GoT-Map-and-Options

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?

Hi E people:

today I figured out two problems of D5 by simply looking at the logs of the API .

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.

Cheers.

I'm currently setting up code climate for Project A and Project F.

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?

@sacdallago

Here are a list of items we should take care after all said and done (feel free to suggest more items):

• rename github repos to something more meaningful then JS16..
• Update about page with links to GitHub repos
• Collect all documentation into a single location under our control (g docs?)
• Backup all databases and create a known offsite backup
• Open a got.issues repositories that will collect user feedback
• bask in the warmth of glory

Dear @/all,

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!

Remember: cereal happens at 7 a.m.!

Hey Guys our Project E representative is not available over the holidays and I was hoping maybe someone else from this team can help us.

I have no idea why our build is failing. Can someone have a look at this please
https://travis-ci.org/Rostlab/JS16_ProjectD_Group5/builds/118503829

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:

1. Via API.
2. Via MediaWiki + running the scrapers again.

The implications are respectively:

1. The API opens for POST requests to directly manipulate scraped data.
2. 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 publishing doesn't work on Travis.

build output of travis, project C10:

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.

Hey guys,
I know its kind of late how have you planned to provide b7 and b6?
And how far are you?

Dear Group 1 and Group 11,

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 ;)

Best regards,
Chris

It would be great, if y'all could get started writing unit tests for our api. I've setup TravisCI and nodeunit already. Find an example unit test here:
https://github.com/Rostlab/JS16_ProjectA/tree/master/test

Please test against the documentation here: https://got-api.bruck.me/doc

Do local function calls, not against the public api!

@Rostlab/js_cs_sose_2016_students Wait for the emaaaaiiiilll 💃

• https://www.facebook.com/aSongOfIceAndData
• https://plus.google.com/116097558064950719723
• https://twitter.com/asoiad

Do you already know how we are going to include your components?

Quote from google groups:

make sure that team F knows how to add this modules to web site

Greets
Yasar :)

@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)

Do you have other suggestions?

From now got* is gonna be the official title of all npm published packages.

Rostlab/JS16_ProjectC_Group10#116 (comment)

Notifications:
@TheZoker @CavidSalahov @jonny3576 @AngeKouemo @Emiliyana

https://quickleft.com/blog/creating-and-publishing-a-node-js-module/

@sacdallago I have a question.

The project B are going to store the results in the database, according to this Rostlab/JS16_ProjectB_Group7#7.

Does it mean that they don't need package any more?
Project F can just use the results from database via API.

https://docs.travis-ci.com/user/deployment/npm/

should be easy :)

Just to reming everyone again of the feature freezes and deadlines @Rostlab/js_cs_sose_2016_students

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)

Deadline:

• 30% test coverage
• ...

Yellou guys, I just wanna check something:

• Rostlab/JS16_ProjectB_Group7#12
• Rostlab/JS16_ProjectC_Group10#161
• Rostlab/JS16_ProjectF#52
• Rostlab/JS16_ProjectB_Group6#50

is not something you may want to gitignore, right?