John Casey wrote on 10/8/18 1:33 PM:
> Hi all,
>
> I've been working on a project for 4-5 years now which I think would make a
> good Apache project, at least in terms of it being valuable, high-quality
> software. We're using it internally for our production systems at work, but
> the code is
www.google.com
Xavier.Galindo1972
On Oct 11, 2018 04:53, "Bertrand Delacretaz" wrote:
Hi,
On Wed, Oct 10, 2018 at 6:00 PM Ed Cable wrote:
> ...One possible option is just to consolidate the lists into dev but I
don't
> think that is good long-term because as community grows we will have
> di
Hi,
On Wed, Oct 10, 2018 at 6:00 PM Ed Cable wrote:
> ...One possible option is just to consolidate the lists into dev but I don't
> think that is good long-term because as community grows we will have
> distinct technical vs. functional/design conversations happening...
Until that happens it's
Responses inline.
Thanks,
-j
On Tue, Oct 9, 2018, at 3:13 AM, Justin Mclean wrote:
> Hi,
>
> > I've been working on a project for 4-5 years now which I think would make a
> > good Apache project, at least in terms of it being valuable, high-quality
> > software. We're using it internally for o
Thanks Kevin,
I'd definitely say that Indy falls short of a truly welcoming project for new
contributors, but that's mainly for the common failings of letting our user
documentation fall out of date and failing to operate the entire development
process out in the open. Initially we did pursue t
