this is great idea, I think git submodules will work for us,
I would suggest to create new organization richfaces-thirdparty to allow migrate non-Git repositories there and do not pollute richfaces organization repositories much.
15:21:16 <wyer> balunasj, sub module works with non git repos too so that is good
You have mentioned  that it is possible to add non-git repositories via git submodules when we discussed it previously.
I'm not sure how does it work.
Hi Lukas yeah I thought it could point to external non git repos, but I was wrong (thinking of something else). Regardless we would still need to bring source into github if its not there to be forked to ensure continuity of the 3rd party source regardless of what occurs in that project.
sure, we would need to clone repository also if it is hosted in Git,
since Git Submodules don't store the referenced repos, they are just storing information where they can be found,
so it will not assure these repos will be accessible in future.
There are also some Git extensions for cloning non-Git SCM repos like SVN, Mercurial, which can help us with process of cloning.
This is great - Lukas I like the idea of creating a sperate github "organisation" to host these. There is no telling how many repose we will have to fork over time.
We'll have to fit this in to our development/release process. So we don't forget to update and tag the forks when we upgrade the components. I suppose it would be ideal if our build used the forkes directly, to make sure we are in fact updating and tagging appropriately. Something with the maven shade plugin perhaps?
These we are able to re-package as Maven dependencies, but not sure we are able to make Maven work together with their build systems.
Btw, there is list of third-party dependencies: http://community.jboss.org/wiki/RichFacesDependencies