Rant: Yii is closed open source

[zekus (Zekus One)]

Job done! Thank you all for the reminder and suggestions. All existing open issues are imported in github. They are a bit messy though because they don’t get any labels or milestones. We will solve this gradually.

This is great! Thank you!

[sensorario]

Job done! Thank you all for the reminder and suggestions. All existing open issues are imported in github. They are a bit messy though because they don’t get any labels or milestones. We will solve this gradually.

I love github! Thank you qiang!

[mikl (Mike)]

Really great news. What about the translation project? Will it migrate, too?

[samdark (Alexander Makarov)]

Translation project relies on SVN ids so either we need to change the process somehow or leave it as is for now.

[mikl (Mike)]

I can live with SVN for now. But also see my suggestion above for how we could build something similar with git.

[jacmoe (Jacob Moena)]

Translation project relies on SVN ids so either we need to change the process somehow or leave it as is for now.

That is a shame!

Actually, the translation project would probably benefit more than yii core from being Github’ed.

So, people want to contribute a translation?

Fine, just make a fork, add a new translation and issue a pull request when done.

People are more likely to contribute to the translation repository than the Yii core repository - for obvious reasons.

So I hope that you find a way to migrate.

[mdomba (Maurizio Domba Cerin)]

It’s not a problem of migration… but keeping records on what is translated… currently the translation files are related to the SVN $id$ variable that is incremental, this way the guys from the translation team “knows” if there is has been some changes in the origin.

[mikl (Mike)]

It’s not a problem of migration… but keeping records on what is translated… currently the translation files are related to the SVN $id$ variable that is incremental, this way the guys from the translation team “knows” if there is has been some changes in the origin.

Yes, but you can achieve something similar in git: http://progit.org/book/ch7-2.html#keyword_expansion

[jacmoe (Jacob Moena)]

That’s basically what I meant by ‘migration’ - Mercurial would have been a lot easier.

But I am sure you can do this with Git. Like Mike linked to, or something else.

Seems to be a fairly common requirement.

[mdomba (Maurizio Domba Cerin)]

I’m still getting used to GitHub as I did not use it before… Mike do you have any idea how to do that on GitHub ?

[mikl (Mike)]

Well, this is not a github feature but a git feature.And i did not try the method explained in the link but the basic idea should be simple:

1. Create (and commit) a .gitattributes file in the source translation folder of the repo (we don’t need this in the translated files):

 *.txt ident

2. Make sure every source translation file contains the string $Id$ somewhere (much like now in SVN)

3. Each time a user checks out such a file, git will insert a SHA-1 checksum of the file into the $Id$ placeholder

4. Before someone commits such a file, git will remove this checksum again (only relevant for those who commit to translation source)

This should do the trick. Now users working on translations will always find a checksum in the source files, which they have to copy to their translated versions. If the source file changes, the checksum will also change.

[mikl (Mike)]

Coming back to the original topic:

4 days after the move to github there are already 62 forks and 10 open pull requests (and even more closed). If that’s not proving that it was the right step then i don’t know what is

[rawtaz]

I second thanks to the team for doing this. Github breathes encouragement, this was really the right step to take.