Open Stack

Hi Leni, welcome!

1) Devstack[1] plays a *main *role in the development workflow.
It's an easier way to get a full environment to work in Manila, we use it
every day. I recommend you to use it in a VM.
You can find many tutorials about how to use Devstack, I just let you one
[2]

2) I can't find *low-hanging-fruit* bugs in Manila. However,
good-first-bugs are tagged as *low-hanging-fruit *for example, cinder's[3]

Today at *15:00 UTC *It's  Weekly Manila Team Meeting at IRC (channel
#openstack-meeting-alt) on Freenode.

Have fun!
Sofia
irc: enriquetaso
[1]
https://docs.openstack.org/zun/latest/contributor/quickstart.html#exercising-the-services-using-devstack
[2]
https://enriquetaso.wordpress.com/2016/05/07/installing-devstack-on-a-vagrant-virtual-machine/
[3] https://bugs.launchpad.net/cinder/+bugs?field.tag=low-hanging-fruit

On Thu, Nov 8, 2018 at 7:41 AM Leni Kadali Mutungi <lenikmutungi at gmail.com>
wrote:

> Hi Tom
>
> Thanks for the warm welcome. I've gone through the material and I would
> like to understand a few things:
>
> 1. What's the role of devstack in the development workflow?
> 2. Where can I find good-first-bugs? A bug that is simple to do
> (relatively ;)) and allows me to practice what I've read up on in
> Developer's Guide. I looked through the manila bugs on Launchpad but I
> didn't see anything marked easy or good-first-bug or its equivalent for
> manila. I am a bit unfamiliar with Launchpad so that may have played a
> role :).
>
> Your guidance is appreciated.
>
> On 10/19/18 5:55 PM, Tom Barron wrote:
> > On 19/10/18 15:27 +0300, Leni Kadali Mutungi wrote:
> >> Hi all.
> >>
> >> I've downloaded the manila project from GitHub as a zip file, unpacked
> >> it and have run `git fetch --depth=1` and been progressively running
> >> `git fetch --deepen=5` to get the commit history I need. For future
> >> reference, would a shallow clone e.g. `git clone depth=1` be enough to
> >> start working on the project or should one have the full commit
> >> history of the project?
> >>
> >> --
> >> -- Kind regards,
> >> Leni Kadali Mutungi
> >
> > Hi Leni,
> >
> > First I'd like to extend a warm welcome to you as a new manila project
> > contributor!  We have some contributor/developer documentation [1] that
> > you may find useful. If you find any gaps or misinformation, we will be
> > happy to work with you to address these.  In addition to this email
> > list, the #openstack-manila IRC channel on freenode is a good place to
> > ask questions.  Many of us run irc bouncers so we'll see the question
> > even if we're not looking right when it is asked.  Finally, we have a
> > meeting most weeks on Thursdays at 1500UTC in #openstack-meeting-alt --
> > agendas are posted here [2].  Also, here is our work-plan for the
> > current Stein development cycle [3].
> >
> > Now for your question about shallow clones.  I hope others who know more
> > will chime in but here are my thoughts ...
> >
> > Although having the full commit history for the project is useful, it is
> > certainly possible to get started with a shallow clone of the project.
> > That said, I'm not sure if the space and download-time/bandwidth gains
> > are going to be that significant because once you have the workspace you
> > will want to run unit tests, pep8, etc. using tox as explained in the
> > developer documentation mentioned earlier.   That will download virtual
> > environments for manila's dependencies in your workspace (under .tox
> > directory) that dwarf the space used for manila proper.
> >
> > $ git clone --depth=1 git at github.com:openstack/manila.git shallow-manila
> > Cloning into 'shallow-manila'...
> > ...
> > $ git clone git at github.com:openstack/manila.git deep-manila
> > Cloning into 'deep-manila'...
> > ...
> > $ du -sh shallow-manila deep-manila/
> > 20M    shallow-manila
> > 35M    deep-manila/
> >
> > But after we run tox inside shallow-manila and deep-manila we see:
> >
> > $ du -sh shallow-manila deep-manila/
> > 589M    shallow-manila
> > 603M    deep-manila/
> >
> > Similarly, you are likely to want to run devstack locally and that will
> > clone the repositories for the other openstack components you need and
> > the savings from shallow clones won't be that significant relative to
> > the total needed.
> >
> > Happy developing!
> >
> > -- Tom Barron (Manila PTL) irc: tbarron
> >
> > [1] https://docs.openstack.org/manila/rocky/contributor/index.html
> > [2] https://wiki.openstack.org/wiki/Manila/Meetings
> > [3] https://wiki.openstack.org/wiki/Manila/SteinCycle
> >
> >
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> --
> -- Kind regards,
> Leni Kadali Mutungi
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 

Laura Sofia Enriquez

Associate Software Engineer
Red Hat PnT <https://www.redhat.com>

Ingeniero Butty 240, Piso 14

(C1001AFB) Buenos Aires - Argentina

senrique at redhat.com
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20181108/d77d772f/attachment.html>