On Friday, December 19, 2014 23:26:15 Albert Astals Cid wrote:
> El Dijous, 18 de desembre de 2014, a les 14:52:12, Sebastian Kügler va
> > On Wednesday, December 17, 2014 08:47:09 Jeff Mitchell wrote:
> > > I understood that to be the case -- I'm really meaning for a general,
> > > KDE-wide solut
El Dissabte, 20 de desembre de 2014, a les 02:08:53, Kevin Kofler va escriure:
> Sebastian Kügler wrote:
> > On Tuesday, December 16, 2014 16:12:05 Ben Cooksley wrote:
> >> For deleting branches, I think we can allow this - given some
> >> protection for certain branches (like the KDE/* branches fo
2014-12-19 22:08 GMT-03:00 Kevin Kofler :
> Sebastian Kügler wrote:
>> On Tuesday, December 16, 2014 16:12:05 Ben Cooksley wrote:
>>> For deleting branches, I think we can allow this - given some
>>> protection for certain branches (like the KDE/* branches for
>>> instance). Note that courtesy of t
Sebastian Kügler wrote:
> On Tuesday, December 16, 2014 16:12:05 Ben Cooksley wrote:
>> For deleting branches, I think we can allow this - given some
>> protection for certain branches (like the KDE/* branches for
>> instance). Note that courtesy of the backup functionality in our
>> hooks, no bran
El Dijous, 18 de desembre de 2014, a les 14:52:12, Sebastian Kügler va
escriure:
> On Wednesday, December 17, 2014 08:47:09 Jeff Mitchell wrote:
> > I understood that to be the case -- I'm really meaning for a general,
> > KDE-wide solution.
> >
> > Personally I don't have an issue with volunteer
On 18 Dec 2014, at 8:52, Sebastian Kügler wrote:
On Wednesday, December 17, 2014 08:47:09 Jeff Mitchell wrote:
I understood that to be the case -- I'm really meaning for a general,
KDE-wide solution.
Personally I don't have an issue with volunteers taking care of
non-official systems if it hel
On Tuesday, December 16, 2014 16:12:05 Ben Cooksley wrote:
> For deleting branches, I think we can allow this - given some
> protection for certain branches (like the KDE/* branches for
> instance). Note that courtesy of the backup functionality in our
> hooks, no branch or tag is ever truly delete
On Thursday, 18 December 2014 14:52:12 CEST, Sebastian Kügler wrote:
Of course it would be prudent to give KDE's sysadmin's access
at some point, but it's not required per se.
Hi, that's been always the case, all sysadmins have root access, and they
also have the "admin" role within Gerrit.
On Wednesday, December 17, 2014 08:47:09 Jeff Mitchell wrote:
> I understood that to be the case -- I'm really meaning for a general,
> KDE-wide solution.
>
> Personally I don't have an issue with volunteers taking care of
> non-official systems if it helps their productivity. If Gerrit wasn't
On 17 Dec 2014, at 6:01, Jan Kundrát wrote:
Hi Jeff, thanks for a very reasonable mail, I don't have much to add
to it in general, except for one item:
But it's not reasonable to expect the sysadmins to support multiple
parallel systems
Maybe there is a misunderstanding of some kind -- I do
Hi Jeff, thanks for a very reasonable mail, I don't have much to add to it
in general, except for one item:
But it's not reasonable to expect the sysadmins to support
multiple parallel systems
Maybe there is a misunderstanding of some kind -- I do not expect sysadmins
to take care of a syste
On Wed, Dec 17, 2014 at 10:23 AM, Jan Kundrát wrote:
> Hi Ben,
Hi Jan,
>
>> It isn't just
>> the tool itself which has to be maintained: we have commit hooks,
>> integration with other bits of infrastructure and so forth which also
>> needs to both be implemented and maintained.
>
>
> In case of
Don't want to weigh in on Gerrit as I don't know it well enough, but as
for Phabricator, Ben may have forgotten but we did evaluate it a while
back. It was neat but had a very serious problem: you needed an account
to even view anything (no public access), and once you got into it
everything wa
On 12 Dec 2014, at 17:25, Luca Beltrame wrote:
Albert Astals Cid wrote:
So what do you suggest, because we already tried gitlab and didn't
work,
is there any more github clones out there that may work for us? I
don't
There are at least a couple:
- Gitbucket (written in Scala, mimics the Gi
Hi Ben,
It isn't just
the tool itself which has to be maintained: we have commit hooks,
integration with other bits of infrastructure and so forth which also
needs to both be implemented and maintained.
In case of Gerrit, there is no need for custom hooks as they stay on
git.kde.org, and ther
On Monday, 15 December 2014 22:25:37 CEST, Kevin Kofler wrote:
That creates the situation that "we
either all switch and have uniformity or we don't and then we end up with
reviewborad+gerrit" (Albert Astals Cid), which to me sounds a lot like
blackmail (of course not by Albert, he's just the m
Hi all,
Going to reply to all the various bits and pieces that have been
mentioned in order now. Apologies for the long mail.
For deleting branches, I think we can allow this - given some
protection for certain branches (like the KDE/* branches for
instance). Note that courtesy of the backup func
Martin Klapetek wrote:
> Our very own manifesto, which we've established not so long ago, does not
> dictate that a project must be kf5 or kdelibs based application to be
> considered a KDE project.
But there *is* an expectation that the projects use KDE infrastructure, so
the implication in "I a
El Dilluns, 15 de desembre de 2014, a les 10:48:16, Milian Wolff va escriure:
> On Saturday 13 December 2014 18:13:41 Albert Astals Cid wrote:
> > El Dissabte, 13 de desembre de 2014, a les 13:46:24, Jan Kundrát va
>
> escriure:
> > > On Friday, 12 December 2014 22:44:39 CEST, Albert Astals Cid wr
Jan Kundrát wrote:
>> - Apache Allura
> Also, loading a list of commits took tens of second at the time I tried it
> :(.
IIRC, I think Allura was just proposed once or twice, without much follow up
(but I'm the least knowledgeable person here. ;)
[kallithea]
> able to find two of them in total
Aaron J. Seigo wrote:
> looks like a pretty cool system. the command line integration (arc) is
> quite nice and powerful.
I re-read the docs and I guess I got confused by the many modules it is made
up of. I'll look into installing it on my own HW during the holidays, to see
how it goes (after
On Mon, Dec 15, 2014 at 11:01 AM, Jan Kundrát wrote:
> On Monday, 15 December 2014 10:46:03 CEST, Lydia Pintscher wrote:
>>
>> Yeah. Wikimedia just switched to it for bug tracking. More will follow.
>
>
> My understanding of the reason behind this switch is that they are PHP
> programmers, so they
On Mon, Dec 15, 2014 at 2:58 AM, Kevin Kofler
wrote:
>
> Albert Astals Cid wrote:
> > It also puts the discussion about a possible switch to gerrit in a weird
> > situaion since we either all switch and have uniformity or we don't and
> > then we end up with reviewborad+gerrit :/
>
> Or we just st
On Monday, 15 December 2014 07:34:24 CEST, Luca Beltrame wrote:
- Apache Allura
https://allura.apache.org/
That is said to support pull requests, but I wasn't able to find an example
of that in their website. Got one?
Also, loading a list of commits took tens of second at the time I tried it
On Monday, 15 December 2014 10:46:03 CEST, Lydia Pintscher wrote:
Yeah. Wikimedia just switched to it for bug tracking. More will follow.
My understanding of the reason behind this switch is that they are PHP
programmers, so they prefer to work with software written in PHP,
Made my life as
On Saturday 13 December 2014 18:13:41 Albert Astals Cid wrote:
> El Dissabte, 13 de desembre de 2014, a les 13:46:24, Jan Kundrát va
escriure:
> > On Friday, 12 December 2014 22:44:39 CEST, Albert Astals Cid wrote:
> > >> That's very different from saying "whole KDE should just
> > >> switch to Ge
On Dec 15, 2014 10:24 AM, "Aaron J. Seigo" wrote:
>
> On Monday, December 15, 2014 10.02:47 Boudewijn Rempt wrote:
> > Just as a datapoint: phabricator is what blender is using now:
> > http://wiki.blender.org/index.php/Dev:Doc/Tools/Phabricator
>
> and many more (and larger):
>
> http://e
On Monday, December 15, 2014 10.02:47 Boudewijn Rempt wrote:
> Just as a datapoint: phabricator is what blender is using now:
> http://wiki.blender.org/index.php/Dev:Doc/Tools/Phabricator
and many more (and larger):
http://en.wikipedia.org/wiki/Phabricator#Users
looks like a pretty cool
On Mon, 15 Dec 2014, Luca Beltrame wrote:
In data sabato 13 dicembre 2014 08:21:15, hai scritto:
We had three ones on plate:
- Phabricator
http://phabricator.org/
https://github.com/phacility/phabricator
I think I've taken a look at that, but it was way too complex than what I
could handle:
In data sabato 13 dicembre 2014 08:21:15, hai scritto:
> We had three ones on plate:
> - Phabricator
> http://phabricator.org/
> https://github.com/phacility/phabricator
I think I've taken a look at that, but it was way too complex than what I
could handle: I have no idea if it fits KDE's needs
Sending this to k-c-d, probably has been sent to me only by mistake: it offers
additional insights on software.
- Messaggio inoltrato -
Oggetto: Re: [Kde-pim] Problems with infrastructure
Data: sabato 13 dicembre 2014, 08:21:15
Da: Helio Chissini de Castro
A: Luca Beltrame
Kevin Kofler wrote:
Hello Kevin,
> wants to use Gerrit. (It's not even a KF5 or kdelibs application, but a
> Qt-only one.) Then he can use whatever tools he wants. Problem solved.
As Aleix said already, this does not help the discussion in any way. I can
see, even if I'm far from being an exper
On Mon, Dec 15, 2014 at 2:58 AM, Kevin Kofler wrote:
> Albert Astals Cid wrote:
>> It also puts the discussion about a possible switch to gerrit in a weird
>> situaion since we either all switch and have uniformity or we don't and
>> then we end up with reviewborad+gerrit :/
>
> Or we just stop th
Albert Astals Cid wrote:
> It also puts the discussion about a possible switch to gerrit in a weird
> situaion since we either all switch and have uniformity or we don't and
> then we end up with reviewborad+gerrit :/
Or we just stop the Gerrit experiment in the core KDE projects as a failure
(it
El Dissabte, 13 de desembre de 2014, a les 13:46:24, Jan Kundrát va escriure:
> On Friday, 12 December 2014 22:44:39 CEST, Albert Astals Cid wrote:
> >> That's very different from saying "whole KDE should just
> >> switch to Gerrit", and I'm not proposing that. Some people have made
> >> themselves
On Friday, 12 December 2014 22:44:39 CEST, Albert Astals Cid wrote:
That's very different from saying "whole KDE should just
switch to Gerrit", and I'm not proposing that. Some people have made
themselves clear that no change is going to happen, and I can live with
that.
Where was that discusse
Albert Astals Cid wrote:
> So what do you suggest, because we already tried gitlab and didn't work,
> is there any more github clones out there that may work for us? I don't
There are at least a couple:
- Gitbucket (written in Scala, mimics the GitHub interface)
- Gogs (written in Go, see my pre
On Wednesday 10 December 2014 16.53:09 Jan Kundrát wrote:
> On Wednesday, 10 December 2014 10:28:59 CEST, Christian Mollekopf wrote:
> > * pull requests/the webinterface: reviewboard is awesome for single
> > patches
> > every now and then, it's rather useless when you work with
> > branches IMO. W
Aaron J. Seigo wrote:
Hello Aaron,
> is a goal[1], then it would make a lot of sense to orchestrate a move to
> something that provides such a "github-like" experience, even if it has
> other drawbacks. Those drawbacks probably don't matter as much. If they
See my reply to Christian to see where
On Wednesday 10 December 2014 15.27:31 Ben Cooksley wrote:
> Hi all,
>
> It has come to my attention that some developers have "issues" with
> KDE infrastructure in certain areas. This is the first time i've heard
> of these "problems" and to my knowledge nobody has ever spoken to
> sysadmin regar
El Divendres, 12 de desembre de 2014, a les 11:27:24, Aaron J. Seigo va
escriure:
> On Thursday, December 11, 2014 23.23:59 Albert Astals Cid wrote:
> > El Dijous, 11 de desembre de 2014, a les 07:48:51, Aaron J. Seigo va
>
> escriure:
> > > individual learning curves is just not very attractive
El Divendres, 12 de desembre de 2014, a les 01:16:14, Jan Kundrát va escriure:
> On Thursday, 11 December 2014 23:20:59 CEST, Albert Astals Cid wrote:
> > You need to understand understand though that changing patch
> > review systems is
> > not your decision to take (nor mine), we need to have a g
On Thursday, December 11, 2014 23.23:59 Albert Astals Cid wrote:
> El Dijous, 11 de desembre de 2014, a les 07:48:51, Aaron J. Seigo va
escriure:
> > individual learning curves is just not very attractive when Github sits
> > there shiny and usable.
>
> and siloed and non-free.
Indeed, and unfor
On Thursday, 11 December 2014 23:20:59 CEST, Albert Astals Cid wrote:
You need to understand understand though that changing patch
review systems is
not your decision to take (nor mine), we need to have a general
agreement/consensus when changing systems as important.
Changing systems is not
El Dijous, 11 de desembre de 2014, a les 07:48:51, Aaron J. Seigo va escriure:
> On Wednesday, December 10, 2014 15.27:31 Ben Cooksley wrote:
> > It has come to my attention that some developers have "issues" with
> > KDE infrastructure in certain areas. This is the first time i've heard
>
> I sus
El Dijous, 11 de desembre de 2014, a les 01:18:57, Jan Kundrát va escriure:
> Anyway, I know that pre-Gerrit proccess was so painful for me that I
> actually decided to invest dozens of hours of my time into this, and get
> the Gerrit + CI ball rolling, and I'm not really willing to go back into
>
> Yyou need to setup git correctly, so that "gerrit" in that command is
>> valid,
>>
>
> I see what you're saying, and you're probably right -- there's a bar,
> indeed. That bar could however be effectively removed by having a
> spoonfeeding,
>
An alternative to the setup documentation is to actua
On Wednesday, December 10, 2014 15.27:31 Ben Cooksley wrote:
> It has come to my attention that some developers have "issues" with
> KDE infrastructure in certain areas. This is the first time i've heard
I suspect the issues are the same ones that led us to experiment with gitlab a
while back. Ch
On Thursday, 11 December 2014 00:51:28 CEST, Albert Astals Cid wrote:
Yes, it is harder.
Yyou need to setup git correctly, so that "gerrit" in that
command is valid,
you need to understand you're pushing to a different server than the "real"
one, you need to commit (i never do format-patch, j
El Dijous, 11 de desembre de 2014, a les 00:41:56, Jan Kundrát va escriure:
> On Wednesday, 10 December 2014 19:41:31 CEST, Albert Astals Cid wrote:
> > D is really important to me since it makes it harder to contribute to non
> > hardcore git users; it took me days to start understanding Qt's
> >
On Wednesday, 10 December 2014 19:41:31 CEST, Albert Astals Cid wrote:
D is really important to me since it makes it harder to contribute to non
hardcore git users; it took me days to start understanding Qt's
gerrit and i
am still not sure i understand it fully, with reviewboard i do git diff a
Albert Astals Cid ha scritto:
>
> I see some problems with gerrit:
> [...]
>
> D) There's no way to create a review without using relatively unfriendly
> gerrit process
>
> [...]
>
> D is really important to me since it makes it harder to contribute to non
> hardcore git users; it took me da
El Dimecres, 10 de desembre de 2014, a les 16:53:09, Jan Kundrát va escriure:
> On Wednesday, 10 December 2014 10:28:59 CEST, Christian Mollekopf wrote:
> > * pull requests/the webinterface: reviewboard is awesome for single
> > patches
> > every now and then, it's rather useless when you work with
On Wednesday, 10 December 2014 10:28:59 CEST, Christian Mollekopf wrote:
* pull requests/the webinterface: reviewboard is awesome for single patches
every now and then, it's rather useless when you work with
branches IMO. With github we have a nice webinterface to review
branches while keeping
[I love our infrastructure, just this bit triggered my reply-to-email reflex]
On Wednesday, December 10, 2014 10:28:59 Christian Mollekopf wrote:
> * deleting branches: This is the only major gripe I have with the kde
> infrastructure. I think everyone should be able to delete branches (except
>
55 matches
Mail list logo
