Open danhammer opened 11 years ago
yup, sander and I spoke a while about this after the emails this morning. here is a preliminary outline
## project name
### subproject title
- task (ongoing)
+ new task
* broadcast
? question or seeking input
you can also combine them (especially useful for broadcasting questions). an example might be
## forma
### ee integration
+ testing the extraction of recent deforestation in protected areas
*? i'm going to be running a lot of test cycles, is it time to upgrade our EC2 machine, thoughts?
## wri
* Just got Data Lab funds in the bank!!!
+ finalize contracts
damn i like that syntax
On Tue, Apr 16, 2013 at 10:41 AM, Andrew W. Hill notifications@github.comwrote:
yup, sander and I spoke a while about this after the emails this morning. here is a preliminary outline
project name
subproject title
- task (ongoing)+ new task* broadcast ? question or seeking input
you can also combine them (especially useful for broadcasting questions). an example might be
forma
ee integration
- testing the extraction of recent deforestation in protected areas*? i'm going to be running a lot of test cycles, is it time to upgrade our EC2 machine, thoughts?
wri
- Just got Data Lab funds in the bank!!!+ finalize contracts
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16459745 .
This makes it really nice to have a command line client for submitting reports. Shit, this actually just made me think of another enhancement for the future. Continuous log mode. So through the day
$ grr config mode continuous $ git commit -a -m 'fucking nailed that bug down' $ git push origin master (right to the fucking master mf) $ grr msg add '- just fixed the security hole in CSRF'
on a mobile device # is a pain to get to. Maybe there can be an optional alternate, like -- Maybe?
On Apr 16, 2013, at 10:42 AM, Aaron Steele notifications@github.com wrote:
damn i like that syntax
On Tue, Apr 16, 2013 at 10:41 AM, Andrew W. Hill notifications@github.comwrote:
yup, sander and I spoke a while about this after the emails this morning. here is a preliminary outline
project name
subproject title
- task (ongoing)+ new task* broadcast ? question or seeking input
you can also combine them (especially useful for broadcasting questions). an example might be
forma
ee integration
- testing the extraction of recent deforestation in protected areas*? i'm going to be running a lot of test cycles, is it time to upgrade our EC2 machine, thoughts?
wri
- Just got Data Lab funds in the bank!!!+ finalize contracts
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16459745 .
— Reply to this email directly or view it on GitHub.
I am really into this. My question, now, is how to organize the subtrees. Suppose I want to cross list a project and team. What then? Not in scope? Ignore if this takes you off track.
On Tue, Apr 16, 2013 at 10:45 AM, Andrew W. Hill notifications@github.comwrote:
This makes it really nice to have a command line client for submitting reports. Shit, this actually just made me think of another enhancement for the future. Daily log mode. So through the day
$ grr config mode log $ git commit -a -m 'fucking nailed that bug down' $ git push origin master (right to the fucking master mf) $ grr msg add '- just fixed the security hole in CSRF'
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460041 .
Yesterday, I had it in 'continuous' mode, it was a monday (which in my conf is a workday) and i never added anything.
Today, an email comes
Andrew,
You have grr in continuous mode but we never saw any updates yesterday. How was the beach?
If you actually did some things yesterday, just respond to this email with some highlights.
Cheers,
Robot
Or have grr watch repos for commits? Either way, I like this idea a lot.
On Apr 16, 2013, at 10:45 AM, "Andrew W. Hill" notifications@github.com wrote:
This makes it really nice to have a command line client for submitting reports. Shit, this actually just made me think of another enhancement for the future. Daily log mode. So through the day
$ grr config mode log $ git commit -a -m 'fucking nailed that bug down' $ git push origin master (right to the fucking master mf) $ grr msg add '- just fixed the security hole in CSRF'
— Reply to this email directly or view it on GitHub.
how was the beach ha!
On Tue, Apr 16, 2013 at 10:49 AM, Robin Kraft notifications@github.comwrote:
Or have grr watch repos for commits? Either way, I like this idea a lot.
On Apr 16, 2013, at 10:45 AM, "Andrew W. Hill" notifications@github.com wrote:
This makes it really nice to have a command line client for submitting reports. Shit, this actually just made me think of another enhancement for the future. Daily log mode. So through the day
$ grr config mode log $ git commit -a -m 'fucking nailed that bug down' $ git push origin master (right to the fucking master mf) $ grr msg add '- just fixed the security hole in CSRF'
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460275 .
i'm in a google hangout with rob and a guy who sounds exactly, EXACTLY like this guy:
http://24.media.tumblr.com/tumblr_m2d9drArf21rtx9who1_500.gif
i keep on having to mute my video. cracking up... MUTE
On Tue, Apr 16, 2013 at 10:50 AM, Aaron Steele eightysteele@gmail.comwrote:
how was the beach ha!
On Tue, Apr 16, 2013 at 10:49 AM, Robin Kraft notifications@github.comwrote:
Or have grr watch repos for commits? Either way, I like this idea a lot.
On Apr 16, 2013, at 10:45 AM, "Andrew W. Hill" notifications@github.com wrote:
This makes it really nice to have a command line client for submitting reports. Shit, this actually just made me think of another enhancement for the future. Daily log mode. So through the day
$ grr config mode log $ git commit -a -m 'fucking nailed that bug down' $ git push origin master (right to the fucking master mf) $ grr msg add '- just fixed the security hole in CSRF'
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460275 .
haha! dude, continuous mode … whoaaaa … thats so nice. so good for asking questions too… like you can record an error output from anything.
On Tuesday, April 16, 2013 at 10:49 AM, Andrew W. Hill wrote:
Yesterday, I had it in 'continuous' mode, it was a monday (which in my conf is a workday) and i never added anything. Today, an email comes Andrew, You have grr in continuous mode but we never saw any updates yesterday. How was the beach? If you actually did some things yesterday, just respond to this email with some highlights. Cheers, Robot
— Reply to this email directly or view it on GitHub (https://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460244).
We were talking a bit about a very flexible summary interface. where you could answer questions like
What were all the new tasks today in the project WRI? What were all the broadcasts today? What were all the mentioned tasks today in team Alpha? What were all the tasks today that referenced 'python'
we need an operator syntax for random comments and questions and jokes. maybe:
! 8=================)
On Tue, Apr 16, 2013 at 10:51 AM, Aaron Steele eightysteele@gmail.comwrote:
i'm in a google hangout with rob and a guy who sounds exactly, EXACTLY like this guy:
http://24.media.tumblr.com/tumblr_m2d9drArf21rtx9who1_500.gif
i keep on having to mute my video. cracking up... MUTE
On Tue, Apr 16, 2013 at 10:50 AM, Aaron Steele eightysteele@gmail.comwrote:
how was the beach ha!
On Tue, Apr 16, 2013 at 10:49 AM, Robin Kraft notifications@github.comwrote:
Or have grr watch repos for commits? Either way, I like this idea a lot.
On Apr 16, 2013, at 10:45 AM, "Andrew W. Hill" notifications@github.com wrote:
This makes it really nice to have a command line client for submitting reports. Shit, this actually just made me think of another enhancement for the future. Daily log mode. So through the day
$ grr config mode log $ git commit -a -m 'fucking nailed that bug down' $ git push origin master (right to the fucking master mf) $ grr msg add '- just fixed the security hole in CSRF'
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460275 .
whoa...
On Tue, Apr 16, 2013 at 10:52 AM, Andrew W. Hill notifications@github.comwrote:
We were talking a bit about a very flexible summary interface. where you could answer questions like
What were all the new tasks today in the project WRI? What were all the broadcasts today? What were all the mentioned tasks today in team Alpha? What were all the tasks today that referenced 'python'
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460430 .
So if you ask, What were all the broadcasts today? A response might look like
@sanderpick just joined the team @danhammer announced "We just got Data Lab money"
@sanderpick announced that the first mobile beta is available for testing
@dan, def gonna roll in projects .. so you can get project updates / news, or team updates / news .. or the combo
On Tuesday, April 16, 2013 at 10:49 AM, Dan wrote:
I am really into this. My question, now, is how to organize the subtrees.
Suppose I want to cross list a project and team. What then? Not in
scope? Ignore if this takes you off track.On Tue, Apr 16, 2013 at 10:45 AM, Andrew W. Hill
<notifications@github.com (mailto:notifications@github.com)>wrote:This makes it really nice to have a command line client for submitting
reports. Shit, this actually just made me think of another enhancement for
the future. Daily log mode. So through the day$ grr config mode log
$ git commit -a -m 'fucking nailed that bug down'
$ git push origin master (right to the fucking master mf)
$ grr msg add '- just fixed the security hole in CSRF'—
Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460041
.— Reply to this email directly or view it on GitHub (https://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460232).
Hhhhhhhhh
On Tue, Apr 16, 2013, at 10:53 AM, Aaron Steele wrote:
whoa...
On Tue, Apr 16, 2013 at 10:52 AM, Andrew W. Hill
notifications@github.comwrote:
We were talking a bit about a very flexible summary interface. where you
could answer questions like
What were all the new tasks today in the project WRI?
What were all the broadcasts today?
What were all the mentioned tasks today in team Alpha?
What were all the tasks today that referenced 'python'
—
Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment -16460430
.
—
Reply to this email directly or [1]view it on GitHub. [RkOat9Y1_FdXL0zywX1whlOlCjwEEuiiKMhtv7O6SFmlyGKZSFW-cxW9rBcOgrIU.gif]
References
+1 for mobile ease
On Tuesday, April 16, 2013 at 10:48 AM, Robin Kraft wrote:
on a mobile device # is a pain to get to. Maybe there can be an optional alternate, like -- Maybe?
On Apr 16, 2013, at 10:42 AM, Aaron Steele <notifications@github.com (mailto:notifications@github.com)> wrote:
damn i like that syntax
On Tue, Apr 16, 2013 at 10:41 AM, Andrew W. Hill
<notifications@github.com (mailto:notifications@github.com)>wrote:yup, sander and I spoke a while about this after the emails this morning.
here is a preliminary outlineproject name
subproject title
- task (ongoing)+ new task* broadcast ? question or seeking input
you can also combine them (especially useful for broadcasting questions).
an example might beforma
ee integration
- testing the extraction of recent deforestation in protected areas*? i'm going to be running a lot of test cycles, is it time to upgrade our EC2 machine, thoughts?
wri
- Just got Data Lab funds in the bank!!!+ finalize contracts
—
Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16459745
.—
Reply to this email directly or view it on GitHub.— Reply to this email directly or view it on GitHub (https://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460182).
So it does some nice organization for you just based on the projects you watch. Oh, and if you have team members that aren't part of projects or somethign, it could be more like
@sanderpick just joined the team @danhammer announced "We just got Data Lab money"
@sanderpick announced that the first mobile beta is available for testing
@robinkraft is pondering mortality @sanderpick [QUESTION] does anybody have an extra site licence for xyz
Then you could imagine how it changes if you ask,
Show me all questions by user?
Does anybody have an extra site...
Do we need to upgrade our EC2...
you could use the search interface to define how your daily summary was organized too! maybe i really want an email of all daily broadcasts but only want to skim tasks by going to the site directly
dude this is so simple. it's like git for getting shit done.
On Tue, Apr 16, 2013 at 10:58 AM, Andrew W. Hill notifications@github.comwrote:
you could use the search interface to define how your daily summary was organized too! maybe i really want an email of all daily broadcasts but only want to skim tasks by going to the site directly
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460845 .
exactly
grrit
On Tue, Apr 16, 2013 at 11:00 AM, Andrew W. Hill notifications@github.comwrote:
exactly
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16460971 .
Just to be clear, this stuff we're talking about will be available via the CLI, right? I won't have to write emails to grr.io, right?
On Tue, Apr 16, 2013, at 11:00 AM, Andrew W. Hill wrote:
exactly
—
Reply to this email directly or [1]view it on GitHub. [RkOat9Y1_FdXL0zywX1whlOlCjwEEuiiKMhtv7O6SFmlyGKZSFW-cxW9rBcOgrIU.gif]
References
i was saying too, the the two uses i think we try to solve beautiful are
I think either cli or email mode should be available
for the daily morning email replies ... right now you get one from each person on each of your teams.. i wonder if it makes sense to consolidate all that into one email ... so everyone has like 1hour to reply to those emails ... dunno
well, what if i set what time i got the emails? then i just got an email of all updates that had happened since my last email?
that is nice and flexible because maybe i only want an email on wednesday and friday (we can dev this far in the future), but it would still work
also, if i ran grr in continuous mode, it would let me add updates all day long, and until your email went out they would still make it into your daily summary
nice dude, that is perf
just reminded me of https://bufferapp.com/ totally diff project, but they have a nice scheduler. you pick a time of day and days of the week. if you upgrade to the paid plan you can pick multiple schedules based on different things! business modellllllss
we have a clear problem statement, and a solid hypothesis on how to solve. how nice is that?!
amaz
so sick guys. feels big.
On Tue, Apr 16, 2013 at 11:05 AM, Andrew W. Hill notifications@github.comwrote:
amaz
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16461344 .
! 8=================)
On Tue, Apr 16, 2013, at 11:07 AM, Aaron Steele wrote:
so sick guys. feels big.
On Tue, Apr 16, 2013 at 11:05 AM, Andrew W. Hill
notifications@github.comwrote:
amaz
—
Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment -16461344
.
—
Reply to this email directly or [1]view it on GitHub. [RkOat9Y1_FdXL0zywX1whlOlCjwEEuiiKMhtv7O6SFmlyGKZSFW-cxW9rBcOgrIU.gif]
References
If there is some structure -- albeit loose structure -- then we can start testing algorithms to suggest "hot streaks" a la NBA Jam or Doldrums a la the Phantom Tollbooth. A quick Poisson modeling, detecting clear outliers in the Bayesian priors on the waiting parameter. This shouldn't be the focus, at all, but may offer a neat feature.
haha. Drop the mic. Boom.
(Sorry for prematurely closing.)
hh
On Tue, Apr 16, 2013 at 11:18 AM, Dan notifications@github.com wrote:
haha. Drop the mike. Boom.
(Sorry for prematurely closing.)
— Reply to this email directly or view it on GitHubhttps://github.com/sanderpick/wolfpack-cli/issues/4#issuecomment-16462065 .
@danhammer digging the thoughts here, but I don't fully understand. Are you saying that a distribution like that could be used to predict what a team might be working on in the future? Show stats about the most active keywords for a given project / team?
We can identify hot streaks or cold streaks on a particular project. Sort of like in NBA Jam. It may encourage others to jump on a hot streak.
The idea, I guess, would be to figure out if people on a particular project are more or less active than usual -- taking into account some random variation in reporting. Just a thought. There are all sorts of other analytics that could be done, maybe, to help encourage us to get shit done.
Would be amazing to see global keyword hot streaks
On Apr 16, 2013, at 2:32 PM, Dan notifications@github.com wrote:
We can identify hot streaks or cold streaks on a particular project. Sort of like in NBA Jam. It may encourage others to jump on a hot streak.
The idea, I guess, would be to figure out if people on a particular project are more or less active than usual -- taking into account some random variation in reporting. Just a thought. There are all sorts of other analytics that could be done, maybe, to help encourage us to get shit done.
— Reply to this email directly or view it on GitHub.
It may be helpful to structure the "what's going on today?" ask. Project-based or team-based categories. This seemed to help me this morning, following @andrewxhill's lead. It may also mitigate the problem of hanging branches or issues, things that are just sort of pushed aside. A gentle reminder to either deal with the branch or prune it.
It could just start as a list of open projects at the end of the e-mail.
Just a thought. BTW FWIW FTW, um, where should we put potential enhancements or issues? Here?