Before you describe your issue, idea or feature, please consider using this issue template.

Type of issue

Improvement detail

Short description on the issue

The server.js in stackle_api has some unused variables. Also the code is not properly formatted and indented.

Possible fix

I have opened a PR #77 which fixes this issue. I have reformatted and indented the code. I have also removed the unused variables.

Stackle does not have a testing framework integrated in to its back end.

Once the user logs in, the landing page view stays the same and navigating to profile or back to home does not do any change.

Search Button

While Searching Organizations Name, I found difficulty to submit search form details. Because there was no Search or Submit button and I've to use "Enter" usually user never expect this.

SOLUTION , if we add a Search Button then it would be really helpful.

Home Page

The home page was not looking attractive to the user, and we know that first Impression is the last impression.

BEFORE

AFTER

Profile Page

I've also tried to change the look of Profile page.

BEFORE

AFTER

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

Short description on the issue

Adding COR Module without writing custom middleware to handle cors issue. Redundant code on writing middleware for cors problem

Possible fix

Installing CORS module from the npm repository

What's the problem?

.gitignore files are not generated with gitignore.io

How can it be fixed?

I found two .gitignore (in stackle_app/ and stackle_api/) files which should be generated with gitignore.io. Stackle is built on MEAN stack so I'll use this technology (Node for _api and Angular for _app) to generate new .gitignore files.

Before you describe your issue, idea or feature, please consider using this issue template.

Type of issue

Improvement detail

Short description on the issue

We should explicitly provide the status code for all the responses.

Possible fix

I have opened a PR #82 for this.

package-lock.json should not be ignored and be committed to the repo.

The models need to be updated to use ES6 syntax and camelCase wherever possible.

I have created multiple PRs fixing each of the model.
#93 For user model
#92 For stack model
#91 For post model

Before you describe your issue, idea or feature, please consider using this issue template.

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

Short description on the issue

In the readme, under architecture section, better to add an architecture diagram rather than explaining the architecture in words

Possible fix

Adding an architecture diagram to the readme

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

In app/lib/validator.js at validateCommentOnPost function only req params( ie postid) is validated but request body ( ie. comment) is not validated.

Type of issue

• Bug / Error
• Idea / Feature
• Improvment detail

Short description on the issue

When reloading the page after a user is logged in, the navigation links to Home, Profile and the Logout is hidden even when the session is active.

Possible fix

Recheck if the a session is active upon page reload.

Implement OAuth 2.0 Authentication to application

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

Adding GitHub OAuth 2.0 to the application using PassportJS

Implement OAuth 2.0 for the application using PassportJS and maintain a server-side session to identify a request from users

File : https://github.com/scorelab/Stackle/blob/master/stackle_app/package.json

Result from http://package-json-validator.com/

{
  "valid": false,
  "errors": [
    "Missing required field: version"
  ],
  "warnings": [
    "Missing recommended field: description",
    "Missing recommended field: keywords",
    "Missing recommended field: bugs",
    "Missing recommended field: licenses",
    "Missing recommended field: author",
    "Missing recommended field: contributors",
    "Missing recommended field: repository"
  ],
  "recommendations": [
    "Missing optional field: homepage"
  ]
}

Hi! I would like to work on this issue.

When someone is referring to a particular program/code, there should be an automatic completion feature- similar to the way people are tagged on social media. After completion, it will be a link leading to the source code to view/edit. This way, it will be easier for users to share and discuss existing code.

Using the technologies : java, node, linux, windows, angular

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

Short description on the issue

stackle-app angular build failing due to insufficient arguements in post service.

Screenshots for the issue

Type of issue

• Bug / Error
• Idea / Feature
• Improvment detail

Short description of the issue

This allows testing the API in-process, without performing network calls, with all the benefits that it brings to the table: fast testing execution and getting coverage metrics of the code. It also allows deploying the same API under flexible and different network conditions. Bonus: better separation of concerns and cleaner code

Possible fix

Merging #73 😄

A good number of developers will not be using Windows as their operating system. Most of the open-source guys will be using Linux and some will be using MacOS. Please add the setup information for this project for both platforms.

Adding TestCase to Stacke_APIs

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

Adding Unit TestCases to test the basic endpoints of stackle Application

Using Mocha.JS and ChaiJS testing of basic endpoints of APIs can be carried out

Current front-end is written with AnguarJS. It is better to use Angular 4 fot the front end because then it will allow us to use Angular CLI which makes most of the work easy when deploying and building the app

The home page for Stackle is really vague and should contain more information about the project or it should at least by spread out evenly through the page. The information is sticked with the top and left and this makes the overall page look poor. The homepage needs to be updated to make the user experience better

Type of issue

• Bug / Error
• Idea / Feature
• Improvement detail

Short description of the issue

Every route is handling the error on its own which is just doubling the effort. It should handle all the error centrally.

Possible fix

I have created a PR #75. A middleware is added, which is working as an error handler. It will catch all the error thrown by any module.

THIS IS A NOT A REAL ISSUE BUT A PLACEHOLDER.

All the practising PRs for Google Code-In 2017 should refer this issue. PRs referring this issue will be closed without merging. Do not refer this issue if you are NOT submitting a practice PR and need your work merged.

I think it's good if there is Pull Request Template. So everyone can make a meaningful PR with ordered and simple structure.

Before you describe your issue, idea or feature, please consider using this issue template.

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

Short description on the issue

There should be gulp instead of grunt for building, testing and serving.

Possible fix

PR #101

Only relates to angular2 branch

Profile needs to contain details about the user. Data of the user can be fetched through the Github API. Need to discuss about what sort of information need to be displayed.
Following fields should be there

• Name
• Github handle
• No of public repositories
• Organization he's part of
• No of post he/she created on stackle
• Email
• Link to Github profile

Linked to #15

USE RES.JSON() INSTEAD OF RES.SEND()

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

res.json() includes json.stringyfy which is a more preferable way for JSON in express

The Spelling of Organisation is wrong as well as the spelling of building

Docker-compose is provided by default in windows and mac machines, but not for linux, while installing docker.

Readme instructions to setup the stackle project through docker, should clearly mention steps to install docker-compose on linux machine.

Before you describe your issue, idea or feature, please consider using this issue template.

Type of issue

Improvement detail

Short description on the issue

We should use ES6 const/let instead of var for declaring variables.

Possible fix

I have created a PR #79 to fix this.

Readme file needed to be updated including a project setup guidance, a brief overview of the app and license type.

File-https://github.com/scorelab/Stackle/blob/master/stackle_api/package.json
Package.json validator says valid, but threw few warnings.

{
"valid": true,
"warnings": [
"Missing recommended field: contributors"
]
}

An issue template would be really helpful in case of new users trying to look for solutions. Beginners may find it difficult to describe all the things in specific bug or a feature, so they can use the issue template to organize the issue in a better way.

There are a few grammatical errors/typos in the readme.
The introduction should read:

Stackle is a web communication portal aimed at providing Open Source organizations a platform to have discussions on their GitHub projects and their issues. It provides GitHub integration which allows the administrator of an organization to create a forum thread for the particular organization. Users signing in are able to view forums of the organizations they contribute to and engage in the forum discussions.

Currently, the README.md file includes the steps needed to set up compose on Linux. Many users on GitHub utilise macOS software, which is not compliant with the Linux directions. By creating a new code for downloading/setting up compose on macOS through Terminal, there will be many more contributors, pull requests, and projects. This new code will not only enhance production, but will largely influence collaboration of macOS users.

This change can be made by implementing a new code or adding on the README.md file so that there are steps for Linux downloading and macOS downloading, as well.

Handle the bad requests.

ADDING A STATUS KEY AND MESSAGE IN EVERY RESPONSE OBJECT SO THAT APIs CAN BE CONSUMED MORE EASILY

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

##Adding a status key in every response object. If an error occurs or data fetching failed then status: false otherwise if the response is successful then the status is true. This would make the API consumption more robust.

This repos should follow Gitflow workflow and follow are the items you have to check.

• There is a master branch and a develop branch.
• master branch is locked for direct commits and,
  • Require pull request reviews before merging is active
  • Require status checks to pass before merging is active
    • Require branches to be up to date before merging
    • Appropriate Status checks are required
  • Enforce all configured restrictions for administrators is active
  • Restrict only maintainers group can push to the master branch
• develop branch is locked for direct commits and,
  • Require pull request reviews before merging
    • Dismiss stale pull request approvals when new commits are pushed is active
  • Require pull request reviews before merging is active
  • Require status checks to pass before merging is active
    • Require branches to be up to date before merging
    • Appropriate Status checks are required
  • Enforce all configured restrictions for administrators is active
  • Restrict only maintainers group can push to the master branch

Creating Separate Routes files for user , stack and posts

Type of issue:

• Bug / Error
• Idea / Feature
• Improvement detail

Routes.js files should be break into separate routes files for post , stack, and user.

Only relates to angular2 branch
The component that will be used by the user to create an issue(post).
Need to decide on the fields that are needed and how the user inputs those data.
Following fields should be there

• Title
• Description
• Organization name (should automatically fill according to the organization user is in)
• tags
• link to issue (github)

Linked to #15

.gitignore can be generated by gitignore.io using Javascript

Before you describe your issue, idea or feauture, please consider using this issue template.

Type of issue

Bug / Error

Short description on the issue

Some of the routes were not sending the response.

Possible fix

I have opened a PR #84 to fix this.

Continuous Integration on Travis CI has been failing for all the PRs and when going through the logs it seems to be due to an issue in the configurations.

useMongoClient option while using connect function in mongoose

Type of issue:

• Bug / Error / Warning
• Idea / Feature
• Improvement detail

DeprecationWarning: open() is deprecated in mongoose >= 4.11.0, use openUri() instead, or set the useMongoClient option if using connect() or createConnection()

Only relates to angular2 branch

Improve the current Login page interface design. The current design does not seem attractive. It also needs a footer.
Current background image repeats as well. Make the interface responsive as well

Linked to #15

Stackle does not have a testing framework integrated in to its front end.

This repos has a Dockerfile but it does not contain any Label Schema labels. Following are the lables we have to have on our Dockers.

• name
• description Shoud be on user's perspective.
• url Should be SCoRe website
• vcs-url Should point to GitHub repo
• vcs-ref
• vendor Shoudl be "SCoRe Lab"
• version
• schema-version