search

yiisoft / yii-core

Yii Framework 3.0 core
https://www.yiiframework.com/
433 stars 75 forks source link

Yii3 Dev organization #129

Closed machour closed 5 years ago

machour commented 5 years ago

Hi there,

The team have been on vacations the past few days, and it was the perfect occasion for me to discover Yii3 state in peace (without big changes happening). That wasn't enough time to fully dive into all the changes, but enough to have a fair grasp, with the awesome help of @hiqsol 🙏

I'd like to propose some ideas regarding how Yii 3 development is organized, because from my outside point of view, the current workflow (or lack of it) is one of the main blocking point if we want to get Yii 3 out.

Maybe something like this is already in use, and I've missed it, but if it doesn't, then I personally think it's a must.

Tests

As you may have noticed, I've been working with @FabrizioCaldarelli on fixing travis setups, tests & various breakages in code. Figured out it will be a good way to get started and see what changed.

You can see the progress here: https://github.com/yiisoft/docs/blob/master/000-packages.md#yii-framework

I personally think that turning and keeping all Travis badges green should be the first focus of the Team as it gets back to working on Yii.

Proposed solution:

Fix them all in a collective effort, then enforce the following rules:

We also need to come up with a way to trigger a travis build of all projects once in a while.

Centralize Discussions

There are quiet a few important points being discussed for Yii3 development, sometimes on Slack, sometimes it's sparks on the 14th comment of a merged PR, .. The big picture have been split along with the packages, and that's not good project-wise.

Proposed solution:

Create a yiisoft/rfcs or yiisoft/todo repo and open an issue in it for every important decisions/discussion currently happening.

We would then either continue the dialog in the newly created issue, or just add a link to point at where the discussion is taking place.

Once concensus have been reached (when it's needed), the issue would be updated with the final decision, making it easier to know that there's a final word, and what that word is.

Project Management

It's currently unclear who's working on what, and where the global situation at.

Proposed solution:

Set up GitHub Projects on the rfcs repo mentioned above, and use it to schedule some kind of roadmap for development.

Columns would go something like:

2019 looks like a promissing year for the framework!

samdark commented 5 years ago
  1. Fully agree about tests.
  2. Discussions for 1.0, 1.1 and 2.0 were happening at the forum. I can create a section there for RFCs.
  3. I can create a board here at github (no need for it to be separate repo, boards are oragnization-wide) but I need someone to take care about it. I know how to do it but sometimes I have too little time to handle it.
machour commented 5 years ago

I'd be happy to help with 3 if you grant me proper access!

samdark commented 5 years ago

@machour invite sent.

fcaldarelli commented 5 years ago

Where will this board be accessible ?

samdark commented 5 years ago

https://github.com/orgs/yiisoft/projects/12

schmunk42 commented 5 years ago

I saw that there's a channel #rfc on Slack, could we please avoid using that and use the forum instead. It's ridiculous that Slack charges you for you own content if you want to search in it later.

fcaldarelli commented 5 years ago

It's not active yet, right?

samdark commented 5 years ago

Closed slack channel.

machour commented 5 years ago

@samdark can the project visibility be set to public? It's currently org members only.

samdark commented 5 years ago

Done.

terabytesoftw commented 5 years ago

Yii 3.0 looks promising, as steve jobs said "the great artists like dylan, picasso, and newton risked failure, and if we want to be great, we have to take risks too".

jk2K commented 5 years ago

maybe we can add roadmap to the board, I don't know what can be done to speed up the release of yii3,

machour commented 5 years ago

@jk2k thanks, I'll open issues for the items in the Roadmap and use the Project to watch over them.

Once tests are okay, it will be easier for more people to help and speed up the project. There's no rush though. :)