Hi, > You are probably right, but as far as I am aware you are not an official > source of ASF policy on this matter.
I am currently assistant VP legal affairs and have made changes to ASF policy before, in particular to the release and distribution policy. I guess you are asking for something official from VP Legal Affairs or the ASF board? If so I can make that happen. > The official policy pages do not stipulate this IMO it does, the project can choose to ignore that if they want. I suggest you read what Roy wrote on this subject, ask why are you the only project (that I'm aware of) who have source releases with compiled code in them, and look at other discussions that have occurred on this subject. > As for prior releases, since 1) the official guidance has not required this > to date; and 2) there is no _legal_ reason to require this (per the LEGAL > thread you linked), I have no personal intention of going back to modify > prior releases. The is incorrect as VP legal (at the time) closed that issue and this has been discussed elsewhere on the legal list. Every single other release candidate containing compiled code across dozens (100's?) of projects have received -1 votes from their PMC and not been released. Saying we all volunteers, while true, doesn't remove the responsibility the PMC has to make sure its releases are open source / comply with ASF policy. Unless you have any other questions, I don't think I have anything more to say on this subject, and will wait to see what the PMC does about this. If you do want my help on this, just ask and I do what I can. Thanks, Justin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
