Drew Jensen wrote:
Guess what... This is exactly what we had done! Have a look here:
http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=21839
fine
and, for more current information, here (Italian)
http://wiki.plio.it/mediawiki/index.php?title=Firma_Digitale
no help because i can't understand it (it would be nice but i can't
speak Italian)
??? - weak at best - I do computer translations of pages all the time to
follow up on things I am interested in. (for example I am reading
everything about the upcoming OpenOffice.org-Kongress being held in
Germany, and therefore discussed in German)
Doesn't work for poetry of course, but it works fine for most technical
writings.
or here (English too, public code repository):
http://ooo-xadessig-it.forge.osor.eu/en/index.html
no help, it's the wrong place i or we can't follow all public places.
OK - this is the line that got my response.
Do you not follow what is happening in the academic world in your
particular field of interest?
You go to no outside conferences, read no RSS feeds from blogs of others
in your field?
In this case, is not this exactly the area of interest the core
developer is working in - are you really saying that if the OO.o
infrastructure is not used to host these 'other OO.o specific' efforts
then Sun developers can not be 'bothered' with keeping up with their work?
no i think you misunderstand me. I read a lot of these resources and i
go to conferences whenever i can (to speak myself or just listen). The
point is that i can't know them all ...
If somehting is OOo related and help or direct communication with the
community is wanted that please use the community channels. That's all
what i wanted to say.
Demotived because of such sentences
"Yes - it is annoying. If such an issue was filed by anybody else (not
Sun employe or core developer) it would have been closed as invalid
asap. This might give the impression, that some community members are
"more equal" than others. "
and the discussion around.
I am sure you know what i mean ... I at least accept and appreciate
the work of any individual contributor and community member if she/he
accept the project rules.
Sorry, I don't know what you mean. If you disagree just say that.
Bottom line for this discussion IMO:
The best answer is just ' Sorry, we (I) made a mistake', then fix it and
move on. (Issue has already been updated I see)
i think that is what we have all agreed. The issue description was
initially pure and useless and it should be avoided. I simply tried to
explain why it can happen. But i agree also that it shouldn't happen.
Not - turn it around against the person reporting the problem and then
showing why (not very well BTW) they are in error.
Finally - It seems to me that the core developers working on security
issues (or perhaps just signatures) would at this point be remiss in
their official duties if they do not pro-actively take steps to keep the
OOoXAdESSigIT developers 'in the loop'.
mmh, i think that is not so easy to answer. I see it a little bit
different. If the OOoXAdESSigIT developer work on something that is
related to OOo they should make it public and should use the known
channels to communicate with other people from the project who work on
it. It can't really work in the other direction from my point of view.
Juergen
Just my un-solicited opinions,
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
