[Tracker-discuss] Getting Started

[Paul Dubois]

I have a somewhat more basic question. Who did the prototype, where are the
results of it, and what if anything needs to be done differently. What
backend, etc.

I am not experienced with subversion but I hate cvs; in particular I hate
the poor cvs branching model / behavior. For my own roundup trackers I use a
two-branch scheme:

main = distribution as received from Richard

Branch this to "ours"; when new distribution received, check it in on main
and integrate changes into "ours".

I use Perforce; Perforce will grant a free license to us as an open-source
project, I believe. However, I'm ok with Subversion as long as the branching
stuff works. This area, however, is one place where open source stuff has
not been as good as the commercial.

We have used a 'fake' user as the owner of roundup with a sudo from
individual maintainer accounts. This works fine. One has no need at all to
be root the way I do it. You build your own dedicated Python and install
into it, so that you aren't related to the root's Python on the machine.




On 10/29/06, Erik Forsberg <forsberg at efod.se> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi!
>
> I don't know if all of the "initial admins" have indicated their
> willingness yet, but you are at least all subscribed to this list - so
> let's get started working!
>
> A bunch of infrastructure- and development-related questions popped up
> in my head, so I wrote them down below. Hopefully, there's someone
> here that can answer them :-) (I did notice at least one
> upfrontsystems.co.za person in the list roster..).
>
> Infrastructure
> ==============
>
> Machine
> - -------
>
> * What kind of machine are Upfront Systems's going to host for the
>   python-dev tracker? How much CPU, memory and disk is available?
>
> * Will the python-dev tracker be the only software running on this
>   machine? (I assume so, since Brett wrote something about root
>   access)
>
> * Which Linux distribution will it run, and who will be responsible
>   to keep the system up to date with security patches etc? We, or
>   Upfront? (I prefer the latter.)
>
> * Does the machine have RAID for its disks? Is there support for
>   monitoring the disks, and who will be responsible for that?
>
> Backup
> - ------
>
> * What backup facilities are included in the hosting offer?
>
> * Are there any alternative ways to make backups, such as usage of
>   rsync, rdiff-backup or similar to some python-community-controlled
>   machine?
>
> Access
> - ------
>
> * Which protocols will be available for access to the machine? I
>   prefer using only SSH (with sftp for file transfers).
>
> On the security side, perhaps we should lock down the root account and
> use sudo to gain root credentials from individual accounts?
>
> Monitoring
> - ----------
>
> * Is there a nagios (or similar) installation somewhere that we can
>   use to monitor the tracker, its backup etc?
>
> Development
> ===========
>
> * Is there a subversion repository we could use for the development of
>   the tracker? So far we've used a module in the CVS repository for
>   roundup (on Sourceforge), but as I prefer subversion and don't enjoy
>   the "stability" of sourceforge, I'd enjoy a stable subversion
>   repository for this development.
>
> * Where should we keep our tracker bugs? I'm happy to keep the
>   http://efod.se/ptt/ (python-tracker-tracker) online if you like.
>
> Cheers,
> \EF
> - --
> Erik Forsberg                 http://efod.se
> GPG/PGP Key: 1024D/0BAC89D9
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>
>
> iD8DBQFFRPXUrJurFAusidkRAhrXAKCHt8LBaI3rbs7G+cov+7DOnEkcBwCfXPDD
> cnawo0QapBpaHMVsNiXz4l4=
> =naYd
> -----END PGP SIGNATURE-----
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061029/c46c2482/attachment.html