From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Cc: Gentoo Catalyst <gentoo-catalyst@lists.gentoo.org>
Subject: [gentoo-catalyst] Re: [gentoo-soc] Catalyst Python reimplementation
Date: Sun, 21 Apr 2013 09:13:13 -0700 [thread overview]
Message-ID: <1366560793.10091.14.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <CAMqzjettXMQym+_mKeiHPkz52qKZpawXRphO4csm7UXHBv4nGA@mail.gmail.com>
On Sun, 2013-04-21 at 05:08 +0400, Dmitry Selyutin wrote:
> Hello everyone!
>
>
> My name is Dmitry and I'm writing here because I've found a proposal
> to rewrite Catalyst in Gentoo GSoC-2013 Ideas page[1]. I know that
> application period hasn't started yet, but I already think that I'd
> like to take up this job. However I've found that before posting
> application I must perform some actions:
>
>
> 1. Use the tools that you will use in your project to make changes to
> code.
This is the big one. To be able to work on catalyst, you first must be
running and using gentoo linux and be familiar with it. Gentoo's
package management tools are central to running and using catalyst to
build various output media. If you are not already using gentoo, you
best get a partition free and install it asap. Become familiar with it.
tools to be familiar with:
portage and it's cli tools, emerge, emaint, portageq
gentoolkit's equery, eclean
You must be familiar with using the above tools and solving build
problems and package installation failures.
Then start trying to use catalyst to generate some targets.
This is all information that will need for you to succeed in your
project proposal.
> 2. Participate in our development community.
> 3. Give us your contact info and working hours.
>
[snip]...
> The other question is that it is really hard to find some project
> which uses python and emit patch to it to pass requirements. Could you
> advice a good bug, please? :-)
>
>
Don't worry about that yet. It is early :)
> If you think I have a chance, I can even answer the third question
> (about work hours, contacts, etc.). :-)
>
>
> Looking forward to your answers!
>
This will be something for your actual proposal. It can be done later.
>
> P.S. Thanks for being so patience to read such a long letter till the
> end!
>
> --
> With best regards,
> Dmitry Selyutin
>
> E-mail: ghostmansd@gmail.com
> Phone: +7(985)334-07-70
next prev parent reply other threads:[~2013-04-21 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 1:08 [gentoo-catalyst] Catalyst Python reimplementation Dmitry Selyutin
2013-04-21 16:13 ` Brian Dolbec [this message]
2013-04-22 17:55 ` [gentoo-catalyst] Re: [gentoo-soc] " Dmitry Selyutin
2013-04-22 18:18 ` W. Trevor King
2013-04-23 14:19 ` Brian Dolbec
[not found] <5178296b.c462b40a.4faf.03fa@mx.google.com>
2013-05-01 0:17 ` Dmitry Selyutin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1366560793.10091.14.camel@big_daddy.dol-sen.ca \
--to=dolsen@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox