does dmca push us further toward distributed rev control?

[Rob Cashwalker]

Of the ones you posted, I like the Blackmail version the best...

There's no easy way to disable the google project. About the best it seems I can do is remove everyone's commit status. As soon as possible following that, I think Jendave should clear out the current git repository and upload a fresh copy from Google, just to make sure there aren't any problems with the attempted commits from SVN.

I don't think there's any need for most of us to use our own clone, requiring merge requests and approvals... Obviously, Braids' min-max AI would stay in her clone until it was ready. The only tricky thing is that uploading is a two-step process... commit (to the local repository) then push the changes to the master repository.

Once you sign up at gitorious.org, you can send a message through their system to one of the admins to be added to the dev team.

[jendave]

Braids, new avatar?

jendave, I can provide an FTP login for cardforge.org, if the build script can handle that.

I think it's just a matter of time before the main google code project would get the same treatment.. I'd still like to know if there was any more specific complaint about Rare's personal project.

If all the devs can try to get onboard with gitorious, then how about we switch by Wednesday?

Yes, please PM me the login info. An FTP upload will be fairly easy. That said be prepared for some major testing

[jendave]

There's no easy way to disable the google project. About the best it seems I can do is remove everyone's commit status. As soon as possible following that, I think Jendave should clear out the current git repository and upload a fresh copy from Google, just to make sure there aren't any problems with the attempted commits from SVN.

Sounds good. Let me know. Note that the changes to the GIT repo (such as the .project change) will most likely need to be re-applied. My attempts to merge the histories of the SVN and GIT repos into one have made a real mess on my local copy. I will clear it out and just upload a clean copy of the SVN codebase.

[Rob Cashwalker]

When you upload the new copy, just change .project file before uploading...

[Snacko]

@ Rob Cashwalker
git follows an ideology that you commit your changes often into your local branch then when ready push all the changes you've made so far into upstream. This allows for a 100% offline revisioned project management that you can later share with others.

And most of you don't need to clone the repository, but if you need it, then you need to know that you have to push all the changes from the main repository to your clone yourself, otherwise it wont update.

[Rob Cashwalker]

I'm setting up Mantis on Cardforge.org, because gitorious doesn't have their own.

cardforge.org/bugz/

Signup for accounts so I can start delegating roles...

Mantis was the only free bug tracker with decent eclipse integration that I could install purely by php scripts. Bugzilla required too many perl modules and ssh access.

[Braids]

well, i will say with certainty that res/mtg-data.txt could be a real problem. it's the most blatant derivation we have of wotc's "property."

The average user doesn't need it,really, only devs and people who want to keep track of their favourite set and for them it can be a separate download, like it was from the beginning.

`
that's good to know. i think it's really important that res/mtg-data.txt be absent from our main repository and all of its history. could someone take care of it? i'd offer, but i don't know what would break. besides, i'm busy `gitting' on board.

[Snacko]

Till the repository isn't public it's possible to completely remove files from history so I suppose jendave could hard delete mtg-data.txt before he pushes the svn import.

[jendave]

Ok. I think I am ready to go. I figured out how to pull the latest SVN commits using git-svn, merge it into a pull from gitorious/cardforge, then push the result to gitorious. I am sure there will still be a lot of cleanup though. I have seen a lot of the dreaded line-endings. Let me know when you want to do the final transfer from svn to git. Then we can remove access to SVN.

[jendave]

It may be a bit early to ask, but after things settle down on git, I would like to re-arrange the directory structure a bit to make it more MAven friendly
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html

Of course, I would make it still work with Eclipse with or without the Maven Eclipse plugin. Any thoughts on using the Maven Eclipse plugin? It would make managing deps MUCH easier.

[zerker2000]

The deck editor provides access to, basically, over 2/3 of the Oracle card database. I do not think removing mtg-data.txt would have much impact on the project's standing under copyright law.

[Rob Cashwalker]

But removing it also eliminates 2+ MB of extraneous data.

Jendave, how about around 3:00 Eastern?

[jendave]

But removing it also eliminates 2+ MB of extraneous data.

Jendave, how about around 3:00 Eastern?

Just to be clear, you mean today, 3pm Eastern? I should be able to do it around 3:30-4pm Eastern today.

[jendave]

Ok. I think I am ready to go. I figured out how to pull the latest SVN commits using git-svn, merge it into a pull from gitorious/cardforge, then push the result to gitorious. I am sure there will still be a lot of cleanup though. I have seen a lot of the dreaded line-endings. Let me know when you want to do the final transfer from svn to git. Then we can remove access to SVN.

It's done. I have grabbed everything up to "r10904 - Added Incandescent Soulstoke" from SVN and put it into gitorious. Please lock SVN.

Dave

p.s. If there are any more checkins to SVN i can easily push them into git so it is not a big deal if a couple slip through until SVN can be locked down

[Jaedayr]

What do those of us who pick up the latest rev from SVN need to do in order to continue using the new system? I have Eclipse and Subversion installed and operating. As of right now my Forge is not working because of a prob in card.java (see the issues).