Giter VIP home page Giter VIP logo

omega's Introduction

Omega Issue Tracker

Traditional issue trackers emphasize metadata and workflow and tend to add considerable overhead to a project. They make little sense for small, highly collaborative teams.

Ω is not traditional. It facilitates squashing issues, not documenting their life stories. No administrivia.

Initial version created during a Big Idea Day at Pulse Energy. More details

Demo

Give it a whirl at http://omegatracker.herokuapp.com. The redis database there is severely limited, but it should suffice as a demo.

Features

  • real-time

    • you never need to refresh to get updates
    • chat with team members in the same context
    • optional growl-like notifications even outside the browser (Chrome only, for now)
  • minimalist

    • everything you need on a single page
    • no need to sign up for yet another account with yet another password
    • use tags and flexible filtering to achieve any workflow you want
    • easy setup thanks to few dependencies
  • projects

    • create as many as you need (one per task/feature works well)
    • can mark 'top secret' if you want some privacy (for total security, host Ω behind your firewall)

Installation

Depending on your needs, you could create your project on the demo site. But to have Ω all to yourself, there are a couple of options:

  1. Install it on your own server

    1. Install node.js (which comes with npm)
    2. git clone [email protected]:wachunga/omega.git
    3. cd omega; npm install
  2. Install it in the cloud via a PaaS like Heroku, OpenShift, etc.

Usage

Start the server:

npm start

Or, to specify options:

node server [--redis] [--port <port>] [--pass <password>]

<redis> - use Redis for persistence instead of json on the file system.

<port> - Where the server listens for connections. Defaults to 1337.

<password> - Password required for accessing project admin section. Defaults to 'admin'. (Default username is also 'admin'.)

Then just open a browser to http://localhost:1337 or wherever.

Tests

Ω is unit tested using Jasmine. Open tests/SpecRunner.html to run the tests.

Contributors

 project: omega
 commits: 254
 files  : 105
 authors: 
   221  David Hirtle            87.0%
    24  Neil Gentleman          9.4%
     6  Drew Miller             2.4%
     2  Russell Porter          0.8%
     1  Farrin Reid             0.4%

Bugs

Our dev instance of Ω is not public (for now), but feel free to file issues on github as usual.

omega's People

Contributors

blakmatrix avatar mlazaric avatar nigelzor avatar russellporter avatar wachunga avatar xer0x avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

omega's Issues

cannot open Admin menu

hello! first of all thank you for your hard work.

I have setup Omega using default settings. When I click Admin button:

  1. I use login credentials
  2. three radio buttons briefly flash on screen
  3. radio buttons disappear. Please see attached screenshot.
    screen shot 2013-12-23 at 4 54 13 pm

I have tested using on Mac using Chrome 31.0, Safari 6.0.5, Firefox 21.0.1

OmegaEvent has no method 'slice' and 'push'

Here's a crash I just encountered running the current omega code:

   info  - transport end
   debug - cleared close timeout for client 776232242829913784
   debug - discarding transport
   debug - setting request GET /socket.io/1/xhr-polling/776232242829913784?t=1321083897421
   debug - setting poll timeout
   debug - clearing poll timeout
   debug - xhr-polling writing 7:::1+0
   debug - set close timeout for client 776232242829913784
   warn  - client not handshaken client should reconnect
   info  - transport end
   debug - cleared close timeout for client 776232242829913784
   debug - discarding transport
   debug - setting request GET /socket.io/1/xhr-polling/17654711111631277475?t=1321083897432

/home/rporter/Omega-Issue-Tracker/server.js:44
    socket.emit('history', history.slice(-HISTORY_ITEMS_TO_SHOW));
                                ^
TypeError: Object #<OmegaEvent> has no method 'slice'
    at SocketNamespace.<anonymous> (/home/rporter/Omega-Issue-Tracker/server.js:44:33)
    at SocketNamespace.$emit (events.js:64:17)
    at connect (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/namespace.js:291:10)
    at /home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/namespace.js:308:13
    at SocketNamespace.authorize (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/namespace.js:252:5)
    at SocketNamespace.handlePacket (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/namespace.js:302:14)
    at Manager.handleClient (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/manager.js:634:30)
    at Manager.handleHTTPRequest (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/manager.js:575:8)
    at Manager.handleRequest (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/manager.js:537:12)
    at Server.<anonymous> (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/manager.js:96:10)

Another crasher, probably related..

   debug - set close timeout for client 1286718887610965918
   debug - xhr-polling closed due to exceeded duration
   debug - clearing poll timeout
   debug - xhr-polling writing 8::
   debug - set close timeout for client 16529574812006731533
   debug - xhr-polling closed due to exceeded duration
   debug - setting request GET /socket.io/1/xhr-polling/1286718887610965918?t=1321148927185
   debug - setting poll timeout
   debug - discarding transport
   debug - cleared close timeout for client 1286718887610965918
   debug - setting request GET /socket.io/1/xhr-polling/16529574812006731533?t=1321148932331
   debug - setting poll timeout
   debug - discarding transport
   debug - cleared close timeout for client 16529574812006731533
   debug - xhr-polling received data packet 5:::{"name":"user message","args":["hmm"]}

/home/rporter/Omega-Issue-Tracker/server.js:133
        history.push(event);
          ^
TypeError: Object #<OmegaEvent> has no method 'push'
    at recordEvent (/home/rporter/Omega-Issue-Tracker/server.js:133:11)
    at Socket.<anonymous> (/home/rporter/Omega-Issue-Tracker/server.js:60:15)
    at Socket.$emit (events.js:64:17)
    at SocketNamespace.handlePacket (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/namespace.js:331:20)
    at Manager.onClientMessage (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/manager.js:436:38)
    at XHRPolling.onMessage (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/transport.js:387:20)
    at XHRPolling.onData (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/transports/http.js:89:10)
    at IncomingMessage.<anonymous> (/home/rporter/Omega-Issue-Tracker/node_modules/socket.io/lib/transports/http.js:60:12)
    at IncomingMessage.emit (events.js:61:17)
    at HTTPParser.onMessageComplete (http.js:133:23)

creating project shuts down server

hello,

When I create a new project, the server shuts down with this message:

Created new project { name: 'LPS',
createdDate: Tue Dec 24 2013 01:04:06 GMT+0000 (UTC),
slug: 'lps',
url: '/project/lps',
closed: false,
deleted: false,
unlisted: false }
wrote projects
24.43.52.122 - - [Tue, 24 Dec 2013 01:04:06 GMT] "POST /project HTTP/1.1" 200 22 "http://[serverinfo]:1337/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36"
Couldn't write projects file.

/usr/lib/node_modules/omega/server/lib/projectDao.js:50
throw err;
^
Error: ENOENT, open '/usr/lib/node_modules/omega/db/projects.json'

omega as a module

This gives more flexibility to work with omega, like sharing the same port with other services and so on.

I can contribute to this if you think this is good.

Problem with socket configuration

Hi i am trying to use this project but i am getting this error

TypeError: Cannot read property 'prototype' of undefined
    at Object.<anonymous> (<project-path>\omega\node_modules\socket.io\lib\store.js:35:41)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (<project-path>\omega\node_modules\socket.io\lib\manager.js:14:13)
    at Module._compile (module.js:569:30)

Project Names - List in Alphabetical Order

Just a FYI, I love Omega but noticed something that might be unintended.

As I create a list of projects, I notice that the list of project names on the front page is not alphabetical.

I think the list would be better if it was alphabetical.. what do you think?

git integration and issue discussion

This is actually very neat to use, love it.

We have a few projects versioning on private git servers, do you guys have plans that kinda integrates git commits / logs in it?

This also implies comment-like stack for each issues, which is also very handy when working with a team.

HELP.md needs update

I am planning to use omega for bug creation/management from node.js. I am unable to find any API's etc, basically how to use it from node. Please update the same of if there is any documentation please point out the same.

Unable to compile typescript files using npm version 3.8.3 and node v5.10.1

I am compiling typescript files using tsc -p src --outDir build it compiles properly. But when I give same in package.json in scripts as "tsc": "tsc -p src --outDir build" and do npm run tsc.

It gives me following error:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'tsc' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'pretsc', 'tsc', 'posttsc' ]
5 info lifecycle [email protected]pretsc: [email protected]
6 silly lifecycle [email protected]
pretsc: no script for pretsc, continuing
7 info lifecycle [email protected]tsc: [email protected]
8 verbose lifecycle [email protected]
tsc: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]tsc: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/satish/Documents/Office/Everteam-Fork/micro-services/records-webapp/src/main/webapp/node_modules/.bin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
10 verbose lifecycle [email protected]
tsc: CWD: /Users/satish/Documents/Office/Everteam-Fork/micro-services/records-webapp/src/main/webapp
11 silly lifecycle [email protected]tsc: Args: [ '-c', 'tsc -p src --outDir build' ]
12 silly lifecycle [email protected]
tsc: Returned: code: 2 signal: null
13 info lifecycle [email protected]~tsc: Failed to exec tsc script
14 verbose stack Error: [email protected] tsc: tsc -p src --outDir build
14 verbose stack Exit status 2
14 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
14 verbose stack at emitTwo (events.js:100:13)
14 verbose stack at EventEmitter.emit (events.js:185:7)
14 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack at emitTwo (events.js:100:13)
14 verbose stack at ChildProcess.emit (events.js:185:7)
14 verbose stack at maybeClose (internal/child_process.js:850:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid [email protected]
16 verbose cwd /Users/satish/Documents/Office/Everteam-Fork/micro-services/records-webapp/src/main/webapp
17 error Darwin 15.0.0
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "tsc"
19 error node v5.10.1
20 error npm v3.8.3
21 error code ELIFECYCLE
22 error [email protected] tsc: tsc -p src --outDir build
22 error Exit status 2
23 error Failed at the [email protected] tsc script 'tsc -p src --outDir build'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the Records package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error tsc -p src --outDir build
23 error You can get information on how to open an issue for this project with:
23 error npm bugs Records
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls Records
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

after clean install on smartosvm - node is unwritable db directory + some warnings

Hi,

  1. after clean install on smartos zone (git-node method) is unwritable db directory.
  2. some warnings in log:
  • connect deprecated multipart: use parser (multiparty, busboy, formidable) npm module instead at node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:56:20
  • connect deprecated limit: Restrict request size at location of read at node_modules/express/node_modules/connect/lib/middleware/multipart.js:86:15
  • connect deprecated methodOverride: use method-override npm module instead at server/app.js:71:17

I know, old project. But nice, so I use, I report :)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.