kicad-developers team mailing list archive

[Andy Peters <devel@xxxxxxxxx>]

> On Mar 7, 2018, at 3:04 PM, Ouabache Designworks <z3qmtr45@xxxxxxxxx> wrote:
> 
> 
> 
> On Mon, Mar 5, 2018 at 9:57 AM, Jon Evans <jon@xxxxxxxxxxxxx <mailto:jon@xxxxxxxxxxxxx>> wrote:
> Hi all,
> 
> Since my day job involves a lot of engineering planning/timelines/etc, I've had this rolling around in my head...
> I started brainstorming some proposed changes to the roadmaps.
> 
> I am using Google drive because that's what is easiest for me to play with; I'm happy to send patches against the official roadmaps if get some buy-in for this.
> 
> Feel free to comment (either directly on the doc or by email) with thoughts on this.
> 
> https://docs.google.com/document/d/1mpxqvxLv497cyfk8KTQijhySSpFxF7ooTtcT_HU86kw/edit# <https://docs.google.com/document/d/1mpxqvxLv497cyfk8KTQijhySSpFxF7ooTtcT_HU86kw/edit#>
> 
> Basically what I am proposing is to put most of the energy into Eeschema for 6.0, with changes to other parts of the software basically being "whatever people have time left over for".  Everything else has been bumped to 7.0
> 
> -Jon
> 
> 
> 
> 
> My wishlist:
> 
> Follow the unix philosophy. All programs must do one thing and do it well. You solve complex problems by chaining simple tools together. If you don't then your tool becomes bloated and hard to use and maintain. EEschema is heading down this path and we need to strip it down to EEschema Lite and put the ancillary features in their own programs.

What features of EESchema are “core” and what are “ancillary?”

-a