lifthrasiirrust · encoding · chrono•

[...] wherein I was contractually barred from even responding to comments on our issue trackers (the Apache license has interesting provisions about official communications).

I had to look at the License again to see the following definition:

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

(Emphasis mine.)

Therefore any comment to the issue tracker and mailing list would count as a "contribution", and a company that strongly prohibits any form of contribution has some official extents to do so for projects using the Apache license. That's interesting.

27
GankroOPrust•

Yep, that's the clause!

Very curious, but honestly I think it makes sense if it does what I think it does: removing serious procedural ambiguities. Like if someone says "oh you can fix this with <code snippet>", there's no question on if that code's actually been given to you to use in the codebase.

Although idk how that works in a dual-license environment.

15
lifthrasiirrust · encoding · chrono•

Yes, I too believe this definition is due to a good cause. Probably you can avoid this by marking every comment with a remark that it is not a contribution, but if a company really wants to forbid the act of contribution, well, it won't like such a try anyway.

8
pingveno•

Huh, that makes me want to remove the Apache licensing on my own crate, Rudy.

2
actuallyzza•

Oh damn. I just came across linked-hash-map looking for an insertion ordered set. It would be nice if there was an easy way for crates to reach out to their downstream users when they are swamped/need maintainers.

7
ldpreload•

It's not totally clear to me that these crates need maintainers—they could just be "done". Especially for smaller amounts of code, it's totally possible for software to be done. As long as it does what it claims and there's someone around to apply security fixes if needed (which it sounds like there is), you don't need your software to be undergoing active feature development to use it.

11
jeremiahs_bullfrog•

I wonder if this would make sense to build into cargo. Perhaps a "deprecated" or some other flag that gets included as a build warning and is posted on crates.io. I always hate it when a dependency gets unmaintained and I end up finding out months later when I come across a bug, want to file a feature request or even submit code. This leads me to replace the library in question when a little maintenance on my part could have kept the project from failing.

7
jaroslaw-jaroslaw•

i think "last update time" would be nice

3
pingveno•

Perhaps ordermap would fit the bill?

6
masklinn•

Yeah I'd suggest ordermap as well, it's an excellent general-purpose hashmap and naturally ordered, with much better iteration behaviour than a linked hashmap as you're just iterating a dense vector instead of chasing pointers.

2