Hi Dennis,
I tried to give some short feedback to a few Reviews I was involved. Feel
free to contact my if you have any question there.
>From the top of my head common problems are:
- Git (Usage, setup, merging, rebase, etc.)
- Understanding the life-circle of certain classes and the way we use
and handle dependence injection. <-> PicoContainer
- Flawful or missing documentation (Java-doc as well as commit messages)
- Git (Yes again)
- Exception handling
To mention a few. (Not saying that this are the most urgent ones)
Best
Matthias
2016-05-26 15:52 GMT+02:00 Dennis Ventzke <dennis.vent...@fu-berlin.de>:
> Hi all,
>
> I'm currently writing a thesis on the optimization of the Gerrit review
> process by introducing a knowledge base (KB) and would be thankful for
> some feedback from anyone who has the time and energy to provide it.
>
> I've put together a short list of 11 possible candidates [1] for you to
> assess. These are all comments taken from Gerrit reviews and I would like
> to know if you deem them worthy of being put into the KB. It should
> contain only solutions to problems that occur frequently, descriptions of
> basic principles that get violated often and other important information
> that is simply helpful to know (especially for someone who's new to
> Saros).
>
> The motivation behind this is the following: If I'm an experienced Saros
> developer and keep encountering the same problem or violated principle
> over and over again while reviewing the work/patches of others, I do not
> want to explain it over and over again. I'd much rather just mention the
> problem by its identifier - for example [CommentWhyNotWhat] - and have
> Gerrit insert the detailed description from the KB.
> Likewise if I'm new to the Saros project I can browse through the KB and
> read the most important entries to avoid doing the most common mistakes.
> The goal here is to avoid unnecessary frustration on both sides, since
> beginners don't want to do the common mistakes and veterans don't want to
> see them.
>
> Since I AM new to the project I have a very limited understanding of what
> these important issues are, which is why I'm asking all of you to bring
> your experience into the process. If you don't think that a candidate
> should go into the KB I would like to know why, so that I can use that
> information to get better candidates.
>
> Thank you very much!
>
> Best regards,
> Dennis Ventzke
>
> [1]
>
> https://docs.google.com/spreadsheets/d/1aFAp1wH1DXFNH8M84aFnsSXPJi0GiOgyRLGR-mr3m6w/edit?usp=sharing
>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
> untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> DPP-Devel mailing list
> DPP-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dpp-devel
>
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
