[sr-dev] Slightly wacky suggestion...

Carlos Ruiz Díaz carlos.ruizdiaz at gmail.com
Fri Aug 30 14:23:42 CEST 2013


+1 for GitHub too


On Fri, Aug 30, 2013 at 4:27 AM, Richard Brady <rnbrady at gmail.com> wrote:

> +1 for GitHub
>
> On 29 Aug 2013, at 17:58, Peter Dunkley <peter.dunkley at crocodilertc.net>
> wrote:
>
> The advantages of concentration are lower costs and richer feature set.  I
> am sure the time of the Kamailio developers is better spent on Kamailio
> than running a tracker, repo, and so on that still won't be as good as the
> concentrated one.
>
> If I was setting up an open-source project today I certainly wouldn't run
> the repo, tracker, etc myself - it just wouldn't make sense.  Even if
> GitHub became evil in the future I could move.
>
> I think it makes sense for any project to review these kind of logistics
> from time to time as we are in a rapidly changing world, and given that
> there was some discussion about code re-structuring before the next major
> release a few months back, now would seem a logical time to give it some
> thought.
>
> I am quite happy with the status-quo if no-one wants to change but do
> think this merits some consideration to make sure we aren't missing out on
> something that could help us.
>
> Regards,
>
> Peter
>
>
> On 29 August 2013 09:41, Olle E. Johansson <oej at edvina.net> wrote:
>
>>
>> 29 aug 2013 kl. 18:29 skrev Peter Dunkley <peter.dunkley at crocodilertc.net
>> >:
>>
>>
>>
>>    - The GitHub concept of forking would make individual developers
>>    branches easier to manage.
>>    - The GitHub concept of forking and push-requests would make it
>>    easier for people who are not core developers to submit patches and for the
>>    core developers to review them and apply them.
>>    - People have been complaining about flyspray for a while and the
>>    GitHub tracker is nicely integrated into the repository making it easy to
>>    relate issues to code and patches.
>>    - The GitHub web-UI means that the code is easier to browse, inspect,
>>    view history (and relate changes to issues) than the "default" Git one that
>>    is in use at the moment.
>>    - There would be no need for anyone to spend time or money
>>    maintaining/patching/fixing the SIP Router Git repo and flyspray.
>>    - Someone else is handling backups and failure recovery.
>>    - The use of markdown means that documentation and code can be
>>    presented together in a nice way with GitHub.
>>
>>
>> I am sure there are more too (which is why so many projects are on there
>> now).
>>
>> Apart from this, there's a massive concentration of code and projects on
>> a single site. Sourceforge now is rumoured to send malware with downloads,
>> what can happen to github in the future? Is this concentration a Good Thing
>> (TM) ?
>>
>> The Internet is distributed.
>> /O
>>
>> Peter
>>
>>
>>
>> On 29 August 2013 08:49, Alex Balashov <abalashov at evaristesys.com> wrote:
>>
>>> Peter,
>>>
>>> What do you see to be GitHub's virtues for this project?
>>>
>>>
>>> Peter Dunkley <peter.dunkley at crocodilertc.net> wrote:
>>>>
>>>>  Hello,
>>>>
>>>> There was some talk about restructuring the Kamailio code (for example,
>>>> putting the core into an "src/" or "core/" directory and having an
>>>> "include/" directory).
>>>>
>>>> Would there be any mileage in considering a move to GitHub for the
>>>> repository at the same time?
>>>>
>>>> Regards,
>>>>
>>>> Peter
>>>>
>>>> --
>>>> Peter Dunkley
>>>> Technical Director
>>>> Crocodile RCS Ltd
>>>>
>>>> ------------------------------
>>>>
>>>> sr-dev mailing list
>>>> sr-dev at lists.sip-router.org
>>>>
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>>>
>>>>
>>> --
>>> Sent from my mobile, and thus lacking in the refinement one might expect
>>> from a fully fledged keyboard.
>>>
>>> Alex Balashov - Principal
>>> Evariste Systems LLC
>>> 235 E Ponce de Leon Ave
>>> Suite 106
>>> Decatur, GA 30030
>>> United States
>>> Tel: +1-678-954-0670
>>> Web: http://www.evaristesys.com/, http://www.alexbalashov.com
>>>
>>> _______________________________________________
>>> sr-dev mailing list
>>> sr-dev at lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>>
>>>
>>
>>
>> --
>> Peter Dunkley
>> Technical Director
>> Crocodile RCS Ltd
>>  _______________________________________________
>> sr-dev mailing list
>> sr-dev at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>
>>
>>  ---
>> * Olle E Johansson - oej at edvina.net
>> * Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden
>>
>>
>>
>>
>> _______________________________________________
>> sr-dev mailing list
>> sr-dev at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>
>>
>
>
> --
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>


-- 
Carlos
http://caruizdiaz.com
+595981146623
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20130830/86a442e0/attachment.html>


More information about the sr-dev mailing list