github would be better than having nothing though.
We wouldn't have such a sophisticated search anymore, right (i.e. pickaxe/regex search)?
Do we have git hooks that we couldn't port? (e.g. for checking line endings and for notifying the IRC bot/snapshot system)
PS: Still not convinced though. What about setting it up at the new server?
>We wouldn't have such a sophisticated search anymore, right (i.e. pickaxe/regex search)?
Those search options are just thin wrappers around standard git commands, so you'd have to use those in your local clone.
> checking line endings
This one is a bit problematic. GitHub doesn't support synchronous hooks that could block pushes. All you can do is mark some commit as failing the checks. There's the concept of "strict checks", but with those, you can't push to protected branches (i.e., master) directly and have to go via a separate branch (plus pull request) instead. I believe that having everything go through a minimum amount of code review via a pull request would be a good idea, as we have some really low-quality commits from time to time (including from me) where issues could be easily caught by having someone else have a quick look. But this should be a separate discussion in any case.
>notifying the IRC bot/snapshot system
These work fine with webhooks. GitHub also has some built-in IRC and Mantis notifiers we might try out.
>What about setting it up at the new server?
See above, it's another thing I'd have to administrate which I am not happy about.
I think the loss in features would be minimal (just a few search options Zapper said, I guess). As far as I know, git hooks are possible with github?
Apart from that, I like the few extra functions, like code review through comments. And we aren't handling the github content fully, meaning that we don't really respond to issues or pull requests in due time. Especially pull requests I find very annoying to incorporate with our separated repository.
>meaning that we don't really respond to issues or pull requests in due time
I don't think that will change. You already have the complete repository on github and can activate notifications for issues and pull requests. I, for example, check the github page frequently. Why would that change if the other server was gone?
>Especially pull requests I find very annoying to incorporate with our separated repository.
Ideally the person who merges the github requests tests them, too. So then you'd need to pull them to your local repository anyway.
(What I am saying is: please test stuff!)
>I am by the way in favour of changing!
But yeah, I am still not completely against it. I just don't see what we would win. And we would lose a bit (even if "just" the search options (which I have used)).
>Using github streamlines a lot of that, so we might consider moving issue tracking over completely as well.
What would be the advantages? Users can report issues on GH already and I don't have the feeling that those have been neglected so far.
We would, again, only lose some features. E.g. release planning (roadmap), which we have used extensively over the last 9 years
>I perceive github as the de-facto standard for open-source communities.
> I usually stop bothering reporting a bug for some project once I notice I have to register a new account in some obscure bugtracker
At least with the personal repositories, I guess? Maybe another reason to switch to github? I know this was an exceptional things but still, github is less prone to major failures, I'd say.
Or to say it differently: how long are we to wait until things return to normal? (See e.g. the problem Randrian got with the missing resource repository). And with that, I am definitely not saying that Isilkor should hurry up and work for us. No. Rather, us switching to a full-fledged git service that is ready to use without one person having to invest hours of work into getting things done on a private server.
(There's no functional difference for non-committers, so I propose we count committer's votes only.)
Though, to switch to github issues could be an opportunity to have a fresh start there: Keep around the old bugtracker for a while (read only perhaps) and only move over the important things. (Crashes, bugs and things that are important to the developers)
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill