From: George Shapovalov <george@gentoo.org>
To: Francois Castonguay <natri98@hotmail.com>
Cc: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] New sub-project Gentoo Science Physics
Date: Tue, 04 Jul 2006 21:15:24 +0200 [thread overview]
Message-ID: <200607042115.25362.george@gentoo.org> (raw)
In-Reply-To: <BAY103-W6C6A024224800CE621153AE710@phx.gbl>
Hi François
Thank you for your interest!
Since you are just starting with Gentoo it is probably not wise to invite you
into some kind of developership right away :), however you still may find
Gentoo Development handbook usefull:
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml
It has a good deal of information on how to write ebuilds, eclasses, what
caveats to expect, - stuff that you will find usefull if you want to step
outside of merely "using" Gentoo. This reference might be usefull too:
http://devmanual.gentoo.org/
although I'd suggest it as a second "more advanced" reading :).
As for the involvement: the natural place to start would be to look at
bugzilla:
https://bugs.gentoo.org
search for sci bugs and start helping. Resolving real problems or just
testing/cleaning up submitted ebuilds. Of course you may as well submit
ebuilds of your own ;) (but search the bugs first! You will be amazed hom
much stuff we have there).
Since you metion you are interested in physics you should probably look here:
https://bugs.gentoo.org/show_bug.cgi?id=138711
The bug is closed, since the herd has already been created (as announced),
however it lists the number of packages that are expected to be added to the
tree eventually. You may try creating ebuilds for some of those that are not
in bugzilla yet. However if you do so, I'd suggest you coordinate with Luis
Medinas, who is the reporter of that bug and who "oversees" the physics
caterogy and herd..
Thanks again for your interest and wellcome!
George
вівторок, 4. липень 2006 18:23, Francois Castonguay Ви написали:
> Good morning all, I’m not sure of the proper protocol to respond to this
> specific mailing list, but I figure this was such a great opportunity, that
> I couldn’t miss it. I have one more year in order to graduate form my
> bachelor in physics and computer science. I have been added on the science
> mailing list for a couple of month now, at the same time that I started
> being interested in Gentoo. I’m now up and running with my first Gentoo
> machine and would like to help the community. I do not know how much my
> contribution can be of an asset but I need to start somewhere. I love
> physics, and I’m starting to enjoy Gentoo. How can I help?
> (Sorry for those who where forced to read my life story, I figure it was
> important to tell where I was before to start anything serious.)
>
> François
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-04 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 16:23 [gentoo-science] New sub-project Gentoo Science Physics Francois Castonguay
2006-07-04 19:09 ` Luis Medinas
2006-07-04 19:15 ` George Shapovalov [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-04 0:40 Luis Medinas
2006-07-04 0:38 Luis Medinas
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=200607042115.25362.george@gentoo.org \
--to=george@gentoo.org \
--cc=gentoo-science@lists.gentoo.org \
--cc=natri98@hotmail.com \
/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