On 08/30/2011 01:51 PM, Jan Pazdziora wrote:
Sure. I'm just pointing out that you might save yourself some
architecture and coding work if you consider the bigger picture and
goals of the project and not just blindly focus on the narrow goal you
have on your plate right now.

The narrow goal that we have on our plate right now is basically the reason why we are implementing this feature.

Of course we want this to be upstream, yes, and that is why Bo and Johannes started the discussion to get feedback of what could be improved.

I have the impression the discussion is getting further from finding a common view as it progressed (the first replies where very valid suggestions). But now we are already on the topic of porting perl pages to Java. While we sure want to help with this in the future (monitoring anyone), it is not in the scope of what we need to deliver and we can't get out of our schedule in order to find the ultimate solution.

If there is no agreement or the visions are too different, may be it would make sense to keep this in our tree for now and we would need to make the right decisions so that merging does not become too hard in the future. I don't find this ideal, because some of the proposals+feedback are not that intrusive, so they could be in the spacewalk tree and would be mostly optional for the user. Even the daemon is a XML-RPC interface so it can easily be replaced.

Adding a logging setup to two stacks surely is less work than adding
it to three, and if there still is the common goal of finishing the
migration, I consider it a valid option to consider, whether to switch
the order in which work is done and make things easier in total.

I think Bo gave very a good explanation why this is not "Logging" but "Auditing": more contextual/semantic data,
security, tamper-proof, use cases, etc.

--
Duncan Mac-Vicar P. - http://www.suse.com/

SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany

_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to