Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: l10n-italy on apps.odoo.com
    Il 11/02/20 17:16, Pedro M. Baeza (Tecnativa) ha scritto:
    OCA is the owner of that account, Andrea. What do you want? To have 13.0 branch registered? That hasn't been done yet AFAIK.

    Regards.


    Hello Pedro,

    not all V12.0 addons are still available but only a few of them

    could you chack that?

    regards

    --
    Andrea Cometa - Presidente Associazione Odoo Italia
    Apulia Software srl - Responsabile Commerciale ed Amministrativo
    Taranto / Milano / Potenza
    Tel: 0999915404 http://www.apuliasoftware.it
    a.cometa@apuliasoftware.it pec: apulia.software@pec.it
    linkedin: http://it.linkedin.com/in/andreacometa
    by Andrea Cometa - 05:45 - 11 Feb 2020
  • Re: l10n-italy on apps.odoo.com
    OCA is the owner of that account, Andrea. What do you want? To have 13.0 branch registered? That hasn't been done yet AFAIK.

    Regards.
    by Pedro M. Baeza - 05:15 - 11 Feb 2020
  • Re: l10n-italy on apps.odoo.com
    Thank you Stéphane,
    i think the owner is not in the Italy PSC members (I also know someone of them) but is someone other.
    i don't kown why but the email address associated to italian addons on apps.odoo.com is openerp-community-reviewer@lists.launchpad.net

    I suppose there was an initial massive data entry operation on apps.odoo.com



    Il 11/02/20 16:51, Stéphane Bidoul ha scritto:
    Hello Andrea,

    You can view the Italy PSC members via this link: https://odoo-community.org/psc-teams/

    Best regards,

    -sbi

    On Tue, Feb 11, 2020 at 4:42 PM Andrea Cometa - Apulia Software srl <a.cometa@apuliasoftware.it> wrote:

    Hello,

    i'm looking for owner of the l10n-italy repository on apps.odoo.com because that repository is not updated,

    odoo helpdesk says the owner is openerp-community-reviewer@lists.launchpad.net but this email is very old and i've got no answer

    someone could help me?

    thanks

    --
    Andrea Cometa | Cybersecurity Manager
    Presidente Associazione Odoo Italia
    Responsabile Commerciale ed Amministrativo Apulia Software srl
    Taranto / Milano / Potenza
    Tel: 0999915404 http://www.apuliasoftware.it
    a.cometa@apuliasoftware.it pec: apulia.software@pec.it
    linkedin: http://it.linkedin.com/in/andreacometa

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    --
    Andrea Cometa - Presidente Associazione Odoo Italia
    Apulia Software srl - Responsabile Commerciale ed Amministrativo
    Taranto / Milano / Potenza
    Tel: 0999915404 http://www.apuliasoftware.it
    a.cometa@apuliasoftware.it pec: apulia.software@pec.it
    linkedin: http://it.linkedin.com/in/andreacometa
    by Andrea Cometa - 05:06 - 11 Feb 2020
  • Re: l10n-italy on apps.odoo.com
    Hello Andrea,

    You can view the Italy PSC members via this link: https://odoo-community.org/psc-teams/

    Best regards,

    -sbi

    On Tue, Feb 11, 2020 at 4:42 PM Andrea Cometa - Apulia Software srl <a.cometa@apuliasoftware.it> wrote:

    Hello,

    i'm looking for owner of the l10n-italy repository on apps.odoo.com because that repository is not updated,

    odoo helpdesk says the owner is openerp-community-reviewer@lists.launchpad.net but this email is very old and i've got no answer

    someone could help me?

    thanks

    --
    Andrea Cometa | Cybersecurity Manager
    Presidente Associazione Odoo Italia
    Responsabile Commerciale ed Amministrativo Apulia Software srl
    Taranto / Milano / Potenza
    Tel: 0999915404 http://www.apuliasoftware.it
    a.cometa@apuliasoftware.it pec: apulia.software@pec.it
    linkedin: http://it.linkedin.com/in/andreacometa

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Stéphane Bidoul - 04:50 - 11 Feb 2020
  • l10n-italy on apps.odoo.com

    Hello,

    i'm looking for owner of the l10n-italy repository on apps.odoo.com because that repository is not updated,

    odoo helpdesk says the owner is openerp-community-reviewer@lists.launchpad.net but this email is very old and i've got no answer

    someone could help me?

    thanks

    --
    Andrea Cometa | Cybersecurity Manager
    Presidente Associazione Odoo Italia
    Responsabile Commerciale ed Amministrativo Apulia Software srl
    Taranto / Milano / Potenza
    Tel: 0999915404 http://www.apuliasoftware.it
    a.cometa@apuliasoftware.it pec: apulia.software@pec.it
    linkedin: http://it.linkedin.com/in/andreacometa
    by Andrea Cometa - 04:40 - 11 Feb 2020

    1 attachments 1 attachments

    signature.asc
  • Re: How can functional people "really" participate in OCA?
    Hello,

    I share Pedro's opinion on the fact that wikis won't solve the problem and will soon become messy.

    Personally I don't think Github is so ugly for functional people. It's just a matter of getting used to it (but I'm a techy and I might miss some barriers).

    To discuss functional issues or propose changes they can open an issue in a specific repository and start a thread there.
    If they want to use g-docs (or whatever public tool) to enrich the discussion they can use it and link it in an issue.
    In this case, I see only one main problem: we have many repos by area (eg: product or warehouse) and the scope of such discussions might be broader.

    Having a forum would be nice as long as there's people taking care of moderation.

    Forum options:

    1. use the odoo module on our instance

    Pros:
    a. we have all in one.
    b. it's already there and could preserve legacy discussions

    Cons:
    a. it sucks in terms of UI, would require some work (see https://odoo-community.org/groups/contributors-15)
    b. if the site is off, the forum is off as well

    2. use a self-hosted external tool as https://www.discourse.org/

    Pros: really nice and effective
    Cons: one more service to maintain

    3. use an external service

    Pros: nothing on our shoulders
    Cons: no control on it


    A note regarding the ML not being available to external people: is not true. You can access it here https://odoo-community.org/groups/contributors-15 but as I mentioned above it would need a lot of love to be improved.

    My $0.02.

    Bests,


    On Tue, Feb 11, 2020 at 11:57 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
    Well, I personally think the wikis will become a collection of unrelated things and non maintainable stuff, and don't bother if I call "laziness" what is sometimes called "functional scope", but if the rest think is good, go ahead.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Simone Orsi - 04:25 - 11 Feb 2020
  • Re: How can functional people "really" participate in OCA?
    Well, I personally think the wikis will become a collection of unrelated things and non maintainable stuff, and don't bother if I call "laziness" what is sometimes called "functional scope", but if the rest think is good, go ahead.

    Regards.
    by Pedro M. Baeza - 11:55 - 11 Feb 2020
  • Re: How can functional people "really" participate in OCA? 
    @Pedro M. Baeza: You are right that readme MUST to be writed well, but I view a Wiki as a place to have an overview on many modules that cooperate to create a flux. Having links or realtime inclusions of module's readme will be useful.

@Jean-Charles Drubay: wow, what a replay! Only the observation that forum is open accessible (at least for reading) by anyone have a browser, mailing list is available only to subscriber (until exposed like in OCA).


Stefano Consolaro 

www.mymage.it
    by Stefano Consolaro - 10:21 - 11 Feb 2020
  • Re: How can functional people "really" participate in OCA? 
    I think that forum and wiki can be used both at the same time in different ways.

The Forum have to be a place to build a discussion around an aspect/feature/problem in a way that different points of view will be considered to fulfill some normative/state of the art rules (eg. national fiscal rules, ISO standards, ...) to reach the most open and flexible solution. The main problem here is to individuate the right title of each thread, a clear argument definition and can be useful to have tags for a fast search.

The Wiki is a tool for write down a "stable" (sorry for the use of a developer's word) vision of the argument. This have to be treated as documentation, well writed, well structure, well formatted, useful if versioning is available to track changes.

There have to be a connection between the tools: a way to traslate the result of a thread in the Wiki and links to the original threads on the Wiki document.

In both the presence of a moderation is necessary, at least at the begin, to create the right "inertial energy" to reach a good result.


Stefano Consolaro 

www.mymage.it
    by Stefano Consolaro - 10:00 - 11 Feb 2020
  • Re: Proposing "Pimolnat" as PSC for Logistics
    Indeed,

    the OCA website is up-to-date but not github:

    image.png

    On Tue, Feb 11, 2020 at 4:02 AM Pimolnat Suntian <pimolnat.s@outlook.com> wrote:
    Hello Stéphane,

    I didn't receive anything, I have checked spam folder too.

    May you please have a look?

    Thanks,

    Pimolnat Suntian

    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    Sent: Wednesday, February 5, 2020 7:06:57 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Proposing "Pimolnat" as PSC for Logistics
     
    Hello Pimolnat,

    I added you to the Logistics PSC. You should receive the GitHub notification within 24h.

    Best regards,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    On Wed, Feb 5, 2020 at 5:22 AM Pimolnat Suntian <pimolnat.s@outlook.com> wrote:
    Thank you so much. I registered on odoo-community.org. My account name is Pimolnat S.

    Regards,

    Pimolnat Suntian

    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    Sent: Wednesday, February 5, 2020 3:47 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Proposing "Pimolnat" as PSC for Logistics
     
    Pimolnat could you register on odoo-community.org so I can add you to the team?

    Best regards,

    -sbi

    On Mon, Feb 3, 2020 at 3:27 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    +1
    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236


    On Mon, Feb 3, 2020 at 2:22 AM <admin@ygol.com> wrote:
    +1

    --
    Yves Goldberg

    ----- Original message -----
    From: Kitti Upariphutthiphong <kittiu@ecosoft.co.th>
    Subject: Proposing "Pimolnat" as PSC for Logistics
    Date: Monday, February 03, 2020 08:57

    Dear community,

    I would like to propose my team member, Pimolnat, https://github.com/ps-tubtim, as the PSC of Logistics

    Pimpolnat has actively participate in OCA for various repository, and can be more focus on Logistics in helping in more reviews and migrations.

    Thank you!

    _______________________________________________


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 34 64

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel - 09:00 - 11 Feb 2020

    1 attachments 1 attachments

    image.png
  • Re: Proposing "Pimolnat" as PSC for Logistics
    Hello Stéphane,

    I didn't receive anything, I have checked spam folder too.

    May you please have a look?

    Thanks,

    Pimolnat Suntian

    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    Sent: Wednesday, February 5, 2020 7:06:57 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Proposing "Pimolnat" as PSC for Logistics
     
    Hello Pimolnat,

    I added you to the Logistics PSC. You should receive the GitHub notification within 24h.

    Best regards,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    On Wed, Feb 5, 2020 at 5:22 AM Pimolnat Suntian <pimolnat.s@outlook.com> wrote:
    Thank you so much. I registered on odoo-community.org. My account name is Pimolnat S.

    Regards,

    Pimolnat Suntian

    From: Stéphane Bidoul <stephane.bidoul@acsone.eu>
    Sent: Wednesday, February 5, 2020 3:47 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Proposing "Pimolnat" as PSC for Logistics
     
    Pimolnat could you register on odoo-community.org so I can add you to the team?

    Best regards,

    -sbi

    On Mon, Feb 3, 2020 at 3:27 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    +1
    MAXIME CHAMBREUIL
    PROJECT MANAGER/CONSULTANT
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236


    On Mon, Feb 3, 2020 at 2:22 AM <admin@ygol.com> wrote:
    +1

    --
    Yves Goldberg

    ----- Original message -----
    From: Kitti Upariphutthiphong <kittiu@ecosoft.co.th>
    Subject: Proposing "Pimolnat" as PSC for Logistics
    Date: Monday, February 03, 2020 08:57

    Dear community,

    I would like to propose my team member, Pimolnat, https://github.com/ps-tubtim, as the PSC of Logistics

    Pimpolnat has actively participate in OCA for various repository, and can be more focus on Logistics in helping in more reviews and migrations.

    Thank you!

    _______________________________________________


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Pimolnat Suntian - 04:01 - 11 Feb 2020
  • RE: TimeSheet with Client Signature

    Hi David,

     

    https://odoo-community.org/shop/product/sale-order-digitized-signature-4156?search=sign&page=7

     

    https://odoo-community.org/shop/product/stock-picking-digitized-signature-4288?search=digitized_signature

     

    https://odoo-community.org/shop/product/project-task-digitized-signature-4025?search=digitized_signature

     

    https://odoo-community.org/shop/product/contract-digitized-signature-817?search=digitized_signature

     

    Regards,

    Rafael Blasco

     

     

    De: David Arnold [mailto:dar@xoe.solutions]
    Enviado el: miércoles, 29 de enero de 2020 3:42
    Para: Contributors <contributors@odoo-community.org>
    Asunto: TimeSheet with Client Signature

     

    Hi All,

     

    Has anybody got an example app / info or use case for a timesheet app with client signing the entry (like delivery do on their mobile tracking solutions)?

     

    Else, any hint how to incorporate a signature field.in the app and (how to) deploy it?

     

    Best Regards,

     

    David A.

    by Rafael Blasco (Moduon) - 06:16 - 10 Feb 2020
  • Re: How can functional people "really" participate in OCA?
    Thank you for all the ideas.

    I now incline to the opinion that there should be one place only for module README. (github may be best place yet, just make it easier).
    For wiki, we would love to use it too, maybe we can start here now https://en.odoodoc.org as Max suggested. But should we focus only on functional use cases or story telling style (more freeform). Also can we write things in own locale?

    Still, +1 for forum that functional people can discuss on daily basis. Their presence in OCA is what most important, I think.

    That's all my novice opinions, after all, I think you guys have better idea what should be done. We will always support.

    Cheers!


    On Sat, Feb 8, 2020 at 8:57 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    I think we can start by setting a forum and use the wiki at https://en.odoodoc.org. 

    From there, we can evaluate in a year if it's a success by looking at the number of members/posts and contributors/pages.

    If it works for the few of us, others will pick it up and join.

    Greame, do you have a software forum in mind?

    For those interested in the wiki, what do you think of the current structure? If you want to make changes, I can set you up as an administrator. I am happy to share the ball here.

    Cheers,

    El sáb., 8 de febrero de 2020 06:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> escribió:
    I don't like Wiki pages as you propose, as we will duplicate data and have inconsistencies between both sources. There must be only one source. What we can do is to create a Wiki page for teaching how to propose a modification in README.rst files of the modules / README.md of the repository for newbie people that is not used to GitHub, and add massively in all the README files this link (we have tools for this) in a special section. Something like:

    """
    Is this README not accurated or are there missing things you have detected? Please visit xxx to learn how you can propose changes in it.
    """

    I know there's still the barrier of RST formatting, but usual redaction doesn't require it (and we can teach about usual formatting things like bold or italic - GitHub also includes some buttons for them in the top bar).

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Kitti Upariphutthiphong - 10:10 - 10 Feb 2020
  • Re: How can functional people "really" participate in OCA?
    Very good details  Jean-Charles Drubay!

    On Mon, Feb 10, 2020 at 8:57 AM Jean-Charles Drubay <jc@komit-consulting.com> wrote:

    Hi,


    In the past years, I also observed difficulties for functional people to contribute to OCA.

    When I ask myself the question "Is there any known OCA contributor who does not have technical skills?" I find it hard to think of anyone.

    So, I also came to the conclusion that existing OCA tools are not adapted to contributors who don't have technical skills.

    We could argue that the step is not so big, that functional people would follow a guideline to create their PR. But deep inside me, foreseeing the step of such a guideline, thinking of the ease of edition of a Google Doc,  I have strong doubts about adoption unless we change tools.


    I have also observed that most of the "good" contributions come from a small number of people who are doing very  high quality work and are investing a lot of time. Big thanks to them.


    Before jumping into solutions, we should try to answer the following questions:


    - What are the types of contributions for contributors without technical skills? (see the first answer from Maxime)

    - What is the current process?

    - What tools for which contributions?

    - If changing tools what is the cost (money / time / moderation level: keeping trolls away vs. review of the changes before accepting the contributions)? Can OCA do it?

    - What the non-technical Contributors should expect from the Community?


    I am sorry for the length of this message, I imagine the best would be to split this discussion per type of contribution, I did not see it coming but I had a lot in mind.


    Here I started to share some of the answers to these questions per type of contribution.


    Update and improve the README per module


    This is probably the second most important.

    It's already readable nicely with images in list of modules within Odoo and in apps.odoo.com.

    I find the github presentation of the README nice too.


    Is there a bigger need to publish README?


    The problem is more about "How to edit and improve the content of the README?".


    The current solution using github+PR is great because repo maintainers can review before merge and we have a good version control which seems important for this very important page.

    Also, all the README are automatically published without the risk of duplicated/outdated content.


    But this PR process is not intuitive for everyone. Should OCA do something about it to simplify it? Could odoo-community.org have a feature where a logged-in contributor could simply edit the text of a README and submit the review with a nice UX to add images, preview the result, compare with the past README, list my on-going submissions, Call for attention from maintainers?

    In the back-ground, Odoo-community.org could take care of submitting the PR.


    In the README, we could have a message "Suggest improvements for this README on odoo-community.org/submit-readme-change"


    Provide designs of new features on Github using issues & Challenge designs proposed by others


    A forum could be a better place than a mailing list, but mailing lists do the job and have been in place for a while. Is there any real benefit of a forum instead?

    Probably better indexing, more searchable, and easier to navigate / read the full discussion.


    Contributors can expect feedback from other functional experts to refine their analysis and understanding of an issue to make better and more generic so it could be integrated into OCA repo later on. Also, there are often some recommendations for existing modules.


    However, the contributors should not expect a technical person to pick-up that specification and start coding.

    Maybe a small feature / tag to "Request for a quote" would be welcome so Technical Contributors could sell their services in a more private way,  but OCA could get a commission from that recommendation.


    Report issues


    All functional and technical issues are in the same place and it's probably fine like this because quite often a classification is required.

    When it comes to functional changes, maybe some functional issues can be closed and reopened as a forum discussion.

    When it comes to Functional Support, maybe it's more about improving the quality of the README.

    When it is a real defect, then it should be kept open as an issue.


    What to expect from the community after an issue is created? Today, nothing... but tomorrow? Maybe also a "Request for a quote" feature? Because the probability a defect is being corrected by a kind technical contributor is low unless he/she face that issue and he/she must correct it?



    Test new PRs on Runbot


    Yes, but if we expect support for testing, then I think we need to make it way easier to start testing a PR because for the time being that not intuitive all all:

    Click on runbot link at the bottom of a PR, search based on the PR ID (seriously?! is it documented somewhere),  understand how to read / use the runbot page, if you are lucky you can test click on a button to enter the test instance with a login / password that you must know (know or die here), 


    We could ask the contributor of the PR to add a "magic" link to with the login info to call some kind of "magic bot".

    That magic link available in the description of the PR could rebuild the test environment if necessary and redirect to the suitable odoo login page.


    How about a module installed on all OCA odoo instances on runbot that would display / present the login and password on the login page to admin / admin?


    Test existing modules on Runbot


    For existing modules, it's fairly easy to test with the Try Me button on the Readme, but here again sometimes we need to force rebuild and it's not too easy to know what should be done once you land on the runbot page.


    That Magic link to test new PRs could also help here.


    Translate modules on Weblate

    No opinion on Weblate


    Participate and provide their opinions on the various mailing lists

    If all points are moved out of Mailing Lists, what will be left to discuss in the mailing list? Maybe not much...

    Maybe all this could be also in a Forum.


    About solutions

    +1 for a forum that could make functional contributors discuss comfortably.

    +1 for README in github with the great process of Pull request + Review before merge and avoid duplicated content BUT tools to facilitate contributions

    +1 for google doc to compile contributions of ideas for the specifications for a module => But I guess this can be agreed when there is such a need appearing within a forum discussion

    -1 for a wiki: because I don't think OCA as the resources to moderate and review the content


    Maybe the forum could have a dedicated "Category" for each OCA-repo and and "Sub-Category" per "Module". Discussions could be linked to a module, but for a new module the discussion should at least start in the correct repo/Category.

    Keep the Readme on Github , but add 2 links [1] for the guideline on how to update the README (how to do a PR + how to format RST) and [2] a link to the dedicated Sub-category page on the forum.


    Getting started as a contributor

    https://odoo-community.org/page/Contribute


    Probably the most important to on-board new contributors, maybe not directly related to this thread so ... 


    Yet this page as some "issues":

    • No future event referenced: not an issue but not encouraging, if we have no event to promote we should not put this as the first link

    • IRC channel: could we find something easier to use? Is it still in use? That's definitely not a "Functional Friendly" communication tool.

    • Testing is not mentioned in "How can you help?"

    • Should we have a dedicated section for the maintenance of the README ?

    Regards,

    Jean-Charles Drubay / Komit / komit-consulting.com



    On Sun, Feb 9, 2020 at 2:37 AM Graeme Gellatly <gdgellatly@gmail.com> wrote:
    Hi

    Not really. Preferably something we already have / dont need to do install. That's why I thought gsuite as we already have it and it costs us nothing. Plus I imagine it ranks well. But I'm not a big user of forums since they closed the odoo ones. Others will know better.

    On Sun, 9 Feb 2020, 2:57 AM Maxime Chambreuil, <mchambreuil@opensourceintegrators.com> wrote:
    I think we can start by setting a forum and use the wiki at https://en.odoodoc.org. 

    From there, we can evaluate in a year if it's a success by looking at the number of members/posts and contributors/pages.

    If it works for the few of us, others will pick it up and join.

    Greame, do you have a software forum in mind?

    For those interested in the wiki, what do you think of the current structure? If you want to make changes, I can set you up as an administrator. I am happy to share the ball here.

    Cheers,

    El sáb., 8 de febrero de 2020 06:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> escribió:
    I don't like Wiki pages as you propose, as we will duplicate data and have inconsistencies between both sources. There must be only one source. What we can do is to create a Wiki page for teaching how to propose a modification in README.rst files of the modules / README.md of the repository for newbie people that is not used to GitHub, and add massively in all the README files this link (we have tools for this) in a special section. Something like:

    """
    Is this README not accurated or are there missing things you have detected? Please visit xxx to learn how you can propose changes in it.
    """

    I know there's still the barrier of RST formatting, but usual redaction doesn't require it (and we can teach about usual formatting things like bold or italic - GitHub also includes some buttons for them in the top bar).

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


    		 
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com

    by Jay Vora - 08:40 - 10 Feb 2020
  • Re: How can functional people "really" participate in OCA?

    Hi,


    In the past years, I also observed difficulties for functional people to contribute to OCA.

    When I ask myself the question "Is there any known OCA contributor who does not have technical skills?" I find it hard to think of anyone.

    So, I also came to the conclusion that existing OCA tools are not adapted to contributors who don't have technical skills.

    We could argue that the step is not so big, that functional people would follow a guideline to create their PR. But deep inside me, foreseeing the step of such a guideline, thinking of the ease of edition of a Google Doc,  I have strong doubts about adoption unless we change tools.


    I have also observed that most of the "good" contributions come from a small number of people who are doing very  high quality work and are investing a lot of time. Big thanks to them.


    Before jumping into solutions, we should try to answer the following questions:


    - What are the types of contributions for contributors without technical skills? (see the first answer from Maxime)

    - What is the current process?

    - What tools for which contributions?

    - If changing tools what is the cost (money / time / moderation level: keeping trolls away vs. review of the changes before accepting the contributions)? Can OCA do it?

    - What the non-technical Contributors should expect from the Community?


    I am sorry for the length of this message, I imagine the best would be to split this discussion per type of contribution, I did not see it coming but I had a lot in mind.


    Here I started to share some of the answers to these questions per type of contribution.


    Update and improve the README per module


    This is probably the second most important.

    It's already readable nicely with images in list of modules within Odoo and in apps.odoo.com.

    I find the github presentation of the README nice too.


    Is there a bigger need to publish README?


    The problem is more about "How to edit and improve the content of the README?".


    The current solution using github+PR is great because repo maintainers can review before merge and we have a good version control which seems important for this very important page.

    Also, all the README are automatically published without the risk of duplicated/outdated content.


    But this PR process is not intuitive for everyone. Should OCA do something about it to simplify it? Could odoo-community.org have a feature where a logged-in contributor could simply edit the text of a README and submit the review with a nice UX to add images, preview the result, compare with the past README, list my on-going submissions, Call for attention from maintainers?

    In the back-ground, Odoo-community.org could take care of submitting the PR.


    In the README, we could have a message "Suggest improvements for this README on odoo-community.org/submit-readme-change"


    Provide designs of new features on Github using issues & Challenge designs proposed by others


    A forum could be a better place than a mailing list, but mailing lists do the job and have been in place for a while. Is there any real benefit of a forum instead?

    Probably better indexing, more searchable, and easier to navigate / read the full discussion.


    Contributors can expect feedback from other functional experts to refine their analysis and understanding of an issue to make better and more generic so it could be integrated into OCA repo later on. Also, there are often some recommendations for existing modules.


    However, the contributors should not expect a technical person to pick-up that specification and start coding.

    Maybe a small feature / tag to "Request for a quote" would be welcome so Technical Contributors could sell their services in a more private way,  but OCA could get a commission from that recommendation.


    Report issues


    All functional and technical issues are in the same place and it's probably fine like this because quite often a classification is required.

    When it comes to functional changes, maybe some functional issues can be closed and reopened as a forum discussion.

    When it comes to Functional Support, maybe it's more about improving the quality of the README.

    When it is a real defect, then it should be kept open as an issue.


    What to expect from the community after an issue is created? Today, nothing... but tomorrow? Maybe also a "Request for a quote" feature? Because the probability a defect is being corrected by a kind technical contributor is low unless he/she face that issue and he/she must correct it?



    Test new PRs on Runbot


    Yes, but if we expect support for testing, then I think we need to make it way easier to start testing a PR because for the time being that not intuitive all all:

    Click on runbot link at the bottom of a PR, search based on the PR ID (seriously?! is it documented somewhere),  understand how to read / use the runbot page, if you are lucky you can test click on a button to enter the test instance with a login / password that you must know (know or die here), 


    We could ask the contributor of the PR to add a "magic" link to with the login info to call some kind of "magic bot".

    That magic link available in the description of the PR could rebuild the test environment if necessary and redirect to the suitable odoo login page.


    How about a module installed on all OCA odoo instances on runbot that would display / present the login and password on the login page to admin / admin?


    Test existing modules on Runbot


    For existing modules, it's fairly easy to test with the Try Me button on the Readme, but here again sometimes we need to force rebuild and it's not too easy to know what should be done once you land on the runbot page.


    That Magic link to test new PRs could also help here.


    Translate modules on Weblate

    No opinion on Weblate


    Participate and provide their opinions on the various mailing lists

    If all points are moved out of Mailing Lists, what will be left to discuss in the mailing list? Maybe not much...

    Maybe all this could be also in a Forum.


    About solutions

    +1 for a forum that could make functional contributors discuss comfortably.

    +1 for README in github with the great process of Pull request + Review before merge and avoid duplicated content BUT tools to facilitate contributions

    +1 for google doc to compile contributions of ideas for the specifications for a module => But I guess this can be agreed when there is such a need appearing within a forum discussion

    -1 for a wiki: because I don't think OCA as the resources to moderate and review the content


    Maybe the forum could have a dedicated "Category" for each OCA-repo and and "Sub-Category" per "Module". Discussions could be linked to a module, but for a new module the discussion should at least start in the correct repo/Category.

    Keep the Readme on Github , but add 2 links [1] for the guideline on how to update the README (how to do a PR + how to format RST) and [2] a link to the dedicated Sub-category page on the forum.


    Getting started as a contributor

    https://odoo-community.org/page/Contribute


    Probably the most important to on-board new contributors, maybe not directly related to this thread so ... 


    Yet this page as some "issues":

    • No future event referenced: not an issue but not encouraging, if we have no event to promote we should not put this as the first link

    • IRC channel: could we find something easier to use? Is it still in use? That's definitely not a "Functional Friendly" communication tool.

    • Testing is not mentioned in "How can you help?"

    • Should we have a dedicated section for the maintenance of the README ?

    Regards,

    Jean-Charles Drubay / Komit / komit-consulting.com



    On Sun, Feb 9, 2020 at 2:37 AM Graeme Gellatly <gdgellatly@gmail.com> wrote:
    Hi

    Not really. Preferably something we already have / dont need to do install. That's why I thought gsuite as we already have it and it costs us nothing. Plus I imagine it ranks well. But I'm not a big user of forums since they closed the odoo ones. Others will know better.

    On Sun, 9 Feb 2020, 2:57 AM Maxime Chambreuil, <mchambreuil@opensourceintegrators.com> wrote:
    I think we can start by setting a forum and use the wiki at https://en.odoodoc.org. 

    From there, we can evaluate in a year if it's a success by looking at the number of members/posts and contributors/pages.

    If it works for the few of us, others will pick it up and join.

    Greame, do you have a software forum in mind?

    For those interested in the wiki, what do you think of the current structure? If you want to make changes, I can set you up as an administrator. I am happy to share the ball here.

    Cheers,

    El sáb., 8 de febrero de 2020 06:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> escribió:
    I don't like Wiki pages as you propose, as we will duplicate data and have inconsistencies between both sources. There must be only one source. What we can do is to create a Wiki page for teaching how to propose a modification in README.rst files of the modules / README.md of the repository for newbie people that is not used to GitHub, and add massively in all the README files this link (we have tools for this) in a special section. Something like:

    """
    Is this README not accurated or are there missing things you have detected? Please visit xxx to learn how you can propose changes in it.
    """

    I know there's still the barrier of RST formatting, but usual redaction doesn't require it (and we can teach about usual formatting things like bold or italic - GitHub also includes some buttons for them in the top bar).

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Jean-Charles Drubay - 04:26 - 10 Feb 2020
  • Re: Activity: reminders
    Yeah, great!

    El dom., 9 feb. 2020 15:37, Alexey Pelykh <alexey.pelykh@gmail.com> escribió:
    “mail_activity_reminder” under “social” repo then?

    On 9 Feb 2020, at 06:37, Roussel, Denis <denis.roussel@acsone.eu> wrote:

    Indeed, that's the limit of that approach even if you can define all your activity types as 'meeting'.

    Le dim. 9 févr. 2020 à 14:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    I personally prefer to have these reminders on any kind of activity.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Pedro M. Baeza - 03:41 - 9 Feb 2020
  • Re: Activity: reminders
    “mail_activity_reminder” under “social” repo then?

    On 9 Feb 2020, at 06:37, Roussel, Denis <denis.roussel@acsone.eu> wrote:

    Indeed, that's the limit of that approach even if you can define all your activity types as 'meeting'.

    Le dim. 9 févr. 2020 à 14:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    I personally prefer to have these reminders on any kind of activity.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Alexey Pelykh <alexey.pelykh@gmail.com> - 03:36 - 9 Feb 2020
  • Re: Activity: reminders
    Indeed, that's the limit of that approach even if you can define all your activity types as 'meeting'.

    Le dim. 9 févr. 2020 à 14:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    I personally prefer to have these reminders on any kind of activity.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Denis Roussel - 02:35 - 9 Feb 2020
  • Re: Activity: reminders
    I personally prefer to have these reminders on any kind of activity.

    Regards.
    by Pedro M. Baeza - 02:25 - 9 Feb 2020
  • Re: Activity: reminders
    As Nathan said, if you set the activity type as 'meeting', you can then define an event directly when creating activity. And then, define reminders as usual on event.

    A little bit more automation could be welcome indeed.

    Le dim. 9 févr. 2020 à 14:11, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    OCA/social IMO

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Denis Roussel - 02:21 - 9 Feb 2020