System Wide Changes

Toshio Kuratomi a.badger at gmail.com
Wed Mar 5 16:20:00 UTC 2014


On Wed, Mar 05, 2014 at 06:56:56AM -0500, Jaroslav Reznik wrote:
> ----- Original Message -----
> > On Thu, Feb 27, 2014 at 03:27:37PM +0100, Marcela Mašláňová wrote:
> > > Hi,
> > > I thought we could prepare all our goals as system wide changes and
> > > some could be left out for addition in next Fedora if we can't make
> > > it.
> > > 
> > > We discussed only additional repo and SCL, but other goals can be
> > > also prepared by people from our group even if we didn't discuss it
> > > yet. For example Reviews or Taskotron don't depend on small group
> > > going to meetings. Do you want to pick tasks and start working on
> > > proposals right now or discuss everything on meetings?
> > > 
> > Note: We should be sending fesco notice of things that we intend to do for
> > F21 *before* the Change deadline.  (Officially... the 3rd of March which has
> > just passed.  But better late than never.)  In particular, if anything we're
> > thinking of has any chance of being a change to how we make or conceive of
> > fedora (as opposed to jsut changes to things inside of fedora) then it
> > should have been proposed to fesco already.
> 
> Well, my intentions and how I presented it to FESCo was - the first deadline,
> come with what you'd like to change in the form of Technical Specs, updated
> PRD etc. And the month after should that "and now - create formal Change
> proposals from these documents".
>
I'm not sure whether I understand you or not.  These are the sentiments that
we expressed at the last FESCo meeting:

18:18:35 <mattdm> abadger1999 the changes process is how we make changes to
how fedora is produced, right/
18:18:37 <mattdm> ?
18:19:02 <abadger1999> mattdm: Not that I've been thinking... I've been
thinking that the Changes process is what is changing within fedora.
18:19:45 <abadger1999> mattdm: The changes to how fedora is produced
continue to be due on Mar 3 and then we work out with releng/infra/etc which
of those things are doable in our timeframe.
18:20:35 <nirik> abadger1999: right, but those things we do do, we also make
into 'changes' so we can track them and have people following them, etc.
18:20:52 <abadger1999> nirik: <nod>  That would be fine for me.
18:21:25 <abadger1999> I just don't want to see new changes to how fedora is
produced for the first time on April 7th
18:21:25 <abadger1999> I just don't want to see new changes to how fedora is
produced for the first time on April 7th


18:29:42 <nirik> #agreed  Fedora Changes Process submission deadline for
system-wide changes is April 7th.  Deadline for true standalone changes will
be sometime later than that.  Changes to how fedora is produced for
fedora.next are still due on March 3rd. (+7,0,0)

18:30:20 <abadger1999> mitr: My feeling is we wnat to have an outline of "We
want these new things" on Mar3rd.   fesco and wg's work out details of what
is needed to implement those new things between then and april 7th.  Have
some plans with contingency plans by april 7th.

As an example, I think that the Cloud Changelist:
https://fedoraproject.org/wiki/Cloud_Changelist

fits the need of having an outline of the Changes to how Fedora is to be
produced.

I tried to make sure that this section of the Playground Repo draft also answered those
questions:
http://fedoraproject.org/wiki/Env_and_Stacks/Playground_repository_(draft)#Identified_needs

At FESCo we decided that we didn't need to have all of the needs and
interactions of changes to how Fedora is produced worked out completely
today but we did want to have them identified.  We do not want any surprises
on April 7th.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/env-and-stacks/attachments/20140305/97086520/attachment.sig>


More information about the env-and-stacks mailing list