Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

On Sun, Oct 30, 2016 at 7:00 PM, Ran Ziv  wrote:

> Thanks Suneel.
> Actually I believe it was the wrong Tal, so I removed his permissions.
>
> Unless I'm missing something, everyone needs to register to confluence
> separately from jira / apache-id etc., here
> .
>

Correct. All need to register separately on Confluence (and its separate
from Jira).

>
> Guys please send your ID once you do that so we could grant you permissions
>
> On Sun, Oct 30, 2016 at 6:07 PM, Suneel Marthi 
> wrote:
>
> > Done - added Tal, John D. Jakob. Ran <- all these users have admin
> > privs, please feel free to add others.
> >
> > On Sun, Oct 30, 2016 at 11:56 AM, John D. Ament 
> > wrote:
> >
> > > Could you add me as well?
> > >
> > > On Sun, Oct 30, 2016 at 11:50 AM Suneel Marthi <
> suneel.mar...@gmail.com>
> > > wrote:
> > >
> > > > Heh Sorry, Ran I added u to confluence - ur ApacheId 'ran' would be
> ur
> > > > login.
> > > >
> > > > You have permissions to add users, please feel free to add others.
> > > >
> > > > On Sun, Oct 30, 2016 at 11:40 AM, Ran Ziv 
> wrote:
> > > >
> > > > > Suneel, could you please provide me (and possibly the rest of us as
> > > well)
> > > > > permissions for creating pages on our Confluence? I don't seem to
> > have
> > > > > these permissions at the moment.
> > > > > Thank you :)
> > > > >
> > > > > On Tue, Oct 25, 2016 at 6:05 PM, Suneel Marthi  >
> > > > wrote:
> > > > >
> > > > > > On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv 
> > > wrote:
> > > > > >
> > > > > > > Done.
> > > > > > > I'll update the project's .travis file now.
> > > > > > >
> > > > > > > What is the process of setting up a Jenkins job?
> > > > > > >
> > > > > >
> > > > > > Needs an Infra ticket.
> > > > > >
> > > > > > >
> > > > > > > -
> > > > > > >
> > > > > > > Regarding shared documents, is Confluence the Apache standard?
> > What
> > > > > about
> > > > > > > using github markup files and have the documents as a part of
> the
> > > > repo?
> > > > > > > Does anyone have any specific preference or other ideas on this
> > > > matter?
> > > > > > >
> > > > > >
> > > > > > Its again up to the project. Projects like Flink, Pirk, Beam have
> > > > markup
> > > > > > files in github and use Jekyll.
> > > > > >
> > > > > > They also use Confluence for few other things.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Oct 25, 2016 at 3:11 PM, Suneel Marthi <
> > smar...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Never heard of CircleCI, and I don't think Infra is gonna
> > support
> > > > > that.
> > > > > > > >
> > > > > > > > Please go ahead and create an Infra ticket to enable Travis
> for
> > > > Aria.
> > > > > > > >
> > > > > > > > On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv  >
> > > > wrote:
> > > > > > > >
> > > > > > > > > Regarding CI - Does Apache also support CircleCI? I assume
> > less
> > > > > > > projects
> > > > > > > > > use it and if that's the case it could possibly be a better
> > > > option
> > > > > > for
> > > > > > > us
> > > > > > > > > if the purpose of using an additional CI environment
> (besides
> > > > > > jenkins)
> > > > > > > is
> > > > > > > > > to allow for quick feedback over PRs.
> > > > > > > > > If not I'll create an Infra JIRA to enable Travis for our
> > > > project.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi <
> > > > smar...@apache.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv <
> > r...@gigaspaces.com
> > > >
> > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi,
> > > > > > > > > > >
> > > > > > > > > > > I have some questions for our mentors:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > 1) CI - we've noticed some Apache projects use online
> > > > services
> > > > > > > rather
> > > > > > > > > > than
> > > > > > > > > > > the infra tools  offered by
> > > Apache.
> > > > > > We're
> > > > > > > > > > leaning
> > > > > > > > > > > towards using TravisCI, however we're somewhat worried
> > that
> > > > > since
> > > > > > > all
> > > > > > > > > > > apache projects are under a single github organization,
> > > > builds
> > > > > in
> > > > > > > > > Travis
> > > > > > > > > > > will take a very long time to start etc..
> > > > > > > > > > >
> > > > > > > > > > >  Are you aware of any such issues (or perhaps Travis
> > offers
> > > > > some
> > > > > > > > > special
> > > > > > > > > > > QoS to Apache projects or so)..?
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Most Apache projects use both Travis (unofficial) and
> > Jenkins
> > > > > > > (Official
> > > > > > > > > > Apache CI).
> > > > > > > > > >
> > > > > 

Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

Done - added Tal, John D. Jakob. Ran <- all these users have admin
privs, please feel free to add others.

On Sun, Oct 30, 2016 at 11:56 AM, John D. Ament 
wrote:

> Could you add me as well?
>
> On Sun, Oct 30, 2016 at 11:50 AM Suneel Marthi 
> wrote:
>
> > Heh Sorry, Ran I added u to confluence - ur ApacheId 'ran' would be ur
> > login.
> >
> > You have permissions to add users, please feel free to add others.
> >
> > On Sun, Oct 30, 2016 at 11:40 AM, Ran Ziv  wrote:
> >
> > > Suneel, could you please provide me (and possibly the rest of us as
> well)
> > > permissions for creating pages on our Confluence? I don't seem to have
> > > these permissions at the moment.
> > > Thank you :)
> > >
> > > On Tue, Oct 25, 2016 at 6:05 PM, Suneel Marthi 
> > wrote:
> > >
> > > > On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv 
> wrote:
> > > >
> > > > > Done.
> > > > > I'll update the project's .travis file now.
> > > > >
> > > > > What is the process of setting up a Jenkins job?
> > > > >
> > > >
> > > > Needs an Infra ticket.
> > > >
> > > > >
> > > > > -
> > > > >
> > > > > Regarding shared documents, is Confluence the Apache standard? What
> > > about
> > > > > using github markup files and have the documents as a part of the
> > repo?
> > > > > Does anyone have any specific preference or other ideas on this
> > matter?
> > > > >
> > > >
> > > > Its again up to the project. Projects like Flink, Pirk, Beam have
> > markup
> > > > files in github and use Jekyll.
> > > >
> > > > They also use Confluence for few other things.
> > > >
> > > >
> > > > >
> > > > >
> > > > > On Tue, Oct 25, 2016 at 3:11 PM, Suneel Marthi  >
> > > > wrote:
> > > > >
> > > > > > Never heard of CircleCI, and I don't think Infra is gonna support
> > > that.
> > > > > >
> > > > > > Please go ahead and create an Infra ticket to enable Travis for
> > Aria.
> > > > > >
> > > > > > On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv 
> > wrote:
> > > > > >
> > > > > > > Regarding CI - Does Apache also support CircleCI? I assume less
> > > > > projects
> > > > > > > use it and if that's the case it could possibly be a better
> > option
> > > > for
> > > > > us
> > > > > > > if the purpose of using an additional CI environment (besides
> > > > jenkins)
> > > > > is
> > > > > > > to allow for quick feedback over PRs.
> > > > > > > If not I'll create an Infra JIRA to enable Travis for our
> > project.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi <
> > smar...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv  >
> > > > wrote:
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I have some questions for our mentors:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 1) CI - we've noticed some Apache projects use online
> > services
> > > > > rather
> > > > > > > > than
> > > > > > > > > the infra tools  offered by
> Apache.
> > > > We're
> > > > > > > > leaning
> > > > > > > > > towards using TravisCI, however we're somewhat worried that
> > > since
> > > > > all
> > > > > > > > > apache projects are under a single github organization,
> > builds
> > > in
> > > > > > > Travis
> > > > > > > > > will take a very long time to start etc..
> > > > > > > > >
> > > > > > > > >  Are you aware of any such issues (or perhaps Travis offers
> > > some
> > > > > > > special
> > > > > > > > > QoS to Apache projects or so)..?
> > > > > > > > >
> > > > > > > >
> > > > > > > > Most Apache projects use both Travis (unofficial) and Jenkins
> > > > > (Official
> > > > > > > > Apache CI).
> > > > > > > >
> > > > > > > > Jenkins is the official CI for all Apache projects while u
> can
> > > also
> > > > > use
> > > > > > > > Travis to validate PRs.
> > > > > > > >
> > > > > > > > YEs, I do see that the Travis builds take forever to launch
> > > > sometimes
> > > > > > > given
> > > > > > > > the large number of Apache projects.
> > > > > > > >
> > > > > > > > For Aria, you can go wth Travis if you choose to (and we need
> > to
> > > > file
> > > > > > an
> > > > > > > > Infra ticket to enable Travis for the project), but Jenkins
> > would
> > > > be
> > > > > > the
> > > > > > > > authoritative CI - most projects now have both enabled.
> > > > > > > >
> > > > > > > >
> > > > > > > > > 2) Pull requests - we're used to reviewing code using PRs
> on
> > > > > github.
> > > > > > > > > However, since the github repo is merely a mirror, it's
> > > > impossible
> > > > > to
> > > > > > > > merge
> > > > > > > > > PRs directly on github, which means we have to rebase the
> PR
> > > into
> > > > > the
> > > > > > > > > master branch and close the PR manually.
> > > > > > > > >
> > > > > > > >
> > > > > > > > Pull Requests for Apache github projects work a 

Re: Questions regarding CI, PR and documentation

[John D. Ament]

Could you add me as well?

On Sun, Oct 30, 2016 at 11:50 AM Suneel Marthi 
wrote:

> Heh Sorry, Ran I added u to confluence - ur ApacheId 'ran' would be ur
> login.
>
> You have permissions to add users, please feel free to add others.
>
> On Sun, Oct 30, 2016 at 11:40 AM, Ran Ziv  wrote:
>
> > Suneel, could you please provide me (and possibly the rest of us as well)
> > permissions for creating pages on our Confluence? I don't seem to have
> > these permissions at the moment.
> > Thank you :)
> >
> > On Tue, Oct 25, 2016 at 6:05 PM, Suneel Marthi 
> wrote:
> >
> > > On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv  wrote:
> > >
> > > > Done.
> > > > I'll update the project's .travis file now.
> > > >
> > > > What is the process of setting up a Jenkins job?
> > > >
> > >
> > > Needs an Infra ticket.
> > >
> > > >
> > > > -
> > > >
> > > > Regarding shared documents, is Confluence the Apache standard? What
> > about
> > > > using github markup files and have the documents as a part of the
> repo?
> > > > Does anyone have any specific preference or other ideas on this
> matter?
> > > >
> > >
> > > Its again up to the project. Projects like Flink, Pirk, Beam have
> markup
> > > files in github and use Jekyll.
> > >
> > > They also use Confluence for few other things.
> > >
> > >
> > > >
> > > >
> > > > On Tue, Oct 25, 2016 at 3:11 PM, Suneel Marthi 
> > > wrote:
> > > >
> > > > > Never heard of CircleCI, and I don't think Infra is gonna support
> > that.
> > > > >
> > > > > Please go ahead and create an Infra ticket to enable Travis for
> Aria.
> > > > >
> > > > > On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv 
> wrote:
> > > > >
> > > > > > Regarding CI - Does Apache also support CircleCI? I assume less
> > > > projects
> > > > > > use it and if that's the case it could possibly be a better
> option
> > > for
> > > > us
> > > > > > if the purpose of using an additional CI environment (besides
> > > jenkins)
> > > > is
> > > > > > to allow for quick feedback over PRs.
> > > > > > If not I'll create an Infra JIRA to enable Travis for our
> project.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi <
> smar...@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv 
> > > wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I have some questions for our mentors:
> > > > > > > >
> > > > > > > >
> > > > > > > > 1) CI - we've noticed some Apache projects use online
> services
> > > > rather
> > > > > > > than
> > > > > > > > the infra tools  offered by Apache.
> > > We're
> > > > > > > leaning
> > > > > > > > towards using TravisCI, however we're somewhat worried that
> > since
> > > > all
> > > > > > > > apache projects are under a single github organization,
> builds
> > in
> > > > > > Travis
> > > > > > > > will take a very long time to start etc..
> > > > > > > >
> > > > > > > >  Are you aware of any such issues (or perhaps Travis offers
> > some
> > > > > > special
> > > > > > > > QoS to Apache projects or so)..?
> > > > > > > >
> > > > > > >
> > > > > > > Most Apache projects use both Travis (unofficial) and Jenkins
> > > > (Official
> > > > > > > Apache CI).
> > > > > > >
> > > > > > > Jenkins is the official CI for all Apache projects while u can
> > also
> > > > use
> > > > > > > Travis to validate PRs.
> > > > > > >
> > > > > > > YEs, I do see that the Travis builds take forever to launch
> > > sometimes
> > > > > > given
> > > > > > > the large number of Apache projects.
> > > > > > >
> > > > > > > For Aria, you can go wth Travis if you choose to (and we need
> to
> > > file
> > > > > an
> > > > > > > Infra ticket to enable Travis for the project), but Jenkins
> would
> > > be
> > > > > the
> > > > > > > authoritative CI - most projects now have both enabled.
> > > > > > >
> > > > > > >
> > > > > > > > 2) Pull requests - we're used to reviewing code using PRs on
> > > > github.
> > > > > > > > However, since the github repo is merely a mirror, it's
> > > impossible
> > > > to
> > > > > > > merge
> > > > > > > > PRs directly on github, which means we have to rebase the PR
> > into
> > > > the
> > > > > > > > master branch and close the PR manually.
> > > > > > > >
> > > > > > >
> > > > > > > Pull Requests for Apache github projects work a little
> different
> > > > unlike
> > > > > > the
> > > > > > > regular github projects.
> > > > > > > See  http://mahout.apache.org/developers/github.html for how
> > other
> > > > > > > projects
> > > > > > > handle PRs.
> > > > > > >
> > > > > > > Feel free to use that to create a similar documentation for
> Aria.
> > > > > > >
> > > > > > >
> > > > > > > > Do you have any recommendation for a different workflow we
> > could
> > > > use
> > > > > > for
> > > > > > > > this purpose? Are there possibly 

Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

On Tue, Oct 25, 2016 at 10:55 AM, Ran Ziv  wrote:

> Done.
> I'll update the project's .travis file now.
>
> What is the process of setting up a Jenkins job?
>

Needs an Infra ticket.

>
> -
>
> Regarding shared documents, is Confluence the Apache standard? What about
> using github markup files and have the documents as a part of the repo?
> Does anyone have any specific preference or other ideas on this matter?
>

Its again up to the project. Projects like Flink, Pirk, Beam have markup
files in github and use Jekyll.

They also use Confluence for few other things.


>
>
> On Tue, Oct 25, 2016 at 3:11 PM, Suneel Marthi  wrote:
>
> > Never heard of CircleCI, and I don't think Infra is gonna support that.
> >
> > Please go ahead and create an Infra ticket to enable Travis for Aria.
> >
> > On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv  wrote:
> >
> > > Regarding CI - Does Apache also support CircleCI? I assume less
> projects
> > > use it and if that's the case it could possibly be a better option for
> us
> > > if the purpose of using an additional CI environment (besides jenkins)
> is
> > > to allow for quick feedback over PRs.
> > > If not I'll create an Infra JIRA to enable Travis for our project.
> > >
> > >
> > >
> > > On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi 
> > wrote:
> > >
> > > > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv  wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have some questions for our mentors:
> > > > >
> > > > >
> > > > > 1) CI - we've noticed some Apache projects use online services
> rather
> > > > than
> > > > > the infra tools  offered by Apache. We're
> > > > leaning
> > > > > towards using TravisCI, however we're somewhat worried that since
> all
> > > > > apache projects are under a single github organization, builds in
> > > Travis
> > > > > will take a very long time to start etc..
> > > > >
> > > > >  Are you aware of any such issues (or perhaps Travis offers some
> > > special
> > > > > QoS to Apache projects or so)..?
> > > > >
> > > >
> > > > Most Apache projects use both Travis (unofficial) and Jenkins
> (Official
> > > > Apache CI).
> > > >
> > > > Jenkins is the official CI for all Apache projects while u can also
> use
> > > > Travis to validate PRs.
> > > >
> > > > YEs, I do see that the Travis builds take forever to launch sometimes
> > > given
> > > > the large number of Apache projects.
> > > >
> > > > For Aria, you can go wth Travis if you choose to (and we need to file
> > an
> > > > Infra ticket to enable Travis for the project), but Jenkins would be
> > the
> > > > authoritative CI - most projects now have both enabled.
> > > >
> > > >
> > > > > 2) Pull requests - we're used to reviewing code using PRs on
> github.
> > > > > However, since the github repo is merely a mirror, it's impossible
> to
> > > > merge
> > > > > PRs directly on github, which means we have to rebase the PR into
> the
> > > > > master branch and close the PR manually.
> > > > >
> > > >
> > > > Pull Requests for Apache github projects work a little different
> unlike
> > > the
> > > > regular github projects.
> > > > See  http://mahout.apache.org/developers/github.html for how other
> > > > projects
> > > > handle PRs.
> > > >
> > > > Feel free to use that to create a similar documentation for Aria.
> > > >
> > > >
> > > > > Do you have any recommendation for a different workflow we could
> use
> > > for
> > > > > this purpose? Are there possibly any common automation tools from
> > other
> > > > > projects, which serve for the same purpose as the "merge PR" button
> > on
> > > > > github?
> > > > >
> > > > > By the way, I saw on Spark's documentation
> > > > >  > > > > ing+to+Spark#ContributingtoSpark-PullRequest>
> > > > > that
> > > > > they mention the merging as if it were done automatically via
> github,
> > > so
> > > > > maybe I'm missing something here (or perhaps they do have some kind
> > of
> > > > > automation for it).
> > > > >
> > > > >
> > > > > 3) Where should project documents and documentation reside at? I've
> > > seen
> > > > > that many projects use confluence for storing development documents
> > > (e.g.
> > > > > contribution guides etc.). If you think that's what we should use
> as
> > > > well,
> > > > > could you please create us such a confluence environment too?
> > > > >
> > > >
> > > > We do have a confluence Wiki that was setup for AriaTosca. -
> > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/Ariatosca+Home
> > > >
> > > >
> > > >
> > > > >
> > > > > Thanks,
> > > > > Ran
> > > > >
> > > >
> > >
> >
>

Re: Questions regarding CI, PR and documentation

[Suneel Marthi]

Never heard of CircleCI, and I don't think Infra is gonna support that.

Please go ahead and create an Infra ticket to enable Travis for Aria.

On Tue, Oct 25, 2016 at 5:24 AM, Ran Ziv  wrote:

> Regarding CI - Does Apache also support CircleCI? I assume less projects
> use it and if that's the case it could possibly be a better option for us
> if the purpose of using an additional CI environment (besides jenkins) is
> to allow for quick feedback over PRs.
> If not I'll create an Infra JIRA to enable Travis for our project.
>
>
>
> On Thu, Oct 20, 2016 at 5:29 PM, Suneel Marthi  wrote:
>
> > On Thu, Oct 20, 2016 at 8:38 AM, Ran Ziv  wrote:
> >
> > > Hi,
> > >
> > > I have some questions for our mentors:
> > >
> > >
> > > 1) CI - we've noticed some Apache projects use online services rather
> > than
> > > the infra tools  offered by Apache. We're
> > leaning
> > > towards using TravisCI, however we're somewhat worried that since all
> > > apache projects are under a single github organization, builds in
> Travis
> > > will take a very long time to start etc..
> > >
> > >  Are you aware of any such issues (or perhaps Travis offers some
> special
> > > QoS to Apache projects or so)..?
> > >
> >
> > Most Apache projects use both Travis (unofficial) and Jenkins (Official
> > Apache CI).
> >
> > Jenkins is the official CI for all Apache projects while u can also use
> > Travis to validate PRs.
> >
> > YEs, I do see that the Travis builds take forever to launch sometimes
> given
> > the large number of Apache projects.
> >
> > For Aria, you can go wth Travis if you choose to (and we need to file an
> > Infra ticket to enable Travis for the project), but Jenkins would be the
> > authoritative CI - most projects now have both enabled.
> >
> >
> > > 2) Pull requests - we're used to reviewing code using PRs on github.
> > > However, since the github repo is merely a mirror, it's impossible to
> > merge
> > > PRs directly on github, which means we have to rebase the PR into the
> > > master branch and close the PR manually.
> > >
> >
> > Pull Requests for Apache github projects work a little different unlike
> the
> > regular github projects.
> > See  http://mahout.apache.org/developers/github.html for how other
> > projects
> > handle PRs.
> >
> > Feel free to use that to create a similar documentation for Aria.
> >
> >
> > > Do you have any recommendation for a different workflow we could use
> for
> > > this purpose? Are there possibly any common automation tools from other
> > > projects, which serve for the same purpose as the "merge PR" button on
> > > github?
> > >
> > > By the way, I saw on Spark's documentation
> > >  > > ing+to+Spark#ContributingtoSpark-PullRequest>
> > > that
> > > they mention the merging as if it were done automatically via github,
> so
> > > maybe I'm missing something here (or perhaps they do have some kind of
> > > automation for it).
> > >
> > >
> > > 3) Where should project documents and documentation reside at? I've
> seen
> > > that many projects use confluence for storing development documents
> (e.g.
> > > contribution guides etc.). If you think that's what we should use as
> > well,
> > > could you please create us such a confluence environment too?
> > >
> >
> > We do have a confluence Wiki that was setup for AriaTosca. -
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/Ariatosca+Home
> >
> >
> >
> > >
> > > Thanks,
> > > Ran
> > >
> >
>

Questions regarding CI, PR and documentation

[Ran Ziv]

Hi,

I have some questions for our mentors:


1) CI - we've noticed some Apache projects use online services rather than
the infra tools  offered by Apache. We're leaning
towards using TravisCI, however we're somewhat worried that since all
apache projects are under a single github organization, builds in Travis
will take a very long time to start etc..

 Are you aware of any such issues (or perhaps Travis offers some special
QoS to Apache projects or so)..?


2) Pull requests - we're used to reviewing code using PRs on github.
However, since the github repo is merely a mirror, it's impossible to merge
PRs directly on github, which means we have to rebase the PR into the
master branch and close the PR manually.

Do you have any recommendation for a different workflow we could use for
this purpose? Are there possibly any common automation tools from other
projects, which serve for the same purpose as the "merge PR" button on
github?

By the way, I saw on Spark's documentation

that
they mention the merging as if it were done automatically via github, so
maybe I'm missing something here (or perhaps they do have some kind of
automation for it).


3) Where should project documents and documentation reside at? I've seen
that many projects use confluence for storing development documents (e.g.
contribution guides etc.). If you think that's what we should use as well,
could you please create us such a confluence environment too?


Thanks,
Ran