metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Re: [DISCUSS] Lowering the barrier to entry to for new users
Date Wed, 20 Dec 2017 10:49:00 GMT
I agree we should streamline #2 and lower the bar, and we can readdress if
we are getting PRs that don't follow the contributing guidelines.  We
should also make a as not everybody knows about the wiki.

For #3, I think the scripts that Nick, Otto, and others have written for
looking at PRs, testing RCs, etc. should get moved in and referenced more
frequently to users.  I believe progress on this has already started, but
we should continue to contribute little utils that simplify baseline tasks.

Finally, I think the migration of docs from wiki to git, and hosted in the
site-book is very important.  I know this was on my list to do and I will
still happily do it when I can get to it, but it may unfortunately be a
while.  Happy to take volunteers or crowd source this a bit.


On Tue, Dec 19, 2017, 11:56 Laurens Vets <> wrote:

> On 2017-12-19 06:19, Justin Leet wrote:
> > One of the topics that came up in recent community meeting was about
> > lowering the barrier to entry for new users.
> >
> > This is a fairly broad topic that I think covers a few different
> > subtopics.
> >
> > 1) Addressing (or making it easier to address) some of the things we've
> > seen on the user group from people getting started.
> > 2) Making contributing easier and the ways to do so more obvious.  This
> > includes things like making it easier to find on our site (compare our
> > page
> > to Storm's, for example).  It also includes things like reassessing our
> > PR
> > template (For example, is everything still useful enough to keep it?).
> > 3) Anything else that would make help users adopt Metron and become
> > actively involved in reviewing, fixes, docs, and all the other sorts of
> > things that make our stuff better.
> >
> > I'm mostly going to open this up to a general discussion and
> > brainstorming,
> > and presumably we come out with some tickets at the end of this.
> I use a github gist that Otto once created for me, maybe I can try and
> turn that into something more official?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message