GitHub

[Dan Meltzer]

They are not.  Until translations are solved and history can  be
imported correctly kde sysadmins only want to support svn.

On 1/7/09, Teo Mrnjavac <teo.mrnjavac at gmail.com> wrote:
> On Wed, Jan 7, 2009 at 7:04 AM, Dan Meltzer
> <parallelgrapefruit at gmail.com> wrote:
>> The downside to any of these options is that we still need to merge
>> back to svn at some point.  As many know, this usually ends up being
>> more work than it's worth.  Until kde supports git officially svn is
>> going to be the point of contact for new contributters and should
>> remain so to prevent a duplication of accounts and a horrid mess when
>> it comes to translations.
>>
>> On 1/7/09, Leo Franchi <lfranchi at kde.org> wrote:
>>> On 6 Jan 2009, at 23:05, Jeff Mitchell wrote:
>>>
>>>> Leo Franchi wrote:
>>>>> On 6 Jan 2009, at 22:04, Jeff Mitchell wrote:
>>>>>> Please understand that I'm not totally down on Github...it has its
>>>>>> place, and works very well for some things, especially for small
>>>>>> personal projects.  But I've also had to do lots of dealing with
>>>>>> what
>>>>>> happens when things go wrong with its model, which starts to break
>>>>>> down
>>>>>> and make things harder when people are doing more than sending
>>>>>> just a
>>>>>> patch or two, especially if they are not sharing an account.
>>>>>>
>>>>>> If Amarok people want to use Github, that's fine; but I would very
>>>>>> strongly recommend that everyone then share an account for Amarok
>>>>>> development work.  It's also worth noting that Github is closed
>>>>>> source,
>>>>>> so if people are uncomfortable with that, they should be looking at
>>>>>> Gitorious or some such thing.
>>>>>>
>>>>>
>>>>> So all that said:
>>>>>
>>>>> what do you recommend for us?
>>>>
>>>> I recommend, if Github is used, that we all share an account.
>>>>
>>>> Whether Github should be used at all is a matter that the group will
>>>> have to decide.  It provides some ease of use in terms of setup, but
>>>> makes things more complicated for anyone outside the project that
>>>> wants
>>>> to track our work while providing patches of their own.
>>>
>>> I meant what are the non-github options? Coming from the relative git
>>> n00b that I am, are the choices github OR we host our own git server
>>> on kollide? Whats the  benefit of doing github we can easily just make
>>> our own server do the same and not have all those nasty issues that
>>> you mention?
>>>
>>> leo
>>>
>>> ---
>>> Leo Franchi                           (650) 704 3680
>>> Tufts University 2010
>>>
>>> lfranchi at kde.org
>>> leonardo.franchi at tufts.edu
>>>
> Couldn't we ask nicely if the k.o admins would consider hosting a git
> server at least for extragear projects that aren't tied to KDE's
> schedule anyway?
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>