Hi all,
Just a heads up on our situation.
TL;DR. How can we manage our fork and be able to share code between our forks
8D
We are currently forking `fxa-{content,auth,oauth}-server` [0][1][2] for our
own needs at webplatform.org.
Using your projects will require us to adjust the theme in a way to make a
clear distinction when our users will authenticate on our site but we also
might have to adapt some fields in the content+auth server so we can
monkeypatch with our MediaWiki installation.
What I got is:
- auth project must be checkout from origin/train-{n}
- content project to be checkedout from oauth branch in the meantime it gets
merged to master
I can isolate what is specific to webplatform (db fields, theme) in a branch
and squash my commits/pull-requests if something can be beneficial to both of
us.
I just want to be sure to understand how you manage branches.
Regarding oauth:
- I understand that you will be supporting OAuth 2 [3] and eventually get
into crypto w/ ed25580.
Ideally for us, we'd use basic oauth2, and, later, to support a more secure key
exchange.
But lets not put two agendas in one project.
Advices are welcome
[0]: https://github.com/webplatform/fxa-auth-server
[1]: https://github.com/webplatform/fxa-oauth-server
[2]: https://github.com/webplatform/fxa-content-server
[3]: https://github.com/mozilla/fxa-oauth-server/pull/29
[3]: https://github.com/mozilla/fxa-oauth-server/issues/7
--
Renoir
~_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
