new repo for File ID server extension

[dlqqq]

cc @Zsailer

I would like to migrate the work done in jupyter-server/jupyter_server#921 into a separate server extension. This gives us much more flexibility to iterate on the File ID service without having to make changes against Jupyter Server core. To do this, we would need a separate repo to store the File ID server extension.

Could you do this for us? I would also like to have write access such that I can make necessary changes early-on and be allowed to merge PRs.

Votes

• @damianavila
  • yes
  • no
• @kevin-bates
  • yes
  • no
• @echarles
  • yes
  • no
• @SylvainCorlay
  • yes
  • no
• @afshin
  • yes
  • no
• @vidartf
  • yes
  • no
• @rahul26goyal
  • yes
  • no
• @ellisonbg
  • yes
  • no
• @ivanov
  • yes
  • no
• @lresende
  • yes
  • no
• @Zsailer
  • yes
  • no
• @blink1073
  • yes
  • no
• @willingc
  • yes
  • no
• @jess-x
  • yes
  • no

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[afshin]

cc: @jupyter-server/jupyter-server-council

[dlqqq]

Because this was brought up in the server meeting last Thursday 9 AM PT (8/25/2022), let's close the vote this Thursday 9 AM PT (9/1/2022), and take action accordingly by Friday.

[Zsailer]

I've updated the top comment to reflect voting state.

[ellisonbg]

I vote yes, but don't have repo permissions to vote.

[blink1073]

@ellisonbg you should have an invitation email

[ellisonbg]

Thanks, I got it and am now able to vote :-)

…

On Mon, Aug 29, 2022 at 12:28 PM Steven Silvester ***@***.***> wrote: @ellisonbg <https://github.com/ellisonbg> you should have an invitation email — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGXUBR6EXNZY6L7TVQI5TV3UFN5ANCNFSM57IOI5FQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Brian E. Granger Senior Principal Technologist, AWS AI/ML ***@***.***) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

[Zsailer]

Ok! We've reached quorum and the consensus is "yes"!

Let's proceed to create the repo. @dlqqq what would you like to call the repo? Once I get confirmation there, I'll create the new repo and add you as collaborator.

[dlqqq]

@Zsailer Thank you! I was thinking it would be created under the jupyter-server org with the repo named as jupyter_server_fileid. This seems to match the convention of other server extensions (using underscores and being prefixed with jupyter_server).

[dlqqq]

Sorry I wasn't able to attend the server meeting earlier; was at a dental appointment.

[Zsailer]

@dlqqq done 🚀 😎 : https://github.com/jupyter-server/jupyter_server_fileid