Closed Frijol closed 4 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
I suspect we can blanket-apply the standard license.
FYI, web-monitoring-ops has since added a license.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
So… is this still important? Someone (or I) can go ahead and add licenses to these. Is the repo list in the OP still accurate?
@Mr0grog thanks! I think the list is accurate but haven't checked in over a year I think
Hmmmm, edgi-hubot-halpy has been archived. Should we still add a license there? (That requires un-archiving it.)
edgi-website (is it relevant to have a license here?)
Ah, yeah, I hadn’t realized there’s not even really an significant documentation or code there — and even if there were, it probably wouldn’t make sense to license for reuse. I’ll skip this one, too.
Do we want/need to put licenses on the forks?
Technically, yes, but our choice of license may be (is, in this case) constrained by the licensing terms of the thing we forked. BUT! In this case, I think we have removed all uses of it (as of edgi-govdata-archiving/edgi-scripts#55), so it maybe better to just archive it and leave it be.
/cc @lightandluck any thoughts there?
Looks like a license has since been added to eis-search.
OK, I updated all the repos except the three kinda fuzzy ones I commented about above.
Cool, thanks! And yay, we get to close this issue finally!
When I was doing the repo audit I noticed that some of the repos don't have licenses.
These repos don't have licenses:
EDGI repos
No License file but has a readme block
Forks