[Pkg-e-devel] some items to discuss

[Lut!n]

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

Hay there
here's a list of items I think we should discuss about in a meeting

 * Team structure / organisation
	how do we organise ourselves to work ? Maintain as a team is good, but
I think ppl could have some 'prefered' pkges though.
	maybe building the deb pkge won't be the only thing to do, so how would
we split the tasks between us / defining what we have to an write a
clear TODO

 * Builds
	What system do we choose for the builds ? I'm using pbuilder, nomed
told me about lp autobuilder network. pro / cons ?
	How do we build.Thiss will be scripted, but how. I have a bash script,
quite hackish, but I saw nomed is a python lover & pretty good in it, so
maybe he has already something ready :)
	when do we build. We should define an update rhythm. My current policy
is 1. Not more than a once-a-week update. this is mostly for end-users,
not qualified geeks. and 2. Try the pkges before uploading, that should
be replaced by a debian-style way to integrate the pkges as nomed said.
Btw I don't think stabilizing by patches and such is a good idea, given
tha amount of patches commited each day.

 * Other
	What will become the edevelop repo ? I don't want it to die. According
to shadoi's stats we're pretty well know there and I don't think it'd be
a good idea to move the primary mirror out of there. That needs to be
discussed
	TODO : we need to have a packaging policy for an easier scriptability,
we should define it for the new pacakges to add.
		adding new pkges (mainly efl-based apps)
		downgrade epochs on enlightenment and emodules (will be done within a
week)

Maybe we could define a meeting date depending on your availability

Greets,
Albin 'Lut!n' Tonnerre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFU57bIjAgwqfG8N8RAv4mAJ49UKOHEWSgYY7DocpeW31f9j2VfACfTWNm
Pm/r9nWhbi/jr6Q74mqZJy0=
=fYjQ
-----END PGP SIGNATURE-----