Hi All,
Matt and I were discussing the move from homegrown hosting to Bitbucket, and I was advocating for going all in: using BitBucket's issue tracker and wiki, and discontinuing further use of our Trac site at yt.enzotools.org. Could we get a simple vote going, -1/+1 for using BitBucket's issue tracker and wiki?
thanks,
J. S.
Hi Jeff,
What do you see as the pros and cons of BitBucket vs. home-grown? Though, generally I think +1: BB is probably just fine, and I refuse to vote unsigned-zero. ;-)
--Brian
On Sun, Feb 27, 2011 at 6:06 PM, j s oishi jsoishi@gmail.com wrote:
Hi All,
Matt and I were discussing the move from homegrown hosting to Bitbucket, and I was advocating for going all in: using BitBucket's issue tracker and wiki, and discontinuing further use of our Trac site at yt.enzotools.org. Could we get a simple vote going, -1/+1 for using BitBucket's issue tracker and wiki?
thanks,
J. S. _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Brian,
What do you see as the pros and cons of BitBucket vs. home-grown?
BitBucket pros: integrated with the repository hosting/tracking stuff; easy sign-in; no worry about maintenance BitBucket cons: would need a one-time transfer of info; no one has much experience using it
home-grown pros: already populated home-grown cons: hard to log into; not well used; now that repository is hosted at BB, would need to be maintained separately
I think that the BitBucket systems, while unknown, are probably just fine for our purposes, and I would rather not have to make Matt manually keep track of Trac just for issue-tracking and the wiki.
j
+1 to BB.
On Mon, Feb 28, 2011 at 8:55 AM, j s oishi jsoishi@gmail.com wrote:
Hi Brian,
What do you see as the pros and cons of BitBucket vs. home-grown?
BitBucket pros: integrated with the repository hosting/tracking stuff; easy sign-in; no worry about maintenance BitBucket cons: would need a one-time transfer of info; no one has much experience using it
home-grown pros: already populated home-grown cons: hard to log into; not well used; now that repository is hosted at BB, would need to be maintained separately
I think that the BitBucket systems, while unknown, are probably just fine for our purposes, and I would rather not have to make Matt manually keep track of Trac just for issue-tracking and the wiki.
j _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+1.
On Mon, Feb 28, 2011 at 10:56 AM, Sam Skillman samskillman@gmail.comwrote:
+1 to BB.
On Mon, Feb 28, 2011 at 8:55 AM, j s oishi jsoishi@gmail.com wrote:
Hi Brian,
What do you see as the pros and cons of BitBucket vs. home-grown?
BitBucket pros: integrated with the repository hosting/tracking stuff; easy sign-in; no worry about maintenance BitBucket cons: would need a one-time transfer of info; no one has much experience using it
home-grown pros: already populated home-grown cons: hard to log into; not well used; now that repository is hosted at BB, would need to be maintained separately
I think that the BitBucket systems, while unknown, are probably just fine for our purposes, and I would rather not have to make Matt manually keep track of Trac just for issue-tracking and the wiki.
j _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Jeff,
Thank you for the explanation. In that case, +1 for BB.
--Brian
On Mon, Feb 28, 2011 at 10:55 AM, j s oishi jsoishi@gmail.com wrote:
Hi Brian,
What do you see as the pros and cons of BitBucket vs. home-grown?
BitBucket pros: integrated with the repository hosting/tracking stuff; easy sign-in; no worry about maintenance BitBucket cons: would need a one-time transfer of info; no one has much experience using it
home-grown pros: already populated home-grown cons: hard to log into; not well used; now that repository is hosted at BB, would need to be maintained separately
I think that the BitBucket systems, while unknown, are probably just fine for our purposes, and I would rather not have to make Matt manually keep track of Trac just for issue-tracking and the wiki.
j
+1 for BB; thanks for the explanation, Jeff.
On 02/28/2011 10:55 AM, j s oishi wrote:
Hi Brian,
What do you see as the pros and cons of BitBucket vs. home-grown?
BitBucket pros: integrated with the repository hosting/tracking stuff; easy sign-in; no worry about maintenance BitBucket cons: would need a one-time transfer of info; no one has much experience using it
home-grown pros: already populated home-grown cons: hard to log into; not well used; now that repository is hosted at BB, would need to be maintained separately
I think that the BitBucket systems, while unknown, are probably just fine for our purposes, and I would rather not have to make Matt manually keep track of Trac just for issue-tracking and the wiki.
j _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Jeff,
On Sun, Feb 27, 2011 at 6:06 PM, j s oishi jsoishi@gmail.com wrote:
Hi All,
Matt and I were discussing the move from homegrown hosting to Bitbucket, and I was advocating for going all in: using BitBucket's issue tracker and wiki, and discontinuing further use of our Trac site at yt.enzotools.org. Could we get a simple vote going, -1/+1 for using BitBucket's issue tracker and wiki?
After we chatted today, I thought about it a lot, and I've come around from my original -1. I'm +1 on this. I think it'll make it a lot easier for people to report issues; it might still stay as an unofficial "todo" list, but I would prefer we make it easier for people to log in and use it. As for the Wiki, we don't really use it very much on Trac, and there are only a few pages on it. It would be easy to move them to either the docs or to the BB wiki. But I'll wait for the votes to come in before playing with this much.
Also, as a quick note for everybody, I've redone the "Developer Documentation" for how to contribute using BitBucket:
http://yt.enzotools.org/doc/advanced/developing.html I'd really love comments on this...
-Matt
thanks,
J. S. _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+0: BB seems good, but I have little experience with either of the BB or Trac systems. So, interpret my signed zero as in "approached from above"
On Feb 27, 2011 8:43pm, Matthew Turk matthewturk@gmail.com wrote:
Hi Jeff,
On Sun, Feb 27, 2011 at 6:06 PM, js oishi jsoishi@gmail.com> wrote:
Hi All,
Matt and I were discussing the move from homegrown hosting to
Bitbucket, and I was advocating for going all in: using BitBucket's
issue tracker and wiki, and discontinuing further use of our Trac site
at yt.enzotools.org. Could we get a simple vote going, -1/+1 for using
BitBucket's issue tracker and wiki?
After we chatted today, I thought about it a lot, and I've come around
from my original -1. I'm +1 on this. I think it'll make it a lot
easier for people to report issues; it might still stay as an
unofficial "todo" list, but I would prefer we make it easier for
people to log in and use it. As for the Wiki, we don't really use it
very much on Trac, and there are only a few pages on it. It would be
easy to move them to either the docs or to the BB wiki. But I'll wait
for the votes to come in before playing with this much.
Also, as a quick note for everybody, I've redone the "Developer
Documentation" for how to contribute using BitBucket:
http://yt.enzotools.org/doc/advanced/developing.html I'd really love
comments on this...
-Matt
thanks,
JS
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (7)
-
Brian O'Shea -
Britton Smith -
Cameron Hummels -
chris.m.malone＠gmail.com -
j s oishi -
Matthew Turk -
Sam Skillman