Re: [Ctags-devel] Future of ctags

[Darren H. <dhi...@us...>]

Hello Frank,

I haven't forgotten you. My main apprehensions have been migrating to Git, and hosting off of SourceForge.

We began using git on a project at work and it has been a ride. While I knew how to use Subversion thoroughly, I do not have such a comfort level with git and don't know how to undo problems that occur. We have had changes wiped out at work that had to be restored when folks would push from their local repository that didn't get fully merged with changes from others. This necessitated the only two guys who know how to get us out of the mess in order to restore the files that got overwritten with older files. Considering how often this has happened, I have some trepidation.

Secondly, I prefer that ctags be hosted on SourceForge. I am uncertain how we can use git to do that, but still host on SourceForge. Can you please explain further to me how that can be done?

Darren

> On Jan 28, 2015, at 10:00 AM, Frank Fesevur <ff...@us...> wrote:
> 
> Hi Darren,
> 
> Is there anything we can do to help you? Any questions we can answer?
> Problems we can solve?
> 
> If you are still in doubt about git and GitHub, please read these
> blogposts by the .NET team of Microsoft. MS has integrated git in
> Visual Studio quite nicely IMHO (Yes, the idea of Linus Torvalds -
> maybe even code he has written - is used a MS product), they are
> active contributing to the development of libgit2 and MS is moving at
> least some of their open source project from their own CodePlex
> platform to GitHub, simply because that is where the community is.
> http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.aspx
> http://blogs.msdn.com/b/vbteam/archive/2015/01/10/we-re-moving-to-github.aspx
> 
> And see how your project has been revived at GitHub. An active
> community has grown there. This week an quite detailed issue and a
> pull request were submitted by two new people. People are finding
> ctags at github and willing to contribute.
> 
> And we really want to move forward, together with you! We'll continue
> to use Sourceforge for the webhosting, the mailing list and probably
> as the download platform, but move the main code repo and issue
> tracker to the GitHub organization. Then fix some last known bugs,
> update the documentation including the man page and prepare for the
> release of exuberant ctags 6.0
> 
> Kind regards,
> Frank
> 
> 
> 2014-12-19 6:23 GMT+01:00 Darren Hiebert <Da...@da...>:
>> 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
>>> 
>>> Ctags-devel mailing list
>>> Cta...@li...
>>> https://lists.sourceforge.net/lists/listinfo/ctags-devel
>>> 
>> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Ctags-devel mailing list
> Cta...@li...
> https://lists.sourceforge.net/lists/listinfo/ctags-devel
>