How are we going to track possible contributions from the community?
Those won't have any bugzilla associated in general. And we want them
and we want to lower the hurdle for other people to contribute.
Especially for the side projects we have (the engine is quite a beast,
but we have smaller or new projects where it is not that hard to
contribute).

Projects using GitHub track everything using pull requests. Those
generally serve as the umbrella for all the associated changes and
issues. We do not have anything like that. Bugzilla maps to issues and
Gerrit changes map to the code part of pull requests. We do not have
the documentation and design in the sources either so we can't check
for those to be provided together with the patch.

--
Martin Sivakl
oVirt / SLA

On Wed, Feb 22, 2017 at 3:43 PM, Yaniv Dary <ydary@redhat.com> wrote:
> As long as a RFE is created at some point for tracking the testing and docs
> I don't mind letting them in.
> If no RFE is created it will get lost and no one will probably use the
> feature, which will be a waste of time for the developer working on that.
> Feature page can probably be a good option to automate a required url, since
> this is also a good option to provide details on the work being done.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
>         8272306
> Email: ydary@redhat.com
> IRC : ydary
>
>
> On Tue, Feb 21, 2017 at 1:01 PM, Sandro Bonazzola <sbonazzo@redhat.com>
> wrote:
>>
>>
>>
>> On Tue, Feb 21, 2017 at 11:56 AM, Michal Skrivanek
>> <michal.skrivanek@redhat.com> wrote:
>>>
>>>
>>> On 21 Feb 2017, at 09:36, Eyal Edri <eedri@redhat.com> wrote:
>>>
>>>
>>>
>>> On Tue, Feb 21, 2017 at 10:34 AM, Sandro Bonazzola <sbonazzo@redhat.com>
>>> wrote:
>>>>
>>>>
>>>>
>>>> On Tue, Feb 21, 2017 at 9:31 AM, Eyal Edri <eedri@redhat.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Feb 21, 2017 at 10:20 AM, Sandro Bonazzola
>>>>> <sbonazzo@redhat.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>> I'm facing a new challenge today, I see new features getting pushed to
>>>>>> oVirt gerrit intentionally out of bugzilla.
>>>>>> The specific case is not really relevant, but just for reference:
>>>>>> https://gerrit.ovirt.org/#/c/65761/ .
>>>>>> Looks like we'll see features getting merged without any RFE opened in
>>>>>> bugzilla for them.
>>>
>>>
>>> this is a common case for master, many patches do not have Bug-Url
>>> including features initially
>>>
>>>>>> With current workflow, auto-generating release notes from bugzilla
>>>>>> doc-texts. this means they won't ever be documented.
>>>
>>>
>>> true. Typically they don’t have to be as for user consumable features
>>> there is typically many patches, and eventually the final part of feature do
>>> have proper tracking, RFE and so on.
>>>
>>>>>>
>>>>>> I'd like to open this public discussion getting comments about how
>>>>>> things will be handled.
>>>>>
>>>>>
>>>>> We can start enforcing bug-url in master branch as well, maybe under
>>>>> certain conditions.
>>>
>>>
>>> I do not see the current practice as problematic
>>>
>>>>
>>>> The issue here is that the decision is to not use bugzilla and use
>>>> something different like trello.
>>>> So enforcing bug-url will collide with the decision from the feature
>>>> owner team.
>>>
>>>
>>> If there is an official decision ( I havn't heard on such ) to move to
>>> another issue tracker for some of the projects then it needs to be planned,
>>>
>>>
>>> Some of the projects decided not to use bugzilla. It’s a project
>>> decision, not an “official” decision affecting other projects.
>>> In this case the reason is that a supposed feature triggered a code
>>> change in a side project using bugzilla.
>>
>>
>> Fair enough for me.
>>
>>
>>>
>>> I would say in that case it either deserves a bugzilla on that side
>>> project, or we decide it’s not important, not a substantial part of the
>>> whole feature, and therefore doesn’t need to be documented/tracked in that
>>> side project and use Bug-Url-less commit to master.
>>>
>>> and maybe consider adding tools/verification for the new tools.
>>>
>>>
>>> But it doesn't make sense to start supporting more than one issue
>>> tracker, we have too many systems already, so if we move, then all projects
>>> needs to move.
>>>
>>>
>>> github issue is fairly common so if we want to support something else in
>>> addition to bugzilla Bug-Url this would be a good candidate
>>>
>>> Thanks,
>>> michal
>>>
>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> --
>>>>>> Sandro Bonazzola
>>>>>> Better technology. Faster innovation. Powered by community
>>>>>> collaboration.
>>>>>> See how it works at redhat.com
>>>>>>
>>>>>> _______________________________________________
>>>>>> Devel mailing list
>>>>>> Devel@ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Eyal Edri
>>>>> Associate Manager
>>>>> RHV DevOps
>>>>> EMEA ENG Virtualization R&D
>>>>> Red Hat Israel
>>>>>
>>>>> phone: +972-9-7692018
>>>>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sandro Bonazzola
>>>> Better technology. Faster innovation. Powered by community
>>>> collaboration.
>>>> See how it works at redhat.com
>>>
>>>
>>>
>>>
>>> --
>>> Eyal Edri
>>> Associate Manager
>>> RHV DevOps
>>> EMEA ENG Virtualization R&D
>>> Red Hat Israel
>>>
>>> phone: +972-9-7692018
>>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>> _______________________________________________
>>> Devel mailing list
>>> Devel@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>>
>>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>> _______________________________________________
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
> _______________________________________________
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel