alamb commented on PR #60: URL: https://github.com/apache/parquet-site/pull/60#issuecomment-2123503469
> @alamb @wgtmac I put a very basic PR together to update _some_ of the references on the website from `parquet-mr` to `parquet-java`. I only chose to do some because I think we have a few questions to figure out first: > > 1. Are we going to change the published artifact name of `parquet-mr` to `parquet-java` or do we just want to keep publishing under mr? I personally suggest not making this change unless there is a compelling usecase. It seems like it doesn't hurt to leave the artifacts as parquet-mr and would only cause downstream pain to update them now for very little gain > 2. Do we want to actually "rewrite history" and update the past references (contributions, etc..) in the docs to refer to `parquet-java` instead? I'm not a fan of rewriting history but figured I'd start a conversation just in case people want to. I recommend against doing this, again on the justification of "what benefit would we get from it"? > 3. Should we also do a sweep and update the contribution guidelines to include the new ways to contribute? I am not sure what this is asking > 4. Should we introduce a new section of the blog called `parquet-java` (I had been hacking using the blog for releases) to add a note (assuming we change the name of the artifact) that things have changed? Maybe we could create a blog post announcing some of the recent changes / activity (e.g. discussion son V3 format, clarifications on repos, new website, etc). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
