Yeah I think I misinterpreted how this feature works. I thought its
just a discussion per project. This is per team I guess, as you
pointed out.
Ok I am migrating back to wiki unless there is some blocker raised.
LZ
On Wed, Nov 29, 2017 at 11:37 AM, Greg Sutcliffe
On 29/11/17 08:47, Daniel Lobato Garcia wrote:
> If it helps, I think
> https://github.com/blog/2471-introducing-team-discussions looks also
> like a good tool for these kind of discussions, without any need for
> a moderator. The discussions are restricted to people in the GitHub
> team.
TLDR:
Yeah, I also think this would make sense. It's basically a wiki with
discussion - ideal.
Greg, can you turn it on in RFC repo so we can test this? If this
fails, we can move to wiki and deprecate that repo.
--
LZ
Lukas @lzap Zapletal
--
You received this message because you are subscribed
On 11/15, Tomer Brisker wrote:
> Since I already suggested this some months ago, obvious +1 from me :)
>
> On Wed, Nov 15, 2017 at 1:41 PM, Greg Sutcliffe
> wrote:
> > +1 to moving them to the Redmine wiki. The RFC repo was a good
> > experiment but handled badly (at
+1 to moving them to the Redmine wiki. The RFC repo was a good
experiment but handled badly (at least some of the blame for that is on
me). At this point I don't think it's possible to rescue it.
On 15/11/17 10:52, Sean O'Keeffe wrote:
> Without wanting to hijack this thread... I think this is
Yea +1 from me too. I think the biggest problem was that merging them has
no direct link to the issue or PRs that resolved a RFC, this meant the
author or someone had to remember to go back, ping someone to merge which
often didn't happen. Whereas with a mailing list its okay to leave a thread
Hey,
this is another proposal to deprecate Github RFC repo and move the
content to our wiki. Reasons:
A) There is zero merged proposals for the past year (Jan-Nov 2017):
https://github.com/theforeman/rfcs/commits/master
B) Activity is very low (comments in 3 PRs last winter, 3 PRs last
summer,