trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Smits <pierresm...@apache.org>
Subject Re: [Discussion] Our GIT repo and Github
Date Wed, 12 Sep 2018 06:40:28 GMT
Of course, There is no need to rush this. And working on a set of
actionable items regarding this after 2.3 is a good goal.

Let's wait and see whether other viewpoints come forward.



Best regards,

Pierre Smits

*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
since 2008*
Apache Steve <https://steve.apache.org>, committer

On Mon, Sep 10, 2018 at 6:30 PM, Steve Varnau <steve.varnau@esgyn.com>
wrote:

> +1  - This would be a good transition to make after 2.3 release.
>
> --Steve
>
> > -----Original Message-----
> > From: Pierre Smits <pierresmits@apache.org>
> > Sent: Monday, September 10, 2018 9:25 AM
> > To: dev@trafodion.apache.org
> > Subject: Re: [Discussion] Our GIT repo and Github
> >
> > If that is the case (regarding the latter aspect of documentation and
> > website), we should disentangle that from current repo and have it in a
> > separate. That would also benefit our (potential) adopters and
> > contributors, as it would not inflate any 'code' download needlessly.
> >
> > Pierre Smits
> >
> > ORRTIZ.COM <http://www.orrtiz.com>
> > OFBiz based solutions & services
> >
> > OEM - The OFBiz Extensions Marketplace1
> > http://oem.ofbizci.net/oci-2/
> > 1 not affiliated to (and not endorsed by) the OFBiz project
> >
> > On Mon, Sep 10, 2018 at 5:48 PM, Hans Zeller <hans.zeller@esgyn.com>
> > wrote:
> >
> > > +1
> > >
> > > That would be a very good idea, IMHO.
> > >
> > > For code changes, that should make things really easy. For
> documentation
> > > and web site changes, I hope it would not make the process any more
> > > complicated than it already is.
> > >
> > > Hans
> > >
> > > -----Original Message-----
> > > From: Pierre Smits <pierresmits@apache.org>
> > > Sent: Monday, September 10, 2018 2:11 AM
> > > To: dev@trafodion.apache.org
> > > Subject: [Discussion] Our GIT repo and Github
> > >
> > > For references:
> > > [1] https://git.apache.org
> > > [2] https://reference.apache.org/committer/git
> > > [3] https://gitbox.apache.org/repos/asf
> > > [4]
> > > https://cwiki.apache.org/confluence/display/TRAFODION/
> > > Trafodion+Contributor+Guide
> > >
> > > Our project uses git as version control solution [1], and we have a
> > > presence thereof at GitHub. The setup allows contributors who work on
> > the
> > > GitHub side (in their forks) to submit PRs and comments thereon from
> > there
> > > [4].
> > >
> > > However, the setup dictates/includes only having read access to our
> > GitHub
> > > repo for our contributors (including those with the commit privilege).
> This
> > > means (AFAIUI) that every commit action needs to take place at the ASF
> > side
> > > of the setup.
> > >
> > > Would it be beneficial to our project to move from our current setup
> to the
> > > 'gitbox' approach that has been made available by the ASF, so that
> there
> > > can the read/write permission for contributors (with the appropriate
> > > privileges) working via the GitHub side?
> > >
> > > WDYT?
> > >
> > > [1] https://git.apache.org
> > > [2] https://reference.apache.org/committer/git
> > >
> > > Best regards,
> > >
> > > Pierre Smits
> > >
> > > *Apache Trafodion <https://trafodion.apache.org>, Vice President*
> > > *Apache Directory <https://directory.apache.org>, PMC Member*
> > > Apache Incubator <https://incubator.apache.org>, committer
> > > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without
> privileges)
> > > since 2008*
> > > Apache Steve <https://steve.apache.org>, committer
> > >
>

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