From Fedora Project Wiki

No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
You could definitely move this into the Template: namespace, then instruct users to use the <nowiki>{{subst}}</nowiki> system of importing a template. More information at [https://secure.wikimedia.org/wikipedia/meta/wiki/Help:Substitution]. --[[User:Ianweller|Ian Weller]] 03:48, 16 January 2009 (UTC)
You could definitely move this into the Template: namespace, then instruct users to use the <nowiki>{{subst}}</nowiki> system of importing a template. More information at [https://secure.wikimedia.org/wikipedia/meta/wiki/Help:Substitution]. --[[User:Ianweller|Ian Weller]] 03:48, 16 January 2009 (UTC)
* [[User:Bruno]]: I think the template could use some more examples or documentation of what is expected in some of the sections.
* [[User:Bruno]]: The information about linking to a kickstart file should have an example of how to link to the git repository in the desired manner.
** [User:Bruno]]: It isn't clear to me what is expected in the details section. Is this where you should include the rational for which packages are going to be included?
 
** [User:Bruno]]: How are the kickstart file contents supposed to be referenced? Is this the source, a link to the source in say the git repository. What happens when a spin is in more than one release?
** [[User:Bruno]]: It seems odd that scope and testing are combined. I would expect scope to cover non kickstart things that need to be (or won't be) done for the Spin. I would expect testing to cover a rough test plan for things unique or especially important to the spin.
** [User:Bruno]]: What kind of dependencies are to be included. Is this a list of bugzilla's for included packages with problems, dependencies on proposed features for the release, something else?
* [[User:Bruno]]: I am not sure why there isn't a status section. Does status kinds of things fall under the dependencies section? If so is it expected to be more verbose about the status in the dependencies section or just links to bugzillas that people need to follow to get the current status. Also when dependencies get completed do they get removed, some comment added or just keep a link?
** [User:Bruno]]: It seems odd that scope and testing are combined. I would expect scope to cover non kickstart things that need to be (or won't be) done for the Spin. I would expect testing to cover a rough test plan for things unique or especially important to the spin.

Latest revision as of 14:49, 2 February 2009

You could definitely move this into the Template: namespace, then instruct users to use the {{subst}} system of importing a template. More information at [1]. --Ian Weller 03:48, 16 January 2009 (UTC)

  • User:Bruno: The information about linking to a kickstart file should have an example of how to link to the git repository in the desired manner.
    • User:Bruno: It seems odd that scope and testing are combined. I would expect scope to cover non kickstart things that need to be (or won't be) done for the Spin. I would expect testing to cover a rough test plan for things unique or especially important to the spin.
  • User:Bruno: I am not sure why there isn't a status section. Does status kinds of things fall under the dependencies section? If so is it expected to be more verbose about the status in the dependencies section or just links to bugzillas that people need to follow to get the current status. Also when dependencies get completed do they get removed, some comment added or just keep a link?