What is the recommended way to fork Nuxeo?

The Getting the Nuxeo source code documentation says:

Contributing to Nuxeo does not require cloning Nuxeo source code

But when I want to play around and modify things and possibly later send various pull requests, is not it best if I have forked the repositories beforehand? I usually commit/push and create branches liberally, which I can't do if I have no write access to the repositories.

After cloning https://github.com/nuxeo/nuxeo , building requires me to clone dozens of other repositories. Is there a recommended way to choose what repositories to clone and what repositories to use directly from upstream? I noticed that some of these repositories have barely ever been forked by anyone, so there must be an alternative to cloning them all?

0 votes

1 answers

1044 views

ANSWER



Hi,

Choosing what to clone or not depends on the kind, the code location and the size of the contribution.
See Contributing to Nuxeo.

Fork then Pull-Request is the GitHub preferred way for sending a patch. It's indeed an easy process.

If you want to contribute changes on an addon for instance, you can clone and/or fork only that repository.

When you build a module, the required dependencies are downloaded from the online Maven repositories.
If you want to perform a full build starting from the source code root (https://github.com/nuxeo/nuxeo), then yes: you will need to locally retrieve the whole source code. You can easily do it with the helper clone.py script.
Clone and fork is not the same thing: you can clone the whole source code (all repositories) and fork only the repository(ies) you want to contribute to.

0 votes