Skip to content

Commit d6eeea0

Browse files
committed
started on gh40 intro, edits
1 parent c753873 commit d6eeea0

File tree

3 files changed

+44
-2
lines changed

3 files changed

+44
-2
lines changed

_includes/past.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ <h3>past</h3>
1818
</div>
1919
</a>
2020
<a href="/carnac/">
21-
<div class="Tile two-h lime">
21+
<div class="Tile one lime">
2222
<img src="/img/tiles/carnac.png" /><h2>carnac</h2>
2323
</div>
2424
</a>

_posts/2012-02-20-carnac-review.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ What started out as an excuse to watch [Youtube](http://www.youtube.com/watch?v=
1111

1212
<br />
1313

14-
<center>![](/img/carnac-logo.png)</center>
14+
![](/img/carnac-logo.png)
1515

1616
## Progress!
1717

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
layout: post
3+
permalink: /github-for-outlook.html
4+
date: 2012-02-21 23:00
5+
title: "GitHub Tasks for Outlook"
6+
author: "@aeoth, @shiftkey and @tobin"
7+
comments: true
8+
---
9+
10+
Unfortunately this is looking like a busy week for many of us, so we're taking the time out this week to do a relatively straightforward idea which was spawned recently in the JabbR room.
11+
12+
While we are heavy users of GitHub, the notifications area of GitHub leaves much to be desired. We've already experimented with mobile clients and desktop clients to make this stuff easier, but a conversation last week around "why not use Outlook?" lead to a candid discussion and a simple specification.
13+
14+
## What will GHT4O do?
15+
16+
The tool should give you an overview of the important things you need to address for the projects you look after:
17+
18+
* New and updated Pull Requests.
19+
* New and updated Issues.
20+
* Display notifications as configured on GitHub.
21+
* View and respond to comments from inside Outlook.
22+
* Leverage Outlook features like email, labels and perhaps tasks to integrate GitHub work with the rest of your day-to-day work.
23+
24+
25+
## The technology under the hood
26+
27+
28+
29+
* Using @jakeginnivan's VSTO helper to build off as a framework
30+
* WPF App
31+
* Settings page to hook in to your github api key.
32+
* Enumerate your projects
33+
* Create a new issue from an email, assign it against a project, apply a label
34+
35+
36+
* Could also create a task in outlook for that, link back to the issue in Github
37+
38+
* Not sure what else we could do to add subsequent emails back to a task as comments
39+
40+
## How can I get involved?
41+
42+
The initial project is up on [GitHub](http://github.com/Code52/github-for-outlook). The [Trello board](https://trello.com/board/github-tasks-for-outlook/4f4234cdbfa22c0070ac4caa) will be updated over the course of today/tomorrow as we sketch out the UI and features to implement. And of course the [JabbR](http://jabbr.net/#/rooms/code52) room is worth checking out too!

0 commit comments

Comments
 (0)