OpenFATE - How to get your most wanted features into openSUSE
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Alternative Title |
| |
| Title of Series | ||
| Number of Parts | 70 | |
| Author | ||
| License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/39541 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSDEM 20095 / 70
3
4
6
16
17
18
19
20
21
22
23
24
25
26
27
29
30
31
32
33
35
40
41
44
46
47
48
50
51
54
55
57
58
59
60
62
65
67
68
69
70
00:00
Projective planeLecture/Conference
00:20
Computer architectureValidity (statistics)Physical systemTrailOpen sourceProduct (business)Cartesian coordinate systemPower (physics)State of matterOpen setLecture/Conference
01:18
ArchitectureClient (computing)VotingPlanningMetadataMathematicsOffice suiteStatisticsService (economics)Electric generatorDatabaseSoftwareClient (computing)CodeProduct (business)Numbering schemeCartesian coordinate systemMereologyMultiplication signState of matterRule of inferenceObject (grammar)Query languageEvent horizonTelecommunicationData managementFormal languageComputer programmingField (computer science)Scripting languageRuby on RailsWeb applicationWeb browserServer (computing)Slide ruleBridging (networking)HookingCodeBuildingLecture/Conference
04:51
Client (computing)Open setCuboidMorley's categoricity theoremSet (mathematics)VideoconferencingConnected spaceMereologySoftware testingMoment (mathematics)Multiplication signPlanningDescriptive statisticsCartesian coordinate systemPhysical systemElectronic mailing listProduct (business)Computer configurationCASE <Informatik>Different (Kate Ryan album)Data managementStatisticsPoint cloudConsistencyWebsiteUniform resource locatorSoftware developerDatabaseSoftware bugSlide ruleSoftwareLecture/Conference
07:40
InterprozesskommunikationQueue (abstract data type)File formatField (computer science)LaptopStatisticsElectronic mailing listForm (programming)Point (geometry)Computer animation
09:28
outputAreaMathematicsExecution unitSoftwareElectronic mailing listComputer animation
09:53
MIDIPlanningComputer animation
10:06
TouchscreenGoodness of fitVotingPlanningElectronic mailing listView (database)Pointer (computer programming)Descriptive statisticsFreezingBuildingMoment (mathematics)Internet service providerPhysical systemInformationSoftware developerProjective planeConfiguration spaceWebsiteServer (computing)EmailLink (knot theory)Service (economics)Open sourceRow (database)Phase transitionOpen setInferenceAsynchronous Transfer ModeLecture/Conference
Transcript: English(auto-generated)
00:14
Hi, my name is Tom, I'm from the tools team of OpenSUSE and I want to show some new project
00:22
that we started that's OpenFade, feature tracking for community features. So it's basically about how to get your features in the next SUSE release.
00:41
We are doing feature tracking with Fade since some years, but this was just internally and at first I want to show you the history and the architecture of the Fade system and then the new OpenFade application and then how to get involved, how you can use it.
01:07
We are using Fade to manage all features for the open source products from SUSE and Novell. That means tracking the schema validation of the XML data that comes in.
01:24
To query the database, we use the XQuery language, which is a kind of SQL query language for XML data. The database also offers metadata that's, for example, product data and some other stuff that the clients need.
01:46
All features are versioned, that means we can see the complete history of each feature, what happened and who changed which data of it. Then we have, you can subscribe to notifications on changes on the features
02:03
and it also has a WebDAF server implemented to add attachments to the features. That's a big picture of the architecture.
02:22
Here, this is the part from the slide before, that's the database and all communication is happening with XML. Up until now, the people inside SUSE used the KDE client and we have some other smaller programs.
02:42
For example, many people have scripts that use the database to generate PDFs or statistics and we have written a KDE fear plus movie, so you can have on your desktop the latest changes and the latest features. The new part is this.
03:03
This is reachable from outside SUSE. We have a schema bridge here, that means that some internal data is filtered out and only open SUSE features get out. The new application that we wrote is the OpenFade web client and tagging and voting server.
03:27
The voting server is an extra server, so that also the build service can use it sometime. It's written in Ruby on Rails both applications and we have some code that can just hook in Ruby objects
03:49
and automatically get vote and taggable and we will use this for the build service too.
04:00
That's a screenshot of the KDE Fade client that has some more features than the web application. You can see here we have hierarchical features to show some dependencies between features.
04:20
Then we have fields to edit all the data that's in a feature. This client also has offline support, so that the product managers of SUSE can go to a plane and work on all features
04:42
and then save them when they are back in the network. It can also cache features, so that we don't have to load all features every time. It can show statistics and also import.
05:03
It has a connection to Bugzilla, so it can directly import bugs to the Fade database. The new OpenFade application should be the central place for tracking feature requests for OpenSUSE.
05:28
The plan is that all features that end up in the next SUSE release are in the system and can be seen by everyone and everyone can comment on them.
05:41
That's the parts of which OpenSUSE feature consists. For this it's a title. We have some tags to categorize the features. Products, description, different actors, references to Bugzilla or to other features or just URLs.
06:00
Then we have a discussion and use case and test cases are optional fields. What do you mean by actors? Actors are, we have different actors in the system. That means we have roles. You can be interested or developer or manager of a feature.
06:21
Well, why don't you call them personnel roles or something like actors, maybe network protocol? I think it's just named on my slide like this.
06:45
Now I want to show you the system. That's what you get when you go to the features.opensuse.org site.
07:01
You can see we are generating a tag cloud. You can see the most interesting tags. It seems we have the most features which are tags for the Yast. On the right side you can see the top voted features at the moment and the features that were updated the last time.
07:23
You can search for features by text. For example, when you search for Yast, you will get a list of features.
07:44
You will see when they were changed. This is what a single feature looks like. On the right side you have the voting applet. Here you can vote up, down or say you don't mind.
08:04
I can vote the feature up. You see the feature has the score of 2. We also generate some... We don't. We have a statistic queue here.
08:22
When you want to edit a feature, you can simply go here and, for example, reply to this command. All the text fields use a special rich text syntax. You can do some nice format when you enter text here.
08:43
For example, you can add a list. When you click on add command, the command gets added and you can see it.
09:00
It's not saved yet. To save the feature, you have to click here. It's a bit slow in my notebook.
09:31
It won't work because I'm not in the network. You have another feature here.
09:43
It's the my features link that will give you all features where you have clicked on watch this feature. You can get a list of the features you're interested in and can see what changes were there.
10:01
I think I showed all the features. The plans that we have for the future to implement an openfade. That's a configurable mail notification so that you can get directly notified when a feature has changed.
10:25
We will use the Hermes server for this, which is also used for other open source sites. It offers to configure your notifications. We want to add more roles for external people so that you can be assigned as developer or info provider
10:44
and can better work with the feature. We have to implement the attachment feature also for openfade so you can up and down load the attachments that are attached.
11:06
Some hints how to create a good feature request that has good chances to be implemented and to end up in the next SUSE release. It has to be a good problem description so that everyone understands what is needed.
11:25
Best thing would be to have a possible solution and to have as much pointers to links, background material as possible so that the people know what it's about.
11:43
At the moment only open source members can create new feature requests in openfade. Editing features can be done by everyone.
12:03
So what can you do with the system? You can enhance the requests that are already stored, give feedback, add tags or even help to implement a feature in fade. For example you can go to build service and prepare something in your home project
12:22
and then it will be easy to use it. Another thing is the openfade screening team that was announced on the mailing list. We tried to get a team together to screen through the existing requests and enhance them a bit.
12:52
The most important thing is that you can, when you go through the feature list and you see features that you like, please vote for them.
13:01
We will use the votes for features as base on what will get implemented in the next SUSE release. Until feature freeze which is at beta 1, we will go through the features and look at the top 15 voted features and we will implement them.
13:26
If they need to be rejected for some reason, we need a very good reason to do this. Please use the voting to express that you like a feature and don't write a comment that says
13:44
yes, cool, I want this too because this clutters the whole discussion and the developers can't get a quick view on the feature.
14:01
The whole system is open source so it can also be used for other projects. I have the links here. Thanks for listening and maybe there are some questions.