atom feed48 messages in net.launchpad.lists.openstackRe: [Openstack] Nodejs in horizon
FromSent OnAttachments
Joshua HarlowMay 24, 2012 10:33 am 
Chuck ShortMay 24, 2012 12:26 pm 
Joshua HarlowMay 24, 2012 12:31 pm 
Devin CarlenMay 24, 2012 12:40 pm 
Gabriel HurleyMay 24, 2012 12:42 pm 
Joshua HarlowMay 24, 2012 12:47 pm 
Gabriel HurleyMay 24, 2012 1:42 pm 
Joshua HarlowMay 24, 2012 1:45 pm 
Gabriel HurleyMay 24, 2012 1:48 pm 
Russell BryantMay 24, 2012 3:37 pm 
Joshua HarlowMay 24, 2012 4:08 pm 
Devin CarlenMay 24, 2012 4:22 pm 
Joshua HarlowMay 24, 2012 4:27 pm 
Russell BryantMay 24, 2012 4:42 pm 
Gabriel HurleyMay 24, 2012 5:45 pm 
Mark McLoughlinMay 25, 2012 12:53 am 
Thierry CarrezMay 25, 2012 1:47 am 
Thierry CarrezMay 25, 2012 2:04 am 
Simon G.May 25, 2012 2:43 am 
Gabriel HurleyMay 25, 2012 3:26 am 
Russell BryantMay 25, 2012 4:33 am 
Simon G.May 25, 2012 5:40 am 
Jay PipesMay 25, 2012 6:20 am 
Simon G.May 25, 2012 7:39 am 
Thierry CarrezMay 25, 2012 7:51 am 
Thierry CarrezMay 25, 2012 8:09 am 
John PostlethwaitMay 25, 2012 9:22 am 
Gabriel HurleyMay 25, 2012 10:53 am 
Kiall Mac InnesMay 25, 2012 11:41 am 
Gabriel HurleyMay 25, 2012 12:35 pm 
Russell BryantMay 25, 2012 1:19 pm 
Gabriel HurleyMay 25, 2012 1:51 pm 
Russell BryantMay 25, 2012 2:32 pm 
Adam YoungMay 25, 2012 3:56 pm 
Gabriel HurleyMay 25, 2012 4:15 pm 
Adam YoungMay 25, 2012 5:33 pm 
Gabriel HurleyMay 26, 2012 7:57 pm 
Thierry CarrezMay 28, 2012 7:20 am 
Matthias RungeMay 29, 2012 12:58 am 
Gabriel HurleyMay 29, 2012 9:29 am 
Adam YoungMay 29, 2012 10:26 am 
Martin PauloMay 29, 2012 9:18 pm 
Devin CarlenMay 30, 2012 1:36 pm 
Adam YoungMay 30, 2012 2:14 pm 
Jan DrakeMay 30, 2012 4:27 pm 
Gabriel HurleyMay 30, 2012 4:44 pm 
Caitlin BestlerMay 31, 2012 10:31 am 
Jan DrakeMay 31, 2012 7:24 pm 
Subject:Re: [Openstack] Nodejs in horizon
From:Thierry Carrez (thie@openstack.org)
Date:May 25, 2012 1:47:39 am
List:net.launchpad.lists.openstack

Devin Carlen wrote:

-1 to introducing formal processes around this. This will happen from time to time. Development may be briefly impacted on other platforms but hindering innovation and telling developers that they are responsible for package availability across every distro is not healthy.

The PPB actually already ruled that new dependencies *need* to be discussed on the mailing-list prior to their introduction, if only so that downstream stakeholders learn about it and can work to solve it.

Like others said, new dependencies impact our whole ecosystem and most of the time a small amount of discussion can go a long way in choosing a solution that is good for everyone, rather than firefighting after the fact.

You are not responsible for package availability across every distro, but you're responsible for playing as nice with them as you can. That's the "Facilitation of downstream distribution" obligation of core projects[1], an obligation that the PPB can enforce.

[1] http://wiki.openstack.org/ProjectTypes

Regards,