-
- Notifications
You must be signed in to change notification settings - Fork 158
Move application code to "src" directory #140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| @klimov-paul what do you think about it? |
| It's OK for new repositories but doesn't make much sense for existing ones. |
| Shouldn't break anything though so if @klimov-paul is OK with the change, I see no problem making it. |
| @samdark if you want to whitelisting code coverage in phpunit.dist.xml @ 9ef0dbd: and after that PR: |
| This matter is already been discussed at yiisoft/yii2#8452 (comment) Change can be applied. However there should be consistency between different repositories. |
| New extensions (queue, di) uses this template, so it's already inconsistent. |
| Give me some time |
| Let's switch. It's making everything a bit more structured. |
| @klimov-paul an elephant is eaten in parts. Let's do it 😃 |
| @samdark @klimov-paul hi, guys. I've created 2 PR in |
| Resolved by commit 7ccba47 |
| @klimov-paul can you tell me what kind of opensource development methodology are you using? I mean situation when you close my PRs
with cherry-picked commits from my branches authored by you. At least it looks like that. @samdark @cebe @qiangxue is it normal? I've never seen it on Github. |
| @zhukovra Of course, you should've been attributed. I think Paul did Since commits are in master, I don't think we can update them without changing hashes (will certainly cause trouble). Sorry. |
| What is all the fuzz is about? The original PR was incomplete: it missing 'debug' folder transfer and path update at 'tests/bootsrtap.php'. I am here to solve the code problems and move functionality forward, so I do. The goal of the development and contributing process is to set code right for the sake of its every user - not to achieve self-affirmation or personal glory. @zhukovra, if it is a glory you seek, try to fix some more significant issues, some of which you will be mentioned at |
| @klimov-paul basing your own commit on existing ones would've been a bit more fair... |
| Further discussion is useless. Thank you @klimov-paul, I understand your position. |
It is better to organize application code under a separate directory like
src. Also, it is a widely used convention.