HackMD
    • Sharing Link copied
    • /edit
    • View mode
      • Edit mode
      • View mode
      • Book mode
      • Slide mode
      Edit mode View mode Book mode Slide mode
    • Customize slides
    • Note Permission
    • Read
      • Owners
      • Signed-in users
      • Everyone
      Owners Signed-in users Everyone
    • Write
      • Owners
      • Signed-in users
      • Everyone
      Owners Signed-in users Everyone
    • Commenting & Invitee
    • Publishing
      Please check the box to agree to the Community Guidelines.
      Everyone on the web can find and read all notes of this public team.
      After the note is published, everyone on the web can find and read this note.
      See all published notes on profile page.
    • Commenting Enable
      Disabled Forbidden Owners Signed-in users Everyone
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Invitee
    • No invitee
    • Options
    • Versions and GitHub Sync
    • Transfer ownership
    • Delete this note
    • Note settings
    • Template
    • Insert from template
    • Export
    • Dropbox
    • Google Drive Export to Google Drive
    • Gist
    • Import
    • Dropbox
    • Google Drive Import from Google Drive
    • Gist
    • Clipboard
    • Download
    • Markdown
    • HTML
    • Raw HTML
Menu Note settings Sharing Help
Menu
Options
Versions and GitHub Sync Transfer ownership Delete this note
Export
Dropbox Google Drive Export to Google Drive Gist
Import
Dropbox Google Drive Import from Google Drive Gist Clipboard
Download
Markdown HTML Raw HTML
Back
Sharing
Sharing Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Comment & Invitee
Publishing
Please check the box to agree to the Community Guidelines.
Everyone on the web can find and read all notes of this public team.
After the note is published, everyone on the web can find and read this note.
See all published notes on profile page.
More (Comment, Invitee)
Commenting Enable
Disabled Forbidden Owners Signed-in users Everyone
Permission
Owners
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Invitee
No invitee
   owned this note    owned this note      
Published Linked with GitHub
Like BookmarkBookmarked
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# PulpCon 2020 planning doc ###### tags: `PulpCon 2020` --- # **VOTING FOR TOPICS IS CLOSED! Thanks everyone for participation.** --- ## Goals * pair programming / review sessions +1 * asciinema demos * Team bonding - social time, maybe a game, or walk/exercise break up long meetings? Smaller group activities? ## Topics * Development Environment Workshop +1 * Using pulplift effectively * What other coding tools are core pulp developers using every day? * What docs does one really need to read to work on pulp? * Ties in with the community and state of plugins topic. * If everyone can share one tool or trick or process they use that resulted in an efficiency boost, we could perhaps produce a useful cheatsheet. * fzf, ripgrep, fd, ncdu * * State of plugins (a candidate for the community session) * No new plugins have been developed in 2020. Last new plugin pulp_npm started at the end of 2019. * "By us", do we know that nobody in the community has written one? We're too overburdened right now with what we have on our plate to commit ourselves. * How can we improve this? * How can we better encourage and support our community to develop new plugins? * ~~4.0.0 release planning~~ Major Release Branching +1 +1 +1 +1 +1 * [bmbouter] Interested mostly in answering: how do we facilitate development of 4.0.0 while at the same time active development on 3.y. * Renamed to "Major Release Branching" to avoid talk about 4.0 features * Lockless pulp * Our aproach to locking on resources forces us to live in the so called synchronization quadrant. Are there ways to get out of it? * Can we remove the need for the resource manager? * Installers +1 +1 * pulp_installer x single container x pulplift x pulp-operator * how to make it less complex and confusing? * Unifying installer documentation (IMHO plugin doc should not contain much more than a reference to the pulpcore installation doc) * Community +1 +1 +1 * Where are the community PRs? How to make the PR process easier for the contributors? * pulplift is not easy and practical (docker seems more friendly to a casual contributor, setting vagrant and an entire VM just for one or two PRs discourages the contributors) * The [noissue] thing always make contributors PRs to fail * [noissue], flake8, black, ... it can make the contributor push so many times, before actually seeing the PR being really tested * https://pulp.plan.io/issues/6938 * [bk] I would like to see community broken down into "How do we get more users" in addition to "Make it better for contributors". I think pulp needs more exposure and users. * Are mailing lists ideal? Should we move towards a more modern form of community engagement * A lot of the conversations happen on Freenode #pulp-dev while there is a #pulp channel for general questions. A lot of the general back-and-forth of the Pulp team could be considered lost to general Pulp users. * Would moving to something like Discourse be an idea for all development and community chatter? * Recap of the relative_path proposals +1 +1 * Review and look at the pros/cons of the proposals so far for the relative_path problem * multi-tenancy +1 +1 * How can we ensure users who don't trust each other can't access content from other users * e.g. one user has a RHEL subscription and another doesn't * e.g. one user uploads a sensitive RPM and another user adds it into their repo * Pulp CI architecture +1 +1 +1 * Problem: our CI is a mishmash of pieces cobbled together through incremental changes over the past few years * Goals: * Redesign our CI architecture to make it not Travis-specific (for move to Github Actions) * Make it so devs can easily run it from inside pulplift * Make it pluggable or easier to add new functionality/checks * Have a way to automatically update repos when there are changes * Pulp 3 CLI design +1 +1 +1 +1 * Discuss latest design ideas based on recent squeezer work * Use cases from community +1 * Allocate a slot or two on the schedule for users and stakeholders to share their use cases and see how we can address their needs * Motivating and perceptions for a UI for Pulp +1 * [bmbouter] believes that not having a UI is significantly holding back the growth of the Pulp community

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lost their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.


Upgrade

All
  • All
  • Team
No template found.

Create custom template


Upgrade

Delete template

Do you really want to delete this template?

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Tutorials

Book Mode Tutorial

Slide Mode Tutorial

YAML Metadata

Contacts

Facebook

Twitter

Discord

Feedback

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions

Versions and GitHub Sync

Sign in to link this note to GitHub Learn more
This note is not linked with GitHub Learn more
 
Add badge Pull Push GitHub Link Settings
Upgrade now

Version named by    

More Less
  • Edit
  • Delete

Note content is identical to the latest version.
Compare with
    Choose a version
    No search result
    Version not found

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub

      Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

       Sign in to GitHub

      HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully