Jan Range (Nov 29 2023 at 11:41): Jan Range (Nov 29 2023 at 11:41):Hi @all,
this topic is meant to cover the PyDataverse Re-Vamp. I have created a first plan on how to proceed. IT is ordered by phases, which are in decreasing importance and increasing complexity.
Feel free to add and/or update points within this doc :raised_hands:
Philip Durbin 🚀 (Nov 29 2023 at 11:49):I added some comments. Looks great!
Brian Brock (Dec 01 2023 at 15:27):I've been working on revamping pyDataverse for some time, and have been unable to reach anyone else who wants to do that.
Brian Brock (Dec 01 2023 at 15:28):Right now I'm implementing methods to access /api/admin, and will be adding a shim class to enable scripting more easily for user management. My group has related needs.
Brian Brock (Dec 01 2023 at 15:28):I have plans to develop those scripts within the next few weeks and am making PRs.
Brian Brock (Dec 01 2023 at 15:29):I'd love to collaborate.
Brian Brock (Dec 01 2023 at 15:30):I've got about 15 years of experience working with Python in managing Linux distributions and packages.
Brian Brock (Dec 01 2023 at 15:31):and probably close to 20 in writing tests. I formerly worked as the kernel QE at Red Hat.
Brian Brock (Dec 01 2023 at 15:32):I'm going to be making progress rapidly, so the earlier we coordinate efforts, the better.
Jan Range (Dec 01 2023 at 15:33):Hi @Brian Brock :wave: That sounds great! Shall we meet-up at some point to exchange?
Brian Brock (Dec 01 2023 at 15:36):I'd like that very much. I think we can help each other a great deal.
Jan Range (Dec 01 2023 at 15:46):Brian Brock schrieb:
I'd like that very much. I think we can help each other a great deal.
Indeed, would be great to collaborate. Speaking of a meeting, which dates would work for you?
Jan Range (Dec 02 2023 at 12:57):PyDataverse tests are running again :raised_hands:
https://github.com/gdcc/pyDataverse/pull/167
Jan Range (Dec 02 2023 at 12:59):Shall we remove Travis-CI and Coveralls? Both do not run anyway.
Philip Durbin 🚀 (Dec 02 2023 at 19:11):As for Travis CI, yes, let's remove it.
Notification Bot (Dec 04 2023 at 14:23):12 messages were moved from this topic to #python > code coverage by Philip Durbin.
Brian Brock (Dec 05 2023 at 00:12):I responded in mail, but to clarify publicly: I blocked off time Wednesday at 8am (UTC-5).
I'm also available most of Thursday and all of Friday.
Jan Range (Dec 05 2023 at 08:16):Great! Wednesday 8AM works well for me :raised_hands:
Jan Range (Dec 21 2023 at 16:25):Hi @all! I've been experimenting with a couple of OpenAPI client-code generators and found that speakeasy provides the most stable and user-friendly solution.
Tested it with my app EasyReview in a CI pipeline. Once the OpenAPI schema of EasyReview changes, the SDK is re-generated automatically. You can find both repositories here:
EasyReview - Parent repo
python-easyreview - Python SDK repo
The generated SDK works perfectly! Additionally, the generation can be customized quite well (sub-structures, namespaces etc.) via the OpenAPI document. Apart from Python, you can also generate Typescript SDKs, which could be interesting for dataverse-js @Guillermo Portas
What are your thoughts? Is this something to consider working towards once the up-stream specifications are fixed?
Jan Range (Jan 17 2024 at 16:14):Thank you to all the participants for attending this first meeting!
Oliver Bertuch (Jan 17 2024 at 22:56):Sorry I couldn't make it - snow chaos... Is there a recording available?
Jan Range (Jan 19 2024 at 11:44):I am sorry, but I have missed to start the recording. However, you can access the notes for the last meeting on the page and here. Rest assured that I will ensure that the next meeting is recorded.
Philip Durbin 🚀 (Jan 22 2024 at 15:09):Ah, I wasn't sure if the plan was to record or not. Next time I'll remind you. :grinning:
Jan Range (Jan 31 2024 at 12:36):Hi everyone! The second pyDataverse Working Group meeting will start in about 2.5 hours at 3 PM UTC. Please feel free to add topics to discuss to today's agenda within the meeting notes.
See you later :raised_hands:
Jan Range (Jan 31 2024 at 16:44):For those who couldn't attend today's meeting, the recording is now available online at py.gdcc.io. Looking forward to seeing you in two weeks :raised_hands:
Jan Range (Feb 14 2024 at 10:35):Hi @all, the next pyDataverse Working Group meeting starts in about 4.5 hours at 3PM UTC. Please feel free to add your topics in the notes and see you later :raised_hands:
Philip Durbin 🚀 (Feb 14 2024 at 11:56):I added a topic. Thanks. See you soon.
Philip Durbin 🚀 (Mar 13 2024 at 13:55):I'll be a little late for today's meeting. I have standup at the same time but usually it only lasts for 15 minutes.
Jan Range (Mar 13 2024 at 14:00):See you all in an hour!
Meeting link - https://unistuttgart.webex.com/unistuttgart/j.php?MTID=m322473ae7c744792437ce854422e52a3
Notes - https://docs.google.com/document/d/19cGiPV3QFlwGXLOKUUzxbyai59yIlSoFV0GOv_Tc2XE/edit?usp=sharing
Jan Range (Apr 09 2024 at 08:49):Dear all,
I hope you're doing well. I wanted to let you know that unfortunately, we've had to cancel the upcoming PyDataverse Working Group Meeting on Wednesday due to conflicting schedules.
However, we'll be back on the 24th of April at 2:00 PM UTC for our next meeting. If you're interested, you can check out notes and recordings of previous meetings and all upcoming ones on our website at py.gdcc.io.
All the best,
Jan
Jan Range (May 08 2024 at 10:35):Dear all, I hope all is well. Unfortunately, I have caught Covid and won't be able to host today's PyWG meeting :frown:
Philip Durbin 🚀 (May 08 2024 at 11:10):Oh no! Sorry to hear, Jan! Get well soon
Philip Durbin 🚀 (May 08 2024 at 13:27):I added "CANCELED" to the event on Google Calendar.
Jan Range (May 08 2024 at 13:33):Philip Durbin schrieb:
Oh no! Sorry to hear, Jan! Get well soon
Thanks Phil :smile:
Jan Range (May 08 2024 at 13:34):Philip Durbin schrieb:
I added "CANCELED" to the event on Google Calendar.
Oh that one I forgot. Website is updated :smile:
Philip Durbin 🚀 (Jul 16 2024 at 20:46):I think this is the thread we us to talk about working group meetings. :thinking:
Are we on for tomorrow? It's in Google Calendar but not https://py.gdcc.io
Also, should we remind people via Google Groups that we're meeting (if we are)?
Jan Range (Jul 16 2024 at 20:49):Sorry @Philip Durbin I have missed updating the website. There are too many things on my desk at the moment :anguish: Meeting will happen tomorrow and I'll update the website. And sure, lets announce it on Google Groups :smile:
Philip Durbin 🚀 (Jul 16 2024 at 20:54):Cool, do you want me to announce it?
Jan Range (Jul 16 2024 at 20:55):That'd be great, thanks :smile:
Philip Durbin 🚀 (Jul 16 2024 at 21:35):Sent! https://groups.google.com/g/dataverse-community/c/jPMDgEoaHI4/m/YVEWpLQ1AgAJ
Jan Range (Jul 16 2024 at 21:35):Thanks @Philip Durbin ! Just updated the website
Philip Durbin 🚀 (Jul 16 2024 at 21:38):Yep, I saw. Awesome.
Jan Range (Jul 17 2024 at 14:42):I have updated the Google Calendar to match the new interval. Oddly, only the option "every third Wednesday" was available, but I guess that was due to editing todays event. Is every 3rd Wednesday fine for you?
Philip Durbin 🚀 (Jul 17 2024 at 14:52):I mean, probably, but if you want every second Wednesday it should work!
Jan Range (Jul 17 2024 at 14:52):I am happy with the 3rd too :smile:
Philip Durbin 🚀 (Jul 17 2024 at 14:53):I think you have to change it to a second Wed first (like Aug 14) and then set the recurring date.
Philip Durbin 🚀 (Jul 17 2024 at 14:55):3rd is fine. It doesn't conflict with Thanksgiving this year. :turkey: Whatever you want.
Jan Range (Jul 17 2024 at 15:05):True, that would've been an option. I was too hesitant in fear of messing up the calendar :grinning:
Jan Range (Jul 17 2024 at 15:05):Happy with the 3rd and also no collisions :raised_hands:
Last updated: Nov 01 2025 at 14:11 UTC