open-learning-exchange / planet Goto Github PK

If you check in login and register , you find type="text" for password, So I think it needs to be change,

We need translation as we have done in Bell App. We need to integrate translation in angular project too.

Add functionality for register (become a member). Same feature as used in Bell.

examples

• our mdwiki on github
• turtleblocks on github

We should explore the Mango query language that has shown up in the CouchDB Fauxton interface to see if it is a better alternative to Map/Reduce views.

Feedback component should have a form which adds the following to a new feedback database:

• The current user adding the feedback
• The route the user is adding the feedback from
• An urgent flag (true/false)
• A type with Bug, Question, or Suggestion
• The text of the feedback. The BeLL-Apps has a rich text editor, but plain text should be fine.

Notes:

• The popup in the BeLL-Apps is very clunky, so let's try to start with some good style here.
• Since it's added as a popup it won't be another route, but a component that is a child of the home component.
• The Vagrantfile will need an update to create a feedback database when it is created.

After trying out GitHub's built in Projects, we've decided it doesn't improve upon waffle.io.

Could someone update the readme and mdwiki to point to this link instead of the project page?

https://waffle.io/ole-vi/planet

I think request need to send to the Manager only. Manager can approve or reject the request. Please check the process from Bell App.

Planet app will have 3 levels

• Center
• Nation
• Community

Each of these level will have different user roles

• Manager (possibly)
• Member (default)

Do we want to have single code base that will handle all levels of application with roles per level?
OR
Do we want to have code base per application level and control only user role view per that code base?

Could we have some ideas posted regarding how can we structure the application and manage code base.

We need a versioning an convention who saved in package.json of our npm package.

This is my proposal planet-{{version}}-{{commit_id}}

only version included in package.json the commit_id is only for artifact (docker) name.

Make a separate html file for each component. Don;t include the html code in typescript file . It is just for structure maintaining so that easy to find the bug .

https://docs.google.com/document/d/12YE4T1Wmvt8PT7Auilo4tSepK3RIm4xRtnPrlfhu7jw/edit?ts=59d286e9

please create log/pictures of experiments:

• create simple cluster of 2 instances
• create same only by script
• add an additional node
• and then remove one if the initial one
• and then the other initial one by script
• cluster of local node + public node
• __________ feel free to fix this ;P

Some people have experienced an error after initializing their virtual machine. It appears to only happen on occasion and has occurred on OSX and Windows, so the cause is unclear at this time.

I had implemented the AuthGuard based on this tutorial to include functionality to save the route the user requests in the query string and then redirect to that page after login.

Currently that's not working as intended, so needs fixing.

while opening planet app Bootstrap dropdown require Popper.js error occurs

I see that we will use tablet as main client of our app, why not designing our app as a responsive app?

Reference: https://www.w3schools.com/html/html_responsive.asp

https://github.com/ole-vi/planet/blob/d80af984ba5df1a8e388cda8ccc6eb241ac7597c/src/app/shared/couchdb.service.ts#L12

1. Hardcoding stuff is not good, we need to create a config file
2. Can we abstracting away that the things that connect to DB is the backend not the client via their browser, so that we can have multiple domain?

I made a few adjustments to the list of members that we're using to make it work with the CouchDB in the Admin Party mode. The problem is that this solution will not work if we decide to use CouchDB admins. I'll link the PR to this momentarily.

@dogi @lmmrssa @leonardmensah Do any of you have a thought on whether we should use CouchDB admins or leave the databases in Admin Party mode?

Similar to #82, the courses link should land on a list of available courses with buttons to manage the course. I'll try to get a screenshot of the design for you to work off of, but in the meantime something similar to the current BeLL-apps will be OK.

For the scope of this issue, please just add HTML & TypeScript code for this. I'd like broader CSS for tables to be used, and have included that as a separate issue #17. That being said, coordinating development with the work on the CSS to incorporate that into this PR would be great!

Add reusable table scss (either in style.scss or another file) to help implement mockup:

add resources to library

are our center s which are right now using 2 databases:

• nations

• communityregistrationrequests

• we should make a special usertype planet which is able to see, edit, create and delete new nations ...

• communityregistrationrequests will help us to show everything about communities on each nation

There was a video that was shared in channel for progressive application development. We could make use of some workers service or listeners that make our planet application run offline.

Docker and Docker Compose for Planet Project for Easy Deployment

Goals

• Creating an automatically builds docker image with versioning in mind
• Creating docker compose which involve couchdb for automated blackbox testing if necessary. And another with rpi-couchdb for deployment in raspberry automagically.
• Integrate docker with Vagrant for development
• Docker for development

"even though I didn’t know whether I was smart enough to complete it, was because I knew I was smart enough to start . Starting is what matters. I’ll be smarter by the finish." - James Bach

TODOs:
For Development (Assuming x86 machine), docker are created for x86 machines

• Create Docker for Angular Project and its Docker Compose | #27
• Add lets encrypt to the Docker Compose | Experiment with plain LE
• Integrate docker creation to CI Build using travis | WIP
• Using docker-compose as testing tools and integrate to CI Build
• Optimize docker and benchmark it with CPU/Mem Utilization

For Production/Community (Assuming ARM machine), docker are created for ARM machines

• Create Docker for Angular Project and its Docker Compose | #41
• Add lets encrypt to the Docker Compose | WIP
• Integrate docker creation to CI Build using travis | WIP
• Optimize docker and benchmark it with CPU/Mem Utilization

We'd like to create a script that would take create design documents (the courses validator is currently our only example).

The script should take the js files with the functions, stringify them, and push them into the correct CouchDB database.

Hi All

For all the maintainers and contributors, we need your help to create a contributions guide called CONTRIBUTING.md which saved in our root repository. Everyone who want to start taking this task can comment to this PR and link the pull request.

Please do drafts here

Since we will creating a CouchDB admin to secure the database, we should create an admin as the first user created in the app so our development can follow with the DB out of the "Admin Party" mode where any client can make any change to the database.

See the below for information on the HTTP request to create an admin user:
http://docs.couchdb.org/en/2.1.0/intro/security.html

The courses component will need to be implemented in a few steps. Let's start with the form so we can populate a courses database. It should:

• Add a document to the database with the form fields found in the current BeLL-Apps on a form submit click with the exception of the attachment
• Not add a document if a resource with the same title currently exists
• Be linked to from the COURSES nav link

Notes:

• No need to bother with the real text editor, you can just use a plain textbox description for now.

Integrate typescript and html linting to Travis CI for better consistency for humans and for computers

example:
https://www.npmjs.com/package/tslint-config-airbnb
https://github.com/airbnb/javascript

I think we need some loading gif or spinner when the page is loading.

Currently when a user is added the login page is reloaded. Modify the login.component.ts to create a session when the user is added.

I'm working on setting up automatic linting before any push to the repository. First thought is to have a pre-push hook, but there is a slight downside that git hooks aren't automatically stored in the repository so everyone would need to run a command to set up the hooks.

That's certainly the simplest solution, though, so I'll be setting this up for the meeting on Wednesday for everyone to take a look at.

I was wondering if we would be including angular universal to bell apps? It could help increase the perceived performance and since we will have to use node.js for that we could also abstract away CouchDB.

We'd like to have a way to fill our CouchDB on setup with mock data.

I think it'd be appropriate to start with the resources database, and if you are feeling up for it you can also fill the courses database.

The resource component will need to be implemented in a few steps. Let's start with the form so we can populate a resources database. It should:

• Add a document to the database with the form fields found in the current BeLL-Apps on a form submit click with the exception of the attachment
• Not add a document if a resource with the same title currently exists
• Be linked to from the LIBRARY nav link

Notes:

• Adding attachments to CouchDB adds a little more complexity to this than needed. Let's get the form working, then at a later time we can implement the attachments.
• Here's an image of the current form for reference:
  

The main navigation link for resources should land on a list view of all resources on the database with a link to add a new resource on the top and some filter/search functionality.

For the scope of this issue, please just add HTML & TypeScript code for this. I'd like broader CSS for tables to be used, and have included that as a separate issue #17. That being said, coordinating development with the work on the CSS to incorporate that into this PR would be great!

I'm going to create some npm scripts for Windows/Vagrant users to allow us to run the ng commands from the host machine (rather than having to vagrant ssh every time.