Github Issues

David Humphrey

unread,

Jan 9, 2013, 10:30:49 AM1/9/13

to dev-p...@lists.mozilla.org

I want to see us move off of Lighthouse and into Github Issues for
Popcorn Maker and Popcorn.js bug tracking. Can I take the temperature
on this list of such a move? The future points toward Github, not
Lighthouse, and I'm sick of various things with them, not least that I'm
paying for all of the pain.

Thoughts? Concerns? Ideas?

Dave

Rick Waldron

unread,

Jan 9, 2013, 10:37:22 AM1/9/13

to David Humphrey, dev-p...@lists.mozilla.org

+9001

My only concern is the loss of history... but I think we could get away
with linking to the "retired" lighthouse from the repo, so if we need to
reference past bugs, we can just point there.

Rick

> ______________________________**_________________
> dev-popcorn mailing list
> dev-p...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/dev-popcorn<https://lists.mozilla.org/listinfo/dev-popcorn>
>

David Humphrey

unread,

Jan 9, 2013, 10:38:38 AM1/9/13

to Rick Waldron, dev-p...@lists.mozilla.org

I share this same concern. I wonder if we should try to migrate the
bugs, or as you say, mothball what we have and just pay to keep it there
for the next few years.

Dave

On 13-01-09 10:37 AM, Rick Waldron wrote:
> +9001
>
> My only concern is the loss of history... but I think we could get
> away with linking to the "retired" lighthouse from the repo, so if we
> need to reference past bugs, we can just point there.
>
> Rick
>
>
> On Wed, Jan 9, 2013 at 10:30 AM, David Humphrey
> <david.h...@senecacollege.ca

> <mailto:david.h...@senecacollege.ca>> wrote:
>
> I want to see us move off of Lighthouse and into Github Issues for
> Popcorn Maker and Popcorn.js bug tracking. Can I take the
> temperature on this list of such a move? The future points toward
> Github, not Lighthouse, and I'm sick of various things with them,
> not least that I'm paying for all of the pain.
>
> Thoughts? Concerns? Ideas?
>
> Dave

> _______________________________________________
> dev-popcorn mailing list
> dev-p...@lists.mozilla.org <mailto:dev-p...@lists.mozilla.org>
> https://lists.mozilla.org/listinfo/dev-popcorn
>
>

Jon Buckley

unread,

Jan 9, 2013, 10:39:36 AM1/9/13

to Rick Waldron, David Humphrey, dev-p...@lists.mozilla.org

Yeah, I think if we just ran a script to increase the Github issue count above where the Lighthouse bug count is, we can have a clear separation between the old tracker and the new tracker.

On 2013-01-09, at 10:37 AM, Rick Waldron <waldro...@gmail.com> wrote:

> +9001
>
> My only concern is the loss of history... but I think we could get away
> with linking to the "retired" lighthouse from the repo, so if we need to
> reference past bugs, we can just point there.
>
> Rick
>
>
> On Wed, Jan 9, 2013 at 10:30 AM, David Humphrey <

> david.h...@senecacollege.ca> wrote:
>
>> I want to see us move off of Lighthouse and into Github Issues for Popcorn
>> Maker and Popcorn.js bug tracking. Can I take the temperature on this list
>> of such a move? The future points toward Github, not Lighthouse, and I'm
>> sick of various things with them, not least that I'm paying for all of the
>> pain.
>>
>> Thoughts? Concerns? Ideas?
>>
>> Dave

>> ______________________________**_________________
>> dev-popcorn mailing list
>> dev-p...@lists.mozilla.org
>> https://lists.mozilla.org/**listinfo/dev-popcorn<https://lists.mozilla.org/listinfo/dev-popcorn>
>>

> _______________________________________________
> dev-popcorn mailing list
> dev-p...@lists.mozilla.org

> https://lists.mozilla.org/listinfo/dev-popcorn

Rick Waldron

unread,

Jan 9, 2013, 10:53:06 AM1/9/13

to Jon Buckley, David Humphrey, dev-p...@lists.mozilla.org

Said magical script could actually be an "import issues" script.

I seem to recall Boaz actually using such a script for a project we had at
Bocoup...

Jon Buckley

unread,

Jan 9, 2013, 11:17:10 AM1/9/13

to Rick Waldron, David Humphrey, dev-p...@lists.mozilla.org

We wouldn't be able to import all of the issues, simply because we're up to ticket #1405 in Lighthouse and issue #266 in Github… but we would be able to get the majority into Github issues. And that sounds like something that'd be worth doing!

Brett Gaylor

unread,

Jan 9, 2013, 11:23:54 AM1/9/13

to Jon Buckley, Rick Waldron, David Humphrey, dev-p...@lists.mozilla.org

On 2013-01-09, at 11:17 AM, Jon Buckley wrote:

> We wouldn't be able to import all of the issues, simply because we're up to ticket #1405 in Lighthouse and issue #266 in Github… but we would be able to get the majority into Github issues. And that sounds like something that'd be worth doing!

I would imagine that we could quickly close many of those bugs as well.

I'm very supportive of moving to Github.
Brett

---
Brett Gaylor
@remixmanifesto

Brian Chirls

unread,

Jan 9, 2013, 12:22:14 PM1/9/13

to Brett Gaylor, Rick Waldron, Jon Buckley, dev-p...@lists.mozilla.org, David Humphrey

Not a bad idea. But I just wanna bump Rick's point about loss of history.
Being able to go back and figure out why certain changes were made is
invaluable.

That said, GitHub should make that even better in the future, since commits
and pull requests will be more tightly linked to the issue discussions.

On Wed, Jan 9, 2013 at 11:23 AM, Brett Gaylor
<br...@mozillafoundation.org>wrote:

Rick Waldron

unread,

Jan 10, 2013, 10:15:31 AM1/10/13

to Brian Chirls, Brett Gaylor, Jon Buckley, dev-p...@lists.mozilla.org, David Humphrey

Here we go....

http://developer.github.com/v3/issues/#create-an-issue

Jon Buckley

unread,

Jan 10, 2013, 11:17:27 AM1/10/13

to Rick Waldron, Brett Gaylor, Brian Chirls, David Humphrey, dev-popcorn@lists.mozilla.org Dev

In terms of preserving information, what does everyone think of having a bot sum up an entire Lighthouse ticket into a single Github issue? Should we go further than that?

Brian Chirls

unread,

Jan 10, 2013, 1:15:33 PM1/10/13

to Rick Waldron, Brett Gaylor, Jon Buckley, dev-p...@lists.mozilla.org, David Humphrey

Excellent. Also, GH now has this new feature.

https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments