Replies: 10 comments 2 replies
-
Hi. Thanks @jcdrubay for your interest to increase Openupgrade contributions. Well, in fact, I don't have the same analysis regarding the situation. Could you elaborate some assertion ?
I don't see what you mean. I observe new people arriving who have "various levels" of contributions. I feel like you can contribute even if you're not an Openupgrade expert. Could you provide examples ?
I'm not sure who you're talking about. Note : I'm not saying that there are no worries at the moment, in terms of quantity of contributors, but I'm not sure I agree with the diagnosis. |
Beta Was this translation helpful? Give feedback.
-
People who do not contribute are not visible, or not much... so it's difficult to find out. I speak from my own experience and the chats I had with a developers from other companies. If you check the list of contributors of the past 5 months, you will see that some of them are coming from the same company Viindoo, so this company has decided to invest in OpenUpgrade because they really want to have it within a fixed deadline. Luckily the OpenUpgrade maintainers have been very quick to respond, review all PRs to encourage them to continue. Other contributors are you, Pedro, Miquel and Stefan. Then there are very few and very minor contributors. https://github.com/OCA/OpenUpgrade/graphs/contributors From the search I did for help request since May 1st, I could see that there is no "transformation" of people asking for help and later on contributing anything (I have added one more slide in my presentation). I myself did some contributions in the past which have been rejected because they did not follow the standard or where workarounds. It's great they were rejected because they were truly not mature. Yet, until a better solution could be merged, these rejected suggestions were the workaround I needed to progress and even complete the upgrade of some projects. I wish these contributes could have helped others. |
Beta Was this translation helpful? Give feedback.
-
I also see that there have been almost no contributions lately other than a few acquaintances and people at our company. I think there are several reasons that contributions are being reduced like this:
I understand what @jcdrubay is trying to say and I think it's a good idea |
Beta Was this translation helpful? Give feedback.
-
There are 554 forks of OpenUpgrade, how many contains code which could be useful? Out of these 554 forks, there are a lot of potential contributions. |
Beta Was this translation helpful? Give feedback.
-
OK.
People then can create Issue / PR with a title like "11.0 - Stock - dirty hack to handle a use case ..." and we flag the PR. Then, if there a thousands of contributions, we'll talk about a more complex / adapted tools. At this stage of this project, developing a dedicated tool seems a bit premature (described in the power point document), and energy consuming. Is it OK for you ? |
Beta Was this translation helpful? Give feedback.
-
Thanks for all the feedback. Due to an overwhelming curiosity, I am not giving up on the initial idea. As a first step, I am trying to compute some metrics which could facilitate the assessment of the workload when deciding to start an upgrade and hopefully also guide on where to start. Maybe, the whole part of dirty contributions won't fit into the first version but instead could work hand in hands with the suggestions to use Github with tags I fully agree that it is a complete overkill for the current community of contributors and number of contributions... but hopefully this will help (at least to satisfy my curiosity in playing with Github APIs, and trying to define a tool could change the future of OCA). Most likely this attempt will be a failure, but with a hope that it can trigger useful ideas. I think that using PR or issues would pollute the OpenUpgrade repo, however discussions could be more appropriate. |
Beta Was this translation helpful? Give feedback.
-
OK ! |
Beta Was this translation helpful? Give feedback.
-
I have made some progress and I added some screenshots to the presentation: https://docs.google.com/presentation/d/1DRd021SUYC3_urTAn-AanJlSDSL5k2xziIh4nMM6jZY/edit#slide=id.g1349d4c55fd_0_59 I could manage to have 100% of data pulled from Github without any manual entry. So this project is really layer on top of github which places the "(module,version)" couple at the center while Github places the repository in the center. The scope is now completely stepping out of OpenUpgrade to enable having an holistic view per module for a specific version. I plan to implement several points which are documented in the slides of "Readme extracts" Once the Prototype phase is complete, I plan to:
|
Beta Was this translation helpful? Give feedback.
-
Hello, I have published a first version. Here are the links to the few main public pages:
Normally, all of these get automatically detected from github, populated in this Odoo, synchronized automatically for updates from Github. Synchronization is still in progress, now facing some delay due to rate limit. Feel free to let me know your thoughts, thanks. |
Beta Was this translation helpful? Give feedback.
-
@jcdrubay Following the discussion on the contributors mailinglist I ended up here and read your arguments. As for my position I work with Openupgrade for our customers and have occasionally contributed a PR. While your solution makes it a bit easier to find unmerged/unfinished Openupgrade code, I believe the real problem that we are facing pertains to all OCA repositories and not only this one - it's the combination of a somewhat high contribution barrier combined with the lack of budget/manpower available to match the speed of churnout of new Odoo releases. And this is not addressed by your solution. I wonder if there is any solution though. What seemed to work well for some years is that OCA itself came together and (crowd)funded the development of OpenUpgrade for the next version, so that a dedicated team could get paid to take up the challenge of taking whatever's lying around (possibly helped by your tool) and make it mature and mergeable. |
Beta Was this translation helpful? Give feedback.
-
Recently, a Survey was sent to request feedback on OpenUpgrade.
In the past, I have used OpenUpgrade several times, I have also been using custom made migration tools (not OpenUpgrade).
I think that OpenUpgrade is a great solution which deserves way more support than it does.
Also, the number of contributors should be a lot more considering how useful and wonderful that solution is.
The existing contributors are highly knowledgeable, committed and supportive people.
Here are my 2 cents, I hope this could help on how to make contributions to OpenUpgrade more "attractive".
In brief, I believe that the current tools based on github PR, Issues and Discussions in a single repo won't allow scaling because they are too demanding on quality for non-expert contributors. The current tools are forcing contributors to be "perfect" contributors. But too many of us are not as good and motivated as the existing contributors...
I imagine that the audience for this new tool(s) is NOT the current maintainers of OpenUpgrade, but all the developers and companies who got discouraged to do any contributions and just wait for OpenUpgrade to be fully ready in the target version before them using it.
Here is a draft specification of what this new tool could be:
https://docs.google.com/presentation/d/1DRd021SUYC3_urTAn-AanJlSDSL5k2xziIh4nMM6jZY/edit#slide=id.p
Beta Was this translation helpful? Give feedback.
All reactions