[OOTB-hive] OOTB contribution issues

[martin at bettercode.com]

> INFRA amongst other things depends on ADDONS and DISTRO (which I think
> is also meant to bundle the former?).
>

I would say that the dependency is the other way round, i.e. ADDONS and
DISTRO depend on INFRA (i.e. somewhere to host the things)

DISTRO is not meant to bundle ADDONS. ADDONS is supposed to be a
collection of addons whose reliability and usability have been
determined to be sufficient. DISTRO is to be a collection of addons
which make CE, in an aggregate that we call 'Honeycomb', more useful and
potentially more reliable and secure if we include "patches" too.
Personally I could envisage a number of different DISTROs for different
purposes, for example I always consider the small business case as well
as certain vertical markets.

I think though that it is very telling that the only addon we can all
agree should be in Honeycomb is the Javascript console - this is not an
addon that is targetted at the end user or end user market! I think we
should probably have a bit more focus on who we are creating these
things for, because I don't think it's developers like ourselves (even
if we all do install JS console as the first action on a new
deployment!)
 
> I'd say very few due to the small workforce. Personally I'd prefer a
> jar-drop-in implementation for simplicities sake.
>

I've never been keen on amps either, but apparently there is some great
advantage to them that I have just never seen for myself.
 
> As for Slack: I think it is awesome and it works great for other Open
> Source projects. There are workarounds for "issues" like
> Google-indexing. Still I'd suggest to keep this can of worms closed
> until the real issues are resolved.

If you can write a bot then yes you can do anything, but then you need
to maintain the bot, defend against potential API retirement etc.


Martin