Changes/fedora-change-wrangler

Fedora-Change-Wrangler

The Motivation for this proposal is to propose using Taiga for the Change processing.Previously using Pagure was proposed for the Same.The new Change Processing workflow aims to simplify the process to improve visibility and ease of management.

Summary

The current process allows contributors to propose changes in upcoming Fedora releases. However, the management of those feature proposals is cumbersome and requires several manual steps. This introduces more opportunity for error and reduces the time available to the Change Wrangler for more valuable contributions to Fedora. In particular, the current process includes artifacts and discussion in the Fedora Wiki, on mailing lists, FESCo tickets, Bugzilla tickets, and Docs tickets.

The current process is cumbersome with several manual steps,this introduces more opportunity for error and reduces the time available for the Change Wrangler. A Cli Tool Written in Python that interacts with Taiga,Pagure and Bugzilla.Functionality includes Promoting,announcing,submitting,accepting and updating the changes across the three platforms and over mailing list.

The new process will consolidate much of the information in Taiga.Proposed Changes will be submitted as an issue in Taiga. The description of the Issue will include the content with few exceptions:

• System-Wide or Self-Contained change will be indicated by a binary in the issue metadata
• Fedora release will be indicated by a milestone in the issue metadata
• Change status will be indicated by a list selection in the issue metadata

Owner

• Name: Manas Mangaonkar
• Email: manasmangaonkar@gmail.com || pac23@fedoraproject.org
• Name: Ben Cotton
• Email: bcotton@redhat.com

Current status

• Targeted release: Fedora 32
• Last updated: 2019-05-16
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

As Part of GSoC 2019 the fedora-change-wrangler tool will be developed to smooth out the workflow,reduce Manual Work involved for both the Contributors and the Change-Wrangler(FPgm). The tool makes it easy by covering all the functionality required for the process of moving forward proposals.

The tool will be developed using Python 3.6+ and will interact with Taiga/Pagure/Bugzilla via their API and the Mailing List via SMTP. The General Workflow would be : 1. Change Owner opens an issue and fills in the fields. When they are ready to submit the Change proposal, they set the status to "Ready for Wrangler". 2. The Change Wrangler (FPgM) reviews the proposal. If it is incomplete, they set the status back to "New" and inform the Change Owner of what's needed. If it is ready to process, then...

Functionality covered 1. Promote

• The issue will be promoted to a user story in taiga,copies the contents of the custom fields from the issue to the user story. Closes the issue.

2. Announce

• The tool would have the functionality to enable announcing the change proposal to devel and devel-announce lists using smtp. It will also automatically change the story status to announced.

3. fesco-submit

• Allowing creation of a new issue in the FESco Pagure repo directly from the command line.

4. Accept

• Once the changes are accepted the change-wrangler can create a tracking bug in Bugzilla along with release notes on Pagure.THe status of the user story is updated to accepted aswell.

5. Update

• Status can be changed to testable if BZ is "Modified" and to Complete is BZ is "ON_QA"

6. Creation of Report

• The user can create a report to provide quick view of changes and their status. It can be in wiki or Html form.

Techstack:

• Python3.6+
• SMTP
• Taiga/Pagure/Bugzilla API's
• Nano/Gedit/Vi ( Inbuilt support to edit text)
• Kerberos(For authentication)

The current sample arg created looks like this [ change-tool convert --taiga <issue no> <issue no> ] . The advantage of this the Manager would be able to specify unlimited no of issues to change at once in a single command using the issue no in taiga to convert to user story.

Benefit to Fedora

Will Make change process easy for everyone involved.

Scope

• Proposal owners:

I will be working with the Change-Wrangler(Ben Cotton) throughout the summer to create this tool from scratch.

• Other developers: N/A (not a System Wide Change)

• Release engineering: #Releng issue number (no release engineering impact is expected)

• Policies and guidelines: N/A (not a System Wide Change)

• Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

Other than the regular updation of the change-wrangler package nothing else will be required.

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

No visible Impact is expected.

Dependencies

No other packages depend on this.

N/A (not a System Wide Change)

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No
• Blocks product? product

Enough buffer time has been allocated to complete this during the GSoC period.

Documentation

Detailed documentation will be done once the coding part of the tool is done.Documentation has been scheduled for july 25th and after.

N/A (not a System Wide Change)