self - introduction
by Chitlesh GOORAH
Hello there,
I'm Chitlesh GOORAH. Most of you already know me for some reason or
another. I have been fairly around the Fedora Project for a while.
Here is my wikipage:
http://fedoraproject.org/wiki/ChitleshGoorah
I would like to join in the Fedora Mentors Team:
- Ambassadors, since several times I've guided new ambassadors with
the procedures
- On the wiki, I feel at ease with MoinMoin.
I will update my wikipage accordingly if there are no objection about
my participation in the Fedora Mentors
Regards,
Chitlesh GOORAH
--
http://clunixchit.blogspot.com
17 years, 10 months
[Fwd: Want to help with fedora porject]
by Máirín Duffy
Hey,
Does anybody have time this or next Friday to help Shivakar out with a Fedora
bug day? (I'm going to be at GUADEC)
~m
-------- Original Message --------
Subject: Want to help with fedora porject
Date: Mon, 19 Jun 2006 02:33:16 -0500
From: Vulli, Srinivasa Shivakar (UMR-Student) <ssvh27(a)umr.edu>
To: <duffy(a)redhat.com>
Hi Ms.duffy,
My name is Shivakar. I have been Redhat and now Fedora for almost 7 years now. I
use fedora at my work, and home for programming and desktop use. I would now
like help fedora project and contribute something back to the community. I would
like you to point me in the right direction.
Coming to me. I am currently doing my MS in Mechanical Engineering at Univ of
Missouri Rolla. I have good programming experience and can program in C, C++,
Perl and Java. As a part of my work as a Graduate Research Assitant with the
Dept. of Elec. Engg I administer a 4 node cluster running Fedora core 4. I
currently work with PVM and MPI for programming parallel image processing
applications.
I am interested in helping out with the fedora-triage (bugzapper) project.
Kindly tell me how I can start. I have looked at the triage guidelines page and
will participate with the group next friday. If there is something I should
know. Kindly mail me.
Thanks,
Shivakar
P.S.: This is the same mail I sent to Rahul Sundaram, and got no reply. Maybe he
is busy. The thing is I believe that when someones hands are itching for work,
you gotta give him some work before the itching stops for high productivity
(just kidding!!). I was just hoping someone would put me in the right track
asap. thats all.
--
Máirín Duffy <duffy(a)redhat.com>
Interaction Designer
Red Hat Network :: Red Hat, Inc.
Westford, MA 978.392.3908
17 years, 10 months
I would like to join the Fedora Project (fwd)
by David Eisenstein
Hi folks,
I received this message yesterday or so. I have not yet responded. Am
not sure how to respond to this query. Normally I respond to queries with
a plug for the project I work with and specifically mentor for (Fedora
Legacy) but somehow I don't think that appropriate for this particular
person. Sounds like this fellow wants to help *develop* software, not
maintain existing software for security vulnerabilities.
Do any of you have suggestions, or would any of you like to respond to
this fellow? I'd appreciate hearing from you either way. Thank you.
Warm regards,
David Eisenstein
---------- Forwarded message ----------
From: Mashuq Rahman <mashuq(a)hotmail.com>
To: deisenst(a)gtw.net
Date: Mon, 19 Jun 2006 06:11:00 +1100
Subject: I would like to join the Fedora Project
Hello,
A bit abt me - I am a 3rd year comp scie student and would like to
help/contribute to Fedora as much as I can with my programming knowledge./
I personally use fedora core 5 on my laptop. I have good knowledge of Java
and working knowledge on C. I dont have any previous experience of working
on a large software development project consisting many people. I hope u
can help and guide me to join the Fedora community and contribute.
hope to hear from you soon
Mashuq
_________________________________________________________________
<<snip of blurb advertising MSN Messenger>>
17 years, 10 months
Intro-time
by Bart Couvreur
Hi everyone,
I'm Bart Couvreur, a member of the Fedora community for quite some time
now (since fc2). I'm active in Translation, Documentation, Websites and
Kadischi. Recently I started an effort to get a Dutch trans-team in
place, to which I got a lot of response and a few pointers to this
project.
So here I am, willing to mentor translators (software, docs, wiki).
Bart aka couf
Key fingerprint = 6AAB 544D 3432 D013 776D 3602 ADB6 6B2A D93F 0F93
PS: I've been reading the list archives and I've seen a banner for this
project, but it never made it to the wiki, maybe we should get it in
place now?
Link: http://people.redhat.com/duffy/misc/mentorbanner.png
17 years, 10 months
error: Installed (but unpackaged) file(s) found
by Marc Wiriadisastra
Hi All,
My first discussion re packaging.
I get this error now a bit of googling and finding that on the mailing
list it relates to an error where the files installed are not listed in
the files section. Please correct me if I'm wrong.
If thats the case that all files installed have to be listed in the
files section how do people go about installing python packages. My
direct example which I'll list here for completeness of the question is
because in my circumstance there is not a build for this python package
using the standard tools.
rm -rf $RPM_BUILD_ROOT
rm -rf ${RPM_BUILD_ROOT}
mkdir -p ${RPM_BUILD_ROOT}/usr/share/%{name}
install -m 644 *.py ${RPM_BUILD_ROOT}/usr/share/%{name}
mkdir -p ${RPM_BUILD_ROOT}/usr/share/%{name}/BitTorrent
install -m 644 BitTorrent/*
${RPM_BUILD_ROOT}/usr/share/%{name}/BitTorrent
mkdir -p ${RPM_BUILD_ROOT}/usr/share/%{name}/images/flags
install -m 644 images/flags/*
${RPM_BUILD_ROOT}/usr/share/%{name}/images/flags
install -m 644 images/*.png
${RPM_BUILD_ROOT}/usr/share/%{name}/images/flags
install -m 644 images/*.ico
${RPM_BUILD_ROOT}/usr/share/%{name}/images/flags
mkdir -p ${RPM_BUILD_ROOT}/usr/share/%{name}/locale/en/LC_MESSAGES
install -m 644 locale/en/LC_MESSAGES/*
${RPM_BUILD_ROOT}/usr/share/%{name}/locale/en/LC_MESSAGES
mkdir -p ${RPM_BUILD_ROOT}/usr/share/%{name}/locale/h4/LC_MESSAGES
install -m 644 locale/h4/LC_MESSAGES/*
${RPM_BUILD_ROOT}/usr/share/%{name}/locale/h4/LC_MESSAGES
Its basically a script to install all the necessary files into the
respective locations. The actual running of the program is a bash
script file that runs it using the python -OO /usr/share/rufus/rufus.py
Am I going about this the completely wrong way?
Regards,
Marc
17 years, 10 months
[Legacy] Mentoring for vulnerability bug tracking -- kernel, and general
by David Eisenstein
Hi,
(Please forgive me for cross-posting, but I thought I'd post this question
to all the relevant groups I could think of. Please let me know if I am
committing a cross-posting felony here. :) )
I am in the process of mentoring someone to help them learn how to do
vulnerability tracking for Fedora Legacy. This evening, we were looking
at doing that for the kernels. We quickly got confused, though, because
we weren't sure how to go about making sure we only report issues into
Bugzilla that would be relevant kernel issues for Fedora Legacy at this
time.
One complicating factor here is that we in Legacy don't necessarily
release kernels in any kind of lock-step with what either Fedora Core or
Red Hat Enterprise Linux does, so the issues we have to fix are a
different subset of issues than what is reported in any given RHSA or
FEDORA release announcement. And even if we did release kernels in
lockstep, no doubt there would still be differing CVE's per distro.
(For those of you not familiar with Legacy processes: we normally put
multiple CVE issues [maybe as many as dozens of CVE's] into a single
bugzilla report for a given .src.rpm component; and we also put multiple
distros in a given bugzilla ticket as well, using a "Version" tag of
"unspecified" and tracking what distros are being worked on and their
statuses via the use of Status Whiteboard entries. For more information
about this, you can refer to
<http://fedoraproject.org/wiki/Legacy/StatusWhiteboard>, and the most
recent completed Legacy kernel bug is here in case you're interested:
<https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=157459>.)
I started to suggest to my mentee this method: Have a look at the latest
release announcements from Fedora Legacy for the kernels that we maintain,
and then look for issues in the usual places (e.g., those resources listed
in <http://fedoraproject.org/wiki/Legacy/VulnerabilityTracking>) that have
come up since we released our latest security-fixed kernels. That would
provide a list of CVE's to then put in a new Bugzilla ticket or add to an
already-existing ticket that would likely be relevant. But is this
enough?
Does this method sound workable to you? Are we missing something? Do you
have you have some better ideas how to track kernel vulnerabilities to get
those vulnerabilities properly listed in a Bugzilla ticket to be worked
on?
A more general question is this: How do we in Fedora Legacy track
vulnerabilities and make sure that we are aware of all the relevant
vulnerabilities for the packages that we maintain, and haven't missed
something?
The fedora-security-list and Josh Bressers are using audit files to track
all relevant security vulnerabilities for their sets of packages, which
are kept in CVS here,
<http://cvs.fedora.redhat.com/viewcvs/fedora-security/audit/?root=fedora>
but we here in Fedora Legacy haven't started using this kind of tool yet.
Is it time for us to start doing so? If so, are any of you interested in
forming some kind of vulnerability tracking team and getting started on
such list(s) for the products we maintain?
Thanks much in advance!
Regards,
David Eisenstein
17 years, 10 months
