Re: Request to join the Debian Python Team
On Thursday, 4 April 2024 18:02:42 CEST Pierre-Elliott Bécue wrote: > > I've bumped your access to maintainer, let's try, and I'll downgrade > when you're done. The project has been transferred and now resides here: https://salsa.debian.org/python-team/packages/shedskin Many thanks once again! Paul
Re: Request to join the Debian Python Team
Paul Boddie wrote on 04/04/2024 at 17:22:35+0200: > On Wednesday, 3 April 2024 19:03:44 CEST Pierre-Elliott Bécue wrote: >> Paul Boddie wrote on 03/04/2024 at 16:21:05+0200: >> > >> > Many thanks for giving me access! Would it make sense to move the existing >> > project into the Python Team's packages collection on Salsa, or is that >> > only permitted for packages that are actually adopted by the team? >> >> On the contrary, please do! > > It seems that the "transfer project" function would be the most appropriate > way of moving the project, but I don't think I am allowed to perform the > transfer. In the settings for my project, the pull-down menu only offers > transfer to the "moin" group where I have some other projects. > > I reviewed the documentation... > > https://salsa.debian.org/help/user/project/settings/migrate_projects#transfer-a-project-to-another-namespace > > ...and I think that the only obstacle is that I am a developer as opposed to > a > maintainer. I suppose that I could re-create the project in the group > instead, > if that is more appropriate. > > Thanks in advance for any assistance that can be offered, and sorry to bring > up such tedious administrative issues! I've bumped your access to maintainer, let's try, and I'll downgrade when you're done. -- PEB signature.asc Description: PGP signature
Re: Request to join the Debian Python Team
On Wednesday, 3 April 2024 19:03:44 CEST Pierre-Elliott Bécue wrote: > Paul Boddie wrote on 03/04/2024 at 16:21:05+0200: > > > > Many thanks for giving me access! Would it make sense to move the existing > > project into the Python Team's packages collection on Salsa, or is that > > only permitted for packages that are actually adopted by the team? > > On the contrary, please do! It seems that the "transfer project" function would be the most appropriate way of moving the project, but I don't think I am allowed to perform the transfer. In the settings for my project, the pull-down menu only offers transfer to the "moin" group where I have some other projects. I reviewed the documentation... https://salsa.debian.org/help/user/project/settings/migrate_projects#transfer-a-project-to-another-namespace ...and I think that the only obstacle is that I am a developer as opposed to a maintainer. I suppose that I could re-create the project in the group instead, if that is more appropriate. Thanks in advance for any assistance that can be offered, and sorry to bring up such tedious administrative issues! Paul
Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)
On 3/25/24 19:17, Julian Gilbey wrote: Hi all, [NB: sent to d-science, d-python, d-devel and the RFP bug; reply-to set to d-science and the RFP bug only] An update on Apache Arrow, and in particular the Python library PyArrow. For those who don't know: Apache Arrow is a development platform for in-memory analytics. It contains a set of technologies that enable big data systems to process and move data fast. It specifies a standardized language-independent columnar memory format for flat and hierarchical data, organized for efficient analytic operations on modern hardware. The project is developing a multi-language collection of libraries for solving systems problems related to in-memory analytical data processing. This includes such topics as: * Zero-copy shared memory and RPC-based data movement * Reading and writing file formats (like CSV, Apache ORC, and Apache Parquet) * In-memory analytics and query processing (from: https://arrow.apache.org/docs/index.html) Pandas has announced that Pandas 3.x will depend on PyArrow in a critical way (it will back the "string" datatype), and it is due to be released imminently. So this is a plea for anyone looking for something really helpful to do: it would be great to have a group of developers finally package this! There was some initial work done (see the RFP bug report for details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021), but that is fairly old now. As Apache Arrow supports numerous languages, it may well benefit from having a group of developers with different areas of expertise to build it. (Or perhaps it would make more sense to split the upstream source into a collection of different Debian source packages for the different supported languages. I don't know.) Unfortunately I don't have the capacity to devote any time to it myself. Thanks in advance for anyone who can step forward for this! Best wishes, Julian Hi, I may not have much available time to help, though I'd love to have Arrow in Debian, as Ceph uses it, and currently use an embedded version. Cheers, Thomas Goirand (zigo)
Re: Membership request
Hi Nicolas, Nicolas Couture wrote on 04/04/2024 at 10:32:05+0200: > Hello Pierre-Elliott, > > Thank you for your response. > > I believe that a contribution track is a way to contribute to the Python team > without being a full member. I am interested in learning > more about the contribution track and how I can get involved. > > Please let me know if there is any additional information or resources that > you can provide. > > Thank you for your time and consideration. > > Best regards, What I was meaning is that before granting full access, it would be good to build trust. To do so, I was offering to create the specific repositories you want to work on in the group and grant you access on these very repositories. After some time we could consider expanding your access to the whole group packages. Would that be fine? -- PEB signature.asc Description: PGP signature
Re: Membership request
Hello Pierre-Elliott, Thank you for your response. I believe that a contribution track is a way to contribute to the Python team without being a full member. I am interested in learning more about the contribution track and how I can get involved. Please let me know if there is any additional information or resources that you can provide. Thank you for your time and consideration. Best regards, Nicolas Couture Open Source Enthusiast On Wed, Apr 3, 2024 at 9:45 AM Pierre-Elliott Bécue wrote: > Nicolas Couture wrote on 27/02/2024 at > 21:00:58+0200: > > > Good day, > > > > As I met "pollo" this morning on OFTC after inquiring about helping out > with the adoption of virtualenvwrapper or researching more into > > the state of packaging pyenv in Debian, he suggested a good starting > point would be to read https://deb.li/PyPolicy which I had not until > > now and then join the team to help out on any team-maintained packages. > > > > I understand the gist of it but I'm starting to think that "pollo" might > actually be a chicken, because he's excellent at laying out > > eggs-amples of policy, but when it comes to packaging, he believes in > free-range. > > > > On with the serious phase of this request: > > > > Why you want to join the team: > > > > * Help maintain specific packages though my interest might be broader > than that and I'm willing to help out on team-maintained > > packages to become familiar with the workflows > > * Salsa login: ncouture > > * I have read and accept > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst > > > > Best regards, > > Hello Nicolas, > > Sorry for not replying to your request earlier. > > And nice of you roasting pollo. :-) > > I'd be glad to give you access to specific repositories (and create > those which you need to have created), but before granting you a full > access to the group, I guess I'd like to see a bit of your contributions > track. > > Would that be a fine compromise for you? > > -- > PEB >
Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)
On 3/25/24 7:17 PM, Julian Gilbey wrote: So this is a plea for anyone looking for something really helpful to do: it would be great to have a group of developers finally package this! There was some initial work done (see the RFP bug report for details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021), but that is fairly old now. As Apache Arrow supports numerous languages, it may well benefit from having a group of developers with different areas of expertise to build it. (Or perhaps it would make more sense to split the upstream source into a collection of different Debian source packages for the different supported languages. I don't know.) Unfortunately I don't have the capacity to devote any time to it myself. Thanks in advance for anyone who can step forward for this! As someone from the Debian-GIS community, I would also be very interested in this! The Apache Arrow C++ library is one of the dependencies to make GDAL/OGR able to read/write (geo)parquet files, a data format with a lot traction in the geo community [0]. Thereby making it possible for QGIS to handle those (on Debian). [0] https://cloudnativegeo.org/blog/2023/09/duckdb-the-indispensable-geospatial-tool-you-didnt-know-you-were-missing/ Regards, Richard Duivenvoorde
