search

OpenIoMeT / Iomet-wiki

The major Wiki page which is the entry point for this program.
4 stars 1 forks source link

To review and update repo #18

Open kaichih opened 7 years ago

kaichih commented 7 years ago

Kumar pointed out:

As, it's been long time, so i am updating the our github repo status. We can remove the repo if it's not required.

Iomet-wiki (Wiki + To track project overall status and plan) - active Weather Shimmer - if IIRC, it was almost ready. Fitbit Shimmer, Google Fit Shimmer - Empty Service Crawler - Empty Iomet-Shimmer-app - Empty (have basic template) openiomet.github.io - https://openiomet.github.io/ - Live iomet-testcases - Empty

Kumar, would you mind leading the discussion and help us to see how we should do with these repo? Thanks,

kaichih commented 6 years ago

@snowmantw , do you have any suggestion?

snowmantw commented 6 years ago

Sorry, I have been busy this week. Although I want to take a review for the whole thing and leave some comments, but I need to postpone it. I will try to utilize my spare time tomorrow, that my current task should be done. At least for the current stage.

snowmantw commented 6 years ago

But a rough and quick thought is we could start from a refreshing and core part of the project. Just put everything in one repo first, and we may need not remove the old one with reviewing. For that I think we just need to name it as iomet-core and we can start our user story milestone under that.

snowmantw commented 6 years ago

Okay. I have some spare time now. This is what I prepare to do:

  1. Quickly build a service from gateway to database on my own cloud machine
  2. Write a list about our first possible user story, focusing on concrete tech needs and those unclear parts
  3. Post the list and server info to everyone. That is, I'm not sure where to publish now, but I think we can figure out
snowmantw commented 6 years ago

And @kaichih , as you may know such personal server only have very limited resource to run the service. So I don't know how far this service can go. I guess we can use it for some pre-pre alpha test for the user story we pick, but any resource support will be appreciated.

kumarrishav commented 6 years ago

Forgot to mention about the domain. It's been already one year and we need to renew the domain if we want to retain those domain name. If domain is not a priority right now, then we can purchase it back whenever required. what do you guys say?

snowmantw commented 6 years ago

@kaichih Especially my machine can only afford 2GB RAM. It is not enough for service nowadays.

snowmantw commented 6 years ago

Well, although RAM is limited and I don't know how to handle the situation, at least I just built the service with such features:

  1. Experimental database (so it is not for real service that need real persistent data; just for testing and evaluating)
  2. Gateway middleware, so we can start to aggregate 3rd-party services for our own service
  3. Docker-based environment

My next step will start to write an app that uses 3rd-party APIs to do some "analysis", and then show them in dummy site that should look have potential to extend to a real web service we wish for this project. Meanwhile, guys, please keep working on our limited resources and project management issues. After all I can only focus on one thing at one time.