Comments (4)
From: @quba42 (quba42)
Date: 2021-05-19T15:53:59Z
This is very much a valid feature request, but I cannot say if and when we will work on it.
It is not currently on our road map (which could change in the future).
Contributions are of course welcome. If anyone is interested in working on this feel free to contact me for some starting help.
See also:
pulp_deb/pulp_deb/app/tasks/synchronizing.py
Line 510 in a3ee34b
from pulp_deb.
From: markawr (markawr)
Date: 2021-05-19T17:45:24Z
Thanks @quba42. Definitely no expectation here to get the feature without doing the work. Myself and a possibly a few colleagues will have to learn how to get a development env setup and start to contribute code. Being new to Pulp it would be useful to have a bit of hand holding and patience as we navigate the process of contributing code and having it made available in a future update of the plugin. I will start by ensuring we are subscribed to the right lists etc., if there any other resources for Pulp n00bs please feel free to share.
from pulp_deb.
From: @quba42 (quba42)
Date: 2021-05-26T07:42:30Z
markawr wrote:
Myself and a possibly a few colleagues will have to learn how to get a development env setup and start to contribute code. Being new to Pulp it would be useful to have a bit of hand holding and patience as we navigate the process of contributing code and having it made available in a future update of the plugin. I will start by ensuring we are subscribed to the right lists etc., if there any other resources for Pulp n00bs please feel free to share.
I have this idea kicking around my head of writing exactly such a guide (how to enter the project). I have a lot of local notes by myself for myself that I could rework and share in some form. The first thing to set up is indeed a development environment. The pulp_installer repo [1] includes a set of development VMs that can be run locally using vagrant + libvirt. I believe the README file in the repo includes some instructions on setting those up. The pulpcore documentation includes some general points on contributing [2] as well as a plugin writer's guide [3]. There are two mailing lists (pulp-list, and pulp-dev) referenced here [4]. Most in person help can be obtained on the freenode IRC channel, which also maintains a matrix bridge. (Though I believe that is currently in flux due to a hostile corporate takeover of freenode).
[1] https://github.com/pulp/pulp_installer
[2] https://docs.pulpproject.org/pulpcore/contributing/index.html
[3] https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide
[4] https://pulpproject.org/get_involved/
You can email me at "quirinp at atix dot de", since this ticket is probably not the best place to continue this exchange. I am sure I can provide an interactive video conference/screen share session at some point as well, perhaps once you hit the first road block in setting up or using the development environment.
from pulp_deb.
From: pulpbot (pulpbot)
Date: 2021-06-15T00:26:48Z
PR: #295
from pulp_deb.
Related Issues (20)
- duplicate key value violates unique constraint "core_publishedmetadata_publication_id_relative__60dd832b_uniq" HOT 12
- Requesting pulp_deb bindings release 2.19.z with updated faraday dependencies HOT 6
- Allow users to set 'origin' and 'label' in release files HOT 1
- Improve the signing service documentation
- Autopublish for Debian plugin like the RPM one does HOT 4
- Distribution Packages and Packages.gz contain incorrect data (Pulp signing-service GPG key) HOT 15
- Missing packages from Packages file HOT 1
- Proxy sync fails when newer binding is used to sync content on older pulp_deb api HOT 2
- Faster async metadata signing HOT 1
- Refactor: `package` and `relative_path` fields on `Content`
- pulp orphan cleanup failure (protected foreign keys) HOT 17
- Cannot sync repo with blank custom field HOT 1
- Ability to use Package filenames when publishing HOT 4
- PackageReleaseComponents are not being properly handled in the case of duplicates HOT 2
- Ability to specify Origin when publishing repository HOT 1
- Add publication options for packages with Phased-Update-Percentage HOT 4
- Please add `names__in` for deb HOT 2
- As a REST api user I would like to know which distributions are included in a publication
- 'NoneType' object has no attribute 'artifact_set_sha256' when syncing a recently updated deb remote HOT 3
- Repo versions not created via sync should not be verbatim published HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pulp_deb.