X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Mon, 5 Oct 2015 21:29:37 -0400 Message-Id: <201510060129.t961Tb3W014963@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (message from Kai-Martin Knaak on Tue, 06 Oct 2015 03:21:18 +0200) Subject: Re: [geda-user] GTK3, Glade interface designer (router, auto?) References: <20151003210701 DOT de392b925f54dadb0a5fedd8 AT gmail DOT com> <1443903758 DOT 1873 DOT 13 DOT camel AT ssalewski DOT de> <56104A0A DOT 9020507 AT xs4all DOT nl> <1443909591 DOT 1873 DOT 18 DOT camel AT ssalewski DOT de> <1443975731 DOT 671 DOT 52 DOT camel AT ssalewski DOT de> <20151004191717 DOT bf8223417541a9306bfbd9ea AT gmail DOT com> <1443997480 DOT 2068 DOT 32 DOT camel AT ssalewski DOT de> <1444070851 DOT 1014 DOT 20 DOT camel AT ssalewski DOT de> <201510060055 DOT t960tgSn013829 AT envy DOT delorie DOT com> Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Rather in formally, though. No dates, no actual poll, no evaluation. > I wouldn't push for such a formal poll. But then again, if anyone > needs help to decide which can of code worms to jump into, I > wouldn't mind if there was such a poll. What we need is enough development time available that we can actually plan some schedules instead of just "when things happen". Then we can pick a time when we can afford to mess up the code base to do some long-overdue internal changes, and have a group of devs active on some big projects together. If we can get to that point, I think picking something to work on would be a small problem :-)