pcb

license check

Bug #1800707 reported by Bert Timmerman on 2018-10-30

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	pcb	Fix Released	Medium	Bert Timmerman	pcb pcb-4.2.0

Bug Description

See attached output.

Kind regards,

Bert Timmerman.

Revision history for this message

Bert Timmerman (bert-timmerman) wrote on 2018-10-30:

license check.txt Edit (104.1 KiB, text/plain)

Bert Timmerman (bert-timmerman) on 2018-10-31

Changed in pcb:
milestone:	none → future-bug-fix-release

Bert Timmerman (bert-timmerman) on 2018-12-01

Changed in pcb:
status:	New → Triaged
importance:	Undecided → Medium
assignee:	nobody → Bert Timmerman (bert-timmerman)

Chad Parker (parker-charles) on 2018-12-01

Changed in pcb:
milestone:	future-bug-fix-release → pcb-4.2.0

Revision history for this message

Chad Parker (parker-charles) wrote on 2018-12-16:

So, what's the plan here? Are we going to go through and update all of the licenses to match?

Revision history for this message

Bert Timmerman (bert-timmerman) wrote on 2018-12-16:

Hi Charles,

This originates from a check the Fedora package manager software does when building an RPM.

The current packager reported this.

I looked into this, made some commits on a topic branch correcting the FSF address, merged into master and I'm done with it --> IMHO the status could become "Fix Committed".

Any step further would involve a massive effort in tracking authors and aligning to a uniform license ... the debate would probably never be concluded ... looks like a can of worms.

Kind regards,

Bert Timmerman.

Bert Timmerman (bert-timmerman) on 2018-12-28