Plans to change to Git?

classic Classic list List threaded Threaded
50 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

sledorze
Better exposure better adoption.

Sent from my iPhone

On 31 août 2011, at 20:22, "Alex Liebert [via Haxe]" <[hidden email]> wrote:

what problem do we currently have, that git is going to solve?

On Wed, Aug 31, 2011 at 11:01 AM, danielku15 <[hidden email]> wrote:
There was a time everyone used CVS. Then a lot of people moved on to SVN.
Nobody likes the people that still use CVS.
Now everybody is moving to Git/Mercurial. Who want's to be like the CVS
people and use still SVN? xD

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747623.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org


If you reply to this email, your message will be added to the discussion below:
http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747679.html
To unsubscribe from Plans to change to Git?, click here.
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Marcelo de Moraes Serpa
In reply to this post by danielku15
what problem do we currently have, that git is going to solve?

Git is distributed. SVN is a monolithic centralized beast. Distributed is good, means anyone can clone the whole repo and be playing with haxe's code in a matter of seconds. Contributing patches is a snap too. 

Any other questions?

On Wed, Aug 31, 2011 at 11:42 AM, danielku15 <[hidden email]> wrote:
Git + Github allows easier contribution of code and provides a better
communication of changes made to haXe (in code).

There are no problems in Windows XP that are solved with Windows 7. But you
all will upgrade some time because it simply is more comfort and provides a
lot of additional stuff you'll love.

Of course you can stay at any old system because it works for your needs.
But all others who like the new systems have to take care of your old system
and use old stuff too. ;)

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747746.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Marcelo de Moraes Serpa
For more info, check this out: http://whygitisbetterthanx.com/

- M

On Wed, Aug 31, 2011 at 12:05 PM, Marcelo de Moraes Serpa <[hidden email]> wrote:
what problem do we currently have, that git is going to solve?

Git is distributed. SVN is a monolithic centralized beast. Distributed is good, means anyone can clone the whole repo and be playing with haxe's code in a matter of seconds. Contributing patches is a snap too. 

Any other questions?

On Wed, Aug 31, 2011 at 11:42 AM, danielku15 <[hidden email]> wrote:
Git + Github allows easier contribution of code and provides a better
communication of changes made to haXe (in code).

There are no problems in Windows XP that are solved with Windows 7. But you
all will upgrade some time because it simply is more comfort and provides a
lot of additional stuff you'll love.

Of course you can stay at any old system because it works for your needs.
But all others who like the new systems have to take care of your old system
and use old stuff too. ;)

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747746.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org



--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Pimm Hogeling
I too prefer Git over SVN. I find Git far more intuitive.

In all fairness, it will definitely not affect my level of contribution to the codebase. I stopped contributing to the haXe project at large because I sent in patches on several occasions, and none of them were actually applied to the codebase. In fact, I wasn't even honoured with a direct response. The patches were apparently not worthy of Nicolas' time.

(In fact - and this is a bit off-topic - it drove me towards writing my own haxelib competitor. If anyone is interested in designing, developing or testing it, please contact me.)

It seems like Nicolas doesn't care about small stuff. He's far too busy with the big stuff. He doesn't care about our contribution; unless such contribution is at least ground breaking. Therefore switching to Git won't do anything for contribution.

It would still be a good move, though. Plus one for Daniel!

2011/8/31 Marcelo de Moraes Serpa <[hidden email]>
For more info, check this out: http://whygitisbetterthanx.com/

- M


On Wed, Aug 31, 2011 at 12:05 PM, Marcelo de Moraes Serpa <[hidden email]> wrote:
what problem do we currently have, that git is going to solve?

Git is distributed. SVN is a monolithic centralized beast. Distributed is good, means anyone can clone the whole repo and be playing with haxe's code in a matter of seconds. Contributing patches is a snap too. 

Any other questions?

On Wed, Aug 31, 2011 at 11:42 AM, danielku15 <[hidden email]> wrote:
Git + Github allows easier contribution of code and provides a better
communication of changes made to haXe (in code).

There are no problems in Windows XP that are solved with Windows 7. But you
all will upgrade some time because it simply is more comfort and provides a
lot of additional stuff you'll love.

Of course you can stay at any old system because it works for your needs.
But all others who like the new systems have to take care of your old system
and use old stuff too. ;)

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747746.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org



--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Marcelo de Moraes Serpa
With git, forks could be maintained  more easily and rebased as needed. So, if Nicolas is not willing to accept patches, just use the best from the official distribution (by rebasing / merging as needed) and keep your own. Eventually use will grow and it will get traction, and the owners of the official one will be forced to merge it back :)

On Wed, Aug 31, 2011 at 12:14 PM, Pimm Hogeling <[hidden email]> wrote:
I too prefer Git over SVN. I find Git far more intuitive.

In all fairness, it will definitely not affect my level of contribution to the codebase. I stopped contributing to the haXe project at large because I sent in patches on several occasions, and none of them were actually applied to the codebase. In fact, I wasn't even honoured with a direct response. The patches were apparently not worthy of Nicolas' time.

(In fact - and this is a bit off-topic - it drove me towards writing my own haxelib competitor. If anyone is interested in designing, developing or testing it, please contact me.)

It seems like Nicolas doesn't care about small stuff. He's far too busy with the big stuff. He doesn't care about our contribution; unless such contribution is at least ground breaking. Therefore switching to Git won't do anything for contribution.

It would still be a good move, though. Plus one for Daniel!


2011/8/31 Marcelo de Moraes Serpa <[hidden email]>
For more info, check this out: http://whygitisbetterthanx.com/

- M


On Wed, Aug 31, 2011 at 12:05 PM, Marcelo de Moraes Serpa <[hidden email]> wrote:
what problem do we currently have, that git is going to solve?

Git is distributed. SVN is a monolithic centralized beast. Distributed is good, means anyone can clone the whole repo and be playing with haxe's code in a matter of seconds. Contributing patches is a snap too. 

Any other questions?

On Wed, Aug 31, 2011 at 11:42 AM, danielku15 <[hidden email]> wrote:
Git + Github allows easier contribution of code and provides a better
communication of changes made to haXe (in code).

There are no problems in Windows XP that are solved with Windows 7. But you
all will upgrade some time because it simply is more comfort and provides a
lot of additional stuff you'll love.

Of course you can stay at any old system because it works for your needs.
But all others who like the new systems have to take care of your old system
and use old stuff too. ;)

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747746.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org



--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Philipp Klose-2
In reply to this post by danielku15
That's sounds complicated. Why not make a new branch ;-)

Am 31.08.2011 19:39, schrieb danielku15:

> With SVN you do not have the possibility to "try something out". If you want
> to make some bigger changes (like Cauê did with the new targets) you simply
> cannot commit your WIP anywhere unless you make your own copy on your SVN
> server. With git you get a clone of the repo and develop the changes into
> your local repository (or/and commit it to your fork on Github). The
> developers of haXe immediatly see that you have made a fork and made some
> cool changes. After you are finished you send a pull request and merge it
> back to the original repo.
>
> Think of this scenario: haXe is on Github. Cauê wants to develop the C# and
> Java targets. He makes a fork and starts developing the targets on his "repo
> copy". People can follow him and watch what he's doing and can start
> contributing to him. After he's finished he send's a pull request to haXe
> and they can merge it back to their system and make a new release haXe 3.0.
>
> Currently the code is quite at a hidden place in Google Code (my opinion).
> Github is a lot more focused on providing the code and share it with
> everyone as a social (coding) network.
>
> @Bruno Baudry
> 1 - I can't really counter that argument xD
> 2 - You probably have to read some theory about git, then you'll se how it
> will improve the workflows. In SVN you have the workflow: develop into the
> local working copy, commit it directly to the central SVN server. In git you
> have this workflow: You develop into your local working copy and commit it
> to your local repository. After you have finished your work you push
> (upload) your work to the (logical) central repository. But in addition SVN
> simply provides a lot of great features. (branching / merging is a lot
> easier).
> 3 - Can't follow that. You can mess up your code with any version control
> system if you know how. But if you don't play around with "deleting commits"
> (which is possible in git using special commands) I can't agree with the
> continus danger of messing up the code. ;)
> 4 - Read some stuff about git and give it a try. It's worth the time to look
> at it. If you have tried out your git once, you'll love it and won't get
> back to SVN.

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Nicolas Cannasse
In reply to this post by Pimm Hogeling
Le 31/08/2011 21:14, Pimm Hogeling a écrit :

> I too prefer Git over SVN. I find Git far more intuitive.
>
> In all fairness, it will definitely not affect my level of contribution
> to the codebase. I stopped contributing to the haXe project at large
> because I sent in patches on several occasions, and none of them were
> actually applied to the codebase. In fact, I wasn't even honoured with a
> direct response. The patches were apparently not worthy of Nicolas' time.
>
> (In fact - and this is a bit off-topic - it drove me towards writing my
> own haxelib competitor. If anyone is interested in designing, developing
> or testing it, please contact me.)
>
> It seems like Nicolas doesn't care about small stuff. He's far too busy
> with the big stuff. He doesn't care about our contribution; unless such
> contribution is at least ground breaking. Therefore switching to Git
> won't do anything for contribution.

You're making quite a generalization from a very-specific case here.

Nicolas

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

bruno baudry
In reply to this post by Marcelo de Moraes Serpa
Don't get me wrong I fully understand the benefits of a distributed version control system.   
But I'm really don't get the urge to do the move :

1 - i know that forks would be anything but healthy for haXe's ecosystem (for its growth) .
2 - only a hand full of masters commit to haxe's repo, so i'd rather let them decide what tool they need.



2011/8/31 Marcelo de Moraes Serpa <[hidden email]>
With git, forks could be maintained  more easily and rebased as needed. So, if Nicolas is not willing to accept patches, just use the best from the official distribution (by rebasing / merging as needed) and keep your own. Eventually use will grow and it will get traction, and the owners of the official one will be forced to merge it back :)


On Wed, Aug 31, 2011 at 12:14 PM, Pimm Hogeling <[hidden email]> wrote:
I too prefer Git over SVN. I find Git far more intuitive.

In all fairness, it will definitely not affect my level of contribution to the codebase. I stopped contributing to the haXe project at large because I sent in patches on several occasions, and none of them were actually applied to the codebase. In fact, I wasn't even honoured with a direct response. The patches were apparently not worthy of Nicolas' time.

(In fact - and this is a bit off-topic - it drove me towards writing my own haxelib competitor. If anyone is interested in designing, developing or testing it, please contact me.)

It seems like Nicolas doesn't care about small stuff. He's far too busy with the big stuff. He doesn't care about our contribution; unless such contribution is at least ground breaking. Therefore switching to Git won't do anything for contribution.

It would still be a good move, though. Plus one for Daniel!


2011/8/31 Marcelo de Moraes Serpa <[hidden email]>
For more info, check this out: http://whygitisbetterthanx.com/

- M


On Wed, Aug 31, 2011 at 12:05 PM, Marcelo de Moraes Serpa <[hidden email]> wrote:
what problem do we currently have, that git is going to solve?

Git is distributed. SVN is a monolithic centralized beast. Distributed is good, means anyone can clone the whole repo and be playing with haxe's code in a matter of seconds. Contributing patches is a snap too. 

Any other questions?

On Wed, Aug 31, 2011 at 11:42 AM, danielku15 <[hidden email]> wrote:
Git + Github allows easier contribution of code and provides a better
communication of changes made to haXe (in code).

There are no problems in Windows XP that are solved with Windows 7. But you
all will upgrade some time because it simply is more comfort and provides a
lot of additional stuff you'll love.

Of course you can stay at any old system because it works for your needs.
But all others who like the new systems have to take care of your old system
and use old stuff too. ;)

--
View this message in context: http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747746.html
Sent from the Haxe mailing list archive at Nabble.com.

--
haXe - an open source web programming language
http://haxe.org



--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org



--
_      _  _     _  _\   /
|_)    |_)|_||  || \ |_)Y
|_)    |_)|  ||_||_/|  \ |

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

singmajesty
I agree that the main contributors should decide what feels most  
comfortable :)


(There's also stuff like this: http://subgit.com/)



On Wed, 31 Aug 2011 12:53:26 -0700, bruno baudry <[hidden email]> wrote:

> Don't get me wrong I fully understand the benefits of a distributed  
> version
> control system.
> But I'm really don't get the urge to do the move :
>
> 1 - i know that forks would be anything but healthy for haXe's ecosystem
> (for its growth) .
> 2 - only a hand full of masters commit to haxe's repo, so i'd rather let
> them decide what tool they need.
>
>
>
> 2011/8/31 Marcelo de Moraes Serpa <[hidden email]>
>
>> With git, forks could be maintained  more easily and rebased as needed.  
>> So,
>> if Nicolas is not willing to accept patches, just use the best from
>> the official distribution (by rebasing / merging as needed) and keep  
>> your
>> own. Eventually use will grow and it will get traction, and the owners  
>> of
>> the official one will be forced to merge it back :)
>>
>>
>> On Wed, Aug 31, 2011 at 12:14 PM, Pimm Hogeling  
>> <[hidden email]>wrote:
>>
>>> I too prefer Git over SVN. I find Git far more intuitive.
>>>
>>> In all fairness, it will definitely not affect my level of  
>>> contribution to
>>> the codebase. I stopped contributing to the haXe project at large  
>>> because I
>>> sent in patches on several occasions, and none of them were actually  
>>> applied
>>> to the codebase. In fact, I wasn't even honoured with a direct  
>>> response. The
>>> patches were apparently not worthy of Nicolas' time.
>>>
>>> (In fact - and this is a bit off-topic - it drove me towards writing my
>>> own haxelib competitor. If anyone is interested in designing,  
>>> developing or
>>> testing it, please contact me.)
>>>
>>> It seems like Nicolas doesn't care about small stuff. He's far too busy
>>> with the big stuff. He doesn't care about our contribution; unless such
>>> contribution is at least ground breaking. Therefore switching to Git  
>>> won't
>>> do anything for contribution.
>>>
>>> It would still be a good move, though. Plus one for Daniel!
>>>
>>>
>>> 2011/8/31 Marcelo de Moraes Serpa <[hidden email]>
>>>
>>>> For more info, check this out: http://whygitisbetterthanx.com/
>>>>
>>>> - M
>>>>
>>>>
>>>> On Wed, Aug 31, 2011 at 12:05 PM, Marcelo de Moraes Serpa <
>>>> [hidden email]> wrote:
>>>>
>>>>> what problem do we currently have, that git is going to solve?
>>>>>
>>>>>
>>>>> Git is distributed. SVN is a monolithic centralized beast.  
>>>>> Distributed
>>>>> is good, means anyone can clone the whole repo and be playing with  
>>>>> haxe's
>>>>> code in a matter of seconds. Contributing patches is a snap too.
>>>>>
>>>>> Any other questions?
>>>>>
>>>>> On Wed, Aug 31, 2011 at 11:42 AM, danielku15  
>>>>> <[hidden email]>wrote:
>>>>>
>>>>>> Git + Github allows easier contribution of code and provides a  
>>>>>> better
>>>>>> communication of changes made to haXe (in code).
>>>>>>
>>>>>> There are no problems in Windows XP that are solved with Windows 7.  
>>>>>> But
>>>>>> you
>>>>>> all will upgrade some time because it simply is more comfort and
>>>>>> provides a
>>>>>> lot of additional stuff you'll love.
>>>>>>
>>>>>> Of course you can stay at any old system because it works for your
>>>>>> needs.
>>>>>> But all others who like the new systems have to take care of your  
>>>>>> old
>>>>>> system
>>>>>> and use old stuff too. ;)
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p6747746.html
>>>>>> Sent from the Haxe mailing list archive at Nabble.com.
>>>>>>
>>>>>> --
>>>>>> haXe - an open source web programming language
>>>>>> http://haxe.org
>>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> haXe - an open source web programming language
>>>> http://haxe.org
>>>>
>>>
>>>
>>> --
>>> haXe - an open source web programming language
>>> http://haxe.org
>>>
>>
>>
>> --
>> haXe - an open source web programming language
>> http://haxe.org
>>
>
>
>


--
Using Opera's revolutionary email client: http://www.opera.com/mail/

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Pimm Hogeling
In reply to this post by Nicolas Cannasse
Yes, I speak out of my own experience. (Four different cases, not one.) I explained why I don't contribute. I did so to demonstrate that the version control system isn't the bottleneck for contribution, at least not for me.

2011/8/31 Nicolas Cannasse <[hidden email]>
Le 31/08/2011 21:14, Pimm Hogeling a écrit :

I too prefer Git over SVN. I find Git far more intuitive.

In all fairness, it will definitely not affect my level of contribution
to the codebase. I stopped contributing to the haXe project at large
because I sent in patches on several occasions, and none of them were
actually applied to the codebase. In fact, I wasn't even honoured with a
direct response. The patches were apparently not worthy of Nicolas' time.

(In fact - and this is a bit off-topic - it drove me towards writing my
own haxelib competitor. If anyone is interested in designing, developing
or testing it, please contact me.)

It seems like Nicolas doesn't care about small stuff. He's far too busy
with the big stuff. He doesn't care about our contribution; unless such
contribution is at least ground breaking. Therefore switching to Git
won't do anything for contribution.

You're making quite a generalization from a very-specific case here.

Nicolas

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Nicolas Cannasse
In reply to this post by danielku15
Le 31/08/2011 19:39, danielku15 a écrit :
> @Elsass Philippe
> Maybe that simply the problem: It's probably to complicated to contribute
> anything.

That seems a bit like an overstatement. A lot of people have already
contributed haXe patches, I don't think they found it was too much
difficult from a technical point of view.

Actually compiler patches are much harder than that because you need to
learn OCaml, and standard library patches happen less frequently.

I don't have anything against Git, although I haven't used it (since at
Motion-Twin we have large binary files for gfxs and pulling the whole
repository would not be feasible), and I think it really looks like a
good idea.

However, changing versioning system require some work time, and I'll
definitely lack some of the nice features of Google code such as the
ability to mark issue as fixed when you commit a "fix #XXXX" message, etc.

It's true that GitHub helps people to keep their own forked version of
the compiler up-to-date, but I don't think that's a good thing
community-wise to have people having their own modified version of haXe,
which might prevent them from reusing/sharing compatible code with other
haXe developers.

So unless the compiler team get flooded with patches and can't handle
them easily with SVN, I think there is no strong point at moving to Git.

Best,
Nicolas

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

bubblebenj
I have zero idea if git is über svn since I've never taste it.
However for you're google code point Nicolas ("fix #XXXX") :

Ben

On Wed, Aug 31, 2011 at 10:04 PM, Nicolas Cannasse <[hidden email]> wrote:
Le 31/08/2011 19:39, danielku15 a écrit :

@Elsass Philippe
Maybe that simply the problem: It's probably to complicated to contribute
anything.

That seems a bit like an overstatement. A lot of people have already contributed haXe patches, I don't think they found it was too much difficult from a technical point of view.

Actually compiler patches are much harder than that because you need to learn OCaml, and standard library patches happen less frequently.

I don't have anything against Git, although I haven't used it (since at Motion-Twin we have large binary files for gfxs and pulling the whole repository would not be feasible), and I think it really looks like a good idea.

However, changing versioning system require some work time, and I'll definitely lack some of the nice features of Google code such as the ability to mark issue as fixed when you commit a "fix #XXXX" message, etc.

It's true that GitHub helps people to keep their own forked version of the compiler up-to-date, but I don't think that's a good thing community-wise to have people having their own modified version of haXe, which might prevent them from reusing/sharing compatible code with other haXe developers.

So unless the compiler team get flooded with patches and can't handle them easily with SVN, I think there is no strong point at moving to Git.

Best,
Nicolas


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

jlm@justinfront.net
On 31 Aug 2011, at 21:19, benjamin Dubois wrote:

http://code.google.com/p/support/wiki/ConvertingSvnToGit

He He 

I prefer this link... 


I think Hg is more approachable generally, I think we had this discussion when haXe went onto SVN, but I don't really follow the sudden interest in changing it now.

;j


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Marcelo de Moraes Serpa
Well, maybe someone could create a git mirror of the SVN codebase that is updated regularly. This would allow a pseudo-official git repo. We git lovers could then ignore SVN and only use the git mirror. 

On Wed, Aug 31, 2011 at 1:35 PM, [hidden email] <[hidden email]> wrote:
On 31 Aug 2011, at 21:19, benjamin Dubois wrote:

http://code.google.com/p/support/wiki/ConvertingSvnToGit

He He 

I prefer this link... 


I think Hg is more approachable generally, I think we had this discussion when haXe went onto SVN, but I don't really follow the sudden interest in changing it now.

;j


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

jlm@justinfront.net

On 31 Aug 2011, at 21:59, Marcelo de Moraes Serpa wrote:

>  ...create a git mirror of the SVN codebase that is updated regularly.

Er Marcelo I think the nightlies auto check for changes... any chance  
you can sync a clone git and hg repository, you may even be able to  
clone the SVN one as say githaxe and hghaxe and then do the  
conversion, I think that would actually be the best option for all  
user, as some design agencies might struggle with anything more  
useable than svn. Just a suggestion.. that takes the load off Nicolas  
and then you have the responsibility for keeping them sync'd and there  
is no 'But I prefer'.

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

jlm@justinfront.net
HaXe is after all multi platform, multi language... so my not mult  
repository, I really think you smart guys can work this out :)

On 1 Sep 2011, at 01:15, [hidden email] wrote:

>
> On 31 Aug 2011, at 21:59, Marcelo de Moraes Serpa wrote:
>
>> ...create a git mirror of the SVN codebase that is updated regularly.
>
> Er Marcelo I think the nightlies auto check for changes... any  
> chance you can sync a clone git and hg repository, you may even be  
> able to clone the SVN one as say githaxe and hghaxe and then do the  
> conversion, I think that would actually be the best option for all  
> user, as some design agencies might struggle with anything more  
> useable than svn. Just a suggestion.. that takes the load off  
> Nicolas and then you have the responsibility for keeping them sync'd  
> and there is no 'But I prefer'.
>
> --
> haXe - an open source web programming language
> http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Nicolas Juneau
In reply to this post by Marcelo de Moraes Serpa
Although git is awesome and, as many people mentionned, easy to work with for
fork and branches, making a switch like that must be carefully weighted. One
of the factors is the familiarity of the developers with the system.

Making the switch to git is not only a switch of programs, but also a switch
in the workflow than everybody in a team must understand - otherwize, some very
bad messes can happen.

I went through some SVN to git switches and although it is indeed an
improvement in the end, it's not only happy land with unicorns and rainbows -
the ride can alienate the team members in the switch and discourage code
contribution. It's cool if you attract newcomers, but less cool if you annoy
the core. And you don't want the core team to stop contributing.

Just sayin'. Don't let the buzzwords go through yor head - there's no silver
bullet.

Le 31 août 2011 15:05:04, Marcelo de Moraes Serpa a écrit :

> > what problem do we currently have, that git is going to solve?
>
> Git is distributed. SVN is a monolithic centralized beast. Distributed is
> good, means anyone can clone the whole repo and be playing with haxe's code
> in a matter of seconds. Contributing patches is a snap too.
>
> Any other questions?
>
> On Wed, Aug 31, 2011 at 11:42 AM, danielku15 <[hidden email]> wrote:
> > Git + Github allows easier contribution of code and provides a better
> > communication of changes made to haXe (in code).
> >
> > There are no problems in Windows XP that are solved with Windows 7. But
> > you all will upgrade some time because it simply is more comfort and
> > provides a lot of additional stuff you'll love.
> >
> > Of course you can stay at any old system because it works for your needs.
> > But all others who like the new systems have to take care of your old
> > system
> > and use old stuff too. ;)
> >
> > --
> > View this message in context:
> > http://haxe.1354130.n2.nabble.com/Plans-to-change-to-Git-tp6745378p674774
> > 6.html Sent from the Haxe mailing list archive at Nabble.com.
> >
> > --
> > haXe - an open source web programming language
> > http://haxe.org
--
Nicolas Juneau

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

danielku15
In reply to this post by Nicolas Cannasse
Nicolas Cannasse wrote
 
That seems a bit like an overstatement. A lot of people have already
contributed haXe patches, I don't think they found it was too much
difficult from a technical point of view.

Actually compiler patches are much harder than that because you need to
learn OCaml, and standard library patches happen less frequently.
 

If the people can see in public how several changes were made and contributed the right way to haxe, they probably start working on haXe too. (of course that is just a thought). Currently you loose the information who contributed anything to haXe unless you keep the patch files somewhere. Using the pullrequests from Github you really see who contributed in which way to haXe and that is quite awesome: https://github.com/jquery/jquery/network

Nicolas Cannasse wrote
 
I don't have anything against Git, although I haven't used it (since at
Motion-Twin we have large binary files for gfxs and pulling the whole
repository would not be feasible), and I think it really looks like a
good idea.
The data you pull/push gets compressed using zlib (deflate). Take a look at the benchmarks: https://git.wiki.kernel.org/index.php/GitBenchmarks#Repository_size_benchmarks

On a CCC podcast I heard that the whole Ruby on Rails Repository in git (all revisions!) is smaller than a single SVN checkout.

Nicolas Cannasse wrote
 
However, changing versioning system require some work time, and I'll
definitely lack some of the nice features of Google code such as the
ability to mark issue as fixed when you commit a "fix #XXXX" message, etc.
You get that feature on github too ;) (the bottom of the page)
https://github.com/features/projects/issues

Nicolas Cannasse wrote
 
It's true that GitHub helps people to keep their own forked version of
the compiler up-to-date, but I don't think that's a good thing
community-wise to have people having their own modified version of haXe,
which might prevent them from reusing/sharing compatible code with other
haXe developers.
But isn't htat exactly the idea behind opensource? Provide the code and let the public extend, modify and share it?






Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Heinz Hölzer-2
In reply to this post by Nicolas Juneau
Am 01.09.2011 04:22, schrieb Nicolas Juneau:
> it's not only happy land with unicorns and rainbows
awesome metaphor ;)

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Plans to change to Git?

Marcelo de Moraes Serpa
> It's true that GitHub helps people to keep their own forked version of
> the compiler up-to-date, but I don't think that's a good thing
> community-wise to have people having their own modified version of haXe,
> which might prevent them from reusing/sharing compatible code with other
haXe 
developers.

Wow! I'm surprised you think like this. HaXe is already open source and there *are* modified versions of the compiler lying around. *The official version will always be the official version*. People can judge and choose their best option, and new contributions will eventually be backported to the official one.

Fact is, SVN is the big elephant in the room. It's just ugly, slow and awkward. It works, yes, but is far from optimal if you compare it with git (or even bazaar and HG).

I'm surprised how closed-minded some developers can be. Take some time to read and try it, Start using it, and you'll eventually make the switch. 

Another thing: The switch to git shouldn't be painful. You can pretty much use *the same workflow* you use for SVN. That's how I learned it.

- Marcelo.




2011/9/1 Heinz Hölzer <[hidden email]>
Am 01.09.2011 04:22, schrieb Nicolas Juneau:

it's not only happy land with unicorns and rainbows
awesome metaphor ;)

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
123