[yt-dev] Issues to Trello?

Nathan Goldbaum nathan12343 at gmail.com
Tue Sep 30 13:24:42 PDT 2014 

Any chance we can export the extant open issues into trello?

https://confluence.atlassian.com/display/BITBUCKET/Export+or+import+issue+data

On Tue, Sep 30, 2014 at 1:21 PM, Matthew Turk <matthewturk at gmail.com> wrote:

> Alright, good idea.  Done, they'll show up here:
>
> https://trello.com/b/hIAP2CzT/issues
>
> On Tue, Sep 30, 2014 at 3:17 PM, Sam Skillman <samskillman at gmail.com>
> wrote:
> > I am +1. Just try it out, see if it is useful. Even if it is only useful
> for
> > one person to manage their work on issues, it is worth it.
> >
> > On Tue, Sep 30, 2014 at 12:52 PM, John ZuHone <jzuhone at gmail.com> wrote:
> >>
> >> Is Trello scriptable?
> >>
> >> John ZuHone
> >> Kavli Center for Astrophysics and Space Research
> >> Massachusetts Institute of Technology
> >> 77 Massachusetts Ave., 37-582G
> >> Cambridge, MA 02139
> >> (w) 617-253-2354
> >> (m) 781-708-5004
> >> jzuhone at space.mit.edu
> >> jzuhone at gmail.com
> >> http://www.jzuhone.com
> >>
> >> On Sep 30, 2014, at 3:05 PM, Cameron Hummels <chummels at gmail.com>
> wrote:
> >>
> >> I see.  This makes more sense now.  But how then are we to close out
> >> solved issues which are completed through a PR?  Through BB and Trello
> both?
> >> Or will solving an issue in BB automatically close the issue in trello?
> >> Just curious how you envisioned the pipeline for issue creation to issue
> >> resolution.
> >>
> >> On Tue, Sep 30, 2014 at 10:59 AM, B.W. Keller <kellerbw at mcmaster.ca>
> >> wrote:
> >>>
> >>> As long as the issues are automatically synced, I think that Matt's
> >>> suggestion is great.
> >>>
> >>> On Tue, Sep 30, 2014 at 1:54 PM, Matthew Turk <matthewturk at gmail.com>
> >>> wrote:
> >>>>
> >>>> I think I have failed to be clear: I am not proposing we *move*, just
> >>>> that whenever a new issue is created *on bitbucket* that a card is
> >>>> created on Trello, through their "mail to board" feature.  But it
> >>>> sounds like it's probably not a winner of an idea anyway.
> >>>>
> >>>> On Tue, Sep 30, 2014 at 12:28 PM, Cameron Hummels <chummels at gmail.com
> >
> >>>> wrote:
> >>>> > Like you mentioned, I'm fearful of having two places to report
> issues.
> >>>> > I
> >>>> > hardly ever look at trello, only really using it during the lead up
> to
> >>>> > 3.0's
> >>>> > release.  I mostly share Nathan's opinions on this matter, so I'm
> open
> >>>> > to
> >>>> > switching, but we lose a lot of the functionality provided by BB
> with
> >>>> > PRs
> >>>> > and such.
> >>>> >
> >>>> > On Tue, Sep 30, 2014 at 9:37 AM, Matthew Turk <
> matthewturk at gmail.com>
> >>>> > wrote:
> >>>> >>
> >>>> >> On Tue, Sep 30, 2014 at 11:35 AM, Nathan Goldbaum
> >>>> >> <nathan12343 at gmail.com>
> >>>> >> wrote:
> >>>> >> > Overall trello is a nicer experience than bitbucket issues.  The
> >>>> >> > major
> >>>> >> > plusses of using bitbucket issues is that it's what we've been
> >>>> >> > using (no
> >>>> >> > need to retrain people) and there's good integration with commit
> >>>> >> > messages to
> >>>> >> > close issues.  If you can get bitbucket issues to sync with
> trello
> >>>> >> > cards
> >>>> >> > somehow, I think we'd have the best of both worlds?
> >>>> >> >
> >>>> >> > Another nice thing about bitbucket issues is that we get an
> e-mail
> >>>> >> > to
> >>>> >> > the
> >>>> >> > dev list whenever a new issue is open.  Could that be replicated
> >>>> >> > for
> >>>> >> > trello?
> >>>> >> > Honestly I had no idea it was even being updated or tracked after
> >>>> >> > the
> >>>> >> > yt-3
> >>>> >> > release.
> >>>> >>
> >>>> >> I was actually planning on using this functionality to replicate
> the
> >>>> >> issues to Trello, as one can have cards created upon email.  Trello
> >>>> >> would just be a display for the issues that are kept on BB.
> >>>> >>
> >>>> >> >
> >>>> >> > All that said, my main concern is about fractioning where issues
> >>>> >> > can be
> >>>> >> > found.  There needs to be one canonical issue list or one
> canonical
> >>>> >> > place to
> >>>> >> > search.
> >>>> >> >
> >>>> >> > On Tue, Sep 30, 2014 at 9:20 AM, Matthew Turk
> >>>> >> > <matthewturk at gmail.com>
> >>>> >> > wrote:
> >>>> >> >>
> >>>> >> >> On Tue, Sep 30, 2014 at 11:18 AM, Chris Malone
> >>>> >> >> <chris.m.malone at gmail.com>
> >>>> >> >> wrote:
> >>>> >> >> > Hi Matt,
> >>>> >> >> >
> >>>> >> >> > I actually haven't been folding Trello into my workflow.  I
> have
> >>>> >> >> > glanced
> >>>> >> >> > at
> >>>> >> >> > the page once or twice and noticed it was full of ideas for
> both
> >>>> >> >> > proposed
> >>>> >> >> > improvements and fixes.  Are the majority of devs actively
> >>>> >> >> > working in
> >>>> >> >> > the
> >>>> >> >> > Trello space?
> >>>> >> >> >
> >>>> >> >>
> >>>> >> >> Hm, maybe I'm delusional about the level of usage.  *I* use it
> all
> >>>> >> >> the
> >>>> >> >> time.  :)  Perhaps that's not the best barometer...
> >>>> >> >>
> >>>> >> >> > Also, do general users have the ability - and the knowledge
> that
> >>>> >> >> > our
> >>>> >> >> > Trello
> >>>> >> >> > setup exists - to create issues on Trello?  As it is now, I
> >>>> >> >> > think the
> >>>> >> >> > barrier to entry for issues is quite low for users on BB.
> >>>> >> >>
> >>>> >> >> Well, the idea would be to have new issues on BB emailed over to
> >>>> >> >> Trello into a special board, where they'd become cards.  This
> >>>> >> >> would be
> >>>> >> >> a unidirectional flow of data, though, and really just a way to
> >>>> >> >> look
> >>>> >> >> at the cards and have a representation of them.
> >>>> >> >>
> >>>> >> >> >
> >>>> >> >> > Chris
> >>>> >> >> >
> >>>> >> >> > On Tue, Sep 30, 2014 at 10:11 AM, Matthew Turk
> >>>> >> >> > <matthewturk at gmail.com>
> >>>> >> >> > wrote:
> >>>> >> >> >>
> >>>> >> >> >> Hi all,
> >>>> >> >> >>
> >>>> >> >> >> What would you all think of having new issues reported to
> >>>> >> >> >> Trello?  I
> >>>> >> >> >> would worry about issues then being updated in two places (or
> >>>> >> >> >> one
> >>>> >> >> >> instead of two), but it feels like Trello is just a way more
> >>>> >> >> >> natural
> >>>> >> >> >> fit for how we work than the BB issue tracker.  Maybe I'm
> wrong
> >>>> >> >> >> on
> >>>> >> >> >> that...
> >>>> >> >> >>
> >>>> >> >> >> Anyway, we can have them forwarded via email, or use one of
> the
> >>>> >> >> >> connectors out there to have them go there.  But maybe it
> would
> >>>> >> >> >> just
> >>>> >> >> >> fragment things.
> >>>> >> >> >>
> >>>> >> >> >> -Matt
> >>>> >> >> >> _______________________________________________
> >>>> >> >> >> yt-dev mailing list
> >>>> >> >> >> yt-dev at lists.spacepope.org
> >>>> >> >> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>> >> >> >
> >>>> >> >> >
> >>>> >> >> >
> >>>> >> >> > _______________________________________________
> >>>> >> >> > yt-dev mailing list
> >>>> >> >> > yt-dev at lists.spacepope.org
> >>>> >> >> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>> >> >> >
> >>>> >> >> _______________________________________________
> >>>> >> >> yt-dev mailing list
> >>>> >> >> yt-dev at lists.spacepope.org
> >>>> >> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>> >> >
> >>>> >> >
> >>>> >> >
> >>>> >> > _______________________________________________
> >>>> >> > yt-dev mailing list
> >>>> >> > yt-dev at lists.spacepope.org
> >>>> >> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>> >> >
> >>>> >> _______________________________________________
> >>>> >> yt-dev mailing list
> >>>> >> yt-dev at lists.spacepope.org
> >>>> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > --
> >>>> > Cameron Hummels
> >>>> > Postdoctoral Researcher
> >>>> > Steward Observatory
> >>>> > University of Arizona
> >>>> > http://chummels.org
> >>>> >
> >>>> > _______________________________________________
> >>>> > yt-dev mailing list
> >>>> > yt-dev at lists.spacepope.org
> >>>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>> >
> >>>> _______________________________________________
> >>>> yt-dev mailing list
> >>>> yt-dev at lists.spacepope.org
> >>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> yt-dev mailing list
> >>> yt-dev at lists.spacepope.org
> >>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>
> >>
> >>
> >>
> >> --
> >> Cameron Hummels
> >> Postdoctoral Researcher
> >> Steward Observatory
> >> University of Arizona
> >> http://chummels.org
> >>
> >> _______________________________________________
> >> yt-dev mailing list
> >> yt-dev at lists.spacepope.org
> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>
> >>
> >> _______________________________________________
> >> yt-dev mailing list
> >> yt-dev at lists.spacepope.org
> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>
> >
> >
> > _______________________________________________
> > yt-dev mailing list
> > yt-dev at lists.spacepope.org
> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20140930/470ae947/attachment.htm>

More information about the yt-dev mailing list