Hi Victoria, Personally I think a community GitHub repo would be the most effective way. The mailing list is great, and very helpful, but personally I don't think it's the ideal place for code because a) people join and leave, and won't know about a given topic unless they search list archives and b) it's not immediately functional the way a Git can be
A community Wiki would work, too, but it's got the same functionality drawback that the mailing list does. A workflow I think could work would be if people fork the kea-contrib Wiki and then submit PRs against the master branch, which would establish an effective guard against spam and abuse, and also offer people a very quick and easy way to get access to community-contributed code by cloning the repo locally and just updating it periodically. my $0.02, Klaus On Thu, Jun 7, 2018 at 4:35 PM, Victoria Risk <vi...@isc.org> wrote: > > Francis, I was thinking that it would be cool to put stuff like this in a > knowledge base or something on the wiki to pull together how to do things > like this. Alternately we could have a GIT repo of contributed > configuration examples that have been validated by users who know what they > are doing. :) Obviously this would need to be treated like any other open > source project, but would be really cool way to share example configs to > increase adoption velocity. Something to consider... Perhaps this is > something Victoria would be interested in looking at? > > Thanks, > Jason > > > Hi Jason, > > We are indeed trying to figure out the best way to support this. Our > current Knowledge base (kb.isc.org) is self-hosted, using some software > that I think was last updated in 2013. We are worried about the lack of > software maintenance. We also turned off the ability for readers to add > comments several years ago, because people were posting technical questions > (and spam) and we didn’t have time to curate it. > > We are looking at several options for where to move the existing content, > and create new content. We haven’t figured it out yet. One option is a web > forum (we have one set up, but haven’t launched it yet at forum.isc.org), > another idea is to use the Kea github repo for contributions. > > Although a forum is easiest for this kind of thing, it is also somewhat > competitive with the mailing list. We are not sure we have time to read > both, and we figure many of you don’t either. We do have a separate > Kea-contrib github repo (https://github.com/isc-projects/kea-contrib), > and maybe people could post configurations there, adding a link to the > configuration file and a description on the main README page for each > configuration? > > What do you all think? What’s the best way to share sample configurations > that work? > > Vicky > > > > > _______________________________________________ > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users > >
_______________________________________________ Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
