X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Injected-Via-Gmane: http://gmane.org/ To: geda-user AT delorie DOT com From: Kai-Martin Knaak Subject: [geda-user] Re: Politics & Launchpad Date: Thu, 08 Oct 2015 04:13:38 +0200 Lines: 53 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet AT ger DOT gmane DOT org X-Gmane-NNTP-Posting-Host: a89-182-58-73.net-htp.de User-Agent: KNode/4.14.1 Reply-To: geda-user AT delorie DOT com Evan Foss wrote: > I am trying to bump this to it's own thread. Ok, I will bite and give my point of view on the launchpad drama. Prehistory: (Markus, please correct me if I present some aspects incorrectly.) Markus got approached by Eugene Mikhantiev whether his build might become the "official" PPA of the geda project. He is doing these builds independently since about 2013: https://launchpad.net/~mehanik/+archive/ubuntu/geda-unstable To all of you who are as ignorant as me until very recently -- a PPA is Ubuntu talk for a self contained repository for a specific software package. It represents a way to get an application in parallel to the core packages and the ones available via the connection to Debian. You have to be an administrator or owner of a launchpad team to associate a PPA. In case of the gEDA_Developers team the only adminstrator and owner is the launchpad team "gEDA_Administrators". So Markus applied to join this team too. Apparently, Markus's application to join got declined. (I hope, I did not get this wrong. Again, please correct me if so) This left him salty. He felt like administrators blocked developers, old boys blocked new kids on the block. In an emotional move he stopped his efforts to review the backlog of bugs in the bugtrackers on launchpad and left the launchpad team gEDA_developers. In addition, he revitalized a long standing idea to have a single place to deal with bugs in all of geda's projects. A team which is as open as possible to everybody with good intentions. And of course a place to present a PPA of the most current version of the geda tools. He asked me about an opinion. I responded, I like the approach and suggested a name for the effort. You guessed it, this is the team "gEDAhead" and its associated project "geda-project" to handle bug reports. gEDAhead: https://launchpad.net/~geda gEDA-project: https://launchpad.net/geda-project Note, that these bugs are exactly the same as those seen in the bug trackers for the individual tools. Bugs can be associated with more than one project in launchpad. Markus set up a weekly snapshot PPA in gEDAhead, too. In summery, gEDAhead currently provides three benefits: 1) a single place to add and access bug reports of all geda tools 2) a low entrance barrier team to join and become involved 3) a weekly build of the geda tools to be used on ubuntu systems and by extension on any debian related distro. I feel like these are steps in the right direction. Let's use the momentum to gedAhead ;-) ---<)kaimartin(>---