http://quantlib.414.s1.nabble.com/Reorganization-of-Git-repository-tp16962p17088.html
It's a shame. However, although I think it is important to have an
Breaking up the library would be great, too. Where again the
in a sense. No dependency or singleton issues there. Nothing for now,
> We tried that. No joy.
>
> Luigi
>
>
> On 18:41, Sun, Nov 15, 2015 Peter Caspers <
[hidden email]> wrote:
>>
>> you can contact the owner through the github support, I will try to
>> send them a polite message in parallel to Luigi's mail above (in case
>> they are not subscribed to this list - which would be weird somehow,
>> but maybe their project is totally unrelated, who knows)
>> Peter
>>
>> On 15 November 2015 at 10:03, Francois Botha <
[hidden email]> wrote:
>> > Ah, I did a quick check and thought the name was available. I see now it
>> > was
>> > registered in May 2014 - not too long ago! (
>> >
https://api.github.com/orgs/quantlib )
>> >
>> > Pity there's no contact info anywhere.
>> >
>> > Francois Botha
>> >
>> > On 13 November 2015 at 13:09, Luigi Ballabio <
[hidden email]>
>> > wrote:
>> >>
>> >> Hi Francois,
>> >> we talked about that, and I'm not against it. We even tried making
>> >> the
>> >> project account on GitHub, just to find that
http://github.com/quantlib>> >> was
>> >> already taken, so in case we'll have to go for quantlib-official or
>> >> something like it.
>> >>
>> >> (Oh, and if you're the owner of the above project and you're reading
>> >> this,
>> >> we would appreciate a lot if you could rename it and free it. Not
>> >> demanding,
>> >> just asking. It would be a nice gesture.)
>> >>
>> >> For the time being, though, the idea was more that of a federation of
>> >> repos, so mine would be the main one for the core C++ library, Eric's
>> >> would
>> >> be the main one for the Excel addin and so on. We kind of wanted to
>> >> de-bureaucratize the thing, as it were, so that if someone wrote
>> >> another
>> >> QuantLib module there would be no need to ask to be included in the
>> >> "official" club. I appreciate that it could be confusing, though, so
>> >> we're
>> >> open to feedback on this.
>> >>
>> >> Later,
>> >> Luigi
>> >>
>> >>
>> >> On Sat, Nov 7, 2015 at 10:16 AM Francois Botha <
[hidden email]>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> Isn't this also a good time to create a quantlib organisation account
>> >>> on
>> >>> github and move the official repository to e.g.
>> >>>
http://github.com/quantlib/quantlib ? Just a suggestion. I definitely
>> >>> don't
>> >>> want to detract from all the effort that Luigi has put in. It just
>> >>> seems the
>> >>> norm for projects to have their own organisation account on github
>> >>> these
>> >>> days.
>> >>>
>> >>> regards
>> >>>
>> >>> Francois Botha
>> >>>
>> >>> On 26 October 2015 at 16:09, Luigi Ballabio <
[hidden email]>
>> >>> wrote:
>> >>>>
>> >>>> [ cross-posted to quantlib-users and quantlib-dev; apologies for any
>> >>>> duplicates. ]
>> >>>>
>> >>>> Hi all,
>> >>>> I'm currently 3 or 4 issues away from setting up the 1.7 release.
>> >>>>
>> >>>> Shortly after doing that, and in concert with the other maintainers,
>> >>>> I'll reorganize the Git repository so that the current, monolithic
>> >>>> one
>> >>>> containing all the modules will be split into smaller ones, with one
>> >>>> module
>> >>>> per current directory; thus, there will be a repository for the core
>> >>>> C++
>> >>>> library, one for the Excel addin and so on.
>> >>>>
>> >>>> This will make it more convenient for the maintainers to manage the
>> >>>> modules for which they have responsibility, and will also make it a
>> >>>> lot
>> >>>> easier to add new modules. We had considered doing this when we
>> >>>> migrated
>> >>>> from subversion to git, and in hindsight we should have gone ahead at
>> >>>> that
>> >>>> time.
>> >>>>
>> >>>> I'm aware this will cause inconveniences to the 500+ people that
>> >>>> forked
>> >>>> the repository on GitHub. I am sorry for this, and I will try to
>> >>>> minimize
>> >>>> the pain: I'll migrate the open pull requests to the new repository,
>> >>>> and
>> >>>> I'll try to make some kind of guide to help those of you with local
>> >>>> changes
>> >>>> to move them to the new fork. In the meantime, your current forks are
>> >>>> not
>> >>>> going away.
>> >>>>
>> >>>> Thanks for the understanding. I'll post a timeline as soon as I have
>> >>>> one.
>> >>>>
>> >>>> Luigi
>> >>>>
>> >>>> --
>> >>>>
>> >>>> <
http://leanpub.com/implementingquantlib>
>> >>>> <
http://implementingquantlib.com>
>> >>>> <
http://twitter.com/lballabio>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> ------------------------------------------------------------------------------
>> >>>>
>> >>>> _______________________________________________
>> >>>> QuantLib-dev mailing list
>> >>>>
[hidden email]
>> >>>>
https://lists.sourceforge.net/lists/listinfo/quantlib-dev>> >>>>
>> >>>
>> >> --
>> >>
>> >> <
http://leanpub.com/implementingquantlib>
>> >> <
http://implementingquantlib.com>
>> >> <
http://twitter.com/lballabio>
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > QuantLib-users mailing list
>> >
[hidden email]
>> >
https://lists.sourceforge.net/lists/listinfo/quantlib-users>> >
>
> --
>
> <
http://leanpub.com/implementingquantlib>
> <
http://implementingquantlib.com>
> <
http://twitter.com/lballabio>