Pulp Community Feedback

Here is a collection of feedback from the Pulp community about their general experiences with Pulp

Feel free to add a heading or subheading to suit your needs.

Pulp's Communication Channels

  • General negative impression of communities that only list IRC for communication
  • Difficulty registering to Freenode to use via Matrix
  • Need to advertise more prominently our Matrix integrations
  • More transparent forums for discussions and decision making

Documentation

  • Pulpcore docs assume knowledge of Pulp 2
  • RPM( or in general plugin) docs do not have end to end steps for "how do I make a new RPM repository"
  • API documentation: example code is typically so abstract as to be useless
  • Lots of docs with not great inter-connectivity, and several places where there's an example or explanation which feels incomplete
  • Lack of tutorial style docs, for example: how to mirror Centos.

Changelogs

  • Change announcements are also a bit inconsistent for modules; it's sometimes challenging to find a changelog, etc.

Contributing to Pulp

The current PR process asks a lot from a user:

  • Create issue in some other tool (plan.io) with minimal guidance (example issues would be useful to explain what the fields mean and which ones need completed)
  • then alter your git commit to reference that issue using the same syntax one would use to reference a github issue
  • adding a commit with a new changelog entry using a specific naming convention
  • open a PR with probably the same content as the other issue

Suggestion:: documenting a complete sample contribution with real-world examples would be a huge help there.

Suggestion: Transform the "[noissue]" to a gh-action tagging pr's / commits without an attached issue.

Select a repo