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