karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie G." <jamie.goody...@gmail.com>
Subject Re: Document archtiectural decisions in Wiki
Date Tue, 07 Feb 2012 12:07:23 GMT
+1. I agree with Andreas, the supporter/against section can go - if
something comes to a vote that'll be on an email thread, just
including a list of whom was involved is sufficient. The rest looks
good :)

Cheers,
Jamie

On Tue, Feb 7, 2012 at 8:50 AM, Andreas Pieber <anpieber@gmail.com> wrote:
> As already stated on IRC I'm very much +1 for documenting those decisions.
> Will make various things much easier to adapt/correct afterwards. Though one
> thing I've found in you're template I do not really like is the
> "supporter/aginst" section. I think this does not really help anybody than
> to "pranger" someone if a decision does not work out as planed. I think we
> should rather add an involved section to make it easier finding out who was
> involved in a decision.
>
> Otherwise rellly cool. Thxs for starting this.
>
> Kind regards,
> Andreas
>
>
> On Tue 07 Feb 2012 11:30:02 AM CET, Christian Schneider wrote:
>>
>> Hi all,
>>
>> I discussed with Andreas on IRC that it is would be good to document
>> architectural decisions in the wiki. The idea is to extract the most
>> important informations from discussions on e.g. the mailing list. The list
>> should allow us to point new developers to decisions that were made so they
>> can inform themselves about these before dicussing the decisions. The list
>> should also allow to revisit decisions from time to time so we have the
>> chance to change a decision if for example the reasons for it change.
>>
>> See
>> https://cwiki.apache.org/confluence/display/KARAF/Architectural+decisions
>>
>> I currently added a first decision for console as it came up on the irc
>> channel. Please document further decisions as you see fit and also help
>> making existing ones more concise.
>> We should of course not document every little decision. I think a good
>> indicator that a decision should be documented is when it is discussed often
>> and or heated :-)
>>
>> Christian
>>
>>
>

Mime
View raw message