Federico Bruni writes:
> Hi folks
>
> I know that a lot of time has been invested on Allura, especially by
> Trevor. So I feel uneasy in writing this email, but I have the
> feeling that the time costraint didn't help to make the best decision
> for the new issue tracker.
It wasn't as much the
David Kastrup writes:
> The main problem I see is that questions like the usefulness of the
> documentation, scalability under duress, helpfulness of community,
> design of the codebase don't really gain a reliable answer before
> taking a full plunge.
I was missing a clear conclusion: given tha
Am 2. September 2015 07:30:09 MESZ, schrieb Federico Bruni :
>Hi folks
>
>I know that a lot of time has been invested on Allura, especially by
>Trevor.
>So I feel uneasy in writing this email, but I have the feeling that the
>
>time
>costraint didn't help to make the best decision for the new is
- Original Message -
From: "josiah oberholtzer"
To: "Federico Bruni" ; "Trevor Daniels"
Cc: "Lilypond bug list" ; "lilypond-devel"
Sent: Wednesday, September 02, 2015 5:19 AM
Subject: Re: Allura at SF is ready
Hi all,
Sorry for being out of touch - other obligations caught up wit
Am 02.09.2015 um 09:33 schrieb David Kastrup:
Federico Bruni writes:
Hi folks
I know that a lot of time has been invested on Allura, especially by
Trevor. So I feel uneasy in writing this email, but I have the
feeling that the time costraint didn't help to make the best decision
for the new
Federico Bruni wrote Wednesday, September 02, 2015 4:29 AM
> Il giorno dom 30 ago 2015 alle 17:57, Trevor Daniels
> ha scritto:
>> I've not heard anything from Federico or Josiah for over a week, so
>> I've no idea what state Allura at Savannah is in. I suggest we wait
>> a few days for news
Il giorno mer 2 set 2015 alle 9:33, David Kastrup ha
scritto:
I think that on the "evaluate other alternatives" angle it would
likely
make more sense to go through with getting Allura up and running.
As we are so close to get Allura up and running, of course it makes
sense.
But I was trying
Federico Bruni wrote Wednesday, September 02, 2015 6:30 AM
> What if we take some time to evaluate other alternatives and in the
We don't really have time, unless you don't mind having an
hiatus in the historical record of the LilyPond Tracker. I
do, which is why I've invested the time and ener
Il giorno mer 2 set 2015 alle 10:09, Urs Liska ha
scritto:
Am 2. September 2015 07:30:09 MESZ, schrieb Federico Bruni
:
Hi folks
I know that a lot of time has been invested on Allura, especially by
Trevor.
So I feel uneasy in writing this email, but I have the feeling that
the
time
costra
Simon Albrecht wrote Wednesday, September 02, 2015 9:34 AM
> Am 02.09.2015 um 09:33 schrieb David Kastrup:
>
>> I seem to remember they announced closing that down in 2016 or so.
>
> That’s only access via VCS – the actual data ‘will remain online for
> years into the future’. Which doesn’t sou
Federico Bruni wrote Wednesday, September 02, 2015 10:15 AM
> Yes, but I was thinking about using an interim solution for some months
> to have some more time to evaluate the self-hosted solutions.
> Sourceforge would not be the best interim solution.
I think you first need to prove our DB wit
Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels
ha scritto:
meanwhile
we use Bitbucket or Github? Not Free services, I know, but at least
their
business model seems honest.
This is on the GC FAQ covering migration to GitHub:
Error "Project cannot be migrated because it has too many
- Original Message -
From: "Federico Bruni"
I'm not concerned about the https issue. I'm concerned about the Allura
usability and the work on the API/patchy stuff which Phil started
recently.
I think Allura will need some time to get used to, but once we are used to
it we will fin
Am 02.09.2015 um 11:27 schrieb Federico Bruni:
Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels
ha scritto:
meanwhile
we use Bitbucket or Github? Not Free services, I know, but at least
their
business model seems honest.
This is on the GC FAQ covering migration to GitHub:
Error "Pro
Il giorno mer 2 set 2015 alle 11:41, Simon Albrecht
ha scritto:
I made the bitbucket repository public:
https://bitbucket.org/fedelibre/lilyissues/issues?status=new&status=open
‘Access denied’ for me…
I made the repository public, not the issue tracker.
Now you can see it
https://codereview.appspot.com/264950043/diff/40001/lily/include/grob-array.hh
File lily/include/grob-array.hh (right):
https://codereview.appspot.com/264950043/diff/40001/lily/include/grob-array.hh#newcode63
lily/include/grob-array.hh:63: // Note: This method may reorder the
array without affec
Federico Bruni wrote Wednesday, September 02, 2015 10:27 AM
>
> Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels
> ha scritto:
>
>>> meanwhile we use Bitbucket or Github? Not Free services, I know, but at
>>> least their business model seems honest.
>>
>> This is on the GC FAQ covering migr
Am 02.09.2015 um 11:59 schrieb Federico Bruni:
Il giorno mer 2 set 2015 alle 11:41, Simon Albrecht
ha scritto:
I made the bitbucket repository public:
https://bitbucket.org/fedelibre/lilyissues/issues?status=new&status=open
‘Access denied’ for me…
I made the repository public, not
[CCing Nacho]
> Nacho has included bugs.lilypond.gnu.org as an alias on the apache
> configuration and he has been asked to set this up as a DNS name.
Well, `bugs.lilypond.gnu.org' apparently doesn't work.
> I've not yet heard back from him, so don't know if this has been
> done.
It seems not
"Trevor Daniels" writes:
>> I made the bitbucket repository public:
>> https://bitbucket.org/fedelibre/lilyissues/issues?status=new&status=open
>
> I don't see how to set up searches; is that possible?
>
> And we'd be limited to 5 developers, unless we pay, it seems.
> Hardly opensource.
More li
Il giorno mer 2 set 2015 alle 12:41, Simon Albrecht
ha scritto:
As you already said, the quality of the import is completely
insatisfactory. Also I find the UI quite crude, with little
flexibility – that’s probably what they offer with the advertised
JIRA software, which may be tested free fro
David Kastrup wrote Wednesday, September 02, 2015 11:46 AM
> "Trevor Daniels" writes:
>
>> And we'd be limited to 5 developers, unless we pay, it seems.
>> Hardly opensource.
>
> More like "hardly gratis". I've just glanced cursorily at the site but
> saw no obvious advertisement of source c
Phil Holmes wrote Wednesday, September 02, 2015 10:31 AM
> Finally, FWIW I have no objection to continuing to use SourceForge for issue
> hosting. I realise it counts as non-free and has had issues over including
> unwanted functionality in downloads, but Google ain't exactly free either,
> a
Werner LEMBERG writes:
> [CCing Nacho]
>
>> Nacho has included bugs.lilypond.gnu.org as an alias on the apache
>> configuration and he has been asked to set this up as a DNS name.
>
> Well, `bugs.lilypond.gnu.org' apparently doesn't work.
>
>> I've not yet heard back from him, so don't know if th
David Kastrup wrote Wednesday, September 02, 2015 8:33 AM
> At the current point of time, we aren't even on Github/Bitbucket. At
> any rate, regarding "promising" solutions there is also the SFC-hosted
> Kallithea https://kallithea-scm.org/> where we likely would get
> more than marginal interes
>> Nacho, instead of the previously proposed alias, please use the
>> better name `lilypond-bugs.gnu.org'! And please tell us as soon as
>> you are done.
>
> Before we do 5 proposals in a row: shouldn't we rather try matching the
> name of our bug reporting list and aim for bug-lilypond.gnu.org?
Il 02/set/2015 13:17, Trevor Daniels ha scritto:
>
>
> David Kastrup wrote Wednesday, September 02, 2015 8:33 AM
>
> > At the current point of time, we aren't even on Github/Bitbucket. At
> > any rate, regarding "promising" solutions there is also the SFC-hosted
> > Kallithea https://kallithe
"Trevor Daniels" writes:
> David Kastrup wrote Wednesday, September 02, 2015 8:33 AM
>
>> At the current point of time, we aren't even on Github/Bitbucket. At
>> any rate, regarding "promising" solutions there is also the SFC-hosted
>> Kallithea https://kallithea-scm.org/> where we likely would
Hi all
I'd like to upload the json file (36 MB) exported from Google Code to
Dropbox to make it available to Gogs developers. It may be useful for
other projects:
https://github.com/gogits/gogs/issues/809
AFAICS the file contains only public stuff. No email addresses (except
those that are a
- Original Message -
From: "Federico Bruni"
To: "Lily-Devel List"
Sent: Wednesday, September 02, 2015 4:11 PM
Subject: sharing Google Code json data dump
Hi all
I'd like to upload the json file (36 MB) exported from Google Code to
Dropbox to make it available to Gogs developers. It
"Phil Holmes" writes:
> - Original Message -
> From: "Federico Bruni"
> To: "Lily-Devel List"
> Sent: Wednesday, September 02, 2015 4:11 PM
> Subject: sharing Google Code json data dump
>
>
>> Hi all
>>
>> I'd like to upload the json file (36 MB) exported from Google Code
>> to Dropbox
Il giorno mer 2 set 2015 alle 17:28, Phil Holmes
ha scritto:
AFAICS it's all in the public domain, so no problem.
uploaded here:
https://www.dropbox.com/s/4cqzfhm31ke3ekq/lilypond-google-code-issues.json?dl=0
___
lilypond-devel mailing list
lilypon
Il giorno mer 2 set 2015 alle 12:51, Federico Bruni
ha scritto:
I'm running the import on github. It takes more time, even if I've
been
whitelisted by github team. I'm currently at:
Issue: 659/4567
Let's see how it works.
Now, after 6 hours, I'm at 3500/4567.
A bit slow because Github API ha
Reviewers: ,
Message:
I came across this rather mishapen wording in NR 4.6.2 – so I changed
it.
Description:
Improve wording for an NR paragraph
The paragraph from "Avoid (or reduce)" in spacing.itely
used 'for example' twice in a row. The description of the
'volta bracket' issue was unclear in
LGTM
Trevor
https://codereview.appspot.com/259710043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2015/09/02 10:13:26, benko.pal wrote:
https://codereview.appspot.com/264950043/diff/40001/lily/include/grob-array.hh#newcode63
lily/include/grob-array.hh:63: // Note: This method may reorder the
array
without affecting the result of
what does "reorder" mean in the current context? the func
https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely#newcode3489
Documentation/notation/spacing.itely:3489: will take up more sp
LGTM,
Marc
Am 02.09.2015 um 21:26 schrieb simon.albre...@mail.de:
Reviewers: ,
Message:
I came across this rather mishapen wording in NR 4.6.2 – so I changed
it.
Description:
Improve wording for an NR paragraph
The paragraph from "Avoid (or reduce)" in spacing.itely
used 'for example' twice
38 matches
Mail list logo
