Hi, Ben,
On Fri, Aug 24, 2018 at 3:48 PM Ben Cotton wrote:
> > Changes as Markdown files
>
> This does address the history, but it loses the metadata aspect that
> makes the current process clunky. Being able to script against the
> metadata fields eliminates trying to parse the wiki text and
On Fri, Aug 24, 2018 at 6:39 AM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> On Thu, Aug 23, 2018 at 11:52:57PM +0200, Miro Hrončok wrote:
> > On 23.8.2018 22:43, Ben Cotton wrote:
> > >Hi community,
> > >
> > >We've traditionally used the wiki for Change proposals because it's
> >
I would definitely love that!
Having the ability to list all changes at a single place, comment, and even
organise them by tags seems like a way forward.
BTW I know that Pagure stores issues in git, so that could solve the
history problem, although I don't know how exactly is that implemented.
Thanks for the feedback so far. Some of the responses are fairly
similar, so I'll try to clump them together:
> Vote in the Change ticket or a FESCo ticket?
The intent, for now, is to still have FESCo vote in a separate ticket,
mostly for their visibility. Alternatively, I could tag all FESCo
On Fri, Aug 24, 2018 at 12:16:09PM +0200, Fabio Valentini wrote:
> On Fri, Aug 24, 2018, 11:38 David Sommerseth wrote:
>
> > On 23/08/18 22:43, Ben Cotton wrote:
> > > Hi community,
> > >
> > > We've traditionally used the wiki for Change proposals because it's
> > > the tool we had. But, it's
On Thu, Aug 23, 2018 at 11:52:57PM +0200, Miro Hrončok wrote:
> On 23.8.2018 22:43, Ben Cotton wrote:
> >Hi community,
> >
> >We've traditionally used the wiki for Change proposals because it's
> >the tool we had. But, it's not necessarily well-suited to the purpose.
> >But now we have Pagure,
On Fri, Aug 24, 2018, 11:38 David Sommerseth wrote:
> On 23/08/18 22:43, Ben Cotton wrote:
> > Hi community,
> >
> > We've traditionally used the wiki for Change proposals because it's
> > the tool we had. But, it's not necessarily well-suited to the purpose.
> > But now we have Pagure, which
On 23/08/18 22:43, Ben Cotton wrote:
> Hi community,
>
> We've traditionally used the wiki for Change proposals because it's
> the tool we had. But, it's not necessarily well-suited to the purpose.
> But now we have Pagure, which can help address some of the
> shortcomings of using the wiki: poor
Sounds like a great idea to me. I'm in favor...
kevin
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
Could you please show us example of such change proposal? I somehow
cannot imagine the real benefit.
V.
Dne 23.8.2018 v 22:43 Ben Cotton napsal(a):
> Hi community,
>
> We've traditionally used the wiki for Change proposals because it's
> the tool we had. But, it's not necessarily well-suited
On 23.8.2018 22:43, Ben Cotton wrote:
Hi community,
We've traditionally used the wiki for Change proposals because it's
the tool we had. But, it's not necessarily well-suited to the purpose.
But now we have Pagure, which can help address some of the
shortcomings of using the wiki: poor
11 matches
Mail list logo