[samba-soc] first cup of coffee, ssh, gpg, & email

[Gerald (Jerry) Carter]

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

Morning (for those of you somewhere near GMT-5),

WARNING: Really long mail to follow....

We have everyone on the list now so let's start with introductions
and how is doing what.

Name			Project
====			=======
Amit Regmi		Samba 3 Management python Framework
Chris Nicholls		Samba 3 Implementation of libmsrpc library
Kalim Moghul		Samba 3 Rewrite of smbclient using libsmbclient
Brad Henry		Samba 4 DsSync protocol & testing suite
Jelmer Vernooij		Samba 4 Upgrade path from Samba 3 -> Samba 4
Asser Schrøder Femø	CIFS FS Dnotify support


Getting Started
===============

We will be hosting all the development on Samba.org.  No need
to setup accounts on sourceforge or somewhere else.  Most projects
will work in a temporary branch directly off the main Samba svn
repository.  The exceptions will be projects that need to maintain
a separate logical identity due to interface design, etc...
(e.g. the python framework).  Steve French will let me know how
he wants to handle the CIFS fs work.  We may just setup a new svn repo
or use the existing lorikeet one possibly.

I also need to know preference on accounts names on samba.org
if you haven't let me know already.  I'll assume first names
unless I hear differently from you by 9am tomorrow (GMT-5).
Also, I will have the username at samba.org email forwarded to
the current address listed on your application unless I hear
otherwise.


Keys
====
What I need from everyone is a GPG signed ssh2 key.  If you aren't
familiar with how this works, here's a quick overview.

(note that I'm assuming a Linux platform here.  It can be done
from Windows using putty.exe and the svn windows port.  If you
absolutely need this, let me know and I'll get in touch with
the one person I know who has done it).

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

Second cup of coffee break.....

Administrative stuff
====================

This list is mostly for administrative ddetails.  All technical discussion
should take place on the samba-technical at samba.org developer list.
So if you have not subscribed to that one yet, have a look at
https://lists.samba.org/listinfo/samba-technical.

I don't mind IRC for short questions or basic room noise, but
please keep design discussions, etc... on the mailing list.  It
provides better accessibility for people other than the 30 or so
monitoring the irc://irc.freenode.net/#samba-technical.  And
it's impossible to search IRC logs for anything worthwhile.

I am generally around on IRC (as is abartlet) but may not
answer if I am extremely busy.  Initially, I'll try to set
aside a few hours a day like office hours.  I'll try 9am - noon
GMT - 5 weekdays.  I am online weekends but I reserve the right
to ignore real work :-)

The next question is what are you goals and what are our
responsibilities?  It's pretty simple.

Our duty is to help to finish so you can get paid :-)
You job is to finish :-)

With that in mind, the first thing we need to do is to establish
a clear scope and deliverables so everyone knows what "finished"
means.  Some of you had more details in the original proposal
than others.  So some of you might have more work at this stage
than others.

Here's how the project/mentor breakdown looks:

Technical Contact	Project		
=================	=======		
Me, Deryck Hodge	Samba 3 Management python Framework
Me, Tim Potter		Samba 3 Implementation of libmsrpc library
Me, Derrell Lipman	Samba 3 Rewrite of smbclient using libsmbclient
A. Bartlett, Metze	Samba 4 DsSync protocol & testing suite
Andrew Bartlet		Upgrade path from Samba 3 -> Samba 4	
Steve French		CIFS FS Dnotify support		

So if each contact person would contact each new developer (on
this list) to start the ball rolling that would be great.  It's
also up to the technical contact if you want to setup actual dates
for milestones or not.

If anyone one either side of the fence has questions, just let me know.

I'm sure I'll remember more things later today.




cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCwArsIR7qMdg1EfYRAjLKAJ9Gh17fTtuPNF3Ha0Fe99Z9bNDowgCbB3ad
gsZDE3Jg4hyLH79S2RsPkWc=
=VIJo
-----END PGP SIGNATURE-----