Send Inkscape-devel mailing list submissions to
inkscape-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
or, via email, send a message with subject or body 'help' to
inkscape-devel-request@lists.sourceforge.net
You can reach the person managing the list at
inkscape-devel-owner@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Inkscape-devel digest..."
Today's Topics:
1. Re: Git (Olof Bjarnason)
2. Re: Git (joakim@...1974...)
3. Re: Git (Sebastian Zartner)
----------------------------------------------------------------------
Message: 1
Date: Tue, 9 Feb 2016 10:44:18 +0100
From: Olof Bjarnason <olof.bjarnason@...400...>
Subject: Re: [Inkscape-devel] Git
To: Krzysztof Kosi?ski <tweenk.pl@...400...>
Cc: Inkscape Devel List <inkscape-devel@lists.sourceforge.net>,
Christoffer Holmstedt <christoffer.holmstedt@...400...>
Message-ID:
<CA+LucOgHOtvruzrZQbEUjjBWM-fFJXDK5eGytEM5gemLaNbr_A@...401...>
Content-Type: text/plain; charset="utf-8"
Nice summary.
I think this boils down to a balance between issue tracker that fits
Inkscapes community (Launchpad's fit Inkscape very well), and developer
preference (git is almost de facto standard nowadays).
Of course, it the two tools would "marry" (using github/gitlab for repo+ci
and Launchpad for issues) it would be great.
Mvh
/Olof
-----------------
3-5-?riga sm?ttingar i n?rheten?
Lek & l?r siffror och bokst?ver via mobilen m.h.a. Alfamem till Android.
https://play.google.com/store/search?q=alfamem
On 9 February 2016 at 10:34, Krzysztof Kosi?ski <tweenk.pl@...1063....> wrote:
> I made a spreadsheet comparing GitHub, GitLab and Launchpad issue trackers.
>
> https://docs.google.com/spreadsheets/d/1Ig16AVpkrdjMTcgy3RPm4GCxY6Vx9lzggGFCX0853Tw/edit?usp=sharing
>
> I also looked into making Jenkins spawn builders in a cloud on demand.
> This appears to be simple to do with the JClouds plugin, and we could
> run Windows builds this way. However, OSX is not available in any of
> the JClouds-supported clouds. As I understand, this is purely due the
> OSX license not allowing virtualization on non-Apple hardware.
> (Although the urge is strong, I will spare you an anti-Apple rant.)
>
> Best regards, Krzysztof
>
> 2016-02-08 22:11 GMT-08:00 Christoffer Holmstedt
> <christoffer.holmstedt@...400...>:
> > 2016-02-08 13:37 GMT+01:00 Martin Owens <doctormo@...972.....>:
> >>
> >> On Mon, 2016-02-08 at 11:44 +0100, Sebastian Zartner wrote:
> >> > > I'll pass it along to the team. We don't discuss product decisions
> >> > or timelines publicly like that, so I can't share more information
> >> > about why this particular subset was chosen. I do hope it can be
> >> > expanded in the future, though.
> >>
> >> That's the biggest difference between open source projects and
> >> proprietary ones. Not just the code freedom, but the willingness to be
> >> open about product development, internal thoughts, attempts and
> >> failures. Keeping things hidden from customers isn't healthy IMO[1]
> >>
> >> I'm not really happy about any of these solutions to be honest.
> >>
> >> But we should keep looking and testing different possible solutions.
> >>
> >> Best Regards, Martin Owens
> >>
> >> [1] Something Canonical got wrong a lot.
> >>
> >
> > "Any of these solutions [...]"...Do you mean both Github and Gitlab?
> >
> > Yea, keeping product development plans behind closed door leaves users
> in a
> > sort of powerlessness state. You don't get any response about the
> future, if
> > there is any hope at all for the feature to be implemented nor have you
> the
> > ability to fix it yourself due to closed source. For JIRA I had a similar
> > case with Atlassian, no response at all if the bug fix was prioritized. I
> > know I needed a feature in Gitlab a year or so ago also; but it was only
> > available in Gitlab Enterprise but others needed that feature as well in
> > Community edition and implemented it themselves. The end result was that
> > Gitlab developers open sourced their closed source version of it.
> >
> > I will keep testing Gitlab CE and gitlab.com, gitlab seems to have
> better
> > issue management than Github.
> >
> > Maybe officially run everything on Gitlab with a official github mirror
> that
> > we can connect to travis-ci?
> >
> > --
> > Christoffer Holmstedt
> >
> >
> ------------------------------------------------------------------------------
> > Site24x7 APM Insight: Get Deep Visibility into Application Performance
> > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> > Monitor end-to-end web transactions and take corrective actions now
> > Troubleshoot faster and improve end-user experience. Signup Now!
> > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> > _______________________________________________
> > Inkscape-devel mailing list
> > Inkscape-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> >
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Tue, 09 Feb 2016 11:55:28 +0100
From: joakim@...1974...
Subject: Re: [Inkscape-devel] Git
To: Bryce Harrington <bryce@...961...>
Cc: inkscape-devel@lists.sourceforge.net
Message-ID: <m3mvraw3tr.fsf@...3213...>
Content-Type: text/plain
Bryce Harrington <bryce@...961...> writes:
> On Fri, Feb 05, 2016 at 09:16:36AM -0800, mathog wrote:
>> On 05-Feb-2016 05:40, Eduard Braun wrote:
>> > In general I would avoid splitting the code repository from the bug
>> > tracker as those two are closely related and often intertwined. It
>> > hinders efficiency a lot when tracking bugs elsewhere.
>>
>> I agree with that - everything in one place. Moving to git is fine so
>> long as the entire history of the project makes the transition, all the
>> bugs, all the revisions, and so forth. There shouldn't be anything
>> "left behind" on launchpad. Not that I have any idea how one would go
>> about doing this sort of migration, never having used git except to
>> download entire projects for a local build.
>
> The git repository itself should be straightforward. I've done bzr ->
> git on a bunch of trees without any trouble. I've not attempted on
> Inkscape itself, but others have already reported they've experimented
> and it went straightforward.
Emacs converted from Bzr to Git. The conversion wasn't straightforward,
but the tool "reposurgeon" helped solve the issues. Inkscape is probably
a more straightforward conversion, as evidenced by the conversions
already demonstrated in this thread.
>
> Bugs I think will be much harder to transition. There is no
> standardized storage for bugs like there is with git, and not really any
> established data spec, so unless a target site advertises a specific
> "Launchpad bug import" function, it's going to be a fair bit of work to
> write a converter.
>
> Launchpad's data sources have an API so exporting the bugs should not be
> a problem technically, just a lot of python coding. Whatever we would
> move them to would obviously need an import API (and ideally an export
> API in case we decide to change providers down the road!) So if we want
> to keep things together, we would HAVE to have someone own this coding
> project. (Unless someone knows of an existing converter tool?)
>
> I do see the value in keeping bug tracking and vcs hosting together - it
> was one of the selling points to move to Launchpad to begin with after
> all. And frankly I'd say its one of the reasons we've stuck with bzr
> longer than we probably should have... But I think there's a point
> where the benefit of moving to git is strong enough to do it regardless
> of whether the bug tracker follows. I don't know where we are on that
> scale, but I do think we're going to eventually hit a point where we
> just gotta move, and handle the bug tracker as a separate problem.
>
> I'm also really skeptical that github/gitlab's bug hosting is going to
> cut the mustard for our bug folks. And like I said, even if it does,
> I'm really worried that transferring the bug data promises would be a
> huge amount of work.
>
> There seems to be some organizational drama going on at Github right
> now:
>
> http://www.businessinsider.com/github-the-full-inside-story-2016-2
My dystopian prediction is that Github will eventually turn into
Sourceforge.
In my view, moving to Gitlab would avoid that risk. Gitlabs core feature
set is free software. If Gitlab also turns into sourceforge, Inkskape
can set up its own Gitlab instance, at least in principle. (I have set
up a Gitlab instance, and it is fairly straghtforward)
> Bryce
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140_______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
--
Joakim Verona
------------------------------
Message: 3
Date: Tue, 9 Feb 2016 12:42:59 +0100
From: Sebastian Zartner <sebastianzartner@...400...>
Subject: Re: [Inkscape-devel] Git
To: Christoffer Holmstedt <christoffer.holmstedt@...400...>
Cc: Inkscape Devel List <inkscape-devel@lists.sourceforge.net>
Message-ID:
<CAERejNbc37NiB4QbvZ7x_S7tTGRtx3CBn7Kn84ZmGCHADT9zqg@...401...>
Content-Type: text/plain; charset="utf-8"
On 9 February 2016 at 07:11, Christoffer Holmstedt <
christoffer.holmstedt@...400...> wrote:
> 2016-02-08 13:37 GMT+01:00 Martin Owens <doctormo@...400...>:
>
>> On Mon, 2016-02-08 at 11:44 +0100, Sebastian Zartner wrote:
>> > > I'll pass it along to the team. We don't discuss product decisions
>> > or timelines publicly like that, so I can't share more information
>> > about why this particular subset was chosen. I do hope it can be
>> > expanded in the future, though.
>>
>> That's the biggest difference between open source projects and
>> proprietary ones. Not just the code freedom, but the willingness to be
>> open about product development, internal thoughts, attempts and
>> failures. Keeping things hidden from customers isn't healthy IMO[1]
>>
>> I'm not really happy about any of these solutions to be honest.
>>
>> But we should keep looking and testing different possible solutions.
>>
>> Best Regards, Martin Owens
>>
>> [1] Something Canonical got wrong a lot.
>>
>>
> "Any of these solutions [...]"...Do you mean both Github and Gitlab?
>
> Yea, keeping product development plans behind closed door leaves users in
> a sort of powerlessness state. You don't get any response about the
> future, if there is any hope at all for the feature to be implemented nor
> have you the ability to fix it yourself due to closed source.
>
I need to add that every request I made against GitHub so far (~25) got
answered within one or two days and some of my suggestions were already
implemented in the meantime. So, at least I have the feeling that they are
somewhat listening to their users.
Having said that, of course the GitHub team never promises anything (and
they always say so in their responses), so you don't have any influence on
what get's implemented.
Sebastian
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
End of Inkscape-devel Digest, Vol 117, Issue 19
***********************************************