-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integration to arxiv2notion #1
Comments
Hi @denkiwakame, Thanks for reaching out and the awesome arxiv2notion project!! I created this repo just for convenience and my personal use case as I imagine it might take a longer time to iterate over the PR/review procedure and more communication costs. Glad to know that you are aware of this work and also active in communication! I totally agree with the plan to integrate these new features arxiv2notion and release a unified version for users. Specifically, there are the TODO items for us
I will allocate some time for the first item after the deadline for neurips (1 month left) ;) Or feel free to merge/move new features to your original repo (this repo is also under MIT) if you want to do it earlier. Does this plan sound good? Thanks again for reaching out, I am pleased to become a member/maintainer for this project. In general, I feel this tool is simple yet super helpful for the researchers who are using Notion to organize/track the literature. Nice initial work!! |
Thank you so much for your prompt response! have invited you as a collaborator to https://github.com/denkiwakame/arxiv2notion . 1) creating PRs for merging arxiv2notionplus
To me, whichever is OK. Fortunately, (a). will not become such a big change in this case. After merging, I will create a changelog and release the new version by tag. 2) who to do these PRs
3) release on the Chrome store
4) move the namespace of arxiv2notion to a group (side topic)
Thanks again for your commitments and kind communication, you can reply when u have time. |
Dear @wangjksjtu, I sincerely apologize for the long time since we last contacted. Your contribution is now listed in the original repository: https://github.com/denkiwakame/arxiv2notion/graphs/contributors I have also submitted a review request to the Chrome Store. As long as the original extension is served under the MIT License, you can still distribute arxiv2notion plus. However, you cannot overwrite my copyright for this extension. You can add your own copyright notice in addition to mine. The biggest contribution of arxiv2notionplus is the improvement of documentation; more than 90% of the extension's code is still written by me. I would appreciate it if you could keep my copyright notice
|
Thanks so much for the follow-up and great integration!! Also, apologize for not having time for this project. I have changed the license as you suggested. Thanks again for creating this tool for the community ;) |
@wangjksjtu
Hi, I'm an original author of https://github.com/denkiwakame/arxiv2notion and happened to know this repository today.
I'm really impressed that this repository has done the major todos of the original repository, solid work. Thank you!
I have been busy for working on some other research projects and, it's embarrassing, have left these todos for a loooong time on this extension (as in denkiwakame/arxiv2notion#3).
I would like to ask you if you're interested in merging these enhancements to the original repository (as pull requests).
After releasing the arxiv2notion, which was originally my personal toolkit, I found that there exists more potential users and demands for this extension than I expected.
While we can also plan to release this extension on Chrome Store, the users may be a bit confused if they find multiple versions (e.g. arxiv2notion / arxiv2notion+ / arxiv2notion++...).
It would be appreciated if I could welcome you as a core maintainer of arxiv2notion (will add acknowledgment for you on README). No worries that I still can review and commit codes when I have some time.
I'm also considering to move the namespace of arxiv2notion to a group like this (https://github.com/neoclide) in the future.
Could you provide your opinion on this ?
The text was updated successfully, but these errors were encountered: