No comments on this particular package, but if the package system rules
are going to change in fundamental ways (imagine this were a programming
language), then those changes must be communicated to everyone.
Also, maybe it's time to think ahead to what other package system rules
there will likely be a desire to change, and get all the rule changes
over with at once, so that we don't get into the habit of changing the
rules on people.
When we're encouraging altruistic third-party contributions through the
package system, and presenting it as open and decentralized, then we
have to be aware of centralized, proprietary behavior that might erode
trust and discourage participation. One thing third parties have to go
on, in absence of formal business relationships and contracts, is the
rules or documentation of how these open-ish systems will work.
Again, no comment on this particular package; just trying to help the
new package system find the mix of centralized and decentralized that it
seems to be looking for.
Neil V.
--
You received this message because you are subscribed to the Google Groups "Racket
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/5675B7F9.3010509%40neilvandyke.org.
For more options, visit https://groups.google.com/d/optout.
