[kde-community] Official KDE mirror on github
me at vhanda.in
Sat Sep 19 14:04:46 UTC 2015
On Sat, Sep 19, 2015 at 3:33 PM, Boudhayan Gupta <bgupta at kde.org> wrote:
> Hi all,
> This discussion is becoming nothing but a royal waste of time.
> Let me summarise:
> 1. We generally agreed before starting that this was going to be a
> read-only mirror.
> 2. For consistency's sake, we cannot enable issues/pull requests for
> only some repos and disable for others.
We can. We might choose not to do so, but it is possible.
Please note that consistency isn't a requirement to be part of KDE. If
I decide to write an application in Rust, which is only for Windows,
and uses a completely different build system, that is allowed.
> Now here's what I think from a common sense perspective:
> 1. Due to point 3, we cannot in any way rely on GitHub being up or
> available at all.
> 2. Due to points 1 and 2, we cannot in any way enable pull requests on
> the GitHub mirrors.
Again we can. Since (2) does not hold true, this point is invalid.
> 3. Regarding point 4, if developers already have personal GitHub
> clones that they use for their own purposes, nothing is stopping them
> from continuing to use them. Those clones are not endorsed by KDE,
> they are under complete control of the individual
> developers/maintainers, they are entirely the responsibility of the
> developers/maintainers, and the developers/maintainers are free to do
> with them as they see fit.
Because maintainers are not responsible for their own projects anyway?
If I'm taking responsibility for a project, I'm also taking
responsibility for other parts of it. In this case Github. No one is
> 4. As for 5 & 6, "better" is a matter of personal taste. We *are*
> moving to Phabricator eventually, which should make things better and
> more GitHub-like for others (although you will need a KDE Identity).
> Here's what developers and maintainers should really do: forget that
> github.com/kde exists.
They can do that if they are comfortable with the status-quo. Some
people are clearly not. Your email disregards the points raised and
implies that the github readonly mirror is only what is acceptable.
That result is clearly not shared by everyone.
> For all practical purposes, it does not exist.
> It isn't there. It should never be a part of your workflow. You should
> never ever look at it. It is simply an additional clone source, just
> like KDE's anongit servers. That's it.
This is the part of your email I really like. Though this is not what
you meant: If projectX choose to also use Github, it is not affecting
your project in anyway. Just ignore it and move on.
More information about the kde-community