From Fedora Project Wiki

(jreznik's answers part 1)
Line 7: Line 7:
'''Sandro Mathys - BOARD'''<br/>
'''Sandro Mathys - BOARD'''<br/>
In my opinion the current policy is the correct approach and should be adhered to.
In my opinion the current policy is the correct approach and should be adhered to.
'''Jaroslav Reznik - BOARD'''<br/>
I support our effort/policies to not bundle libraries (and currently fighting with surgery of such a library ;-). The real question is - what can we do if we're not able to unbundle libraries, especially for the first class packages like Firefox and upstream is not responding to our needs. Exceptions should be granted temporary, case-by-case (no free ride for any package) and raised upstream. In case of no reply (one release time?)- we should act even it would mean breaking some features/packages. Top case is Firefox - as I understand it correctly, it's not like they refuse unbundling libraries (some are unbundled already) but some people refuse to do - upstream is probably lacking any policy. I think one, two releases timeframe is ok to make it better. 


=== What ideas do you have related to the implementation of the stable updates vision? ===
=== What ideas do you have related to the implementation of the stable updates vision? ===
Line 12: Line 16:
'''Sandro Mathys - BOARD'''<br/>
'''Sandro Mathys - BOARD'''<br/>
While I understand the need for stability, I think Fedora is well-known and popular for being bleeding-edge. Many developers and users feel that Fedora is becoming too stable recently and not the place to develop new things anymore. The stable updates vision recommends such users to use rawhide instead but I think that's very often a tad too broken for most people so we'd need something in between, similar to the branches of future releases but implemented as a rolling release like rawhide.
While I understand the need for stability, I think Fedora is well-known and popular for being bleeding-edge. Many developers and users feel that Fedora is becoming too stable recently and not the place to develop new things anymore. The stable updates vision recommends such users to use rawhide instead but I think that's very often a tad too broken for most people so we'd need something in between, similar to the branches of future releases but implemented as a rolling release like rawhide.
'''Jaroslav Reznik - BOARD'''<br/>
I support any effort that makes our systems more "stable". But I don't think current implementation covers everything what's needed as I think it's much more deeper and wider problem - just banning updates does not work (even it can look like from some povs). It goes up to our release process (what is the use for usually not usable Rawhide and two!!! hyper conservative releases out the wild for example?), to our tools - auto qa, auto rebuilds notifications to documentation (all changes has to be properly communicated!). I know it's a big (huuuuuge) task but it's not possible to decouple it -> I don't like current implementation. We are just loosing our flexibility.


=== Is there any new initiative you would like to see happen during your term to improve packaging? ===
=== Is there any new initiative you would like to see happen during your term to improve packaging? ===
'''Jaroslav Reznik - BOARD'''<br/>
I'd like to see the same packaging process for pre-review time and post-import time (same process). Now with dist-git I think it's much more feasible. Something like OBS would be nice to have too but I know, manpower...


=== Do you think it's important to have more people vote in Fedora elections? If so, how would you encourage that? ===
=== Do you think it's important to have more people vote in Fedora elections? If so, how would you encourage that? ===

Revision as of 15:15, 8 November 2010

Candidates should add their responses directly on this wiki page.
Please note that not all questions need to be answered, e.g. a FAmSCo candidate should not need to answer very technical questions.

Main questions

What is your take on bundled libraries?

Sandro Mathys - BOARD
In my opinion the current policy is the correct approach and should be adhered to.

Jaroslav Reznik - BOARD
I support our effort/policies to not bundle libraries (and currently fighting with surgery of such a library ;-). The real question is - what can we do if we're not able to unbundle libraries, especially for the first class packages like Firefox and upstream is not responding to our needs. Exceptions should be granted temporary, case-by-case (no free ride for any package) and raised upstream. In case of no reply (one release time?)- we should act even it would mean breaking some features/packages. Top case is Firefox - as I understand it correctly, it's not like they refuse unbundling libraries (some are unbundled already) but some people refuse to do - upstream is probably lacking any policy. I think one, two releases timeframe is ok to make it better.


What ideas do you have related to the implementation of the stable updates vision?

Sandro Mathys - BOARD
While I understand the need for stability, I think Fedora is well-known and popular for being bleeding-edge. Many developers and users feel that Fedora is becoming too stable recently and not the place to develop new things anymore. The stable updates vision recommends such users to use rawhide instead but I think that's very often a tad too broken for most people so we'd need something in between, similar to the branches of future releases but implemented as a rolling release like rawhide.

Jaroslav Reznik - BOARD
I support any effort that makes our systems more "stable". But I don't think current implementation covers everything what's needed as I think it's much more deeper and wider problem - just banning updates does not work (even it can look like from some povs). It goes up to our release process (what is the use for usually not usable Rawhide and two!!! hyper conservative releases out the wild for example?), to our tools - auto qa, auto rebuilds notifications to documentation (all changes has to be properly communicated!). I know it's a big (huuuuuge) task but it's not possible to decouple it -> I don't like current implementation. We are just loosing our flexibility.

Is there any new initiative you would like to see happen during your term to improve packaging?

Jaroslav Reznik - BOARD
I'd like to see the same packaging process for pre-review time and post-import time (same process). Now with dist-git I think it's much more feasible. Something like OBS would be nice to have too but I know, manpower...

Do you think it's important to have more people vote in Fedora elections? If so, how would you encourage that?

Sandro Mathys - BOARD
Yes, definitely. I would try to increase the awareness of just how important it is to vote in elections but I think in the end the real problem is that people just don't vote even if they now why they should. Probably only some kind of directly connected reward would help to chance that but unfortunately I can't come up with a good idea on how that could look like.

Do you run Fedora on the computer you use most often? If so what Desktop? If not, why not?

Sandro Mathys - BOARD
Yes, I do - actually Fedora 14 with the lovely KDE desktop is running on all of them: my office workstation, my home workstation (there's also a win7 for fancy gaming purposes on that one, though), my laptop and my netbook.

Marcus Moeller - FAmSCo
Yes, I run the latest version of Fedora (managed with Spacewalk) on my office PC and mixed Versions of Fedora at home.

Do you think Fedora should focus on the Desktop? Or someplace else? If so, where?

Sandro Mathys - BOARD
Focusing sounds much like we should stop doing what we're good in - to allow everyone to work on everything. I sure think Fedora should focus more on the desktop than on servers, but as long as there's someone thinking Fedora should become the #1 server distribution why stop them working on that goal? Better have some features that only a few people ask for than missing features a lot of people would need.

Marcus Moeller - FAmSCo
Fedora is a good choice for a lot of tasks, e.g. desktops but even servers. If you are in need of running the latest version of http, php or mysql why not stick with Fedora?

What do you think of the Community Working Group that was just established?

Sandro Mathys - BOARD
I like the CWGs purpose very much and I offered to serve in it myself. Nevertheless, I'm not exactly sure whether the tasks for the CWG are not actually tasks of the board, the steering committees and the mentors. But the people who decided to create the CWG thought about that already for sure. Maybe a clearer delimitation should be made but I think what the CWG really does and is responsible for will only become clear once it's been actively working for a while.


What if anything would you do about the number of more seasoned contibutors that are reducing involvement in the project?

Sandro Mathys - BOARD
Getting Fedora back into a state where things (can) get done and where bleeding edge is lived.


In one sentence, can you summarize what the Board does and in another what FESco does and in a third what FAmSCo does ?

Sandro Mathys - BOARD
The board works on the vision of Fedora and the strategy to get there (and eventually to implement the non-technical points in the strategy). FESCo works on how to implement the strategy, mostly from a technical point of view. FAmSCo works on the strategy, and supports the implementation of it, regarding the ambassadors' main task which is to promote Fedora locally.

FAmSCo Questions

FAmSCo_questionnaire