Agreed. Some of the project management stuff and bylaws fit there, but let's 
get the misleading docs off and push the architecture and deployment stuff into 
the source base via site-book. That way we might just keep it consistent with 
versions.

Simon 

> On 19 Jun 2017, at 07:11, Casey Stella <ceste...@gmail.com> wrote:
> 
> +1 to moving away from the wiki.  I really don't like it.
> 
>> On Mon, Jun 19, 2017 at 10:00 AM, Justin Leet <justinjl...@gmail.com> wrote:
>> 
>> I'm mostly +1 for moving away from the wiki, and keeping things lined up
>> with source. I do think it has a place though as a spot to put some Apache
>> type stuff, and maybe link recordings of talks or meetups and such.
>> 
>> On Jun 13, 2017 4:15 PM, "Nick Allen" <n...@nickallen.org> wrote:
>> 
>> +1 for migrating away from the Wiki. I am not a fan.  It is too difficult
>> to keep in-sync with the source code.  It also doesn't get the loving care
>> and review that a PR does in our community.
>> 
>> On Tue, Jun 13, 2017 at 2:27 PM, zeo...@gmail.com <zeo...@gmail.com>
>> wrote:
>> 
>>> I suggested in the past and got some buy in, but never had time to move
>>> everything into GitHub.  I vote to mostly or entirely archive the wiki.
>>> 
>>> Jon
>>> 
>>>> On Tue, Jun 13, 2017, 5:19 PM Laurens Vets <laur...@daemon.be> wrote:
>>>> 
>>>>> On 2017-06-13 14:09, Otto Fowler wrote:
>>>>> I think there are things in the wiki that are very very out of date,
>> to
>>>>> the
>>>>> extent that they are confusing people looking at Metron.
>>>>> Basically anyone going to DOCS HOME from the site is being thrown
>> into
>>>>> documentation that is sure to confuse them.
>>>>> 
>>>>> Does anyone have any ideas how we can address this?   Can we prune
>> the
>>>>> wiki
>>>>> and remove the out of date information ( better less than wrong )?
>>>>> Should
>>>>> we replace DOCS HOME with the site book link?
>>>> 
>>>> Throw out the old/wrong stuff asap.
>>>> 
>>>> I also wouldn't mind trying to get some structure in it but is the wiki
>>>> still necessary if everything will be in markdown in the source
>>>> eventually?
>>>> 
>>> --
>>> 
>>> Jon
>>> 
>> 

Reply via email to