Changes

== Project Name Description ==

== Project Description Leaders ==

Description should be no longer than a paragraph*Brett van Gennip - bvangennip@learn.senecac. Include links to any relevant on.ca*<s>Eugene Khabian</s> -line resourcesRemoved*Vitalijs Bluzmans - vbluzmans@learn. For example,http://googlesenecac.on.com or [http://developerca*Tarinur Choudhury - trchoudhury@learn.mozillasenecac.org MDC]on.ca

== Project Leader(s) Responsibilities ==

Name(s) of primary people working on the project. If you want to join a project as leader, discuss * SPEC File Formation & Desktop Integration - Tarinur* Repository Configuration - Vitaly* Testing Minefield with other leaders first. SELinux and Fedora 13 Include links to personal pages within wiki- Brett

NOTE: only == Project Leader(s) should add names here. You '''can’t''' add your own name to the Contributor list.Details ==

* Target: Current supported Fedora releases (Fedora 13 and Fedora 14) Approach to packaging:# Pull from a standard URL (as of now http://nightly.mozilla.org/)# Package that binary nightly/beta as an RPM# Add to a repository and regenerate/update metadata Approach to repo access:# Make a repo "release" RPM that provides .repo file and public key Approach to SELinux:# Modify the RPM packaging to setup SELinux appropriately#* File labels and policy need to be managed in the RPM package Installation locations:* Must not conflict with distro-provided install locations* Should be in the standard path* Should start up with a --profile-manager* Should appear in the graphical menus, with a different name than the stable release* Make appear on the GUI menus - Minefield (Firefox nightly) - Firefox (Developer Preview) == Project Details Deployment == * Deploy on HW in CDOT initially (Chile)* Deliver scripts to Armen for deployment on Mozilla infrastructure == Release Targets ==

Provides more depth than the Project Description* 0. This is the place for technical discussions, project specs, or other details1 - Proof of concept* 0. If this gets very long, you might consider breaking this part into multiple pages and linking 2 - Cleaned-up release* 0.3 - Scripts delivered to them.Armen

Goals * 0.1 - Proof of concept Fully working proof of concept including early mock up of nightly RPM and repository installation RPM. === Progress made on 0.1 Milestone === Please see our latest blog posts on the status of milestone 0.1. This wiki will feature a brief overview of how the project is progressing. ==== Brett van Gennip - Testing Minefield with SELinux and Fedora 13 ==== Brett had downloaded Minefield and attempted to replicate the error message that was coming up for people. Overall, he had no success making the error message show up which proved to be a bit of an issue to how he can understand the issue. Certain things came up such as: while running firefox, Minefield would not open. While running Minefield, firefox would not open. At no point was he able to run both at the same time. Overall, he plans to speak with people on IRC to try to make some sense of these issues.  Please see blog for each releasemore details:* [http://brettvangennip.wordpress.com/2010/11/05/0-1-repository-setup-for-firefox-nightly-and-betas/ Minefield and Firefox] ==== Tarin - RPM Building and Repository Setup ==== Tarin had setup the Repository and made it so that you are able to download the nightly via iraq.proximity.on.ca repository. He has also packaged the nightlies in an RPM format. Which means that he has created a SPEC file for the RPM to work with Fedora 1x machines in both 32 bit and 64 bit architectures. Our repository is located at [http://iraq.proximity.on.ca/ffrepo/ Nightly Repository]. Please see blog for more details: [http://tarinc.wordpress.com/2010/11/05/milestone-1-continued/ Milestone 1 Continued] ==== Vitaly - Building Firefox/Fedora Repository ==== Vitaly had setup the Repository on one of the servers in Seneca's open source room locations. He had proceeded in creating a script that will automate the process of setting up the repo's into the directory for which they are to be downloaded from.  Our repository is located at [http://iraq.proximity.on.ca/ffrepo/ Nightly Repository]. Please see blog for more details: [http://vbluzmans.wordpress.com/2010/11/05/in-quest-of-building-firefoxfedora-repository/ Building Firefox/Fedora Repo] * 0.2- Cleaned-up release Finalize spec files and implement automation. === Progress made on 0.2 Milestone === Please see our latest blog posts on the status of milestone 0.2. This wiki will feature a brief overview of how the project is progressing. ==== Tarin ====[http://tarinc.wordpress.com/2010/11/25/release-0-2-update/ Release 0.2 Update] * 0.3- Scripts delivered to Armen === Progress made on 0.3 Milestone === Please see our latest blog posts on the status of milestone 0.3. This wiki will feature a brief overview of how the project is progressing.

This ''' November 12th, 2010 ''' - EUGENE IS Back - STATUS: (BRETT) setup a different profile for That i run firefox and minefield together the way i just describe it. what does he want ? can we do it or is where your regular updates will gothe builders Responsibility to figure it out.. . or does it even matter TARIN > It sounds like it is related to profiles TARIN IS Compiling 32 bit minefield on ChileTARIN IS Compiling 64 bit minefield on IRAQ Problems :  REVISIT SPEC FILE - Figure out how to make it more Vitaly - Figure out signing of public keys - password: In these senecaCdotEugene - make a spec file by the end of the day  '''October 12th 2010 Notes''' * BUGZILLA - 600317 lists.fedoraproject.org/mailman/listinfo Problem --> When you should discuss download the status or your work, your interactions with other members nightlies you get a set of source code. This is inconvenient and adds another step for people to start testing the nighties and Beta versions of the community (esoftware.g WE NEED betas to co-exist with the firefox Original working package.  '''Day One Notes - October 8th 2010'''Project:Repository Setup for Mozilla Nightlies and Betas Many web developers want access to the latest Firefox pre-releases, Seneca including the nightly builds and beta releases. Mozilla)'s build team wants to make these accessible as parallel-installable binaries, problems you have encountered, etcreleased through a Fedora-compatible repository. This project involves setting this up.  Subprojects:  * Build configuration for the RPM files. * Repository configuration RPMs.* Getting SELinux to work with the nightlies.   Website --> [http://nightly.mozilla.org/ Firefox Nightlies] point 1 install repositories installing a YUM system to grab Point 2 installation of the Repositoriespoint 3 create account on bugzilla 2 repositories for x86 and 64-bit -->producting the rpms  Creating spec files for nightlies ... pull in nightly build and package automate it using a script from the website  repository setup -> signing it -->  create the rpm for the repo seperate nightlies and beta?? AND x86 and 64-bit ??

Put detailed technical information into --> Problem --> Getting SELinux to work with the Project Details page (i.e., update it as you go), and save this section for news about participation in the projectnightlies.