Git Repository

[cfull1]

Not to rehash an old topic, but what were the reasons for sticking with the svn repository?
Was it mostly just because sourceforge hosts the forum?

Git has some nice features, such as pull requests, downloads, tickets, etc.
I find myself wanting to develop some of EG's core, but understandably don't have write access to the repository.
Not sure how to go about doing this.

Any thoughts?

[cfull1]

I would really like to hear other's opinions about this.

As I start to make changes in the code, I feel so limited!
I can't make any changes with out committing to the server.
I can't make any personal branches, and Heaven forbid I try to merge those branches later.

SVN is so outdated and open source projects can benefit the most from DCVS.
I know EG was built on SVN, and the builder has functions for SVN only.
But these can be easily updated to work with Git.

The only other change I notice would have to be made is the use of $LastChangedRevision$ (which Git doesn't have since it isn't based on revisions).
Typically I see that this is replaced with a last modified date.

The repo currently is very unorganized.
As Pako's been making most of the changes lately (much appreciated), his branch has all the updated code.
Trunk however hasn't been updated for two years and there is one tag of a very old version.
Here's a good diagram of how a Git workflow/repo could look. However, ours doesn't have to be that elaborate.

Maybe this seems daunting to some.
I'm willing to make the conversion to Git and update the code to handle it.
I guess I was just hoping to get others on board as well.

Here is some good info about Git.

[blackwind]

I'm in favor of a move to GitHub, and I've suggested such to Pako. If someone's offering to put in the work to make it happen, I see no reason to delay any further. As is, this project is bordering on dead; if those who want to change that are able to contribute in a more meaningful way, that has to be a good thing.

[krambriw]

Fine for me as well

[cfull1]

Glad to have you guys' support!

I'll get started on it this weekend.
I'll merge all branches into a development branch and commit released versions to a master branch and tag those releases.

As far as versioning goes should we just move to numbers (0.4.1.6) or dates (0.4.1.20130516)?

[cfull1]

I'm going to create an organization to hold the repo (something like "EventGhostDev").

For those who don't know:
The repo gets tied to the organization rather than a user.
The organization has groups (default being owners with full access).
Users can be added to groups.

Does anyone have a problem with the approach of creating an organization rather than a regular account to hold the repo in?

[blackwind]

As far as versioning goes should we just move to numbers (0.4.1.6) or dates (0.4.1.20130516)?

If we're going to switch, I say we move to the standard GNU versioning system and drop the fourth number entirely -- next release is 0.4.2, the one after that is 0.4.3, the next major release is 0.5.0, and so forth. There's no need for anything more complex than that, nor was there ever.

Does anyone have a problem with the approach of creating an organization rather than a regular account to hold the repo in?

Seems like this is the method used by most of the major projects on GitHub, so I'm game.

[cfull1]

If we're going to switch, I say we move to the standard GNU versioning system and drop the fourth number entirely -- next release is 0.4.2, the one after that is 0.4.3, the next major release is 0.5.0, and so forth. There's no need for anything more complex than that, nor was there ever.

That works for me. Would any of those parts jump to a two digit number? 0.9.11?

[blackwind]

Yep, 0.4.10 follows 0.4.9, just as 0.10.0 follows 0.9.x.

[krambriw]

I would like to see Pako's comment here as well,

Pako is it OK for you as well?

[topix]

I haven't used git till now but seeing it used very often today. I think it's good to move to git. With the versioning i would go the way blackwind suggested. More info (date) could be put in the About dialg in the program itself (maybe?). And creating a organization based repo sounds logical to me.
Now i have one more point on my todo list: learn using git

[blackwind]

Where'd you go, Pako?

[Pako]

I'm sorry.
I am now (and for about one month I will be) very busy.
I can not respond to your posts and PM.

Pako

[cfull1]

Pako,

We understand. I think it would be nice just to have your approval of moving to git, not that you have to put any effort into it.

[cfull1]

Currently going through and organizing the repo: Merging branches, updating empty commit messages, and squashing unnecessary commits.

I'm noticing Bitmonster used svn variables frequently

Code: Select all

# $LastChangedDate$
# $LastChangedRevision$
# $LastChangedBy$

Do you guys think it's necessary to somehow continue this in git (making note of last edited and by whom)?
I can't see it mattering for those who checkout the repo but those who use the installer. Thoughts?