- note the answer update below
As one of close-voters I can share what would definitely stop me from voting back then - or make me vote to reopen now that question is closed.
Given your comments in this question it feels quite doable:
I did my research and I am still open on this question since years, and nobody wants to give me a decent example to know how this is done in an appropriate way. All the repos I found generally are either made by people who does not care about quality (it's just a bunch of really hacked up scripts) nor platform transferability, nor addressing the different phases (development, testing, deployment, installing). In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer.
Now, let's see...
- All the repos I found...
- List these repos in your question.
- If list is very long, list a few that looked best to you.
- If it's very long and you can't select a few, just list them all in a "references" section at the bottom (it's not really hard to do it's not really hard to do)
- ...either 1) made by people who does not care about quality nor 2) platform transferability, nor 3) addressing the different phases 4) In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer
- Above makes your requirements - just list these in the question.
- If you not only list reqs but also clarify which particular requirements aren't met by particular repos in previous list I mentioned then I would upvote your question instead of closing
...well - that's it.
#update
Above applies only to old version of the question:
- Revision 1: Starting a new project in python and qt. Where can I find... Revision 1: Starting a new project in python and qt. Where can I find...
Since then it has been revised and I think improved sufficiently for reopening.
My downvote and vote to close are revoked at rev 2. At rev 3, I upvoted.
- note the answer update below
As one of close-voters I can share what would definitely stop me from voting back then - or make me vote to reopen now that question is closed.
Given your comments in this question it feels quite doable:
I did my research and I am still open on this question since years, and nobody wants to give me a decent example to know how this is done in an appropriate way. All the repos I found generally are either made by people who does not care about quality (it's just a bunch of really hacked up scripts) nor platform transferability, nor addressing the different phases (development, testing, deployment, installing). In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer.
Now, let's see...
- All the repos I found...
- List these repos in your question.
- If list is very long, list a few that looked best to you.
- If it's very long and you can't select a few, just list them all in a "references" section at the bottom (it's not really hard to do)
- ...either 1) made by people who does not care about quality nor 2) platform transferability, nor 3) addressing the different phases 4) In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer
- Above makes your requirements - just list these in the question.
- If you not only list reqs but also clarify which particular requirements aren't met by particular repos in previous list I mentioned then I would upvote your question instead of closing
...well - that's it.
#update
Above applies only to old version of the question:
Since then it has been revised and I think improved sufficiently for reopening.
My downvote and vote to close are revoked at rev 2. At rev 3, I upvoted.
- note the answer update below
As one of close-voters I can share what would definitely stop me from voting back then - or make me vote to reopen now that question is closed.
Given your comments in this question it feels quite doable:
I did my research and I am still open on this question since years, and nobody wants to give me a decent example to know how this is done in an appropriate way. All the repos I found generally are either made by people who does not care about quality (it's just a bunch of really hacked up scripts) nor platform transferability, nor addressing the different phases (development, testing, deployment, installing). In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer.
Now, let's see...
- All the repos I found...
- List these repos in your question.
- If list is very long, list a few that looked best to you.
- If it's very long and you can't select a few, just list them all in a "references" section at the bottom (it's not really hard to do)
- ...either 1) made by people who does not care about quality nor 2) platform transferability, nor 3) addressing the different phases 4) In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer
- Above makes your requirements - just list these in the question.
- If you not only list reqs but also clarify which particular requirements aren't met by particular repos in previous list I mentioned then I would upvote your question instead of closing
...well - that's it.
#update
Above applies only to old version of the question:
Since then it has been revised and I think improved sufficiently for reopening.
My downvote and vote to close are revoked at rev 2. At rev 3, I upvoted.
- note the answer update below
As one of close-voters I can share what would definitely stop me from voting back then - or make me vote to reopen now that question is closed.
Given your comments in this question it feels quite doable:
I did my research and I am still open on this question since years, and nobody wants to give me a decent example to know how this is done in an appropriate way. All the repos I found generally are either made by people who does not care about quality (it's just a bunch of really hacked up scripts) nor platform transferability, nor addressing the different phases (development, testing, deployment, installing). In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer.
Now, let's see...
- All the repos I found...
- List these repos in your question.
- If list is very long, list a few that looked best to you.
- If it's very long and you can't select a few, just list them all in a "references" section at the bottom (it's not really hard to do)
- ...either 1) made by people who does not care about quality nor 2) platform transferability, nor 3) addressing the different phases 4) In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer
- Above makes your requirements - just list these in the question.
- If you not only list reqs but also clarify which particular requirements aren't met by particular repos in previous list I mentioned then I would upvote your question instead of closing
...well - that's it.
#update
Above applies only to old version of the question:
Since then it has been revised and I think improved sufficiently for reopening.
My downvote and vote to close are revoked at rev 2. At rev 3, I upvoted.
As one of close-voters I can share what would definitely stop me from voting back then - or make me vote to reopen now that question is closed.
Given your comments in this question it feels quite doable:
I did my research and I am still open on this question since years, and nobody wants to give me a decent example to know how this is done in an appropriate way. All the repos I found generally are either made by people who does not care about quality (it's just a bunch of really hacked up scripts) nor platform transferability, nor addressing the different phases (development, testing, deployment, installing). In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer.
Now, let's see...
- All the repos I found...
- List these repos in your question.
- If list is very long, list a few that looked best to you.
- If it's very long and you can't select a few, just list them all in a "references" section at the bottom (it's not really hard to do)
- ...either 1) made by people who does not care about quality nor 2) platform transferability, nor 3) addressing the different phases 4) In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer
- Above makes your requirements - just list these in the question.
- If you not only list reqs but also clarify which particular requirements aren't met by particular repos in previous list I mentioned then I would upvote your question instead of closing
...well - that's it.
- note the answer update below
As one of close-voters I can share what would definitely stop me from voting back then - or make me vote to reopen now that question is closed.
Given your comments in this question it feels quite doable:
I did my research and I am still open on this question since years, and nobody wants to give me a decent example to know how this is done in an appropriate way. All the repos I found generally are either made by people who does not care about quality (it's just a bunch of really hacked up scripts) nor platform transferability, nor addressing the different phases (development, testing, deployment, installing). In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer.
Now, let's see...
- All the repos I found...
- List these repos in your question.
- If list is very long, list a few that looked best to you.
- If it's very long and you can't select a few, just list them all in a "references" section at the bottom (it's not really hard to do)
- ...either 1) made by people who does not care about quality nor 2) platform transferability, nor 3) addressing the different phases 4) In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer
- Above makes your requirements - just list these in the question.
- If you not only list reqs but also clarify which particular requirements aren't met by particular repos in previous list I mentioned then I would upvote your question instead of closing
...well - that's it.
#update
Above applies only to old version of the question:
Since then it has been revised and I think improved sufficiently for reopening.
My downvote and vote to close are revoked at rev 2. At rev 3, I upvoted.
As one of close-voters I can share what would definitely stop me from voting back then - or make me vote to reopen now that question is closed.
Given your comments in this question it feels quite doable:
I did my research and I am still open on this question since years, and nobody wants to give me a decent example to know how this is done in an appropriate way. All the repos I found generally are either made by people who does not care about quality (it's just a bunch of really hacked up scripts) nor platform transferability, nor addressing the different phases (development, testing, deployment, installing). In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer.
Now, let's see...
- All the repos I found...
- List these repos in your question.
- If list is very long, list a few that looked best to you.
- If it's very long and you can't select a few, just list them all in a "references" section at the bottom (it's not really hard to do)
- ...either 1) made by people who does not care about quality nor 2) platform transferability, nor 3) addressing the different phases 4) In alternative, they give you fully CI/IDE solutions that are unreachable by a single developer
- Above makes your requirements - just list these in the question.
- If you not only list reqs but also clarify which particular requirements aren't met by particular repos in previous list I mentioned then I would upvote your question instead of closing
...well - that's it.