Advertisement
Guest User

Untitled

a guest
May 7th, 2013
77
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.93 KB | None | 0 0
  1. On Wed, 2013-04-24 at 09:01 +0100, Richard Purdie wrote:
  2. The TSC talked about it and agreed a particular direction. Its clear
  3. that some people don't like the direction so they just ignored it and do
  4. their own thing anyway.
  5.  
  6. This is the wrong way to go about making decisions and I'm extremely
  7. disappointed people are doing this.
  8.  
  9. It's maybe worth pointing out that this change was discussed on the
  10. mailing list at the time. During that thread, two members of the
  11. TSC spoke in favour of the change and neither they nor anybody else
  12. pointed out that it was contrary to the TSC's stated policy.
  13.  
  14. So, although I agree it is a bit unfortunate that meta-oe has decided
  15. to go off and plough its own furrow, it doesn't seem that the TSC made
  16. much of an effort to dissuade them at the time and I can understand how
  17. Martin might have interpreted the responses he got as approval.
  18.  
  19. At this point I assume I'm free to ignore the TSC since we now have
  20. precedent for it?
  21.  
  22. As far as I know you've always been free to do that. It's up to the TSC
  23. to enforce its own decisions if it wishes to.
  24.  
  25. All that said, I have had a suspicion for a while that the TSC is
  26. perhaps becoming superfluous to requirements. When the TSC was first
  27. set up, the environment within which OE operated was very different:
  28. this was a time before the Yocto Project and before oe-core, when
  29. everything was in a single tree, a vast number of people had
  30. indiscriminate commit access, and there was no identified maintainer who
  31. was empowered to make decisions about which patches went in and which
  32. didn't.
  33.  
  34. Nowadays it seems (and I don't intend this as a criticism) that most of the
  35. technical direction is coming from the Yocto side and the OE project
  36. itself is mostly just going along for the ride. Plus, every layer does
  37. now have its own maintainer so the original power vacuum that the TSC
  38. was created to fill no longer exists. In this sort of scenario it seems
  39. as though OE is rather over-equipped with governance mechanisms (the
  40. TSC, the e.V. board and the e.V. membership itself) that aren't
  41. necessarily accomplishing very much.
  42.  
  43. Also, now that we have a multiplicity of layers rather than a single
  44. monolithic tree, it isn't entirely obvious where the TSC's authority
  45. begins and ends. I think everyone would agree that oe-core falls under
  46. the aegis of the TSC, but beyond that it isn't totally obvious which
  47. layers do and don't count as part of "OE" for that purpose.
  48.  
  49. And finally, it's been apparent during the last few TSC and board
  50. elections that it is a bit of a struggle to attract high-quality
  51. candidates to stand for membership of either body. I don't think we've
  52. had an election which was actually contested for quite some time: this
  53. makes the elections themselves seem like just a waste of everybody's
  54. time.
  55.  
  56. So, maybe it's time that we as a project had a bit of a re-think
  57. regarding what sort of governance structures we actually need and want
  58. in this day and age.
  59.  
  60. p.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement