Re: [cdt-dev] CDT on Github

[Marc Dumais <marc.dumais@xxxxxxxxxxxx>]

Hi Doug,

Indeed, Theia, or eventually the C/C++ IDE product based on it, will also need an awesome gdb debug adapter. 

We have recently done some prototyping on this, where we got code-debug (https://github.com/WebFreak001/code-debug) to (minimally) run on top of Theia's recent DAP contribution. We reached-out to the author, but he did not seem interested to make it multi-IDE, so we would probably need to fork it, if we want to do serious work on it, for Theia. 

That being said, it's ery early in the game and no final decision is made on our side.  We are willing to consider other DAs, specially if there is good potential for collaboration. 

I did have the same question as Marc-Andre, about doing this work as part of the existing CDT project. It seems that a more IDE-neutral "home" would be good, and more likely to attract a wide array of IDE contributors. The project could still be under the Eclipse Foundation, but perhaps as a new project?

Regards,

Marc

---

From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Monday, October 29, 2018 2:44 PM
To: CDT General developers list.; Nathan Ridge
Subject: Re: [cdt-dev] CDT on Github

 

Hey, Marc, while I have you here, I imagine Theia will also need a gdb debug adapter. There was certainly a lot of buzz on Theia at EclipseCon and it should be on our list of supported IDEs as well. I actually think it does certain things better than VS Code and am giving it a serious look. Hopefully we can work together on it.

 

Doug.

 

 

From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> On Behalf Of Marc Dumais
Sent: Monday, October 29, 2018 2:31 PM
To: Nathan Ridge <zeratul976@xxxxxxxxxxx>; CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] CDT on Github

 

Hi there,

 

" I find them awkward having to work in a fork that needs to be magically kept up to date and stuff"

 

That's only true for non-committers, AFAIK. Committers should have required permissions to create branches on the main repo, so pull requests can originate from there, rather than a fork, if preferred. 

Regards,

 

Marc

 

---

From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Monday, October 29, 2018 2:22 PM
To: Nathan Ridge; CDT General developers list.
Subject: Re: [cdt-dev] CDT on Github

 

Good question. For the new repos, it would be Github Issues and Pull Requests. I actually find their Issues better than bugzilla. But I've never been a fan of Pull Requests, mainly because I find them awkward having to work in a fork that needs to be magically kept up to date and stuff. But that's how Github works and that's where most new open source projects end up. Working in VS Code and the _javascript_ world in general has been eye-opening on that.

For org.eclipse.cdt, I don't suggest any changes. Basically all we'd be doing is moving the existing repo, https://github.com/eclipse/cdt, to our new org, maybe with a rename to make it clear it's the Eclipse plug-ins.


HTH,
Doug

-----Original Message-----
From: Nathan Ridge <zeratul976@xxxxxxxxxxx>
Sent: Monday, October 29, 2018 2:14 PM
To: Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>; CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: CDT on Github

> Any thoughts for or against?

I don't have any opinion on the location of the repository itself.

However, I wonder: would this affect bug tracking (Bugzilla) or code reviews (Gerrit)? I prefer both of those over their Github equivalents.

Regards,
Mate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev