Port extensions from old website

[samdark]

• Use the same data.
• Use the same URLs.

[cebe]

why? or what for? same question also for #16

[samdark]

Because 1.1 will be still there.

[cebe]

yeah, we should copy 1.1 data but it does not need to be read-only...

[qiangxue]

Copying 1.1 data to yiicamp.com could make the latter very messy because we plan to use a different way to list extensions. It also has ownership problem since yiicamp.com will use its own user system.

[cebe]

okay, now I see what the issue is about.

[qiangxue]

I hope authors of 1.1 extensions and wiki articles will copy their work to yiicamp.com gradually so that we can phase out 1.1 content ultimately.

[qiangxue]

Perhaps we should start developing yiicamp.com now? We can limit the initial scope of yiicamp.com to contain extensions and wiki articles only with limited features.

I don't think users will like the situation that the extensions/wikis on yiiframework.com are read only and there's no place to upload/update them.

[samdark]

OK.

[cebe]

I think so too, lets start with yiicamp now to see how it works. First aming at minimal necessary funcitionality.

[samdark]

@qiangxue can you create another repo for yiicamp?

[qiangxue]

https://github.com/qiangxue/yiicamp.com

[samdark]

Who's going to set up initial structure?

[qiangxue]

Feel free to create it if you have extra time to burn. I probably will do it during the weekend if it has not been done by then. Perhaps we can use the basic project template for simplicity? The admin features will be just subpages.

[samdark]

Done. Layout it a bit borked but overall it should be OK.

[cebe]

ref yiisoft/yii2#2395

[cebe]

• implement star/bookmark Implement star/bookmark for wiki and extensions #166
• implement rating Implement +1 / -1 rating for comments, wiki and extensions #167

[cebe]

related: #19