[kde-community] Official KDE mirror on github

[Jaroslaw Staniek]

On 18 September 2015 at 14:00, Ben Cooksley <bcooksley at kde.org> wrote:
> On Fri, Sep 18, 2015 at 11:54 PM, Jaroslaw Staniek <staniek at kde.org> wrote:
>> On 18 September 2015 at 13:42, Boudhayan Gupta <bgupta at kde.org> wrote:
>>> Ladies and gentlemen, as you read this mail github.com/kde is being
>>> populated by the initial sync of all repositories.
>>>
>>> Maybe someone should make a public announcement?
>>>
>>> Shout out to Ben, he truly is a superhero.
>>
>> Thanks a lot!
>> Is it possible to enable Issues support for a given project? (as I
>> said needed by the bountysource infra at least)
>
> From what I saw of the above consensus, issues and pull requests would
> be disabled as those should go through our usual infrastructure
> (todo.kde.org / bugs.kde.org / reviewboard.kde.org) - if there is a
> post otherwise i'd be happy to be pointed to it though?

I see what you mean but there was no discussion about this matter in
this thread at least.

For code I maintain I welcome:
- any form of patches even if they come via pull requests, just like
for me emailed patches are also better than no patches
- any form of donations for features -> for that Issues are needed

It's possible to fork these mirrors to get this support and I am doing
this now for a test in case of kreport.git.
https://github.com/staniek/kreport-1

But again, please consider this as less controlled/predictable
activity - that forking will happen anyway, as this is the value of
github-based collaboration, and (IMHO) sense of our existence on
github.

>>
>>>
>>> On 17 September 2015 at 20:00, David Edmundson
>>> <david at davidedmundson.co.uk> wrote:
>>>>
>>>>
>>>> On Thu, Sep 17, 2015 at 1:12 PM, Patrick von Reth <vonreth at kde.org> wrote:
>>>>>
>>>>> Hm I have an existing github mirror with some stars. Instead of
>>>>> creating a new mirror I'd prefer to just set KDE to the new owner of
>>>>> the Project.
>>>>> I guess this is not the only project where that kind of migration is
>>>>> preferable.
>>>>> So what to do for those projects?
>>>>>
>>>>
>>>> We would need to add you as an admin member of the github KDE group, then
>>>> you click "Transfer ownership" in the repo settings.
>>>> Stars and forks migrate (I tested this just now).
>>>>
>>>> Providing the repo names match KDE, the script we have shouldn't create a
>>>> new repo but will just push into this one.
>>>>
>>>> More info at: https://help.github.com/articles/transferring-a-repository/
>>>>
>>>> David
>>>>
>>>>
>>>> _______________________________________________
>>>> kde-community mailing list
>>>> kde-community at kde.org
>>>> https://mail.kde.org/mailman/listinfo/kde-community
>>> _______________________________________________
>>> kde-community mailing list
>>> kde-community at kde.org
>>> https://mail.kde.org/mailman/listinfo/kde-community
>>
>>
>>
>> --
>> regards, Jaroslaw Staniek
>>
>> KDE:
>> : A world-wide network of software engineers, artists, writers, translators
>> : and facilitators committed to Free Software development - http://kde.org
>> Calligra Suite:
>> : A graphic art and office suite - http://calligra.org
>> Kexi:
>> : A visual database apps builder - http://calligra.org/kexi
>> Qt Certified Specialist:
>> : http://www.linkedin.com/in/jstaniek
>> _______________________________________________
>> kde-community mailing list
>> kde-community at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-community
> _______________________________________________
> kde-community mailing list
> kde-community at kde.org
> https://mail.kde.org/mailman/listinfo/kde-community



-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek