https://bz.apache.org/ooo/show_bug.cgi?id=3959
--- Comment #306 from Scott Kallen <[email protected]> --- (In reply to orcmid from comment #299) > (In reply to Joe L from comment #297) > > >>>> Assigned To:[email protected] <<<<< > [ ... ] > > Fire the guy this assigned to, and get someone who will promote the user > > request. > > > > (scratching head) I still don't understand why this one guy wants to stand > > in everyone's way. Does he work for M$ or it is a job beyond his ability? > > :-p ;-) > > Who says Mathias Bauer is standing in the way? > > The assignment probably existed from before Apache OpenOffice, since this > bugzilla repository was inherited from Oracle who continued it from Sun. > Please look at comments ##51, 54, 64, 76 (all in 2007) with more information > in comments ## 89, 92, 96 (in 2008) and then #224 in 2014. Mathias has not > commented on this issue since 2008. Yet you will find that he took it > seriously and analyzed how difficult it would be to do. Considering that he > was a seasoned OpenOffice developer, assuming he is a roadblock is > unwarranted as is the magical thinking that the complexity of the solution > is irrelevant to the importance of the feature to some. > > This is not a business and we don't operate on a corporate model where > people are fired. > > I have switched the assignment to the generic default so you can see there > is no one responsible for this incident. And even if someone was listed, > because they took custody of the issue, that does not mean they are > promising to implement the enhancement. Michael knew what he was doing and > he was not promising an implementation either. Obviously, circumstances > were such that the feature has never been implemented. > > To be clear. No current experienced developer has taken on assigning this > issue to themselves and figuring out how to take its development further. > There is no timeline and there is no project of the imagined kind ready to > force this enhancement into reality. > > I suggest those who find outlines to be an indispensible feature find a > product where the feature is available. Here it is at best available > someday in an indefinite and very speculative future. ... Ands this closes the subject for me. The problem here is that the coders are making the calls as to what needs to be implemented. They're basing it on ease of coding, not user need. With the comment above representing actual policy of OO, this feature will never see the light of day and I think we can all quit trying to "teach the pig to sing." It's never going to happen. Honestly the only reason I was pulling for this feature was because I was rooting for Open Source. It's done and like Linux Desktop, it will never be a major player. Too bad. So long and thanks for all the fish. -- You are receiving this mail because: You are the assignee for the issue. You are on the CC list for the issue.
