From herrold@owlriver.com Tue Feb 18 11:53:30 2003 Date: Tue, 18 Feb 2003 10:43:45 -0500 (EST) From: R P Herrold Reply-To: fedora-devel@videl.ics.hawaii.edu To: Fedora Devel List Subject: [Fedora-devel] RPH 2/18 concerns: was: UPDATE: Status of Everything Else well -- not exactly -- I an concerned that you are not covering all the bases. Perhaps, once a Bugzilla is in place, there will be a more systematic approach. QA Matters ============== I posted a proposed QA outline, and there is no mention here. http://www.owlriver.com/projects/fedora/ at: http://www.owlriver.com/projects/fedora/fedora-flow.txt I have requested comment and feedback on IRC a couple times, and no substantial objection or comment has been raised negatively. But it is not mentioned here either. Anyone can post a collection of source and built RPM's -- heck -- I do it, with an express non-signed state for publicly available accesss, and a GPL disclaimer on the directory tree. On Tue, 18 Feb 2003, Warren Togami wrote: > I'm thinking about trying PHP/MySQL CMS systems like PostNuke or Drupal > for the homepage. Scripted weblog news, personal accounts with blogs, > wiki, etc. would be nice for our project to have. Does anyone have any > recommendations for a CMS? CMS - contra ====================== I think this is a mistake, because a CMS simply does not CVS well. Part of an open project and development is an open (readible) CVS or sources. > > Packages > > ======== > > It is time to include packages into the preliminary Fedora repositories. Due Diligence and Release Process ======================================== Without the due diligence of a systematic QA structure? What happens when a end user inadvertently loses their personally important data and asserts it was a Fedora package which did it? I have consciously not sought an account, for I am uneasy on this issue. Vserver Safety ==================== The protocol for setting up a clean build vserver has been alluded to several times -- but I do not see it documented. How do I ensure that only I as a builder have had access to it? Build Environment =================== How do _I_ verify that I have a clean environment? Where will the tripwire sums be maintained? Will it be nailed to a formal Red Hat release and updates? -- At what interval will updates be applied? Will it include any non RH production quality binaries (i.e., Raw Hide stuff) ever? Content of others? Trustworthiness ================= What assurance do I (and by implication the consumers of Fedora binaries) have that it is not offering a subverted tool? > > We will need to discuss peer review and package inclusion requirements, > > all stuff that should be drafted soon. 'peer review' is in part a sub-element of QA. > > For now please focus on new and useful packages for Fedora and > > conversion of FreshRPMS. I personally am working on alsa at the moment. Roadmap Need ================= Is ALSA GPL'd? Is it appropiate for inclusion in Fedora? What is the license criteria for a package to be included in Fedora? It is fun to package, harder to do the paperwork. Harder still to design first and then implement. dcran and I have spent a week on getting RPM to build on a new arch. I am relying on the promise of the payoff of documentation, which to me is worth much more than a simple package build. > Please keep submitting packages. In particular I feel it is important > to get Matthias Saou's media player packages into Fedora quickly in > order to attract the users (and thus more developers.) Fork Concern ==================== This is, essentially, a fork. That is your right as to GPL content, and Mathias has said he has no problem, generally, with it. But by definition, forked packages will cause confusion to a end consumer of FreshRPMS and Fedora -- How will an end user know which to use? -- Russ Herrold _______________________________________________ Fedora-devel mailing list Fedora-devel@videl.ics.hawaii.edu http://videl.ics.hawaii.edu/mailman/listinfo/fedora-devel