[Outreachy] internship contribution

>
> Hi, I am Nsengiyumva Wilberforce From Uganda. I am happy that my first
> application for outreachy internship was accepted.
>
> When I read about Git in the project list, I got interested and I will
> be glad to be hooked into this community and get my hands dirty in
> contributions. I am eager to learn new things from my mentor and the
> entire community.
>
> I will be glad to hear from the community on some tips on how to get
> started with contribution.
>
> And more so would like to get in touch with the my mentor

>
> Hi Wilberforce,
>
> On Sun, Oct 9, 2022 at 6:46 AM NSENGIYUMVA WILBERFORCE
> <nsengiyumvawilberforce@gmail.com> wrote:
> >
> > Hi, I am Nsengiyumva Wilberforce From Uganda. I am happy that my first
> > application for outreachy internship was accepted.
> >
> > When I read about Git in the project list, I got interested and I will
> > be glad to be hooked into this community and get my hands dirty in
> > contributions. I am eager to learn new things from my mentor and the
> > entire community.
> >
> > I will be glad to hear from the community on some tips on how to get
> > started with contribution.
> >
> > And more so would like to get in touch with the my mentor
>
> As you also sent me a private message, I already replied privately.
> But for the public record and maybe other applicants for an Outreachy
> internship who might be interested in working on Git, we have
> information about how to get started contributing on the following
> pages:
>
> - https://git.github.io/Hacking-Git/
> - https://git.github.io/General-Microproject-Information/
>
> About microproject ideas, we haven't set up a specific page yet for
> this Outreachy round. Maybe we will do it but you shouldn't count on
> it. You can still take a look at the pages for the previous GSoC or
> Outreachy rounds like:
>
> - https://git.github.io/SoC-2022-Microprojects/
> - https://git.github.io/Outreachy-23-Microprojects/
> - https://git.github.io/SoC-2020-Microprojects/
>
> You will see that some ideas are quite generic and we propose them
> over and over as they are still valid.
>
> You are welcome to ask specific questions (publicly is preferred so
> that others can benefit).
>
> Thanks again for your interest in working on Git,
> Christian.

> On Mon, Oct 10, 2022 at 2:19 PM NSENGIYUMVA WILBERFORCE
> <nsengiyumvawilberforce@gmail.com> wrote:
>>
>> I see most of the articles are UNIX based, does it mean that I should
>> have a UNIX based operating system in order to contribute?
>> Currently, I have windows installed 11 on my PC
> 
> You can install a Linux virtual machine on your PC and develop in this
> virtual machine, or you can install the Git for Windows SDK from:
> 
> https://gitforwindows.org/#contribute
> 
> It might be best to install both development environments. I will not
> be able to help you much with development environment issues if you
> develop on Windows, but if it works for you, that could be Ok,
> especially if you use GitGitGadget too.

>
> On 10/10/2022 12:22 PM, Christian Couder wrote:
> > On Mon, Oct 10, 2022 at 2:19 PM NSENGIYUMVA WILBERFORCE
> > <nsengiyumvawilberforce@gmail.com> wrote:
> >>
> >> I see most of the articles are UNIX based, does it mean that I should
> >> have a UNIX based operating system in order to contribute?
> >> Currently, I have windows installed 11 on my PC
> >
> > You can install a Linux virtual machine on your PC and develop in this
> > virtual machine, or you can install the Git for Windows SDK from:
> >
> > https://gitforwindows.org/#contribute
> >
> > It might be best to install both development environments. I will not
> > be able to help you much with development environment issues if you
> > develop on Windows, but if it works for you, that could be Ok,
> > especially if you use GitGitGadget too.
>
> The git-for-windows/git fork has some information that is helpful
> for developing Git on a Windows machine [1]. This also includes
> details about recommending a Linux VM with Windows' Hyper-V system
> because compiling and testing Git is so much faster on Linux.
>
> [1] https://github.com/git-for-windows/git/blob/main/CONTRIBUTING.md
>
> Good luck!
> -Stolee

>
> Maybe WSL can be used?: https://learn.microsoft.com/en-us/windows/wsl/install
>
> On Mon, Oct 10, 2022 at 6:55 PM Derrick Stolee <derrickstolee@github.com> wrote:
> >
> > On 10/10/2022 12:22 PM, Christian Couder wrote:
> > > On Mon, Oct 10, 2022 at 2:19 PM NSENGIYUMVA WILBERFORCE
> > > <nsengiyumvawilberforce@gmail.com> wrote:
> > >>
> > >> I see most of the articles are UNIX based, does it mean that I should
> > >> have a UNIX based operating system in order to contribute?
> > >> Currently, I have windows installed 11 on my PC
> > >
> > > You can install a Linux virtual machine on your PC and develop in this
> > > virtual machine, or you can install the Git for Windows SDK from:
> > >
> > > https://gitforwindows.org/#contribute
> > >
> > > It might be best to install both development environments. I will not
> > > be able to help you much with development environment issues if you
> > > develop on Windows, but if it works for you, that could be Ok,
> > > especially if you use GitGitGadget too.
> >
> > The git-for-windows/git fork has some information that is helpful
> > for developing Git on a Windows machine [1]. This also includes
> > details about recommending a Linux VM with Windows' Hyper-V system
> > because compiling and testing Git is so much faster on Linux.
> >
> > [1] https://github.com/git-for-windows/git/blob/main/CONTRIBUTING.md
> >
> > Good luck!
> > -Stolee

> thank you all for your suggestions, let me see what is easy for me
> 
> On Mon, Oct 10, 2022 at 7:58 PM Luna Jernberg <droidbittin@gmail.com> wrote:
>>
>> Maybe WSL can be used?: https://learn.microsoft.com/en-us/windows/wsl/install

>
> On 10/10/2022 2:17 PM, NSENGIYUMVA WILBERFORCE wrote:
> > thank you all for your suggestions, let me see what is easy for me
> >
> > On Mon, Oct 10, 2022 at 7:58 PM Luna Jernberg <droidbittin@gmail.com> wrote:
> >>
> >> Maybe WSL can be used?: https://learn.microsoft.com/en-us/windows/wsl/install
>
> If you do go the WSL route, then please share your learnings by updating the
> contributing doc either in git-for-windows/git [1] or here on the mailing list.
>
> [1] https://github.com/git-for-windows/git/blob/main/CONTRIBUTING.md
>
> Thanks,
> -Stolee

>
> Simple steps that I followed on windows 10
> -open the command line application with administrator rights
> -run wsl --install.
> - Restart the computer
> -check installed distributions, wsl --list --online
> -run ubuntu distribution, wsl -d ubuntu
> -add username and password
> After the above steps I was able to set up git on ubuntu
> NB: to start wsl when you stopped, just type wsl -u "the username u
> created" in the command line
>
> On Mon, Oct 10, 2022 at 9:22 PM Derrick Stolee <derrickstolee@github.com> wrote:
> >
> > On 10/10/2022 2:17 PM, NSENGIYUMVA WILBERFORCE wrote:
> > > thank you all for your suggestions, let me see what is easy for me
> > >
> > > On Mon, Oct 10, 2022 at 7:58 PM Luna Jernberg <droidbittin@gmail.com> wrote:
> > >>
> > >> Maybe WSL can be used?: https://learn.microsoft.com/en-us/windows/wsl/install
> >
> > If you do go the WSL route, then please share your learnings by updating the
> > contributing doc either in git-for-windows/git [1] or here on the mailing list.
> >
> > [1] https://github.com/git-for-windows/git/blob/main/CONTRIBUTING.md
> >
> > Thanks,
> > -Stolee

> Hi team, I am reading through "My first contribution"
> when I run make all doc, I get the following;
>
> SUBDIR git-gui
>     SUBDIR gitk-git
>     SUBDIR templates
> make -C Documentation all
> make[1]: Entering directory '/mnt/c/Users/USER/documents/git/Documentation'
> make[2]: Entering directory '/mnt/c/Users/USER/documents/git'
> make[2]: 'GIT-VERSION-FILE' is up to date.
> make[2]: Leaving directory '/mnt/c/Users/USER/documents/git'
>     XMLTO git-version.1
> /bin/sh: 1: xmlto: not found
> make[1]: *** [Makefile:355: git-version.1] Error 127
> make[1]: Leaving directory '/mnt/c/Users/USER/documents/git/Documentation'
> make: *** [Makefile:2720: doc] Error 2
>
> How should I go about it?

> NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com> writes:
> 
> > Hi team, I am reading through "My first contribution"
> > when I run make all doc, I get the following;
> >
> > SUBDIR git-gui
> >     SUBDIR gitk-git
> >     SUBDIR templates
> > make -C Documentation all
> > make[1]: Entering directory '/mnt/c/Users/USER/documents/git/Documentation'
> > make[2]: Entering directory '/mnt/c/Users/USER/documents/git'
> > make[2]: 'GIT-VERSION-FILE' is up to date.
> > make[2]: Leaving directory '/mnt/c/Users/USER/documents/git'
> >     XMLTO git-version.1
> > /bin/sh: 1: xmlto: not found
> > make[1]: *** [Makefile:355: git-version.1] Error 127
> > make[1]: Leaving directory '/mnt/c/Users/USER/documents/git/Documentation'
> > make: *** [Makefile:2720: doc] Error 2
> >
> > How should I go about it?
> 
> Googling "xmlto: not found", the first result is
> 
>     https://command-not-found.com/xmlto
> 
> The page lists how to get and install it for various platforms, and
> WSL/Windows should be included there.
> 
> I believe "My first contribution" recommends to first read the
> top-level INSTALL before continuing (and if not, it should be
> updated to).  Simpler things first---building and installing the
> vanilla source code without any of your changes should be simpler
> and you should become confident in doing that, before you start
> modifying anything. Otherwise, when you encounter a problem, you
> would not be able to tell if you broke it with your change, or your
> basic set-up is not complete (e.g. missing necessary tools like
> xmlto) and unable to build and install from even vanilla set of
> sources.

>
> On 2022-10-11 21:42:52-0700, Junio C Hamano <gitster@pobox.com> wrote:
> > NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com> writes:
> >
> > > Hi team, I am reading through "My first contribution"
> > > when I run make all doc, I get the following;
> > >
> > > SUBDIR git-gui
> > >     SUBDIR gitk-git
> > >     SUBDIR templates
> > > make -C Documentation all
> > > make[1]: Entering directory '/mnt/c/Users/USER/documents/git/Documentation'
> > > make[2]: Entering directory '/mnt/c/Users/USER/documents/git'
> > > make[2]: 'GIT-VERSION-FILE' is up to date.
> > > make[2]: Leaving directory '/mnt/c/Users/USER/documents/git'
> > >     XMLTO git-version.1
> > > /bin/sh: 1: xmlto: not found
> > > make[1]: *** [Makefile:355: git-version.1] Error 127
> > > make[1]: Leaving directory '/mnt/c/Users/USER/documents/git/Documentation'
> > > make: *** [Makefile:2720: doc] Error 2
> > >
> > > How should I go about it?
> >
> > Googling "xmlto: not found", the first result is
> >
> >     https://command-not-found.com/xmlto
> >
> > The page lists how to get and install it for various platforms, and
> > WSL/Windows should be included there.
> >
> > I believe "My first contribution" recommends to first read the
> > top-level INSTALL before continuing (and if not, it should be
> > updated to).  Simpler things first---building and installing the
> > vanilla source code without any of your changes should be simpler
> > and you should become confident in doing that, before you start
> > modifying anything. Otherwise, when you encounter a problem, you
> > would not be able to tell if you broke it with your change, or your
> > basic set-up is not complete (e.g. missing necessary tools like
> > xmlto) and unable to build and install from even vanilla set of
> > sources.
>
> Maybe he is on Windows and using Git-for-Windows SDK? I'm not sure
> what's included there, but I can imagine that man-pages is useless
> on Windows, they would prefer html docs instead. Perhaps, they want:
>
>         make all && make -C Documentation html
>
> When building only html, xmlto is not necessary to be installed.
>
> --
> Danh

> Please reply inline or inter-leaved.
>
> Perhaps this documentation can help you get started with building Git
> from source. (I suspect you're missing something like libcurl
> development files, too).

>
> On 2022-10-12 13:37:48+0300, NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com> wrote:
> > I am using ubuntu(wsl)
>
> Please reply inline or inter-leaved.
>
> Perhaps this documentation can help you get started with building Git
> from source. (I suspect you're missing something like libcurl
> development files, too).
>
> https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
>
> --
> Danh