[Gluster-Maintainers] Move out of bugzilla to github issues --> for everything...

[Nigel Babu]

Hello,

I have had concerns about this move for a while. Michael and I are not official
maintainers of Gluster, but implicitly, we maintain infrastructure for Gluster
and I have opinions to add from that point of view. We've already published our
[infra plans for 2017][1]. Having such a large change obviously impacts our
plans. My opposition to this plan is from the point of view of "Is it worth
it?".

* Is it worth changing practically all our scripts and workflow to move to
  GitHub? Any move will create even more work for the project in terms of work
  the infra team has to do.
* What about people who use the features of bugzilla not in Github issues? For
  example, whine. It's a very important for feature for those who want to
  triage bugs on time. Yes, we can write hacks, but that further leads to "Is
  it worth it"?
* Storage for log files and cores is a story we haven't sorted out yet. We will
  need to re-invent the wheel in terms of a hosting service for these files
  (more work).
* This is also going to create more work downstream. I bet we have scripts and
  queries written based on bugzilla. We could argue that we don't have to care
  about downstream, but if we had a [RACI][2], they'd be under "consulted" or
  at least "informed".
* Have we had conversations with projects of Ansible who do use Github for
  their pain points? I'm curious to see if we have any learnings. Michael has
  mentioned that the Github bot that Ansible folks use runs into Github's API
  limits. I'm reasonably sure we'd run into the same problem.
* The document discusses security bugs going into bugzilla. How do we make it
  less confusing for someone filing a bug. What about a bug file which later is
  found to be a security bug? How do we address that?
* If our goal is to make things simpler, we're actually moving in the opposite
  direction. Issues can be disabled or enabled. Pull requests cannot. It's not
  often that a project uses Github issues for bug tracking and does not use
  pull requests. That is confusing to *me*.

These is not a conclusive list, but this much already has me convinced that the
move is **NOT** worth it. In fact, it will cause enough fires to keep us busy
for 3 to 4 months needlessly. We have enough pieces to work on without adding
new fires.

[1]: http://lists.gluster.org/pipermail/gluster-infra/2017-February/003194.html
[2]: https://en.wikipedia.org/wiki/Responsibility_assignment_matrix

--
nigelb

On Wed, Feb 08, 2017 at 02:04:07PM -0500, Shyam wrote:
> Hi,
>
> In today's maintainers meeting I wanted to introduce what it would take us
> to move away from bugzilla to github. The details are in [1].
>
> Further to this, below is a mail detailing the plan(s) and attention needed
> to make this happen. Further I am setting up a maintainer meet on Friday
> 10th Feb, 2017, to discuss this plan and also discuss,
> - Focus areas: ownership and responsibility
> - Backlog population into github
>
> Request that maintainers attend this, as without a quorum we *cannot* make
> this move. If you are unable to attend, the please let us know any feedback
> on these plans that we need to consider.
>
> Calendar and plans for moving away from bugzilla to gihub:
> 1) Arrive maintainer consensus on the move
>   - 15th Feb, 2017
>   - This would require understanding [1] and figuring out if all
> requirements are considered
>   - We will be discussing [1] in detail on the coming Friday.
>
> 2) Announce plans to the larger development and user community for consensus
>   - Close consensus by 22nd Feb, 2017
>
> 3) (request and) Work with Infra folks for worker ant like integration to
> github instead of bugzilla
>   - Date TBD (done in parallel from the beginning)
>
> <<Assuming we are able to get (3) done by 24th Feb>>
>
> 4) Announce migration plans to larger community, calling out a 2 week
> window, after which bugzilla will be closed (available for historical
> reasons), and gerrit will also not accept bug IDs for changes
>   - 27th Feb, 2017
>
> 5) Close bugzilla and update gerrit as needed
>   - 10th Feb, 2017 weekend
>
> 6) Go live on the weekend specified in (5)
>
> Shyam
> [1] http://bit.ly/2kIoFJf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20170220/8a6ff931/attachment.sig>