[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: What is the git workflow for kdelibs ?
From: John Layt <johnlayt () googlemail ! com>
Date: 2012-10-30 11:49:36
Message-ID: CAM1DM6mjvNi7y_X8V5KG-pz6xws+E1ks=gny0-pjZJm6LfiV7g () mail ! gmail ! com
[Download RAW message or body]
On 30 Oct 2012 11:23, "David Jarvie" <djarvie@kde.org> wrote:
>
> On Tue, October 30, 2012 11:16 am, David Faure wrote:
> > On Sunday 28 October 2012 09:16:56 Alexander Neundorf wrote:
> >> Ok, thanks.
> >> Is this documented somewhere ?
> >
> > No (I described it in an email some time ago, but it's not on any wiki)
> > If you have an idea for where we could document it, I will then push
other
> > module maintainers to also write up the git workflow they want to see,
> > since I
> > myself have the same question in other modules.
> >
> > I think community.kde.org would be the right place (it's internal, it
> > doesn't
> > affect KDE app devels outside of git.kde.org), but all I can see about
git
> > is
> > http://community.kde.org/Sysadmin/GitKdeOrgManual
> > which is more about the technical setup.
> >
> > Maybe start a new webpage at the toplevel of community.kde.org?
> > GitWorkflowForEachModule? :-)
>
> Wouldn't techbase be more appropriate? It's technical information, plus
> techbase is where other policies are kept.
>
> I must say that the split between community.kde.org and techbase.kde.org
> isn't very satisfactory because the boundaries are blurred, and it's easy
> to miss information if it's in the other one from what you expect it to be
> in.
We have a section on TecBase for Git related documentation, and I think our
Git workflow is needed information for anyone attempting to access our
repos so belongs on TechBase. See techbase.kde.org/Developmemt/Git where
I've linked under Policy to various proposals. We also need to formally
update the old SVN Commit Policy to reflect the new age, I did start on it
but stalled waiting for the kdelibs workflow to be finalised.
John.
[Attachment #3 (text/html)]
<p><br>
On 30 Oct 2012 11:23, "David Jarvie" <<a \
href="mailto:djarvie@kde.org">djarvie@kde.org</a>> wrote:<br> ><br>
> On Tue, October 30, 2012 11:16 am, David Faure wrote:<br>
> > On Sunday 28 October 2012 09:16:56 Alexander Neundorf wrote:<br>
> >> Ok, thanks.<br>
> >> Is this documented somewhere ?<br>
> ><br>
> > No (I described it in an email some time ago, but it's not on any \
wiki)<br> > > If you have an idea for where we could document it, I will then \
push other<br> > > module maintainers to also write up the git workflow they \
want to see,<br> > > since I<br>
> > myself have the same question in other modules.<br>
> ><br>
> > I think <a href="http://community.kde.org">community.kde.org</a> would be \
the right place (it's internal, it<br> > > doesn't<br>
> > affect KDE app devels outside of <a \
href="http://git.kde.org">git.kde.org</a>), but all I can see about git<br> > > \
is<br> > > <a href="http://community.kde.org/Sysadmin/GitKdeOrgManual">http://community.kde.org/Sysadmin/GitKdeOrgManual</a><br>
> > which is more about the technical setup.<br>
> ><br>
> > Maybe start a new webpage at the toplevel of <a \
href="http://community.kde.org">community.kde.org</a>?<br> > > \
GitWorkflowForEachModule? :-)<br> ><br>
> Wouldn't techbase be more appropriate? It's technical information, \
plus<br> > techbase is where other policies are kept.<br>
><br>
> I must say that the split between <a \
href="http://community.kde.org">community.kde.org</a> and <a \
href="http://techbase.kde.org">techbase.kde.org</a><br> > isn't very \
satisfactory because the boundaries are blurred, and it's easy<br> > to miss \
information if it's in the other one from what you expect it to be<br> > \
in.</p> <p>We have a section on TecBase for Git related documentation, and I think \
our Git workflow is needed information for anyone attempting to access our repos so \
belongs on TechBase. See <a \
href="http://techbase.kde.org/Developmemt/Git">techbase.kde.org/Developmemt/Git</a> \
where I've linked under Policy to various proposals. We also need to formally \
update the old SVN Commit Policy to reflect the new age, I did start on it but \
stalled waiting for the kdelibs workflow to be finalised.</p>
<p>John.</p>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic