[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tracecompass-dev] "Official" Tracecompass github?
|
Alright, since people seem to have ideas of how it could be useful, we
can give it a try. It does not cost anything to experiment a bit!
I went ahead and created https://github.com/tracecompass/tracecompass
The master branch is updated manually at the moment, I'll look into
setting up a cron job to update it automatically.
If any committers want write access, just ping me or Matthew. But please
don't flood it with tons of "WIP" branches, personal repositories still
exist for a reason ;)
We will also have to clarify that we cannot take pull requests directly,
and direct people to the contributor instructions.
Cheers,
Alex
On 2015-06-03 03:47 AM, Geneviève Bastien wrote:
Oh, so it would be an "official" "experimental" branch, like the
dorsal-experimental branch, but for everyone. Maybe a github team? With
a repo that everyone on the team can push to? or send pull-requests to,
just for "incubation".
The way I did it for dorsal-experimental is the branch was just a merge
of all the students' branches, sometimes with latest master and new
students would sometimes start their work with the dorsal-experimental
branch instead of master to take advantage of other's work.
But my advice: just don't keep features in experimental branches for too
long, that branch gets nightmarish real quick and you are in hell when
each feature separately makes it to master and you need to resolve all
the conflicts ;-) The way you describe it (everyone working on top of
everyone else's work) puts more pressure on developers to send their
features to master instead of keeping it in incubators.
On the other hand, an official experimental branch somewhere, but not in
main tree, is very useful. For proof, the dorsal-experimental branch has
been published more than once, so people could try out students' works
while it waits for cleanup and push to master.
So... I guess I don't answer the question at all!
Geneviève
On 06/01/2015 12:54 PM, Matthew Khouzam wrote:
Genevieve, here is the situation:
Let's say student team a pushes a github copy of tc,
student team b pushes another copy.
3 colleagues also have copies
right now it's controlled.
But, let's say Marc Andre develops a gzip feature tc. like import gzip.
I go: oh, I can make a ctf parser with gzip compression, then I add gzip
to the state system backend. I ask Alex to review the idea, and he likes
it so much he adds gzip compression to remote traces before transmitting
them. He asks for Bernd's opinion.
That situation both excites and scares me.
But the more I think about it, the more I dislike working with github
and I think we may just need another incubator for featurelings.
Matt
On 15-05-29 10:13 PM, Geneviève Bastien wrote:
Matthew, by many forks, do you mean many copies of the whole repo or
many branches on one repo?
I don't think we need an "official" tracecompass github. As Marc-André
says it would be confusing. If you use patches to communicate, then you
can very well put them on a branch on your personal repo and your
interlocutor can pull them from your remote repository. That's how we do
it at Poly: everyone has his own remote repo and we pull the works from
our colleagues as we need it before it gets to the real official
tracecompass git. Or maybe I don't understand what your intent really is.
Geneviève
On 05/29/2015 11:27 AM, Matthew Khouzam wrote:
I think we are all in agreement to that. We need to only have one vector
of entry. Just like we will guide people sending patches on this mailing
list to gerrit, we should do that with github, and maybe even have an
automated friendly response to pull requests like : Please contribute
this patch via gerrit, here's a link to how to do it...
Matthew
On 15-05-29 09:50 AM, Bernd Hufmann wrote:
Hello
Github is interesting if contributors want to quickly exchange and
share code during a development phase. But it should not be used as
integration platform of new features.
The Trace Compass repo at Eclipse should be the main repository and
main repository for integrating contributions. Also, the contribution
process defined by Eclipse and
used by Trace Compass should be used integrating features to Trace
Compass.
Bernd
On 05/27/2015 11:32 PM, Marc-André Laperle wrote:
I think one problem with having an "official" github repo is the
confusion it creates. People created pull requests for Eclipse
project mirrors and no one noticed them. I also don't really think
it's necessary either. It should be manageable to have many forks. I
think Matthew is just being too awesome by having that many forks :)
BTW, you can rename repositories too if that helps.
________________________________________
From: tracecompass-dev-bounces@xxxxxxxxxxx
[tracecompass-dev-bounces@xxxxxxxxxxx] on behalf of Alexandre
Montplaisir [alexmonthy@xxxxxxxxxxxx]
Sent: Tuesday, 26 May 2015 5:50 PM
To: Matthew Khouzam
Cc: tracecompass developer discussions
Subject: Re: [tracecompass-dev] "Official" Tracecompass github?
Ok so, I asked the EMO, but they've told me that Eclipse mirrors on
Github are no longer supported and that they will eventually be removing
the ones currently there. So scratch that option.
This made me realize, since we are not controlling the remotes neither
at Eclipse or Github, we would have to setup a server somewhere with a
cron job that pulls from Eclipse and then pushes at Github, and other
potential mirror locations. This is not exactly hard to do, but we would
need to find a host or individual willing to host and maintain this.
On 2015-05-25 05:53 PM, Matthew Khouzam wrote:
I tend to communicate by patches. ;)
I didn't know about that one, it is the right way to do things,
let's go
for it!
On 15-05-25 05:41 PM, Alexandre Montplaisir wrote:
Hi Matthew,
How about https://github.com/eclipse ? ;)
Any project can ask to get mirrored on Eclipse's Github. We would just
have to ping our EMO.
However, if we don't intend on accepting external contributions
through Github, I am not sure it would be really useful. You mention
you have 7-8 forks of the project, are you really sharing patches with
7-8 different people?
If it's only to pull paches, you could use one unique repo and setup
several remotes locally.
On the other hand, if you do want to share patches with other people
(and not send to to the "official" repo, at least not right away),
then from what I understand of how Github works, you would *still*
have to handle 7-8 forks on your own Github.
Thoughts?
Cheers,
Alex
On 2015-05-25 05:16 PM, Matthew Khouzam wrote:
Hi all,
If you look at my github, you will see 7-8 forks of trace compass.
The
reason is, we are not using github properly IMO.
We need a curated tracecompass main repo on github, and for people to
fork from that one. I'm not sure about the IP implications of doing
this, does anyone know if we're allowed to do that? We cannot I
think,
use ericsson's official github. I am still trying to find who is in
charge of it, maybe Efficios's github could be the official
tracecompass
branch? If we get a company name behind it, I think the workflow will
clean up like this.
Thoughts?
Matthew.
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
