Just wanted to let everyone know I've created a git repo for the Wine Wiki from the CVS one at SourceForge. You can find it at: https://bitbucket.org/kauble/wine-wiki-migration
Since it's a fresh repo, I thought editing the history should be ok (just moved the right info into Author & Committer fields and made the commit message formatting more consistent). I do still have the unedited branches from cvsimport and can put those up too if there's any demand for them.
I've been talking with Dimi about what we would need to upgrade MoinMoin, and once he can find some time, he said he would setup a regular archive of the Wine Wiki's data. I also like the idea of using tags to mark which wiki version is in use, but I'm not sure how many times the wiki has been upgraded. If anyone knows what versions of MoinMoin we've used and when the upgrades took place, I can add the extra tags.
I don't know if there's much interest in just moving this to the Wine git repo yet. If not, I can probably review patches, but would be happy to add someone else as an admin if they have a bitbucket account.
- Kyle
I'd like to port our theme over to this.
Also, yes, I think we should look into WineHQ hosting the git for this.
-N
On 10/07/2012 06:06 PM, Kyle Auble wrote:
Just wanted to let everyone know I've created a git repo for the Wine Wiki from the CVS one at SourceForge. You can find it at: https://bitbucket.org/kauble/wine-wiki-migration
Since it's a fresh repo, I thought editing the history should be ok (just moved the right info into Author& Committer fields and made the commit message formatting more consistent). I do still have the unedited branches from cvsimport and can put those up too if there's any demand for them.
I've been talking with Dimi about what we would need to upgrade MoinMoin, and once he can find some time, he said he would setup a regular archive of the Wine Wiki's data. I also like the idea of using tags to mark which wiki version is in use, but I'm not sure how many times the wiki has been upgraded. If anyone knows what versions of MoinMoin we've used and when the upgrades took place, I can add the extra tags.
I don't know if there's much interest in just moving this to the Wine git repo yet. If not, I can probably review patches, but would be happy to add someone else as an admin if they have a bitbucket account.
- Kyle
On Mon, Oct 8, 2012 at 9:18 AM, Jeremy Newman wrote:
I'd like to port our theme over to this.
Also, yes, I think we should look into WineHQ hosting the git for this.
I've played with the code just a little on my own machine and MoinMoin 1.9.5. I haven't made much progress yet; some of the old MoinMoin methods used for themes were deprecated.
I've been able to make the old theme load, but it has several glitches. I was planning on trying to adapt the old theme to run on v1.9.5 exactly like it runs at the Wine Wiki. After that, I was going to work on importing the current WineHQ theme to MoinMoin.
If I make any patch-worthy changes while the repo is on my account, I'll post them (probably in a branch so there can be some code review).
- Kyle
Am 08.10.2012 01:06, schrieb Kyle Auble:
Just wanted to let everyone know I've created a git repo for the Wine Wiki from the CVS one at SourceForge. You can find it at: https://bitbucket.org/kauble/wine-wiki-migration
Not sure if bitbucket is the right place, there are not much repos regarding wine. Have a look at github, there we have e.g. 49 wine forks (https://github.com/mirrors/wine/network/members) and it's recommended by http://wiki.winehq.org/GitWine There is also some wine-specific stuff on repo.or.cz, e.g. http://repo.or.cz/w/wine.git/forks
I've been talking with Dimi about what we would need to upgrade MoinMoin, and once he can find some time, he said he would setup a regular archive of the Wine Wiki's data. I also like the
That sound good.
On Mon, Oct 8, 2012 at 5:17 PM, André Hentschel wrote:
Am 08.10.2012 01:06, schrieb Kyle Auble:
Just wanted to let everyone know I've created a git repo for the Wine Wiki from the CVS one at SourceForge. You can find it at: https://bitbucket.org/kauble/wine-wiki-migration
Not sure if bitbucket is the right place, there are not much repos regarding wine. Have a look at github, there we have e.g. 49 wine forks (https://github.com/mirrors/wine/network/members) and it's recommended by http://wiki.winehq.org/GitWine There is also some wine-specific stuff on repo.or.cz, e.g. http://repo.or.cz/w/wine.git/forks
I actually just chose Bitbucket for my personal code-sharing account (private repos, I've been using a lot of python recently, and sometimes I just have to be a silly, stubborn contrarian ;-)
So Bitbucket just happened to be where I posted the repo. I'm hoping we can move it to WineHQ's git server relatively soon, but if anyone on Github wants to clone it too, that would be great. Since there are more people, it would probably be better for code review, and if someone else wants to manage it, I would have no problem setting my fork on Bitbucket to track a Github version as upstream.
- Kyle
Am 09.10.2012 06:22, schrieb Kyle Auble:
On Mon, Oct 8, 2012 at 5:17 PM, André Hentschel wrote:
Am 08.10.2012 01:06, schrieb Kyle Auble:
Just wanted to let everyone know I've created a git repo for the Wine Wiki from the CVS one at SourceForge. You can find it at: https://bitbucket.org/kauble/wine-wiki-migration
Not sure if bitbucket is the right place, there are not much repos regarding wine. Have a look at github, there we have e.g. 49 wine forks (https://github.com/mirrors/wine/network/members) and it's recommended by http://wiki.winehq.org/GitWine There is also some wine-specific stuff on repo.or.cz, e.g. http://repo.or.cz/w/wine.git/forks
I actually just chose Bitbucket for my personal code-sharing account (private repos, I've been using a lot of python recently, and sometimes I just have to be a silly, stubborn contrarian ;-)
So Bitbucket just happened to be where I posted the repo. I'm hoping we can move it to WineHQ's git server relatively soon, but if anyone on Github wants to clone it too, that would be great. Since there are more people, it would probably be better for code review, and if someone else wants to manage it, I would have no problem setting my fork on Bitbucket to track a Github version as upstream.
FWIW i created such a clone: https://github.com/AndreRH/wine-wiki
On 9 October 2012 00:17, André Hentschel nerv@dawncrow.de wrote:
Am 08.10.2012 01:06, schrieb Kyle Auble:
Just wanted to let everyone know I've created a git repo for the Wine Wiki from the CVS one at SourceForge. You can find it at: https://bitbucket.org/kauble/wine-wiki-migration
Not sure if bitbucket is the right place, there are not much repos regarding wine. Have a look at github, there we have e.g. 49 wine forks (https://github.com/mirrors/wine/network/members) and it's recommended by http://wiki.winehq.org/GitWine
I realize github is fairly popular at the moment, but do we really want to recommend proprietary git hosting services? Also, https://git.wiki.kernel.org/index.php/GitHosting has a good overview of what's available in terms of git hosting sites.