Re: [Pulp-dev] Turning release notes into user content

[Dennis Kliban]

On Mon, Apr 20, 2020 at 2:38 PM Melanie Corr  wrote:

> Hi all,
>
> As part of the effort to broaden awareness of Pulp and increase
> interactions with both current and future community members, I am looking
> into increasing frequency of blog posts on the Pulp site. This will also
> help with a social media strategy also.
>
> Currently, I can see that there is a high level of transparency on the
> site, with release note update information being regularly posted, but with
> some effort this could be slightly more digestible for the reader.
>
> I would like to try and take this content that is gathered with the
> towncrier tool to see if I could develop the output into user content, for
> example, why this incremental update benefits the user, how does fixing x
> bug make the user's life easier, and so on.
>
> To do this, I would need to collect the output of towncrier myself, or the
> draft output if I wanted to prepare a post in advance of a release.
>
> Can you advise how I would go about collecting this?
> If you have any further suggestions, I would love to hear them.
>
>
You will need to install 'towncrier' from PyPI and then run it from the
root of the pulpcore repository. Here are the commands I use for that.

pip install towncrier
git clone https://github.com/pulp/pulpcore
cd pulpcore
towncrier --version x.y.z --draft


Thanks,
>
> --
>
> Melanie Corr, RHCE
>
> Community Manager
>
> Red Hat 
>
> Remote, Ireland
>
> mc...@redhat.com
> M: +353857774436 IM: mcorr
> 
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] [Meeting Minutes] Sprint 71 Planning

[Robin Chan]

17-April-2020

New Sprint 71 query: https://pulp.plan.io/issues?query_id=150

New Agile board: https://pulp.plan.io/agile/board?query_id=151

Stats on how we did in previous 2 week  Sprint 70 Query
:

 New - 14

 Assigned - 5

 Post - 9

 Modified - 10

Closed - CURRENTRELEASE - 8

Closed - WORKSFORME - 1

Closed - NOTABUG - 1

Closed - DUPLICATE - 1

Closed - WONTFIX - 0

Closed - COMPLETE - 0


Action Items from last Sprint Planning

   -

   5932 : Dkliban will update & ensure we
   have a good plan before re-adding
   -

  Turn into task & wrote a new one - to be added to sprint.
  -

   ggainey/dkliban intern
   -

  Lots of thoughtful discussion going on in email thread
  -

  CLI design discussion gearing up (whether we use it for an intern
  project or not)
  -

   Potential work:
   -

  Potential work related to openshift installation procedure
  -

   Last sprint said we would work on this, but not on sprint:
   -

  RPM: https://pulp.plan.io/issues/6387
  -

  Will be added to sprint when staffing in RPM mtg/team


Dates:

https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans

Sprint candidates:

https://pulp.plan.io/issues?query_id=26

Pending Items:

   -

   Add import/export for container


Action Items:

   -

   rchan: Clear Sprint Candidate https://pulp.plan.io/issues?query_id=26


   -

   rchan: send out planning minutes
   -

   Rchan update agile board for sprint & Move new, assigned, post issues to
   new sprint
   -

   Publish https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans
   -

   Dkliban: add import/export story for container plugin
   -

   Mini teams can also remove items moving to next sprint


Robin Chan

She/Her/Hers

Satellite Software Engineering Manager - Pulp

Red Hat 

IRC: rchan

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Turning release notes into user content

[Melanie Corr]

Hi all,

As part of the effort to broaden awareness of Pulp and increase
interactions with both current and future community members, I am looking
into increasing frequency of blog posts on the Pulp site. This will also
help with a social media strategy also.

Currently, I can see that there is a high level of transparency on the
site, with release note update information being regularly posted, but with
some effort this could be slightly more digestible for the reader.

I would like to try and take this content that is gathered with the
towncrier tool to see if I could develop the output into user content, for
example, why this incremental update benefits the user, how does fixing x
bug make the user's life easier, and so on.

To do this, I would need to collect the output of towncrier myself, or the
draft output if I wanted to prepare a post in advance of a release.

Can you advise how I would go about collecting this?
If you have any further suggestions, I would love to hear them.

Thanks,

-- 

Melanie Corr, RHCE

Community Manager

Red Hat 

Remote, Ireland

mc...@redhat.com
M: +353857774436 IM: mcorr

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Pulp 3 CLI planning

[David Davis]

A recording of the hammer vs pulp-admin presentation is available on our
youtube channel (thanks bmbouter!):

https://youtu.be/mrI7RhLr2zs

Also, it looks like we'll meet at 9am ET (1pm UTC) on Friday April 24 to
write some user stories for the Pulp 3 CLI on #pulp-meeting (freenode).

David


On Fri, Apr 17, 2020 at 10:53 AM David Davis  wrote:

> I also plan to have a brief meeting to talk about my experience as a
> Katello developer using both hammer (the Foreman CLI) and pulp-admin as a
> developer and end user. I encourage anyone interested in helping out on the
> Pulp 3 CLI to attend.
>
> The talk will be on Monday April 20th from 10:30am to 11:00am (2:30pm to
> 3:00pm UTC).
> Video conf link: https://meet.google.com/poi-qysn-itx
>
> David
>
>
> On Fri, Apr 17, 2020 at 7:06 AM David Davis  wrote:
>
>> It appears there is both interest from users and Pulp developers in
>> having a CLI for Pulp 3 so I'd like to start gathering some user stories. I
>> think the next step would be to have a meeting in #pulp-meeting on freenode
>> some time next week. The only available slots I have before noon ET would
>> be either Thursday or Friday at 9am ET (13:00 UTC). I'd propose we meet one
>> of those days and work on some user stories.
>>
>> Thoughts?
>>
>> David
>>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] MODIFIED issues

[David Davis]

During the pulpcore team meeting last week, we noted that after the latest
pulpcore release there were a number of issues in redmine still at
MODIFIED. I took an action item to go through them and they seem to fall
into four categories:

1. Issues that got filed against pulpcore but were fixed in a plugin

I think that item 1 is worth trying to fix by automation. The commit
validation could check that the issue project for the attached issue
matches the repo. I have a proof of concept here:

https://github.com/pulp/plugin_template/pull/209

2. Issues without code changes (eg tasks, epics, etc) getting set to
MODIFIED upon completion
3. Issues that got pulled/reverted before the release went out

Optimally, we'd set these to CLOSED when they are completed. I think the
release person could also check though. I'd propose we add a step to the
release guide that asks the release person to clean up any items at
MODIFIED after releasing.

4. Issues against the installer and plugin_template.

Looking for feedback on what to do with these.

David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev