On 12/16/2011 09:44 AM, Stefan Andersson wrote:
T!
This was answering the second part of my questions. Still one more:
I agree completely with your opinion here. No overhead and total
distribution -> less work and control = more focus on better and more
code.
How and when will it be integ
T!
This was answering the second part of my questions. Still one more:
I agree completely with your opinion here. No overhead and total distribution
-> less work and control = more focus on better and more code.
How and when will it be integrated with the generator like with "svn://" ?
Stefan
- I'd like to refer you back to a recent discussion of the same topic,
here [1] and here [2], no need to re-iterate all the arguments from there.
- But on a general note, I find the idea of a central 'qooxdoo-contrib'
organisation on Github less attractive, because less contemporary. It
forces
Hey,
What would be the best git solution of contributed code?
We don't have a clear vision what to do with the contrib and how to move it to
git. But I think one thing is clear. In times of github, where everybody can
create a repo with one click, is no need for having such a general repositiry
I think you seem to have answered the necessary questions and what you have
been doing here can be used for qooxdoo-contrib.
I would be glad to adhere to this approach if the core team can tell their
opinion.
Two more questions to the core team:
1. How does the generator comply with this? Can
On Thu, Dec 15, 2011 at 14:35, Stefan Andersson
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
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?
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
On Thu, Dec 15, 2011 at 10:47, Stefan Andersson
wrote:
> Dear core team!
>
> What would be the best git solution of contributed code?
>
> - one repository independent of each contributed project?
>
> Should every contribution have its own branch in a common repository i.e.
> different from qooxdo
Dear core team!
What would be the best git solution of contributed code?
- one repository independent of each contributed project?
Should every contribution have its own branch in a common repository i.e.
different from qooxdoo?
- this might be messy due to branches of each project
Submodule
