[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Documentation
- To: openldap-technical@openldap.org
- Subject: Re: Documentation
- From: Radovan Semancik <radovan.semancik@evolveum.com>
- Date: Mon, 2 May 2016 10:37:16 +0200
- Dkim-filter: OpenDKIM Filter v2.9.0 hermes.evolveum.com 0AE20365A0E
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evolveum.com; s=46F1F96C-8266-11E5-BB5D-6C9186186C84; t=1462178422; bh=anHyIOQmKxWLfLB4Lnb9tTJePXhBnQlIE9Ezv7KJ2Pg=; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; b=XJPtYBB3F+C8gnJtt8qhofr3jOKTIuzipgW3peHPAQhAdG3vxl4qFIeTU4aIfqOn/ uQjpyT92IxhrRlrZSMHPitl7LgsIUW2v0NydrEqYvai4Zl4TRW+3ezYW0xf8yJMDbN 0UUnl+RjSEnMhPUKlXKWGmIb4l2GZMAO7WbS7nvw=
- In-reply-to: <572501C2.8050202@symas.com>
- References: <CAPcb_GLyBceNA79Ji5jgsKcG+MojH6uw-9HJ1xfaRVeJEkj_4Q@mail.gmail.com> <CAPcb_GKQ+Mw6V=SDTyZ01t8JjZq_i_A6H5Pi+Hnh6JqZcwZurw@mail.gmail.com> <CAPcb_GLpEwo79qDz5QzNmuzu7SiL5v5d-fki=fcqeegwpp95XQ@mail.gmail.com> <CAPcb_G+Tx7C-k6e7=1e9nkw1qeU=8Je8+cCFvt+xdSOGdEveXA@mail.gmail.com> <CAKU=tE_9PseaxRL4innZ6o=mERGmQVr5JGjAkWnv20cJ72RovA@mail.gmail.com> <CAKU=tE8vtVwE-mzQcc5D0VK4Znr9f+GM9RTV4oYQbBs7wgpyeg@mail.gmail.com> <CAKU=tE-ntod9APeM_-gn_5tNqx=oAzf4Kqq1HHsBXgxtw7m9pg@mail.gmail.com> <CAKU=tE_+koU7gUZf=dRGbixMoQrdtv+ECkvyZ=zE9B=-_-6xMQ@mail.gmail.com> <CAKU=tE8H1nnFeDDGS0G+v+bCWmU=CTunXpGvghbY4WUzHLzLVg@mail.gmail.com> <572501C2.8050202@symas.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
On 04/30/2016 09:04 PM, Howard Chu wrote:
The process of creating a patch with git is the same, whether we use
github or not. I don't believe that's particularly meaningful.
My thoughts exactly. Some 3-4 years ago. Then I've actually tried to run
a project on github. It siginificanly lowers the contribution barrier.
It is much easier to press "pull request" button than to bundle the
patch in command-line, send it to the mailing list (subscribe there
first), then wait for the maintainer, check all the time whether the
patch was merged, ...
Github-like approach makes a big difference. I see it in midPoint (which
I'm maintianing) and I see it in ConnId (where I'm regularly
contributing). I also see how bad it is without github for several
Apache projects that I watch closely. And I will probably never
contribute to these (unless I really have to) because the overhead is so
high.
To state that openly: I would probably never contribute to OpenLDAP
documentation if I have to bundle a patch in a mail to a mailing list.
I'm quite likely to contribute if there is a convenient "pull request"
button or if it is maintained in a wiki.
We are running the midPoint project on github for several years. But I'm
not afraid. I can still check all the code changes in any git tool I
like. As a maintainer you do not need to rely on github. And if github
would disappear at this very moment we will be running on a different
site before the day is over. With no loss in the source code history.
This is git, the migration is really trivial. So I believe that the
benefits greatly outweigh the risks.
If you do not like github go for gitlab. You can even host that yourself.
--
Radovan Semancik
Software Architect
evolveum.com