[Gta04-owner] Wakelocks working on GTA04/Replicant
Paul Kocialkowski
contact at paulk.fr
Sun May 11 10:03:36 UTC 2014
> Maybe we should only have one tree since asking others to look into
> foreign trees does not work.
>
> So I suggest that Replicant simply imports (or mirrors):
>
> https://github.com/goldelico/gta04-replicant/
>
> and the others. instead of running its own GTA04 code repo.
What exactly are you suggesting? I don't think we can merge the trees
just yet, I'm not ready to accept a handful of the changes you made in
the Replicant upstream tree. If you're talking about having separate
branches, but in the same repo, I don't really see the point.
It's not that hard to keep track of the two different repos and import
the patches we want from one to the other.
> Why this way around? You are in the exceptionally comfortable situation that
> a hardware vendor is maintaining the system…
>
> If we choose it the other way round, we are never sure that GTA04 development gets
> the priority by Replicant developers it needs (there was some time where Replicant did
> not develop at all for GTA04 because of lack of resources).
So that's why I think it's still relevant to have separate trees. I'm
not closed to external contributions, but not everything is good to have
in Replicant upstream and I want to keep things in order, so it makes
sense to have a Goldelico tree with all the exciting new features (e.g.
fixed Hayes-RIL in device/goldelico/gta04), but I'm never going to
accept that in Replicant upstream.
I guess the important thing for end users is to have an option at all,
whether it's coming from Replicant or from Goldelico doesn't change
much.
If you're worrying about duplicating the effort, we can easily
coordinate that by talking about what we do on the mailing list and
looking at each other's changes before getting back to working on a
particular topic.
Also, note that we're in the development phase, but it will soon be over
(my roadmap for gta04 is getting smaller and smaller every day) so this
won't be an issue for long and when both out trees are fully-featured,
we can decide about whether to keep a single repo and where it should
be.
> And if you have upstream patches, please submit them to Lukas.
We could make it a habit to submit patches that seem relevant for the
other in the mailing list like many projects do, I'm find with that :)
--
Paul Kocialkowski, Replicant developer
Replicant is a fully free Android distribution
Website: http://www.replicant.us/
Wiki/Tracker: http://redmine.replicant.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20140511/e0da1175/attachment.asc>
More information about the Replicant
mailing list