Re: [Ctags-devel] Future of ctags

[Frank F. <ff...@us...>]

Hi Darren,

I don't have much to add to other posts (all of them have contributed
to the github repo).

The two most important features for me are github's Pull Requests (PR)
and the Travis CI integration.

With the way gibhub allows you to fork/copy a repo, do your changes
and submit a PR, it is very easy for everybody to submit their
improvements to the upstream project. Most of the code that is
contributed the last months has been PRs.

The Travis CI integration is also very useful. This means that the
code gets compiled every time something is pushed to the repo. This
way we make sure the code compiles in Linux and Windows. And with the
new introduced units tests, Travis CI checks if the new code does not
break old code. Because this also works for submitted PRs those basic
checks are done before new code is reviewed.

Regards,
Frank



2014-12-19 6:55 GMT+01:00 Darren Hiebert <dhi...@us...>:
> Frank,
>
> If I understand you correctly, you are proposing that the source code no longer be hosted at SourceForge, which is what I would prefer. What are the reasons that you believe that SourceForge cannot provide the support necessary?
>
> Darren
>
>> On Dec 12, 2014, at 2:41 AM, Frank Fesevur <ff...@us...> wrote:
>>
>> Hi Darren,
>>
>> How are things going? Are you running into problems? If so, is there
>> anything I can do to help you?
>>
>> Regards,
>> Frank
>>
>>
>> 2014-11-19 17:24 GMT+01:00 Frank Fesevur <ff...@us...>:
>>> 2014-11-19 7:15 GMT+01:00 Darren Hiebert <dhi...@us...>:
>>>> Hello Frank,
>>>>
>>>> I am here and ready to talk about making this happen. I need a few days to come up to date on the links you posted, and get myself back in shape for building a release. How do you propose merging? Merging the changes in the github back into the Subversion repository on SourceForge?
>>>>
>>>> Darren
>>>
>>> Great to hear from you!
>>>
>>> The easiest way is to build it is to clone the github repo (git clone
>>> https://github.com/fishman/ctags.git) and do the normal building
>>> steps.
>>>
>>> All the code in the SVN is already in the github repo. We think the
>>> best way is to start/continue using git and store the repository at
>>> github.
>>>
>>> At the moment the repo is a personal repository of Reza Jelveh aka
>>> "fishman". We want to convert that repository into an organization.
>>> One of the advantages of organizations on github is that is gives you
>>> more control over permissions and it is not tied to one person
>>> anymore. And by converting the repo all the history already build is
>>> preserved. Once it is converted, we use that git repository as the new
>>> upstream repository.
>>>
>>> I already created an organization named "exuberant-ctags"
>>> https://github.com/exuberant-ctags
>>>
>>> At this moment it is still empty, but I will set it up any time soon.
>>> That means adding the collaborators of the current repo as owner or
>>> developer and then move the repository. I want to add you as an owner
>>> as well, but I need to know your github account name for that. Of
>>> course, the original members of the sf-team can be added as well if
>>> they are still interested in ctags.
>>>
>>> After that I think we can prepare a release. Some cleanup (both code
>>> and docs) has to done, but it is pretty stable code.
>>>
>>> Regards,
>>> Frank
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Ctags-devel mailing list
>> Cta...@li...
>> https://lists.sourceforge.net/lists/listinfo/ctags-devel
>>
>