Hi all,
Sorry it's taken me awhile to respond, but this past couple of weeks has served
as a good reminder that those of us working on Indy probably don't have the
time to devote to building a real community yet. As Shane pointed out, we
haven't really even exercised the features available on
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
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
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 our production systems at work, but
> the code is open (hosted on GitHub). Our process to date
Hi John, our VP is on route to China at the moment but I would say this is
not a strength of many developers but the concept of community over code is
an important one that we would support you in building.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache
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 open (hosted on GitHub). Our process to date has
