<br>On Wednesday, October 29, 2014, Ondrej Wisniewski <<a href="mailto:ondrej.wisniewski@dektech.com.au">ondrej.wisniewski@dektech.com.au</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi Dolph,<br>
<br>
I guess it sounds complicated but in the end our setup is really
not much different from the community workflow, a least this is
the intention. What I am trying to achieve is a possibility for
the team of developers to share code among each other by using a
central Git repository.</div><div></div></div></blockquote><div><br></div><div>The community already shares code through Work In Progress Gerrit reviews, and not necessarily by landing commits. We pastebin git diffs that can be quickly shared and applied. We occasionally maintain experimental branches on personal github accounts. Git itself is decentralized, so your developers can push and pull from each other directly if necessary. I'm sure others can suggest more innovative ways to share code peer-to-peer.</div><div><br></div><div>There's no need to create barriers between your developers and the rest of the world. We're all one community. Please let them join.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div>This is according to the centralized
workflow using distributed Git as described in the official Git
documentation (see ref. [1]).<br>
<br>
If I understand correctly, we cannot use the OpenStack community
Git servers as our central Git repository since developers cannot
push to them. And we don't want to go through Gerrit and the code
review procedure just to share a bit of code with somebody else in
the team. Thus the need for a local mirror.</div></div></blockquote><div><br></div><div>"need"</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div><br>
<br>
Additionally also a local Gerrit server was set up to allow for
internal code review within the team before submitting anything to
the community server <a href="http://review.openstack.org" target="_blank">review.openstack.org</a>
(which will be done eventually). This is also helpful in case our
Internet connection goes down, as we will still be able to follow
the complete workflow inside the LAN.<br>
<br>
Hope this explains a little better the motivation for the
described setup.<br>
<br>
Ondrej<br>
<br>
[1]
<a href="http://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows" target="_blank">http://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows</a><br>
<br>
<br>
<i>On 10/29/2014 02:14 PM, Dolph Mathews wrote:</i> </div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">I've been following the conversation,
probably like many others, wondering why in the world you need
such a complicated, high-maintenance workflow? What's the use
case? Why can't your developers use <a href="http://review.openstack.org" target="_blank">review.openstack.org</a>?
In your first email, you used the phrase "t<span style="font-family:Helvetica,Arial,sans-serif;font-size:13px">rying
to set up an OpenStack development workflow in our company"
but what you're building is not an OpenStack development
workflow at all - it's an expensive private island. The
community's workflow is quite well documented here: </span><font face="Helvetica, Arial, sans-serif"><a href="https://wiki.openstack.org/wiki/Gerrit_Workflow" target="_blank">https://wiki.openstack.org/wiki/Gerrit_Workflow</a></font>
<div class="gmail_quote"><br>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>