drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Guzenko <ihor.huzenko....@gmail.com>
Subject Re: [DISCUSS]: Thoughts
Date Thu, 30 Jan 2020 15:00:13 GMT
Hello Charles,

Thank you very much for starting this important discussion. These are all
important things but at the current moment, I don't have a clear vision
where we could start from. The item which is most interesting to me is the
second one, but I've never been involved in building an open-source
community, don't even know where to start. I'm not sure that just making
good documentation and the first impression will attract developers with
strong motivation to contribute.  So I'm very excited to learn about
projects which managed to build such a community, maybe we really could
find some new fresh ideas about how to attract new community members.


On Thu, Jan 30, 2020 at 4:18 PM Charles Givre <cgivre@gmail.com> wrote:

> Hello all,
> I mentioned in the Drill hangout last week that I had spoken with one of
> the original mentors for the Drill project (Isabel Drost-Fromm) and asked
> her advice about the future of Drill.  To paraphrase what she told me:
> 1.  There are two ways for open source projects to succeed.   The first
> and riskier approach is with a single corporate sponsor.  The obvious risks
> are that since the corporate sponsor is footing the bill, they will
> prioritize their own needs over and sometimes against community needs.
> (This is not unique to Drill). The slower but less risky approach is to
> build a community around a project, join forces and slowly drive it
> forward.  She pointed out that some of the Apache foundation's longest
> running projects were run in this way.
> 2.  We should focus our efforts on community building:  She suggested a
> lot of what she described as "would be obvious in retrospect" such as
> making sure the documentation is really solid, and having a user experience
> in the beginning.  She said we should use the resources of the Apache
> foundation to help publicize new releases etc.  Also we should make it easy
> to become a committer.   IMHO, I would add that we really should seek out
> additional code reviewers as we don't have enough and PRs take a long time
> to get approved.
> 3.  Do a lot of what a vendor would do:  Update the website and
> documentation to reflect things like: who is using Drill, who is offering
> professional support for Drill etc.
> 4.  Define a mission:  We should work to define a mission for Drill?  IE
> Why does/should it exist and what business problem does it solve?  IMHO it
> solves a very large one, but more people need to know about it.  That's why
> I'm not giving up on it yet.
> @Isabel, I hope I captured the essence of what you were telling me here.
> Thanks everyone,
> --C

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