Started the day by summarising day 1.
To experience the process of checking out, modify and uploading code, mel chua showed us :
http://fedoraproject.org/wiki/Websites/ShowUs
Get started
The intructions given are good. It makes an implied assumption that the user is included in the “sudo” program permissions file
A little polishing would help improve the experience and perception of the newbie to FOSS.
A small note stating that root permissions are required to install the git package would be helpful and or an alternative way like “su – root” can also be used to perform the install.
“sudo yum -y install git gettext python-genshi python-setuptools babel python-feedparser” or
“su – root” Enter Password :
“yum -y install git gettext python-genshi python-setuptools babel python-feedparser”
The following steps must be executed by the user in the user’s dir.
“git clone git://git.fedorahosted.org/git/fedora-web.git”
“cd fedora-web/fedoraproject.org”
“make”
make test
make stoptest
I was unable to download because of timeouts. I believe that the port was blocked, which led to the next step.
As root
“Yum install wireshark”
Now seeing which port was being used by git would be simple like
In one root console, type
“wireshark -i eth0”
In another user console
“git clone git://git.fedorahosted.org/git/fedora-web.git” and we are done.
The answer in the root console was returned as:
“bash: wireshark: command not found”
“$ rpm -qa| grep wire” shows
wireless-tools-29-4.fc11.i586
wireshark-1.2.2-1.fc11.i586
A search for wireshark came up blank.
More searching and experimenting finally showed
tshark
A name change is alright when deemed necessary.
If some info or link to start tshark as wireshark or ethereal is included it would be nice .
As a note the GUI is absent from rpm.
http://localhost:5000/en/index = Fedora 12: United works
cd to the ~/fedora-web/spins.fedoraproject.org
and typing “make test” shows an error.
The “out” dir needs to be created in ~/fedora-web/spins.fedoraproject.org/
ls /home/nyp1/fedora-web/spins.fedoraproject.org/httpd/conf file uses the out dir as the document root.
Any help in resolving or explanations to the why these issues would be appreciated.
Tiraths's Blog 
November 11, 2009 at 12:02 am |
« A little polishing would help improve the experience and perception of the newbie to FOSS. »
On the other hand, those instructions are targeted at people who will be able to hack on Python, and those people are usually (but not always) not newbies.
However, the main message of the page is « if you think you can do better, then do it, and show it to us ». This is how FOSS works, and this applies for the wiki page in itself as well.
If you believe than rephrasing it would make it clearer, go ahead and rephrase it. In the worst case, your contribution will be reverted (keep in mind that a wiki is a versioned system), but more likely, your contributions will be most welcome, kept and even improved by someone else coming after you 🙂
About wireshark, your issues come from the fact that the package is split in several parts:
# yum list wireshark\*
Loaded plugins: presto, refresh-packagekit
Available Packages
wireshark.i686 1.2.2-1.fc12 fedora
wireshark.x86_64 1.2.2-1.fc12 fedora
wireshark-gnome.x86_64 1.2.2-1.fc12 fedora
I believe the GUI package you are looking for is the last one 🙂
November 16, 2009 at 9:35 am |
Dear bochecha,
Wiki Documentation
On the issue of wiki documentation. I agree that if one can edit it to make it better then the improvement should be contributed. Fortunately or otherwise, even after learning the process, it is can be described as tedious. The process, what ever it is, could be clearly shown as a wiki and the link to this wiki page be shown on every page so that it is fast and a time saving process. The process should encourage the client to contribute inclusive of all the essential security that has been installed.
Yum and Packaging
How the package is split up is not the issue. Its the messages to resolve difficulties. The issue is that yum’s sole function is to take care of these things, remove difficulties or hurdles, make the user’s life that much simpler and may I add productive, when installing programs. As a side note I observe that the GUI is a X86_64 package, the pc was a 686, so yum would exclude it, shouldn’t it? I believe that explains my side.