I think copy/paste is a good feature to have, it's not just you! Re. roadmap, I have now gone through my document and assigned priorities based on my guess, and owners (i.e. primary developers) also based on my guess. Developers who are going to work on things for V6, please comment or email me letting me know if you were already planning to take point on some of these roadmap items, and/or if you'd be willing to help with others.
The priority system I'm using (open to modification): P0 - Must Ship: These features define what 6.0 is at a minimum P1 - Important: We should really aim to get these features into 6.0 (i.e. maybe delay the release to get them in, on a case-by-case basis), but it wouldn't be a disaster to ship 6.0 without them P2 - Nice to Have: These can go into 6.0 if they are done in time, but they shouldn't delay 6.0 release Feel free to chime in if you think I've misjudged the priority of anything. Keep in mind, my point is not to keep anyone from working on anything by saying it's a lower priority, but rather to try to clarify what the "minimum" set of things we should have for 6.0 is, so that we can focus attention on them. -Jon On Wed, Mar 7, 2018 at 3:39 AM, Fabrizio Tappero <fabrizio.tapp...@gmail.com > wrote: > Hello, > as Andy mentioned, I consider quite important to have schematic components > embedded into schematic file. This will allow people to share small > schematic sheets and schematic snippets without painful lib cache file. In > Eagle and in Altium the "make library from schematic" capability is/was a > great feature. > > In my opinion, the limitation of not being able to copy and paste > schematic portions (outside a kicad project) is a big limitation for > anybody who makes/reuse/share a lot of schematics. > > Am I the only one suffering from the inability to reuse schematics? > > my 2c > Fabrizio > > > On Tue, Mar 6, 2018 at 9:03 PM, Jon Evans <j...@craftyjon.com> wrote: > >> I will be sure to send a proposed update to the official doc after there >> is no more churn on my scratch pad doc. >> I am not allowing anyone to edit, only I can edit (anyone can comment, >> and I have been incorporating changes based on people's comments) >> >> I think the next pass (now that it has been a day with no one making any >> more comments on my doc) is to think about who is going to do what to make >> sure the manpower thing makes sense. >> >> -Jon >> >> On Tue, Mar 6, 2018 at 2:33 PM, Wayne Stambaugh <stambau...@gmail.com> >> wrote: >> >>> I'm fine with using this for bike shedding as long as the results get >>> updated in the actual road map and this is not the official road map. >>> One caveat, by allowing anyone to edit this file, you may loose control >>> of it's content. That's one of the things I don't like about launchpads >>> blueprints. I also don't want this to turn into a popularity contest. >>> We have to make sensible decisions based upon project requirements and >>> manpower limitations so all final decisions are made by the lead >>> development team. >>> >>> On 3/5/2018 12:57 PM, Jon Evans 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/1mpxqvxLv497cyfk8KTQijhyS >>> SpFxF7ooTtcT_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 >>> > >>> > >>> > _______________________________________________ >>> > Mailing list: https://launchpad.net/~kicad-developers >>> > Post to : firstname.lastname@example.org >>> > Unsubscribe : https://launchpad.net/~kicad-developers >>> > More help : https://help.launchpad.net/ListHelp >>> > >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : email@example.com >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : firstname.lastname@example.org >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : email@example.com Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp