Skip to content

chore: Create a doap file - #10233

Merged
alamb merged 2 commits into
apache:mainfrom
tisonkun:doap
Apr 25, 2024
Merged

chore: Create a doap file#10233
alamb merged 2 commits into
apache:mainfrom
tisonkun:doap

Conversation

@tisonkun

Copy link
Copy Markdown
Member

This closes #10133.

cc @alamb

Signed-off-by: tison <wander4096@gmail.com>
Comment thread doap.rdf
</description>
<bug-database rdf:resource="https://github.com/apache/datafusion/issues" />
<mailing-list rdf:resource="https://lists.apache.org/list.html?dev@datafusion.apache.org" />
<download-page rdf:resource="https://github.com/apache/datafusion/releases" />

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have a download page actually, and I suggest we should create one.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The official releases will be on the apache download site https://downloads.apache.org/datafusion/ (they are currently on https://downloads.apache.org/arrow/)

However I think the vast majority of datafusion users will get datafusion via crates.io or a direct github link 🤔 I wonder if other types of releases / release page are needed

Any thoughts @andygrove ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good question. We may omit this attribute right now.

The situation is somehow complicated due to the existing ASF policies, which make some assumptions in the old days.

Here is the policy: https://infra.apache.org/release-download-pages.html

You can see a formal Download page has a lot of requirements to follow. But for DataFusion, most users just use cargo add datafusion and never care if such a page exists.

We recently had a discussion on the general@incubator.a.o for related topics; while I understand your suggestion here, and we should do what is helpful for our users.

However, Arrow has a release/download page, and I check it meets all the requirements. So if people in DataFusion have time to implement it, we can avoid any further concern.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good -- I filed to track #10236

@alamb alamb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much @tisonkun 🙏 This looks great

I left a few comments / suggestions, but we could also do them as follow ons

Once we merge this PR I will follow the instructions in https://projects.apache.org/create.html to change the apache site (I think it needs to be a PMC member to do this)

Comment thread doap.rdf Outdated
Comment thread doap.rdf
</description>
<bug-database rdf:resource="https://github.com/apache/datafusion/issues" />
<mailing-list rdf:resource="https://lists.apache.org/list.html?dev@datafusion.apache.org" />
<download-page rdf:resource="https://github.com/apache/datafusion/releases" />

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The official releases will be on the apache download site https://downloads.apache.org/datafusion/ (they are currently on https://downloads.apache.org/arrow/)

However I think the vast majority of datafusion users will get datafusion via crates.io or a direct github link 🤔 I wonder if other types of releases / release page are needed

Any thoughts @andygrove ?

Comment thread doap.rdf Outdated
Comment thread doap.rdf Outdated
Comment thread doap.rdf
Comment thread doap.rdf Outdated
Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
@tisonkun

Copy link
Copy Markdown
Member Author

I think we can merge it as is now. There is no blocker, and we can keep improving if any other good suggestions are made.

@andygrove andygrove left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @tisonkun

@alamb
alamb merged commit bab39f7 into apache:main Apr 25, 2024
@alamb

alamb commented Apr 25, 2024

Copy link
Copy Markdown
Contributor

I think we can merge it as is now. There is no blocker, and we can keep improving if any other good suggestions are made.

I agree -- thank you @tisonkun and @andygrove

@alamb

alamb commented Apr 25, 2024

Copy link
Copy Markdown
Contributor

I added what I think is the entry. See #10133 (comment) -- will keep that updated

ccciudatu pushed a commit to hstack/datafusion that referenced this pull request Apr 26, 2024
* chore: Create a doap file

Signed-off-by: tison <wander4096@gmail.com>

* Apply suggestions from code review

Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>

---------

Signed-off-by: tison <wander4096@gmail.com>
Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
@tisonkun
tisonkun deleted the doap branch April 26, 2024 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a DOAP (description of a project file)

3 participants