* Ignacio Marambio Cat?n <[EMAIL PROTECTED]> [2006-03-17 12:04]:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> >
> > Someone on the infrastructure team can develop a public procedure for
> > shutting down a list. This procedure will then get OGB blessing, and
> > be carried out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Someone on the infrastructure team can develop a public procedure for
> shutting down a list. This procedure will then get OGB blessing, and
> be carried out for each of the above lists. I'd also be happy to see
> draft process submissi
* Eric Lowe <[EMAIL PROTECTED]> [2006-03-17 11:21]:
> Al Hopper wrote:
> >On Thu, 16 Mar 2006, Mike Kupfer wrote:
> >
> >>I think opensolaris-code can just go away. It was originally created
> >
> >Agreed.
> >
> >>during the Pilot program, when there was a single consolidation and a
> >>lot fewer
Al Hopper wrote:
On Thu, 16 Mar 2006, Mike Kupfer wrote:
I think opensolaris-code can just go away. It was originally created
Agreed.
during the Pilot program, when there was a single consolidation and a
lot fewer people. When I proposed it, I thought of it as a stopgap
measure to deal wi
On Thu, 16 Mar 2006, Mike Kupfer wrote:
> > "sch" == Stephen Hahn <[EMAIL PROTECTED]> writes:
>
> sch> I think I would like to hear about how to eventually close some
> sch> of the program-wide aliases, as consolidations and communities
> sch> evolve their own code submission discussions
> "sch" == Stephen Hahn <[EMAIL PROTECTED]> writes:
sch> I think I would like to hear about how to eventually close some
sch> of the program-wide aliases, as consolidations and communities
sch> evolve their own code submission discussions.
I think opensolaris-code can just go away. It
