Child pages
  • Improving the effectiveness of communication in the group "In-Portal Development Team".
Skip to end of metadata
Go to start of metadata

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/ffda170e852b451b#

I propose to increase the effectiveness of communication in the group "In-Portal Development Team", making possible some elements structuring topics.

  1. If the topics created to discuss a problem, it would be easy to make out it's title as: "Problem: <Short description of the problem>". In such a topic would be natural to find out what is the problem, how the problem is urgent, why it may be important, post links to topics of different solutions.
  2. If the topic was created to discuss some solution of the problem, it would be easy to make out it's title as: "Solution: <Short description of the solution>". In this topic would be naturally provide links to topics of problems that this solution helps to decide, describe in detail what is the essence of solution, and discuss how this solution is adequate for the linked problems. Also, a particular solution can be a source of new problems. If someone has a desire to discuss these issues, it probably makes sense for these problems to create separate topics, in accordance with paragraph 1) and make link references accordingly.

3 Comments

  1. *1) If the topics created to discuss a problem, it would be easy to make out
     it's title as: "Problem: <Short description of the problem>". In such atopic
    would be natural to find out what is the problem, how the problem is urgent,
     why it may be important, post links to topics of different solutions.*

    All topics with a problems should be posted to
    in-portal-bugs@googlegroups.com group instead of
    in-portal-dev@googlegroups.com group. But topics about project itself
    should instead go to in-portal-org@googlegroups.com.

    *2) If the topic was created to discuss some solution of the problem, it
    would be easy to make out it's title as: "Solution: <Short description of
    the solution>". In this topic would be naturally provide links to topics of
    problems that this solution helps to decide, describe in detail what
    is theessence
    of solution, and discuss how this solution is adequate for the linked
    problems. Also, a particular solution can be a source of new problems. If
    someone has a desire to discuss these issues, it probably makes sense for
    these problems to create separate topics, in accordance with paragraph 1)
    and make link references accordingly.*

    If there is a solution, then is posted to discussion where problem is
    described instead of creating a new discussion. Whatever topic is a problem
    or a solution is determined purely on group, where it's being posted to, so
    no additional prefix is needed.

    Also at time of posting of user, who posts isn't aware that his topic will
    be a solution to other topics around many posted over the years, then he
    can't add "Solution:" prefix to it. Renaming topic later also doesn't makes
    much sense since it will break conversation layout in every used e-mail
    client, which uses conversations, like "Mail.app", "Sparrow.app", "Gmail".

    On Thu, Dec 27, 2012 at 2:15 PM, Erik Snarski <s...@jamajo.lv> wrote:
    > 1) If the topics created to discuss a problem, it would be easy to make
    > out it's title as: "Problem: <Short description of the problem>". In such
    > a topic would be natural to find out what is the problem, how the problem
    > is urgent, why it may be important, post links to topics of different
    > solutions.

  2. I'm only saying, that there are separate groups (e-mails) to write to
    depending on what you want to post:

       - improvement/feature
       - bug/problem
       - general question (not code related)

    If there is a situation where you posted into wrong groups, then simply
    repost to correct one.