elementary-dev-community team mailing list archive

[Dane Henson <dane@xxxxxxxxxxxxxxxx>]

One does not simply fork launchpad.
On Jul 13, 2013 2:52 PM, "Cassidy James" <cassidy@xxxxxxxxxxxxxxxx> wrote:

> Chris,
>
> Launchpad is technically open source, but it's designed to be used only on
> Canonical's infrastructure and they aren't interested in making it run
> elsewhere. It's open source so that people can help Canonical out, not so
> people can set up their own instances.
>
> Regards,
> Cassidy James
>
> On Sat, Jul 13, 2013 at 5:13 AM, Chris Timberlake <game64@xxxxxxxxx>
> wrote:
>
> Fabian,
>
> Correct me if I'm wrong but isn't launchpad open source? There's been much
> talk about Launchpad mock-ups and redesigns, etc. Maybe you could simply
> fork launchpad as opposed to creating a replacement?
>
> http://blog.launchpad.net/general/launchpad-is-now-open-source
>
>
> On Wed, Jul 10, 2013 at 2:55 PM, Fabian Thoma <fabian@xxxxxxxxxxxxxxxx>wrote:
>
>> So I'm gonna enter that conversation here, if we want to have automated
>> builds for debian based systems not on Launchpad we really need the
>> following:
>>
>>    1. Hardware (we already got a virtual server capable of building the
>>    daily isos, so it should be able to handle this, if needed we can also go
>>    dedicated)
>>    2. a build daemon, which is buildd that debian uses for it's build
>>    machines (we can use that 1 to 1 like launchpad)
>>    3. a system managing builds and versions (which I'd prefer to build
>>    or use something highly flexible and adapt)
>>    4. a repo server that hosts the packages and can support high traffic
>>    (that's a matter of renting it really)
>>
>> I don't see any issue in these things, especially the hardware and build
>> based stuff. Building something to manage the builds and versions should
>> not be a big deal either, but the real question has to be if we want to go
>> and diy a Launchpad replacement or use something finished and integrate the
>> build part into it.
>>
>>
>> On Wed, Jul 10, 2013 at 11:42 PM, Sergey "Shnatsel" Davidoff <
>> sergey@xxxxxxxxxxxxxxxx> wrote:
>>
>>> what do we need in order to get our own repo and automated build
>>>> infrastructure? Is it a hardware issue?
>>>>
>>>
>>> A lot of things I'm afraid. Off the top of my head, the list is as
>>> follows:
>>>
>>>    1. hardware
>>>    2. pbuilder configuration (mostly done)
>>>    3. some piece of software to accept dput uploads (should exist, but
>>>    not found yet)
>>>    4. some piece of software to create and maintain the repository
>>>    (should exist, but not found yet)
>>>    5. lots of integration scripts to write and secondary systems to set
>>>    up (mailer to report failed builds, etc)
>>>    6. some UI to be able to make sense of all that and manage the setup
>>>    (probably doesn't exist)
>>>
>>> --
>>> Sergey "Shnatsel" Davidoff
>>> OS architect @ elementary
>>>
>>> --
>>> Mailing list: https://launchpad.net/~elementary-dev-community
>>> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~elementary-dev-community
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>>  <http://elementaryos.org/> *Fabian Thoma* | *Council Member*
>> elementary OS
>> fabian@xxxxxxxxxxxxxxxx / elementaryos.org
>>
>> --
>> Mailing list: https://launchpad.net/~elementary-dev-community
>> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~elementary-dev-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> *------------------------------**------------------------------**
> Chris Timberlake*
> Technical Architect
> Phone: 515-707-5109
> Game64@xxxxxxxxx
>
>
> --
> Mailing list: https://launchpad.net/~elementary-dev-community
> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~elementary-dev-community
> More help   : https://help.launchpad.net/ListHelp
>
>