New GitHub repo & Lighthouse project tracker are up
1 view
Skip to first unread message
theRocket
Jul 29, 2008, 9:45:26 PM7/29/08
to Racing on Rails
Okay, here's a couple "home bases" for my changes to Scott's code for
the WSBA.
For the coders out there who are interested, I was able to clone
Scott's subversion repo, from which I can make changes using Git but
still keep pace with his changes (via git-svn rebase). I pushed the
clone to the GitHub public repo here:
http://github.com/theRocket/wsbaracing/
Notice under the "Networking" tab, all of Scott's commit history is
still there (and there's a lot of it). Nice work, Scott!
For those of you finding bugs, the issue tracking site is also ready
to go:
http://osc.lighthouseapp.com/
osc stands for "Open Source Cycling". It just builds off an idea I
had earlier this year.
Anyone who sets up a profile should be able to submit a ticket. I
believe I can close those directly with my commits to the GitHub repo
(although I haven't figured out integration yet, I know the RailsCore
team uses it).
Anybody know what the heck I'm talking about (besides Scott), or even
give a hoot?
the WSBA.
For the coders out there who are interested, I was able to clone
Scott's subversion repo, from which I can make changes using Git but
still keep pace with his changes (via git-svn rebase). I pushed the
clone to the GitHub public repo here:
http://github.com/theRocket/wsbaracing/
Notice under the "Networking" tab, all of Scott's commit history is
still there (and there's a lot of it). Nice work, Scott!
For those of you finding bugs, the issue tracking site is also ready
to go:
http://osc.lighthouseapp.com/
osc stands for "Open Source Cycling". It just builds off an idea I
had earlier this year.
Anyone who sets up a profile should be able to submit a ticket. I
believe I can close those directly with my commits to the GitHub repo
(although I haven't figured out integration yet, I know the RailsCore
team uses it).
Anybody know what the heck I'm talking about (besides Scott), or even
give a hoot?
theRocket
Jul 30, 2008, 1:37:35 AM7/30/08
to Racing on Rails
On Jul 29, 6:45 pm, theRocket <edaroc...@gmail.com> wrote:
> Anybody know what the heck I'm talking about (besides Scott), or even
> give a hoot?
I made a new issue in LightHouse, and I plan to resolve the issue
automagically with my next push to GitHub. You, too, can experience
this power.
Too much stout beer late at night? Possibly.
Scott
Jul 30, 2008, 12:46:05 PM7/30/08
to Racing on Rails
I have to be honest here. Your enthusiasm is great; I appreciate your
help; and I think it's great that we've got a larger discussion going.
But…this is a quite a bit of talk about the "how," not the the "what."
I think we should be focusing the discussion along the lines of Ian's
last email.
The current "how"/source control/issue tracking/hosting may be
imperfect, but it has been effective. Meanwhile, we've got hours and
hours of great ideas just begging for development time. Why not spend
our time of getting things done, and only fix the "how" when it starts
to become a problem?
I understand everyone's desire to do their work the way they would
like to do it—we all need to compromise to work together—but I'd like
to stick with Subversion and Trac for the immediate future.
Ryan, if you can register for a Trac account, I'm happy to give you
full admin rights. Send me a couple patches, and I'm happy to give you
full Subversion rights, too. Same goes for anyone else. Just ask!
help; and I think it's great that we've got a larger discussion going.
But…this is a quite a bit of talk about the "how," not the the "what."
I think we should be focusing the discussion along the lines of Ian's
last email.
The current "how"/source control/issue tracking/hosting may be
imperfect, but it has been effective. Meanwhile, we've got hours and
hours of great ideas just begging for development time. Why not spend
our time of getting things done, and only fix the "how" when it starts
to become a problem?
I understand everyone's desire to do their work the way they would
like to do it—we all need to compromise to work together—but I'd like
to stick with Subversion and Trac for the immediate future.
Ryan, if you can register for a Trac account, I'm happy to give you
full admin rights. Send me a couple patches, and I'm happy to give you
full Subversion rights, too. Same goes for anyone else. Just ask!
theRocket
Jul 30, 2008, 1:33:15 PM7/30/08
to Racing on Rails
Scott,
I appreciate your honesty. I think we can have our cake and eat some
of it, too. Please read past the technical mumbo-jumbo (first 3
paragraphs) for the politically sensitive material!
I don't know any subversion commands, except clone and commit. I have
already done one of those - I cloned your code. I will use the other
if/when you want my changes back. Otherwise, I don't plan on learning
any more subversion until I "have to" (i.e. get paid for it).
In the meantime, I use Git for my local repository, only because it
allows me to easily branch & merge my different lines of development.
This is a hobby, and I enjoy my workflow using Git. If Rails Core
team is using it themselves, I think that says enough for me. git-svn
is that compromise that allows the two worlds to work together.
As far as issue tracking, I can add/close issues in Trac if you want
me too. It looks like these systems will not play nice together like
git-svn, but I will do the extra leg work to duplicate issues as
needed. I was thinking of WSBA-specific issues going on my ticket
system because I was thinking I would be the guy in charge of WSBA's
customizations.
So that brings me to my "what" for this discussion (hopefully the
others have hung on this long). What are the non-technical drawbacks
& advantages of keeping the code that is customized for the WSBA in a
separate system (SVN/Trac vs Git/Lighthouse)? What are my obligations
to remain in the existing track if I am working specifically for the
benefit of the WSBA?
I am thinking I owe your two years of coding work a heavy dose of
respect, and therefore will keep pulling your changes and submitting
mine as requested. However, you did license it MIT, and perhaps the
WSBA is different enough from OBRA and the others to merit some
customization? If I am to do that customization work pro bono, I
think I am entitled to use a different source control system.
I do not expect you or I to have all the opinions on this. For
example, I see that David V. is not entirely comfortable with your
hosting environment. To be honest, I am not entirely either (not
having looked at any availability stats, but just in principal). So
moving a machine, or even changing machines/OS's, is not going to
necessarily be smooth. But maybe it's necessary?
It appears you have been the only developer on this project the entire
time (or at least the only one committing) for what appears to be well
over a thousand revisions. I can imagine it would be hard to have
some rabble-rouser like me come in and suggest drastic changes. For
that, I apologize - it is just my tendency. But maybe it is time to
let someone else take a pull?
Respectfully,
RyanR>
(360) 927-2340
I appreciate your honesty. I think we can have our cake and eat some
of it, too. Please read past the technical mumbo-jumbo (first 3
paragraphs) for the politically sensitive material!
I don't know any subversion commands, except clone and commit. I have
already done one of those - I cloned your code. I will use the other
if/when you want my changes back. Otherwise, I don't plan on learning
any more subversion until I "have to" (i.e. get paid for it).
In the meantime, I use Git for my local repository, only because it
allows me to easily branch & merge my different lines of development.
This is a hobby, and I enjoy my workflow using Git. If Rails Core
team is using it themselves, I think that says enough for me. git-svn
is that compromise that allows the two worlds to work together.
As far as issue tracking, I can add/close issues in Trac if you want
me too. It looks like these systems will not play nice together like
git-svn, but I will do the extra leg work to duplicate issues as
needed. I was thinking of WSBA-specific issues going on my ticket
system because I was thinking I would be the guy in charge of WSBA's
customizations.
So that brings me to my "what" for this discussion (hopefully the
others have hung on this long). What are the non-technical drawbacks
& advantages of keeping the code that is customized for the WSBA in a
separate system (SVN/Trac vs Git/Lighthouse)? What are my obligations
to remain in the existing track if I am working specifically for the
benefit of the WSBA?
I am thinking I owe your two years of coding work a heavy dose of
respect, and therefore will keep pulling your changes and submitting
mine as requested. However, you did license it MIT, and perhaps the
WSBA is different enough from OBRA and the others to merit some
customization? If I am to do that customization work pro bono, I
think I am entitled to use a different source control system.
I do not expect you or I to have all the opinions on this. For
example, I see that David V. is not entirely comfortable with your
hosting environment. To be honest, I am not entirely either (not
having looked at any availability stats, but just in principal). So
moving a machine, or even changing machines/OS's, is not going to
necessarily be smooth. But maybe it's necessary?
It appears you have been the only developer on this project the entire
time (or at least the only one committing) for what appears to be well
over a thousand revisions. I can imagine it would be hard to have
some rabble-rouser like me come in and suggest drastic changes. For
that, I apologize - it is just my tendency. But maybe it is time to
let someone else take a pull?
Respectfully,
RyanR>
(360) 927-2340
Scott
Jul 30, 2008, 2:12:06 PM7/30/08
to Racing on Rails
Hey, thanks for taking my comments in the spirit I intended them. I
don't take any of this discussion personally. I welcome it. Can't help
but dump what's in my head about the whole project, and probably best
that it's written down and _not_ only in my head.
OK, let's try the git-svn, Lighthouse for new WSBA stuff approach.
Don't get me wrong—there's plenty to like about git and Lighthouse.
Let's see how it all works for us over time, then I'm happy to make
changes based on that.
Happy to talk to EasyStreet about hosting if you all want to go that
route. Otherwise, David, Martin, Ryan: please do what you feel is
best.
Naw, I'm happy to let other developers take a pull. I wouldn't mind
sitting on for a good while! In that, er, spirit/metaphor, I'll send
you admin login info later for everything relevant.
On Jul 30, 10:33 am, theRocket <edaroc...@gmail.com> wrote:
> Scott,
don't take any of this discussion personally. I welcome it. Can't help
but dump what's in my head about the whole project, and probably best
that it's written down and _not_ only in my head.
OK, let's try the git-svn, Lighthouse for new WSBA stuff approach.
Don't get me wrong—there's plenty to like about git and Lighthouse.
Let's see how it all works for us over time, then I'm happy to make
changes based on that.
Happy to talk to EasyStreet about hosting if you all want to go that
route. Otherwise, David, Martin, Ryan: please do what you feel is
best.
Naw, I'm happy to let other developers take a pull. I wouldn't mind
sitting on for a good while! In that, er, spirit/metaphor, I'll send
you admin login info later for everything relevant.
On Jul 30, 10:33 am, theRocket <edaroc...@gmail.com> wrote:
> Scott,
theRocket
Jul 31, 2008, 1:56:54 PM7/31/08
to Racing on Rails
Scott,
I pushed your "admin_ui" branch to GitHub, since I saw the most recent
activity there in Trac. What other recent changesets am I missing?
Check out the cool network graph here:
http://github.com/theRocket/wsbaracing/network
If you click in the drawn region and press your left key arrow, you
can go back in time. Hovering over the nodes with your mouse will
give you the commit message and the SHA1 hash of the commit object.
Here's a nice discussion about our unlikely marriage from one of the
rails core guys, Koz:
http://www.koziarski.net/archives/2008/2/23/on-git
Food for thought,
RyanR>
I pushed your "admin_ui" branch to GitHub, since I saw the most recent
activity there in Trac. What other recent changesets am I missing?
Check out the cool network graph here:
http://github.com/theRocket/wsbaracing/network
If you click in the drawn region and press your left key arrow, you
can go back in time. Hovering over the nodes with your mouse will
give you the commit message and the SHA1 hash of the commit object.
Here's a nice discussion about our unlikely marriage from one of the
rails core guys, Koz:
http://www.koziarski.net/archives/2008/2/23/on-git
Food for thought,
RyanR>
Scott Willson
Jul 31, 2008, 2:07:54 PM7/31/08
to racing-...@googlegroups.com
Hey, that's cool. And thanks for the link.
But you should stick with trunk for now. The admin_ui branch is still
experimental—I'm trying to come up with a easy-to-use, consistent UI
for all the similar admin screens—but it's not full functional and I
might even ditch the whole thing. Sorry for the red herring.
But you should stick with trunk for now. The admin_ui branch is still
experimental—I'm trying to come up with a easy-to-use, consistent UI
for all the similar admin screens—but it's not full functional and I
might even ditch the whole thing. Sorry for the red herring.
theRocket
Sep 5, 2008, 8:12:15 PM9/5/08
to Racing on Rails
Scott,
I tried 'git-svn rebase' to get all your latest commits to trunk (8/19
to 9/4).
http://github.com/theRocket/wsbaracing/commits/master
Rolling my commits back on top of yours was a little clunky - glad I
practiced with just the README. Hopefully, if I am creating mostly
new functionality there will not be merge conflicts.
Next we should try pushing my changes to the svn repo and see what
happens on your end. Fun stuff!
Thanks,
RyanR>
I tried 'git-svn rebase' to get all your latest commits to trunk (8/19
to 9/4).
http://github.com/theRocket/wsbaracing/commits/master
Rolling my commits back on top of yours was a little clunky - glad I
practiced with just the README. Hopefully, if I am creating mostly
new functionality there will not be merge conflicts.
Next we should try pushing my changes to the svn repo and see what
happens on your end. Fun stuff!
Thanks,
RyanR>
Scott Willson
Sep 17, 2008, 12:26:36 PM9/17/08
to racing-...@googlegroups.com
Hey, sorry I've been so slow to respond on this.
We're at Rails 2.1 on all the sites now, BTW.
Let me know if you want to try some source control dance moves. Are
there significant changes in github?
Scott
Reply all
Reply to author
Forward
0 new messages