X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 13 Feb 2019 04:33:51 +0100 (CET)
To:	geda-user AT delorie DOT com
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	[geda-user] pcb-rnd is no longer on geda mailing lists
Message-ID:	<alpine.DEB.2.00.1902130410000.21900@igor2priv>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com

Hi all,

the generic policy is that we provide "official" pcb-rnd support over any 
channel our users can reach us. Since 2013, these channels included 
geda-user@ and geda-help@.

This is changing now: we are no longer providing pcb-rnd support on these 
mailing lists. This means:

- if you need help with using or switching to pcb-rnd, please mail me 
directly or even better subscribe to the pcb-rnd mailing list or join our 
IRC channel (#pcb-rnd on repo.hu) where we provide real-time help

- the last pcb-rnd release announcement I relayed from the pcb-rnd mailing 
list to geda-user was for version 2.1.1 (today); if the geda community 
wishes to relay future pcb-rnd release announcements, someone will need to 
volunteer for forwarding them

- I've alerady unsubscribed from geda-help and will unsubscribe from 
geda-user later on, so please don't expect to reach me via these 
lists.

Plans for the future:

Meanwhile pcb-rnd is developing as fast as it did in the past few years. 
We have great plans for 2019 too. We still have scheduled releases and we 
still do a _lot_ between two releases. We are also building up our EDA 
ecosystem (coralEDA) in collaboration with other EDA-related projects.

For example I plan to have some more fetures that have long time user 
request history. For example I plan to develop an _optional_ "click on a 
network/component/pin on the PCB layout and get it selected on the 
schematics or vice versa" support - I figured how to do it in a nice, 
generic way, without any integration between the tools, allowing any new 
tool to enter the same system very easily. In 2018 we found an sch editor 
project that is interested in collaborating on these things so we can 
finally add such improvements.

Best regards,

Igor2

- Raw text -