Re: Git forge requirements discussion

2020-02-13 Thread Kamil Paral
On Wed, Feb 12, 2020 at 10:35 AM Kamil Paral wrote: > On Tue, Feb 11, 2020 at 10:42 PM Ben Cotton wrote: > >> On Tue, Feb 11, 2020 at 4:37 PM Matthew Miller >> wrote: >> > >> > Can you put the voting/polls idea in the form of a user story? >> > >> I think #44 on the list I sent covers that: >>

Re: Git forge requirements discussion

2020-02-12 Thread Kamil Paral
On Tue, Feb 11, 2020 at 10:42 PM Ben Cotton wrote: > On Tue, Feb 11, 2020 at 4:37 PM Matthew Miller > wrote: > > > > Can you put the voting/polls idea in the form of a user story? > > > I think #44 on the list I sent covers that: > As a Fedora team member, I can vote +1/abstain/-1 on issues so

Re: Git forge requirements discussion

2020-02-11 Thread Matthew Miller
On Thu, Jan 23, 2020 at 04:02:42PM +0100, Kamil Paral wrote: > I don't think we have some very special requirements. For the planned > blocker review async discussion, we need API to be able to add comments and > edit the ticket description, ideally also adjust ticket tags, milestones or > some

Re: Git forge requirements discussion

2020-01-23 Thread Kamil Paral
On Wed, Jan 22, 2020 at 10:00 AM Adam Williamson wrote: > Hey folks! > > There's a post on the Community Blog: > > https://communityblog.fedoraproject.org/git-forge-requirements > > and a thread on devel@: > > >