Missing Licenses (in regro org)

[jakirkham]

When doing an internal review of license here, we noticed the following things don't have licenses. Some of these look a bit older so am not sure if they are all still used. Guidance and helping getting proper licenses into repos (or finding them in case I missed them) would be really helpful 😄

• libcfgraph
• circle_worker
• cf-graph2
• make-cf-graph
• cf-auto-tick
• graph-upstream
• 00-find-feedstocks

[CJ-Wright]

Most of these are not used, so we should most likely archive them.

[jakirkham]

I suspect archiving unused things would help.

For now, it would be great to know, which of these is still relevant. Then we can add licenses to those. The rest we can merely note as not relevant.

[jakirkham]

So which of these are still relevant?

[CJ-Wright]

I think these are the relevant bot ones.

• cf-scripts
• cf-graph-countyfair
• cf-worker

[jakirkham]

Great, thanks for pointing those out. For those what should be the intended license? BSD 3-Clause?

[CJ-Wright]

I think you can pull the license from here:

cf-scripts/License

Line 1 in b060bf1

BSD 3-clause license

[jakirkham]

Oh, it's dual licensed?

[CJ-Wright]

I would just use the numfocus license for things other than cf-scripts

[CJ-Wright]

(cf-scripts was cobbled together from a bunch of other projects when it started out)

[jakirkham]

Sure. Makes sense.

To clarify, do you mean the BSD 3-Clause part of that license?

[CJ-Wright]

Yes

[jakirkham]

Thanks for clarifying.

[jakirkham]

Also which one were you referring to as cf-worker? Am not seeing that repo ATM.

[CJ-Wright]

Sorry it's circle worker

[jakirkham]

Thanks CJ.

One last question, how should libcfgraph be licensed? This seems important from a downstream usability standpoint.

[CJ-Wright]

@scopatz thoughts?

[CJ-Wright]

I think it makes sense to have the data repos under a CC license, although I'm not certain which one.

[jakirkham]

CC0 is pretty easy. People are allowed to use this data any way they see fit with no restrictions.