Wine Gecko repo

[Jacek Caban]

Hi,

A few months ago, SourceForge did some deep changes in their Git (and
not only) repo hosting. While doing it, the location of repos has
changed (which is extremely stupid, if you ask me). The problem is that
while doing the update, they also switched to their own Web interface
for git. And this shiny new interface doesn't work at all for Wine Gecko
repo (wine-gecko.git probably too big and complicated). See [1], it
claims to be analyzing the repo, but it has been like that since the
switch was done. I contacted them [2] and they are aware of the problem,
but it's still not fixed.

I already got some questions about outdated sources. Also, our Wiki
points to this Git in a few places. I never updated those links because
I was waiting for the new repo to work. I think it's time to move the repo.

The question is, where should it go?

- Github seems to be the choice for most project currently and it's
already used by Wine Mono.
- Reconsider source.winehq.org. This was not chosen due to account
management overhead, but that's the only way to avoid problems similar
to recent Sourceforge one (Github nor anyone else is going to give us
any guarantees)
- Other ideas?

I'd appreciate opinions.

Thanks,
Jacek

[1] https://sourceforge.net/p/wine/wine-gecko/ci/master/tree/
[2] https://sourceforge.net/p/forge/site-support/4299/

[Henri Verbeet]

On 13 August 2013 12:28, Jacek Caban  wrote:
> The question is, where should it go?
> - Github seems to be the choice for most project currently and it's
>
> already used by Wine Mono.
> - Reconsider source.winehq.org. This was not chosen due to account
>
> management overhead, but that's the only way to avoid problems similar
> to recent Sourceforge one (Github nor anyone else is going to give us
> any guarantees)
> - Other ideas?
>
> I'd appreciate opinions.

I'm not much of a fan of github in general, and I think it's a bit
awkward that Wine Gecko and Wine Mono aren't available from WineHQ, so
I'd be in favour of hosting it at source.winehq.org. If account
management is the issue, perhaps we could have a setup where Alexandre
pulls from from Vincent and you and pushes to those repositories, but
then perhaps that's worse in terms of overhead.

[Vincent Povirk]

There is dedicated git hosting software (such as gitolite and gitosis
- most people in #git seem to prefer gitolite) that provides
account-based access to Git repositories without providing any general
shell access. Perhaps something like that could be set up on
source.winehq, running on a dedicated, limiter user account?

Apparently you can also set a user's shell to git-shell to limit that
user to the operations needed to push or fetch.

Then again, if shell accounts with limited access weren't good enough
then I don't know if something like this will help.