Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Issues with "Singles" libraries #28

Closed
evanshultz opened this issue Dec 5, 2017 · 6 comments
Closed

Issues with "Singles" libraries #28

evanshultz opened this issue Dec 5, 2017 · 6 comments
Assignees
Labels
Help wanted Workforce is very welcomed KLC issue

Comments

@evanshultz
Copy link
Collaborator

evanshultz commented Dec 5, 2017

Sounds like a relationship problem...

Many of the libraries merged in #13 do not have correct footprint associations. These need to be of the form <Library>:<Footprint>, and they also need to match existing footprints in the official footprint libs.

@evanshultz evanshultz added Help wanted Workforce is very welcomed KLC issue labels Dec 5, 2017
@antoniovazquezblanco
Copy link
Collaborator

I can generate a report on S5.1 and S5.2 rules and split it by libs so that smaller and more concise issues can be generated. Those would be easyer to attack than this.

I am having troubles with the checklib script and some encoding messages. I will try to fix that and after that I will generate the report.

@antoniovazquezblanco
Copy link
Collaborator

antoniovazquezblanco commented Sep 18, 2018

Peding libs:

  • Driver_Motor.lib
  • FPGA_Xilinx.lib
  • FPGA_Xilinx_Artix7.lib
  • FPGA_Xilinx_Kintex7.lib
  • FPGA_Xilinx_Spartan6.lib
  • FPGA_Xilinx_Virtex5.lib
  • FPGA_Xilinx_Virtex6.lib
  • FPGA_Xilinx_Virtex7.lib
  • Interface.lib
  • Interface_CAN_LIN.lib
  • Interface_Ethernet.lib
  • Interface_USB.lib
  • LED.lib
  • MCU_Intel.lib
  • MCU_Microchip_PIC18.lib
  • MCU_Microchip_SAML.lib
  • MCU_Module.lib
  • Memory_Flash.lib
  • Memory_RAM.lib
  • Memory_UniqueID.lib
  • Power_Protection.lib
  • Reference_Voltage.lib
  • Regulator_Linear.lib
  • Regulator_Switching.lib
  • Sensor_Temperature.lib
  • Timer.lib
  • Transformer.lib
  • Transistor_BJT.lib
  • Transistor_FET.lib
  • Triac_Thyristor.lib

@antoniovazquezblanco
Copy link
Collaborator

All the problems included in this issue have been moved to smaller tasks. Closing this report in favor of the smaller units.

@evanshultz
Copy link
Collaborator Author

@antoniovazquezblanco
Just a question why make so many little issues when a checklist in this one big issue would work also? Is it because you prefer to have smaller pieces of work that can be closed rather than one massive task? Either way can work and I'm not chastising you, but it seems like a lot of effort to create so many issues so I just wanted to know your preference.

@antoniovazquezblanco
Copy link
Collaborator

I prefer small issues that can be closed. Maybe this was a little bit too much but nevermind.

I believe the simpler and focused the issue is, the easier to close it is.

@Ratfink
Copy link
Collaborator

Ratfink commented Sep 19, 2018

This way we could assign each small issue individually to avoid duplicated work, like happened in some parts of #520. Plus, all the tiny issues can be added to a project so we can easily track progress without having to look at comment diffs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Help wanted Workforce is very welcomed KLC issue
Projects
None yet
Development

No branches or pull requests

3 participants