On Saturday, 2015-09-19, 23:06:47, Eike Hein wrote:
> On 09/19/2015 10:32 PM, Kevin Krammer wrote:
> > I don't see there this github review is coming from.
>
> Review is an interactive process where you ask for changes and
> iterate. Once you open the door to doing it on GitHub, you will:
>
> *
On 2015-09-20, Jaroslaw Staniek wrote:
> But effectively it won't be reviews because the KDE reviewers won't use it.
> Or do you think we need some dracon law because our community cannot do
> self-control?
I have just been fooled once regarding github and KDE. That makes me not
On 2015-09-20, Kevin Krammer wrote:
> First, I have no idea where this "use github for review" comes from at =
> all.
> Who wants to do that in the first place?
The github pull requests comes automatically with review abilities, so
once it is there and one already interacts with
On Saturday, September 19, 2015 04:17:11 PM Martin Klapetek wrote:
> so I haven't really organized any sprints myself but have participated
> in many, some good, some less good. So here's my personal take
> on this speaking from experience:
Thanks, it was really appreciated!
For those wondering,
On 21 September 2015 at 01:27, Michael Pyne wrote:
> On Mon, September 21, 2015 00:05:33 Jaroslaw Staniek wrote:
>> PS: Freedom of forking - derivative works is not so terrible, it's a
>> pilliar of FOSS.
>
> Last time I tried it, running git-clone against our KDE git
On Sun, Sep 20, 2015 at 6:05 PM, Jaroslaw Staniek wrote:
> This is about r-w git repo for KDE and non-KDE devs.
> In git times the need is easier to understand for someone who
> interacts with 3rd party projects at code level.
>
> What is your workflow in this case?
> Do you send
On Mon, September 21, 2015 00:05:33 Jaroslaw Staniek wrote:
> PS: Freedom of forking - derivative works is not so terrible, it's a
> pilliar of FOSS.
Last time I tried it, running git-clone against our KDE git infrastructure
still worked just fine, and thus forking is quite easy to do. Did this
On Sun, Sep 20, 2015 at 7:57 PM, Jaroslaw Staniek wrote:
> I see you're not used to the diverse term on github-alike sites:
> forking is more like creating a feature branch. The repo is separate
> but changes can be merged back (how it's a matter of tool set).
It is just like
On Sun, Sep 20, 2015 at 12:35 PM, Sune Vuorela wrote:
> On 2015-09-20, Jaroslaw Staniek wrote:
>> But effectively it won't be reviews because the KDE reviewers won't use it.
>> Or do you think we need some dracon law because our community cannot do
>>
On Sunday, September 20, 2015 06:39:02 PM Bhushan Shah wrote:
> We don't need to replace Facebook.. tada.
>
> Facebook is not part of our development nor anything.. So lets not
> compare with facebook.. When we talk about github and do our reviews
> there. It will be recorded there and if github
On Sun, Sep 20, 2015 at 8:20 PM, Martin Klapetek
wrote:
>
> Gnome in their years history of github mirroring had 4 pull requests
> (it was mentioned in the other thread...one of the others).
Sorry no [1]
On Sunday, September 20, 2015 10:50:43 AM Martin Klapetek wrote:
> Gnome in their years history of github mirroring had 4 pull requests
> (it was mentioned in the other thread...one of the others).
>
> So we might very likely be talking non-issues here anyway.
100% agreed
-Riccardo
On 09/20/2015 01:31 PM, Anne Wilson wrote:
> Hehe! Only on a KDE list could an exhortion to stop bikeshedding become
> the latest bikeshed!
The Debian community is currently having a bikeshed over
whether to call a new community tool Bikeshed. We can't
hope to compete.
> Anne
Cheers,
Eike
On 09/20/2015 02:26 PM, Loïc Grobol wrote:
> Let's try not to be extreme. If someone was able to post a pull
> request, they should be able to switch to Phab if they want to
> participate when notified.
Let's not be naive, either. People are lazy. That's been
one of the arguments for enabling
On 20 September 2015 at 14:29, Eike Hein wrote:
> Let's not be naive, either. People are lazy. That's been
> one of the arguments for enabling GitHub pull requests.
IIRC the main argument was not laziness, it was discoverability. But
if we have a nice wiki page to guide people in
On Sun, Sep 20, 2015 at 8:39 AM, Loïc Grobol wrote:
> Granted even before that, we can see if
there is enough pull request attempts to justify writing such a bot.
>
Gnome in their years history of github mirroring had 4 pull requests
(it was mentioned in the other
On Sun, Sep 20, 2015 at 10:59 AM, David Edmundson <
da...@davidedmundson.co.uk> wrote:
>
> I said that number but wrt "GTK" not "Gnome"
>
Oops, my apologies then. Somehow I've interchanged them in my memory.
Cheers
--
Martin Klapetek | KDE Developer
On 19/09/2015 15:24, Eike Hein wrote:
>
>
> On 09/19/2015 02:12 PM, Myriam Schweingruber wrote:
>> Some of you wanted the mirror on Github because apparently there
>> are developers out there who are too lazy (or too dumb) to learn to
>> use new tools. Are those developers we want?
>
>
On 2015-09-20, Riccardo Iaconelli wrote:
> How exactly have you been fooled?
> Proposal #1 - accepted,
Proposal #1 was a pure mirror. No other services used. Before the
initial mirror was actually completed, the next proposal comes up to
start doing even more github.
>
On 19 September 2015 at 20:14, Eike Hein wrote:
> Making the bot post Phab traffic back to GitHub is a
> fix to the notification problem, but doesn't help with
> getting the requestee to participate unless you make a
> full bridge.
Let's try not to be extreme. If someone was able to
On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote:
> Free software needs free tools.
I am sorry, but sadly this is not the state of the art. KDE has been created
with many non free tools and currently co-exists in many non-free
environments. We can either decide to live with it and
On Sunday, September 20, 2015 02:39:53 PM Loïc Grobol wrote:
> IIRC the main argument was not laziness, it was discoverability. But
> if we have a nice wiki page to guide people in the switching process,
> it should be relatively painless. In any way, we can still try and see
> if the issue
On Sunday, September 20, 2015 01:51:19 PM Laszlo Papp wrote:
> I just do not happen to see this case strong enough to support,
> personally. We have not even tried to see how the mirror works out,
> and we already think of whether or not it is a big problem not
> allowing pull requests, et al. It
On Sun, Sep 20, 2015 at 8:29 AM, Eike Hein wrote:
> On 09/20/2015 02:26 PM, Loïc Grobol wrote:
> > Let's try not to be extreme. If someone was able to post a pull
> > request, they should be able to switch to Phab if they want to
> > participate when notified.
>
> Let's not be
On 2015-09-20, Emil Sedgh wrote:
> What if we create a bot that makes a review request on our internal tool
> (Phab/Reviewboard) for each Github Pull request and tries to make a
> bridge between KDE's infrastructure and Github?
>
> A bot that would sync the
On Sunday, September 20, 2015 03:01:09 PM Luigi Toscano wrote:
> Riccardo Iaconelli ha scritto:
> > On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote:
> >> Free software needs free tools.
> >
> > I am sorry, but sadly this is not the state of the art. KDE has been
> > created with many
On Sunday, September 20, 2015 03:01:09 PM Luigi Toscano wrote:
> Riccardo Iaconelli ha scritto:
> > On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote:
> >> Free software needs free tools.
> >
> > I am sorry, but sadly this is not the state of the art. KDE has been
> > created with many
On Sun, Sep 20, 2015 at 3:56 PM, Martin Klapetek
wrote:
> On Sun, Sep 20, 2015 at 10:53 AM, Bhushan Shah wrote:
>
>> On Sun, Sep 20, 2015 at 8:20 PM, Martin Klapetek
>> wrote:
>> >
>> > Gnome in their years history of
Riccardo Iaconelli ha scritto:
> On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote:
>> Free software needs free tools.
>
> I am sorry, but sadly this is not the state of the art. KDE has been created
> with many non free tools and currently co-exists in many non-free
> environments.
On Sun, Sep 20, 2015 at 6:33 PM, Riccardo Iaconelli wrote:
> exactly, as soon as we could.
> But not all tools simply are technical alternatives. Can we replace Facebook?
> Sure, we could join Diaspora. But we would be missing out on the community
> already present on Facebook.
Selfie suggests that it would use a webcam to take a picture. A misleading name
is not a good name IMHO.
On 19 September 2015 20:08:06 BST, Rajeev Bhatta wrote:
>Selfie is better than Kapture for sure.. :)
>
>On Saturday, September 19, 2015 08:38:41 PM Eike Hein wrote:
On Sun, Sep 20, 2015 at 10:53 AM, Bhushan Shah wrote:
> On Sun, Sep 20, 2015 at 8:20 PM, Martin Klapetek
> wrote:
> >
> > Gnome in their years history of github mirroring had 4 pull requests
> > (it was mentioned in the other thread...one of the
On 2015-09-20, Martin Klapetek wrote:
> Gnome in their years history of github mirroring had 4 pull requests
> (it was mentioned in the other thread...one of the others).
>
> So we might very likely be talking non-issues here anyway.
Gnome is actively advicing against
On Sun, Sep 20, 2015 at 11:19 AM, Sune Vuorela wrote:
> On 2015-09-20, Emil Sedgh wrote:
> > What if we create a bot that makes a review request on our internal tool
> > (Phab/Reviewboard) for each Github Pull request and tries to make a
> > bridge between
Hi David,
Nice idea to have a wiki page explaining the process. I was going through the
text and have some suggestions for some of the text on the wiki page.
"GitHubMirror
KDE is managing a mirror of projects.kde.org on Github.
We want to make KDE sources easy to find, share and build upon;
I went back to the beginning of this discussion, and think a few
issues have been passed over. For instance, this one which has nothing
to do with the Github mirror, and everything to do with improving our
own software / discoverability:
On Mon, Aug 17, 2015 at 1:10 AM, Jos van den Oever
On 20 September 2015 at 23:55, David Narvaez wrote:
> On Sun, Sep 20, 2015 at 4:11 PM, Jaroslaw Staniek wrote:
>> Hi
>> I'd like to ask if this can be technically feasible and something we want:
>
>
>
> The subject sounds to me like a terrible idea,
37 matches
Mail list logo