2010-03-05 Meeting Agenda

From ArchServer Wiki

Jump to: navigation, search

When and where

The 2010-03-05 meeting, is the first official Archserver meeting, held in #Archserver-meeting on the Freenode network at 23:00 UTC.

The log for this meeting can be found on http://irclogs.archserver.org/archserver-meeting/2010-03-05 as well as http://irclogs.archserver.org/archserver-meeting/2010-03-06 (note: the meeting started 2010-03-05 at 23:00 UTC and ended 2010-03-06 at around 01:45, thats why there are two links).

Agenda

Please add anything you think needs to be discussed.

Item Description Responsible Person Notes Due Date Decision
Kernel LTS or Standard upstream? CentOS? Debian? Right now we are using the "normal" kernel of AL, 2.6.32, this will be the next LTS kernel maintained by the Kernel Devs. Should we stick with this and/or provide more patches then this kernel? We are sticking to Kernel 2.6.32 (which will be the official LTS-kernel of AL and a lot of other distros).
ArchServer Package Portal General discussion. Licence? Shadowbranch CMS has been tested to work with PostgreSQL, working on front-end for current dev maintained packages. Then adding AUR style additions. sbnet is going to prepare a short demo by next week.
Installation ISO Current Status triplem The iso itself is working, we need to put more work into AIF and the adaption of this for ArchServer. The following additional actions have been decided:
  • 'nicedream' and faelar_AS to follow up: test the installation ISO on a USB stick and report their results back to triplem and/or jowilkin
  • 'fukawi2' to follow up: to test the installation ISO on real hardware and report their results back to triplem and/or jowilkin
  • 'ras0ir' to follow up: file an enhancement request on the bug tracker to investigate dual-arch iso for a future release
Licenses Current Status Actions:
  • 'fukawi2' to follow up: next meeting agenda: docs licensing
  • 'fukawi2' to follow up: update motd and issue.ssh to a simpler ArchServer "advertising" message
  • 'fukawi2' to follow up: fix double display of motd and issue.ssh when logging in through SSH
Decisions for Package Additions we need to decide on a process, this should be a short discussion to gather ideas, on how these decisions could be made triplem IMHO, we should provide a process on how to decide which packages in which version do come into the main repositories and what to put into the server-community repo. Could be done through a four/six-eye principal, meaning, someone suggests a package and two TUs agree on this package. At least one TU is needed which maintains this package. Decisions:
  • at least 2 TU should agree that a package should be added
  • and one TU must be willing to maintain it
  • right now, we are using the TU mailing list for this process, but this process should be handled by the APP in the future as well (-> see Actions on the topic Sign-Off of Packages).
  • There was an unclear point in which repository contains which package (-> Forum)

Actions:

  • Discussion to make clear which package is contained in what repository in our forum (see link above).
Sign-Off of Packages we need to decide on a process to provide sign-offs and reviews for all PKGBUILDS, here we should just discuss and gather some ideas Maintenance of 'ChangeLog' files. Script to monitor. Decisions:
  • sign-off is done on the tusers mail list, by 1 dev requesting sign-off, and (at least) 2 other devs sign-off after testing it themselves
  • this process it moved to the APP once we can code it in

Actions:

  • 'sbnet' to follow up: investigate writing a package nomination and adoption module for the APP
  • 'sbnet' to follow up: investigate package sign-off process for the APP
Upstream bugs/changes We need a more formal/automated way to track bugs upstream or in Arch Linux. jowilkin This could include scripts to compare our packages to AL packages or compare the version of our packages to upstream latest stable versions (a la Frugalware). Moved to next meeting --> see Forum Entry
Uploads ISOs and other stuff into binary repository It would be good to provide md5s for important downloads (e.g. ISOs, VBox Images). Can we make this "automatic"? Moved to next meeting
Infrastructure Report General update on the infrastructure of the project. fukawi2 Informations/Decisions:
  • We do own a 32bit HP DL380 G3 (in AU) and we are going to provide this as a part of our build farm as well as a replacement for the current Lithium, as a 64bit solution, we are waiting for a replacement from Phillip (this is not yet decided and the timeframe is open), or if this will not come, we are offered a 64bit Environment from jowilkin, which could be used as an interim solution.
  • Leaseweb provides a Dell R200 (Quad-core Intel Xeon 2.16g, 1gb RAM, 2 x 160gb HDD) dedicated server (incl. 300Gb traffic) for 45€/month (Hydrogen).
Financial Report General update on the project financial status. fukawi2
Retrieved from "http://wiki.archserver.org/index.php/2010-03-05_Meeting_Agenda"
Personal tools
Toolbox