On Thu, Dec 15, 2011 at 14:35, Stefan Andersson
<[email protected]>wrote:
> Derrell!
>
> Good to see it sharp in action!
>
> How do you solve the login credentials for different users? Is it possible
> to separate different users?
>
Each user has his own github account and ssh keys.
Now a submodule is as a branch and which makes it difficult to branch the
> submodules without getting plotted. What is your solution to that?
>
> Isn't it better to have separate independent projects where branching is
> possible?
>
The typical use of subprojects is to use an external library, and to be
sure that all users of our own project are using the same commit (or tag or
other specification of a specific version) of each of the external
projects. It is possible to branch subprojects, because they are themselves
git repositories. I haven't looked into that in detail, though. It's kind
of in contradiction to the concept that everyone is using a common version
of the subproject.
There's nothing that stops the upstream project from branching, and nothing
that stops a subproject from linking to one of the branches of the upstream
project.
In my case, I'm actually the primary developer on one of the upstream
projects too, and I'm now using the subproject as my development
environment for that. When I make changes to the subproject, I push commit
them and push them upstream, and commit the main project too (since a
subproject changed, and it knows that) and push it upstream. In this way,
all users get the latest version of both the main project and the
subproject(s).
As far as different users, I've set this up as a github "organization"
which allows creating teams of people. Teams can be given permissions on
one or more repositories, including, pull only, or push/pull. For my
project, we have team members forking the project (in the github meaning of
the term) and cloning to their local machine. When they have changes ready,
they push to their github repository and use github to issue a "pull
request" to me. I've set up all of the team members as pull-only, so they
can fetch and merge from upstream before issuing their pull requests, but
they never push directly into the main repository. By adding them as team
members, though, we can use the github issue tracker and assign tasks to
them. The github issue tracker is extremely limited but the integration
with commits, and its commenting features including being able to comment
on specific lines of code, is nice.
Derrell
------------------------------------------------------------------------------
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.
But none more important than the need to reduce IT complexity
while improving strategic productivity. Learn More!
http://www.accelacomm.com/jaw/sdnl/114/51507609/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
