Repo reorganisation

[Toshbrown]

An issue to document and track the impending repo reorganisation.

All repos under the me-box organisation are likely to be renamed or archived starting on the 13th July 2017

To Rename

Platform

• [x] databox-app-server --> platform-app-server
• [x] databox-sdk --> plaform-sdk

Core

• [x] databox-cm --> core-container-manager
• [x] databox-logstore --> core-syslog
• [x] databox-arbiter --> core-arbiter
• [x] oauth-intermediary --> core-oauth-intermediary
• [x] databox-export-service --> core-export-service

Store

• [x] databox-store-blob-mongo --> store-json
• [x] databox-store-iot --> store-timeseries
• [x] databox-store-hls-video --> store-video

Lib

• [x] python-databox --> lib-python-databox
• [x] node-databox --> lib-node-databox (Fix npm repo too (does it will have databox-prefix?))

Source

• [x] databox-datasource-mock --> source-sdk-mock
• [x] databox-source-mobile --> source-sensingkit

Driver

• [x] databox-driver-mobile --> driver-sensingkit
• [x] databox-driver-google-takeout --> driver-google-takeout
• [x] databox-driver-phillipshue --> driver-phillips-hue
• [x] databox-driver-twitter-stream --> driver-twitter
• [x] databox-os-monitor-driver --> driver-os-monitor

App

• [x] databox-app-light-graph --> app-light-graph
• [x] databox-app-twitter-sentiment --> app-twitter-sentiment
• [x] Occupancy-as-a-Service --> app-oaas

To Merge

Merge example apps and drivers into /samples in the language specific lib

• [x] lib-node + databox-driver-template-node + databox-app-template-node + databox-app-sensordemo-node + databox-driver-sensordemo-node
• [x] lib-python + databox-driver-template-python

To Archive

• [x] databox-local-registry
• [x] databox-netdev
• [x] databox-store-mock
• [x] ready-steady-cook
• [x] databox-vagrant
• [x] databox-store-blob (Remember to update manifests to use store-json)
• [x] databox-app-mock
• [x] databox-export-destination
• [x] databox-store-passthrough
• [x] databox-driver-template-node
• [x] databox-app-template-node
• [x] databox-app-sensordemo-node
• [x] databox-driver-sensordemo-node
• [x] databox-app-template-java

[mor1]

Nice, thanks :) What is the "npm repo"?

[Toshbrown]

https://www.npmjs.com/package/node-databox

It's where node pulls in its packages from ;-)

[mor1]

Ah, gotcha. (Yes, I know what NPM is :) We would still want to publish the library, obviously. (And the OCaml one into OPAM, the Python one into whatever the current set of Python packaging systems is, and so on.)

I don't know how much control one has over packaging and distribution for Node-- is it reasonable to include samples in the package? If not, then perhaps that's an argument for splitting node-databox from node-databox-samples or something?

On 13 July 2017 at 08:11, toshbrown notifications@github.com wrote:

https://www.npmjs.com/package/node-databox

It's where node pulls in its packages from ;-)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/me-box/databox/issues/52#issuecomment-314992240, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKP4CwxVttf2Oc3Heit7X7xtWMkzFsPks5sNcMFgaJpZM4OVWCu .

-- Richard Mortier mort@cantab.net

[yousefamar]

AFAIK what people normally do is have example dirs (and source dirs for things that compile to JS) in .npmignore and build dir in .gitingore, so I think we can just do that too. Not sure if there are similar things for other package managers.

[Toshbrown]

I decided to name the libraries using this schema

lib-{lang}-databox

This way when published to external places they will be findable by searching for databox.

[mor1]

cool, let's go with that for now. if further decomposition is required in future (eg to lib vs samples) we'll deal with it then