For code clean-up (whosoever has the rights and will be doing it), I
suggest to merge last year's GSoC branch i.e. "GSOC2015-merged" with the
master branch (after some bug-fixes and testing).
Basically, what I'm suggesting is the following structure for the git repo -
'master' branch - tested and updated code by developers for the
current/next-to-come release
'release' branch - what actually goes online
That's the way many other organizations manage their repositories on
github. ref: OpenSSL <https://github.com/openssl/openssl>
This way the developer's github profile is updated and his code will be
publicly visible on the master branch of our repo.
On Wed, May 25, 2016 at 12:17 PM, Gauravjeet Singh <
gaurav.ishwer...@gmail.com> wrote:
> On Wed, May 25, 2016 at 8:37 AM, Christopher Sean Morrison
> <brl...@mac.com> wrote:
> > Commit access is given after at least two successful pull requests /
> patches
> > that are flawless improvements. Do you have any pending?
>
> In OGV repository, I had sent two pull requests, which are still pending.
> #34 : https://github.com/BRL-CAD/OGV-meteor/pull/34
> #31 : https://github.com/BRL-CAD/OGV-meteor/pull/31
>
> #31 is a minimal pull request, I didn't change much of code. However,
> #34 can be categorised as an improvement in OGV.
>
> Also, I worked on BRL-CAD website.
> https://github.com/BRL-CAD/web/pull/13
> I am not sure if it counts, but I had a successful pull request in
> BRL-CAD website (#13)
>
> > If not, I suggest
> > reordering your timeline to work on something minimally productive first,
> > then moving to the merge cleanup work. If you do, drum up support for
> > someone to review them.
>
> Still, I'd find something to work upon for another PR that serves as
> an improvement in OGV.
> If everything goes well, I may be able to send another PR by today.
>
>
> --
> Fear is wisdom in the face of danger. It’s nothing to be ashamed of
>
> Gauravjeet Singh
> http://github.com/gauravjeetsingh
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
> untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>
--
Regards
Shubham Chauhan
2013099
B.Tech CSE
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
