This week generally has been interesting, I have actually for the first 
time gotten my hands dirty with setting up a project with all js dev 
dependencies, a task which i mostly usually left to scaffolding scripts for 
various setups. 
This week I have been able to do the following:

   - firstly i submitted a PR 
   here https://github.com/openwisp/django-netjsonconfig/pull/58 , to serve as 
   a temporal fix to the wrong schema validation in the advanced mode editor 
   on the vpn configs module of the django-netjsoncofig project. I intend to 
   fix this problem once and for all with the library I am building this 
   summer.
   - I have also setup my development environment for the project
   - I have setup the project structure, dependencies, dev dependencies, 
   build flows, linting rules, coding standards.
   - I have also included an examples folder which will be used for testing 
   UI features during development. And I intend to include a command to 
   automatically launch a server for the examples.
   - I also talked with the my mentor(@nemesisdesign) about the setup I had 
   and got his approval to proceed with it.
   - I made my first push to initialize my project's repo within the 
   openWisp organisation
   - Also officially became a member of the organisation on github.
   - My final setup package.json is given below
   {
     "name": "netjsonconfig-editor.js",
     "version": "1.0.0",
     "description": "Javascript based UI for editing netjson. contains and 
   advanced mode raw json editor and a GUI based netjson editor. Has inbuilt 
   validation following json-schema standards",
     "main": "index.js",
     "scripts": {
       "lint": "jshint --verbose src/js/**.js",
       "minify": "uglifyjs build/js/bundle.js -o build/js/bundle.min.js",
       "build": "npm-run-all build:*",
       "watch": "npm-run-all --parallel watch:*",
       "build:copy-css": "cpx 'src/css/**/*.*' temp/css",
       "watch:copy-css": "cpx 'src/css/**/*.*' temp/css --watch",
       "build:lint": "npm run lint",
       "watch:lint": "npm run lint",
       "build:browserify": "mkdir -p ./temp/js && browserify 
   src/js/index.js -o temp/js/bundle.js",
       "watch:browserify": "mkdir -p ./temp/js && watchify src/js/index.js 
   -o temp/js/bundle.js",
       "build:babel": "babel temp -d build",
       "watch:babel": "babel temp -d build",
       "build:minify": "npm run minify",
       "watch:minify": "npm run minify",
       "test": "echo \"Error: no test specified\" && exit 1"
     },
     "repository": {
       "type": "git",
       "url": "git+https://github.com/openwisp/netjsonconfig-editor.js";
     },
     "keywords": [
       "json",
       "editor",
       "netjson",
       "openWisp",
       "openWisp 2",
       "validation",
       "javascript",
       "UI",
       "django-netjsonconfig",
       "netjsonconfig-editor.js",
       "netjsonconfig",
       "editor.js"
     ],
     "author": "gastonche",
     "license": "ISC",
     "bugs": {
       "url": "https://github.com/openwisp/netjsonconfig-editor.js/issues";
     },
     "homepage": 
   "https://github.com/openwisp/netjsonconfig-editor.js#readme";,
     "dependencies": {
       "jquery": "^3.2.1"
     },
     "devDependencies": {
       "babel-cli": "^6.24.1",
       "babel-preset-env": "^1.5.1",
       "browserify": "^3.8.0",
       "cpx": "^1.5.0",
       "jshint": "latest",
       "mkdir": "*",
       "npm-run-all": "^4.0.0",
       "uglify-js": "^3.0.11",
       "watchify": "^3.8.0"
     }
   }
   
    A more detailed explanation of this flow can be found here 
    https://groups.google.com/d/topic/openwisp/wYJQ0qMz9qs/discussion 

Overall the community bonding period has been a great opportunity to 
understand the goals of the community, meet the members, and also see how 
important my project is to the growth of the community. I am looking 
forward to the effective commencement of coding come the 30th May.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to