| # |
Oct 10th 2010, 22:20 |
PhpNut |
savant: did it let you change your email ? |
| # |
Oct 10th 2010, 22:19 |
PhpNut |
just found it out last night |
| # |
Oct 10th 2010, 22:19 |
PhpNut |
not sure what the issue is yet |
| # |
Oct 10th 2010, 22:19 |
PhpNut |
on your profile |
| # |
Oct 10th 2010, 22:19 |
savant |
thats hilarious |
| # |
Oct 10th 2010, 22:19 |
savant |
im sorry |
| # |
Oct 10th 2010, 22:19 |
PhpNut |
yes |
| # |
Oct 10th 2010, 22:19 |
savant |
wait, 1 field only? |
| # |
Oct 10th 2010, 22:19 |
savant |
thats all I tried to change |
| # |
Oct 10th 2010, 22:18 |
PhpNut |
have you tried that? |
| # |
Oct 10th 2010, 22:18 |
PhpNut |
you can change 1 field at a time only |
| # |
Oct 10th 2010, 22:18 |
PhpNut |
savant: that is a known issue |
| # |
Oct 10th 2010, 22:18 |
savant |
true |
| # |
Oct 10th 2010, 22:18 |
PhpNut |
some of the translations suck, but it is much better than original bakery |
| # |
Oct 10th 2010, 22:18 |
savant |
you cannot update your email, fact. |
| # |
Oct 10th 2010, 22:18 |
savant |
there is a bug |
| # |
Oct 10th 2010, 22:18 |
PhpNut |
first thing on the agenda is to update to the version that allows editing of the auto translated articles |
| # |
Oct 10th 2010, 22:17 |
PhpNut |
yes |
| # |
Oct 10th 2010, 22:17 |
savant |
like everything else? |
| # |
Oct 10th 2010, 22:17 |
savant |
haha |
| # |
Oct 10th 2010, 22:17 |
PhpNut |
so expect to see some crap coming in soon :) |
| # |
Oct 10th 2010, 22:17 |
savant |
well this would be slightly different |
| # |
Oct 10th 2010, 22:17 |
savant |
hence a maintainer of that |
| # |
Oct 10th 2010, 22:16 |
PhpNut |
there is no longer moderation on articles |
| # |
Oct 10th 2010, 22:16 |
savant |
right |
| # |
Oct 10th 2010, 22:16 |
PhpNut |
I like the idea, but it could be hard to implement it properly if a user is not using the correct naming conventions etc |
| # |
Oct 10th 2010, 22:16 |
savant |
Quite a few articles could easily be plugins, or are plugins and havent been updated |
| # |
Oct 10th 2010, 22:15 |
savant |
will the files be vetted (as large != component/behavior etc) |
| # |
Oct 10th 2010, 22:15 |
savant |
and then? |
| # |
Oct 10th 2010, 22:15 |
PhpNut |
savant: there are plans to move large code blocks to archive files right now |
| # |
Oct 10th 2010, 17:06 |
savant |
A good example of where this would be useful is http://bakery.cakephp.org/articles/interlock/2010/08/22/configure-plugin |
| # |
Oct 10th 2010, 16:54 |
savant |
comments? |
| # |
Oct 10th 2010, 16:54 |
savant |
but that is up for discussion |
| # |
Oct 10th 2010, 16:53 |
savant |
And what will happen if a user does not wish to attach a project to their github profile |
| # |
Oct 10th 2010, 16:53 |
savant |
I have not yet considered how re-translation is handled |
| # |
Oct 10th 2010, 16:53 |
savant |
Once it is moved over, the user can be given an opportunity to update their article, and a link to the github clone url can be added to the article automatically |
| # |
Oct 10th 2010, 16:52 |
savant |
upon verification of proper plugin creation, a user can be sent an email notifying them that they can clone over the plugin to their own github profile, and it would be an automated process on the bakery servers to move the code over |
| # |
Oct 10th 2010, 16:51 |
savant |
and packaged with the plugin (although this process would be more brittle) |
| # |
Oct 10th 2010, 16:51 |
savant |
the article itself might be used as a readme, and if the plugin was built correctly, those codeblocks which are classes would be removed and the article slightly updated as a readme |
| # |
Oct 10th 2010, 16:50 |
savant |
a notification can be raised to someone curating this - I would volunteer if no one else wishes to - who can verify that a plugin was properly generated |
| # |
Oct 10th 2010, 16:49 |
savant |
from there, inflecting classnames would be used to properly name files and move them into their respective paths, with any extraneous, unparsed classes going into the "libs" dir to be sorted manually |