Contribute to Open Source. Search issue labels to find the right project for you!

Upload original work to Github


Hey, to get the original set of work onto Github, start with this:

  • Clone the repo link for SensorFog
  • Copy/Paste Arduino + RaspberryPi project folders into the cloned repo
  • In the command line( from SensorFog directory ): git add .
  • In the command line: `git commit -m “Enter your message here”
  • In the command line: git push
  • Sip tea slowly
Updated 27/06/2017 01:57

write a linguist client library in Go; remove concept of "detect scripts"


There appears to be a ported version of GitHub’s linguist project ported to Go but it’s not in the form of a client library where we could actually use it as an importable package like:

import (

func main() {
    project := repository.New(".")

>>> Ruby

This would be a good way to remove the concept of writing “detect scripts” for each of the packs. We could detect the language pack, then create the project based on the language pack.

Additional thoughts: perhaps If linguist detects a language pack we do not have support for yet, we could potentially ask if the user would like to send a report to draft in the form of an enhancement request.

Updated 27/06/2017 01:44

Implement QueryBuilder


The purpose of QueryBuilder class is to convert URI/URL query key-values to Camo-acceptable options. Here’s an example:

  1. send GET request to the endpoint: /companies?match=name>goo&show=name,location,logo
  2. the req value grabbed by express will convert the query to: { match: 'name>goo', show: 'name,location,logo', }
  3. With QueryBuilder’s conversion, we should be able to do following Camo statement: const result = await Company.find({ name: 'goo' }, { populate: ['name', 'location', 'logo'] });

Tasks: - [ ] Create a separate QueryBuilder class with its constructor taking an object as a parameter - [ ] Create a “private” translator function that will convert URL query properties to Camo-acceptable properties - [ ] Create a “private” parser function that will parse URL query values to Camo-acceptable values - [ ] Create a getter instance function for query (e.g. { name: 'goo' }) - [ ] Create a getter instance function for options (e.g. { populate: ['name', 'location', 'logo'] }) - [ ] Create a unit test for QueryBuilder (ensure it covers at least 80% of QueryBulider class) - [ ] Manually test e2e flow to make sure QueryBuilder is working correctly

Query Specs: TBD

Updated 27/06/2017 01:40

Show tweet intent button


ツイートしたい、けどツイッターを見に行くと時間を無駄にしてしまう… そう思わせて、すかさず「ツイートするボタン」を与える。タイムラインを見ずにツイートできるので、思わぬ誘惑に引っかかって時間を浪費することがなくなる!

Updated 27/06/2017 01:21

KCRM Analytics page updates

  • add date selector control to default template. This should control data sensitive data
  • change the 3 metrics to the following, and make these seperate components from the leadman app
    • number of new leads created
    • leads lost (ie cancelled)
    • leads won (ie closed)
  • show the total number inside the circle
  • add new components for quotes data (from payments app)
    • number of proposals issued
    • number of quotes issued
    • number of quotes accepted


Updated 27/06/2017 01:18

Find & Replace Notes


Michael Matzdorff asks:

“find and replace” notes text a possibility

There’s a few ways we could do this:

  • Database Manipulation (best from a user perspective, but risky as we’re messing with the database)
  • XML Manipulation (slightly more annoying for the end user, but less risky. Need to get our FCPXML API working first)
  • GUI Scripting (easiest - but less reliable from an end user perspective)

Something to ponder!

Updated 27/06/2017 01:09

Changes up snap logic and cleans up test app


Creates an abstract class for snapping unblocking the ability to add SnapToGrid logic inside the UI module. It also improves the logic being used for calculating the user bearing to snap properly. Before merging, this PR still needs test added.

btw the reason for the large line change size is the addition of a GeoJSON file (sorry 😄 ).

cc: @ericrwolfe @danesfeder @zugaldia

Updated 27/06/2017 01:04

Document bulk create (sync) endpoint


A check should be added on POSTs to /api/documents that checks to see if the object submitted is an array or a simple object. This endpoint will be used by client documents that store Sylow data client-side, and need to periodically sync their contents back to the server, rather than creating one API call for each change that occurs.

For simple objects submitted to the server, it will assume that it represents one document that is to be created (current behaviour). For arrays, the server will assume it is a series of documents to be upserted or indeed deleted. The server will start by iterating over the documents in question. If the document consists of a document ID and a simple deleted: true flag, the document in the database should be deleted (provided the user has the rights to do so, of course). All documents in the request that do not have this deleted flag should be saved to the database using an upsert function. The server must refuse to save a document if the user does not have the right to modify the document in question.

Updated 27/06/2017 00:45

Say short message of taking care the user


サイコロを振り終わったあと、サイコロの目に応じた言葉をユーザーにかける 。メッセージは常に出ていて、サイコロをふるたびにアニメーションとともに更新される (英語と日本語が両方を書いたら、ちょっとした英語の勉強にもなるかも) Related: マイクラのトップ画面、ニコニコの右上

e.g. - I have been awhile. ひさしぶり〜 - Have a nice day! よい1日を!

Updated 27/06/2017 00:45

Potential: Command and subcommand API


Right now all commands are handled through the EssentialsCommand class, which does not support automated parameter parsing nor subcommands. As of ebaf3e128f1bcc54840adcc5dd5e458d66ce5c5e there are multiple commands that have, in themselves, various subcommands with various functions. I propose that we make a relatively simple and automated Command / Subcommand API to shorten command declarations, simplify code and improve readability. This change would be implemented in tandem with #6 and #9

Updated 27/06/2017 00:37

Add $adminvm policy keyword


Since dom0 is special, it’s better to refer to it by special policy keyword, instead of name like any other VM. For example this will make $anyvm not matching $adminvm more logical. Also, dom0 name is Xen specific, so we will need some flexibility here when porting Qubes to other hypervisor anyway.

For Qubes 4.0, policy will recognize both dom0 and $adminvm.

Cc @rootkovska

Updated 27/06/2017 00:35

Sanitize form input fields


Form input for the login/password fields as well as the url input and tag input fields is not sanitized.

The inputs in these fields should be sanitized to ensure these fields do not open an attack vector for malicious code.

Updated 27/06/2017 00:33

Additional action on cap


Upon capping when updating a position, optionally perform some action. This could, for instance, be used to set a “grounded” flag when a player lands on the floor, or schedule components which are no longer visible on the screen to be destroyed.

Related: #2, capping.

Updated 27/06/2017 00:30

Write a function for calculating the expected cost per data point.


Prerequisite Issues

  • [ ] #2

Issue Overview

The expected cost per data point is simply the expected cost for a dataset divided by the number of data points in the dataset. It is a way of normalizing expected cost such that logical comparisons may be made between the expected cost of two datasets of different size.

Expected Cost Per Data Point

Where |D| is the number of records in the dataset D. For information on what E represents, see Issue #2 .

Tasks to Close Issue

  • [ ] Design a function signature for this function. It can be presented in a reply to this issue.
  • [ ] Write unit tests for the function which will sufficiently test it.
  • [ ] Implement the function such that it passes all the unit tests.
  • [ ] Generate documentation.
Updated 27/06/2017 00:22

Reposition with built-in capping


Add methods to ComponentFactory which updates the position but ensures that it does not exceed a given minimum or maximum value.

The updatePosition method is the most critical place to have this, but adding all bounds at the same time might be unwieldy. I’m considering creating updateX and updateY methods which are overloaded with minimum and maximum limits.

Updated 27/06/2017 00:26

imlazy library


Hi @lubien,

I’m looking for libraries that uses iterables to make lazy operations to learn different solution approaches. I think that you could be interested in imlazy library.


Updated 27/06/2017 01:48 1 Comments

SDLBox dispatch collision events


Feature: SDLBox should fire collision events upon noticing that two Components are colliding.

Subfeature: “Collision categories”, Components only collide with other Components of the same category. Each Component might want to belong to multiple categories. Special meta-categories “ALL” and/or “NONE”? More maps for registering and retrieving categories?

Updated 27/06/2017 00:14

Build shopping list


We want to know what it will cost to provide particular functionality, i.e.:

Cost for a arduino, wifi shield, ½/4/8 relay, sensor Cost for arduino, wifi shield, sensor(s) Cost for arduino, ethernet shield, relay(s) etc.

To be able to budget what a piece of automation (input and/or output) will cost to implement.

Updated 27/06/2017 00:04

Add duty of transparency when prioritizing against a circle strategy


As a Lead Link, I’d like to be able to count on people to call out when they are prioritizing something substantial against the guidance of a circle-level strategy or prioritization, so that I can use strategies to guide the circle while knowing I’ll get the visibility and can consider how to respond to any prioritizations that are opposite my published strategies. This will also help people understand that a strategy isn’t a mandate, but just a heuristic to generally privilege when most else is equal.

Updated 27/06/2017 00:00

Fork me on GitHub