[samba-soc] Email, Dates, Keys, & SCM

Tue Jun 6 15:41:13 GMT 2006

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

WARNING!  Extremely long mail to follow....

If you have questions or problems please email me
(and CC the list).

cheers, jerry

Deadlines
=========

For all involved devs and mentors -- These are the dates
set by Google.

June 30, 2006:
- - All mid-program evaluations of student progress due
  by 17:00 Pacific Daylight Time
- - Google begins issuing mid-term student payments

OSCON, July 24-28, 2006:
- - Google gives community update at OSCON 2006

August 21, 2006:
- - All student projects due by 08:00 Pacific Daylight Time
- - Final mentor evaluations of student progress commence
- - Student evaluations of mentors commence

September 5, 2006:
- - All mentor and student evaluations due by 08:00 Pacific
  Daylight Time
- - Google begins issuing final student payments
- - Google program administrators begin review of students'
  evaluations of their mentors

September 25, 2006:
- - Google begins issuing payments to mentoring organizations

For devs working with me, I'll finish the review of
your requirements in a few hours hopefully.

For all projects, let's set the following milestone dates.
Consider all times in GMT.

Milestone #1   = 23:59pm, June 28, 2006
Milestone #2   = 23:59pm, Aug 4, 2006
Final Code Due = 16:00, Aug 21, 2006

I will take snapshots of your source trees on the final
deadline for review.

Email & Usernames
=================

I thought I could find some way to publish bzr trees
without requiring ssh.  Can't seem to find it. So I need
ssh keys from everyone after all.  Details on generating
keys are later in this mail.

And if you have a preferred username, let me know.  Right
now I'm just using a variant of first initial + last name
or the email address listed on your SoC project.  You
will then each have a $username at samba.org email address
which forwards to the addr from your SoC proposal.

Keys
====

What I need from everyone is a GPG signed ssh2 key.  This
is for all project developers.  If you aren't familiar
with how this works, here's a quick overview.

Generate the ssh key:

$ ssh-keygen -b 1024 -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/lizard/.ssh/id_rsa): <ENTER>
Enter passphrase (empty for no passphrase): <ENTER PASS>
Enter same passphrase again: <REENTER PASS>
Your identification has been saved in /home/lizard/.ssh/id_rsa.
Your public key has been saved in /home/lizard/.ssh/id_rsa.pub.
The key fingerprint is:
ad:9f:c1:cd:52:76:c9:f1:e5:44:42:0b:9b:b8:09:be lizard at rain

Generate the gpg key:
(http://webber.dewinter.com/gnupg_howto/english/GPGMiniHowto.txt)

$ gpg --gen-key

gpg (GnuPG) 1.4.0; Copyright (C) 2004 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

<...just use the defaults for the next few prompts about key type
and expiration period...>

Real name: Lee Zard
Email address: lizard at samba.org
Comment:
...
pub   1024D/B19B246E 2005-06-27
	Key fingerprint = B9AB EBD1 AD4B 0059 30B8
			  FD9B 87B7 8B73 B19B 246E
	uid   Lee Zard <lizard at samba.org>
sub   2048g/74380834 2005-06-27

Now upload the key to a keyserver.  Your key ID is the last 4 bytes
of the key fingerprint (B19B246E in this case).

$ gpg --keyserver pgp.mit.edu --send-key B19B246E

Now sign you ssh public key
$ cd ~/.ssh
$ gpg --detach-sign --armor id_rsa.pub

You need a passphrase to unlock the secret key for
user: "Lee Zard <lizard at samba.org>"
1024-bit DSA key, ID B19B246E, created 2005-06-27

Now email me the two files: id_rsa.pub, id_rsa.pub.asc

Bazaar-NG
=========

Once we have keys setup, you will need to install bzr &
the bzrtools plugin set.  Details are at
http://bazaar-vcs.org/Download?action=show&redirect=DownloadBzr
Note that we are working on a report of having problems
using bzr with a proxy server.

Once you have bzr setup, here is the fastest way to
get started.

Download the appropriate tarball from
http://www.samba.org/~jerry/bzr/archives and unpack it.

Then create your own local branch:

$ mkdir ~/src && cd ~/src
$ bzr branch "path to unpacked bzr tree" samba-soc

The merge any recent changes from the official tree

$ cd ~/src/samba-soc
$ bzr merge http://www.samba.org/~jerry/bzr/SAMBA_{3,4}.bzr
(depending on which tree you are working on.
$ bzr commit -m "sync with main tree"

Now you have a working, local tree.  Bzr will remember
the last location merged from so you don't have to inlude
the full URL after the first one.

Once we have the ssh acces setup, you will be able
to publish your tree at http://people.samba.org/bzr/$username/

Make sure you have the rspush plugin install correctly.

$ bzr help rspush

Also make sure that your permissions are ok.  I'm attaching
a simple script to add work read/execute perms to a tree.

$ fix_bzr_perms ~/src/samba-soc

Now publish the tree:

$ cd ~/src/samba-soc
$ bzr rspush $username at people.samba.org:/data/bzr/$username/samba-soc

I would like to see everyone using bzr have a published
tree (even if you have no code to show yet) just so I know
things are working ok.  Let's try to have this done by
23:59 pm, Wed, June 7.  That gives us about 36 hours.
Not critical, but I'd like to make sure everyone has the
access and tools they need.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEhaIZIR7qMdg1EfYRAmwiAKCwSC8vmxB52sCSsb5U3GSl/qcH4wCgivW5
iA99N7/xu0hJ1GPbig2zG2k=
=WbMP
-----END PGP SIGNATURE-----
-------------- next part --------------
#!/bin/bash

REPO=$1

## check command line args

if [ "x${REPO}" = "x" ]; then
	echo "Usage: $0 <bzr_dir>"
	exit 1
fi

## check for a valid bzr repo

if [ ! -d ${REPO} ]; then
	echo "${REPO} is not a directory!"
	exit 2
fi
bzr info ${REPO} 2>&1 > /dev/null
if [ $? -ne 0 ]; then
	echo "${REPO} is not a bzr repo!"
	exit 2
fi

## Set permissions

find ${REPO} -type d -exec chmod 755 {} \;
find ${REPO} -type f -exec sh -c "chmod g+r,o+r {}; if [ -x {} ]; then chmod g+x,o+x {}; fi" \;