[opensuse-project] Feature implementation details
Hi! As we now have openFate, it is finally much clearer what will end up in the next release. However, Fate lacks one part of the information - how is a feature implemented. I believe the best way to provide this information is using openSUSE wiki. But I did not find any structure in Wiki where it would fit. Did I overlook something or should we create e.g. en.opensuse.org/Features/... and link features from openFate to these pages? Any other suggestion? Stano -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Am Montag, 9. Februar 2009 15:59:39 schrieb Stanislav Visnovsky: Hi Stano,
As we now have openFate, it is finally much clearer what will end up in the next release. However, Fate lacks one part of the information - how is a feature implemented.
I believe the best way to provide this information is using openSUSE wiki.
I disagree. The best place for this information is Fate. The description field gives us all we need to structure the text and add a paragraph "And this is how this is implemented:". Adding this to the features' description helps all involved parties such as documenter and tester dealing with features. And all in all this kind of information should really be part of a DONE feature.
Did I overlook something or should we create e.g. en.opensuse.org/Features/... and link features from openFate to these pages? I would not be a fan ;-)
Klaas -- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Klaas Freitag wrote:
Am Montag, 9. Februar 2009 15:59:39 schrieb Stanislav Visnovsky: Hi Stano,
As we now have openFate, it is finally much clearer what will end up in the next release. However, Fate lacks one part of the information - how is a feature implemented.
Stano, i'm not sure what you mean with "how", but i guess you mean "what will be the outcome" of implementation...
I believe the best way to provide this information is using openSUSE wiki. I disagree. The best place for this information is Fate. The description field gives us all we need to structure the text and add a paragraph "And this is how this is implemented:". Adding this to the features' description helps all involved parties such as documenter and tester dealing with features. And all in all this kind of information should really be part of a DONE feature.
+1 vote! IMHO we should (at least try to) specify exactly (in some appropriate level of detail) when we can consider the feature done. And this should be done in the feature (openFate) itself and it should be done _before_ the implementation starts. It might not be easy for some cases, but it's important. Except knowing when to close the feature as done it will help us to better estimate the efforts, and QA and users testing the feature will know what to test/expect. I pretty much hope this will become a standard part of the process :O) - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkma5DYACgkQgEhGpmN+6QHh/gCeLdfJwupRON1CrY/uEKXfHTxS puoAnR8Jk2nmHjAqYR5WtpCiYPUaym/t =N/MU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Mon, 2009-02-09 at 15:59 +0100, Stanislav Visnovsky wrote:
Hi!
As we now have openFate, it is finally much clearer what will end up in the next release. However, Fate lacks one part of the information - how is a feature implemented.
Hmm. Although I'm not a developer, I would think that openFATE would be
an easier experience for detailing how to implement a feature - in the
same way that mailinglists and Bugzilla are over the wiki. You can see
who is developing what, what the ideas are, all in a 'conversation'
format.
--
Kevin "Yeaux" Dupuy - openSUSE Member
Public Mail:
On Tue, Feb 10, 2009 at 12:59 AM, Stanislav Visnovsky
Hi!
As we now have openFate, it is finally much clearer what will end up in the next release. However, Fate lacks one part of the information - how is a feature implemented.
I believe the best way to provide this information is using openSUSE wiki. But I did not find any structure in Wiki where it would fit.
Did I overlook something or should we create e.g. en.opensuse.org/Features/... and link features from openFate to these pages?
Any other suggestion?
Stano
There are obvious advantages to the wiki and to fate. Separating them isn't ideal (it almost always leads to things getting out of sync), so my suggestion would be wiki-fate! :D It'd be really nice to have all original fields editable as a wiki (ideally with the same wiki software?). (And comments editable by owners) This way the feature request can really be more accurate, and progress tracked. And often you have pretty crappy/vague feature requests and if that feature is to go ahead -- it's pretty messy looking at the original request. So it'd be nice to have this in a wiki format, while retaining the whole fate structure. Just an idea :) -- Eric Springer, PGP Fingerprint: 097D E98D 9278 FE86 2659 2959 DA9E 90BD F183 2F88 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
participants (5)
-
Eric Springer -
Jan Kupec -
Kevin Dupuy -
Klaas Freitag -
Stanislav Visnovsky