Re: [PHP-DOC] SVN Account Request: alejandrorodas
Nice work \o/ -Hannes On Mon, Dec 12, 2011 at 04:55, Yago Ferrer yago.fer...@gmail.com wrote: Hannes, All new members are committing their own files. I wrote a guide specific to help them after they get their own account. They are also subscribed to this E-Mail list. BTW: we have already translated 80%! If you are the administrator of another language I recommend you to write a few words in the credits page to get other people to help: It REALLY helps. This is how I´m getting most of the new members. (see http://www.php.net/manual/es/) Thanks! Yago On Sun, Dec 11, 2011 at 3:40 AM, Hannes Magnusson hannes.magnus...@gmail.com wrote: Approved. There are now _bucket load_ of people with spanish translation karma.. are all these new members active? Giving people svn account as a price for having translated several files is ok, but if they then never commit anything then it defeats the purpose of having svn account.. -Hannes On Sat, Dec 10, 2011 at 03:28, Yago Ferrer yago.fer...@gmail.com wrote: Can you please active this account? Thanks! Yago 2011/12/7 Yago Ferrer yago.fer...@gmail.com Philip, Can you please activate Alejandro´s SVN account? He said that many students at his university of computer science are taking advantage of our work and now its time for him to give back. These are the files he translated so far: /es/reference/pdo/prepared-statements.xml /es/reference/pdo/pdo/lastinsertedid.xml /es/reference/pdo/pdo/prepare.xml /es/reference/pdo/pdo/query.xml /es/reference/pdo/pdo/quote.xml Please find the files attached. Thank you! Yago On Tue, Dec 6, 2011 at 4:44 AM, Alejandro Rodas alexrd...@gmail.com wrote: I would like to have an SVN account to help with the Spanish translation of the PHP Manual. -- Yago Ferrer -- Yago Ferrer -- Yago Ferrer
[PHP-DOC] Contributions are ready for review
Hello PHP EN Documentation team, There are contributions within the online editor queue for this language. Please review, then commit or delete these patches. Patches for review : --- * (update) On 2011-05-26 09:31:28 by uw : en/reference/mysqlnd_ms/concepts.xml * (update) On 2011-06-27 21:34:04 by guilhermeblanco : en/language/predefined/errorexception/construct.xml * (update) On 2011-08-16 11:29:39 by rdohms : en/reference/strings/functions/strrchr.xml * (update) On 2011-08-21 16:53:17 by ch : en/reference/snmp/snmp/construct.xml * (update) On 2011-08-21 17:01:11 by ch : en/reference/snmp/book.xml * (update) On 2011-08-31 21:40:23 by breck7 : en/reference/network/functions/header.xml * (update) On 2011-09-24 04:35:10 by mch : en/language/predefined/variables/server.xml * (update) On 2011-10-11 06:36:22 by mch : en/reference/amqp/constants.xml * (update) On 2011-10-12 00:44:09 by mch : en/reference/gearman/gearmanclient.xml * (update) On 2011-10-22 14:16:59 by anonymous #11769 : en/language/operators.xml * (update) On 2011-10-27 04:16:08 by anonymous #11351 : en/reference/mysqlnd_ms/ini.xml * (update) On 2011-11-13 19:18:10 by anonymous #12333 : en/reference/curl/functions/curl-setopt-array.xml * (update) On 2011-11-15 11:21:38 by anonymous #12333 : en/reference/bzip2/functions/bzwrite.xml * (update) On 2011-11-15 11:21:59 by anonymous #12333 : en/reference/apc/apciterator/construct.xml * (update) On 2011-11-15 11:26:44 by anonymous #12333 : en/reference/apc/functions/apc-bin-dumpfile.xml * (update) On 2011-11-15 11:32:27 by anonymous #12333 : en/reference/zlib/functions/gzgetss.xml * (update) On 2011-11-15 11:35:47 by anonymous #12333 : en/reference/amqp/amqpexchange/publish.xml * (update) On 2011-11-15 11:39:06 by anonymous #12333 : en/reference/apache/functions/apache-getenv.xml * (update) On 2011-11-15 11:42:47 by anonymous #12333 : en/reference/apache/functions/apache-note.xml * (update) On 2011-11-15 11:43:59 by anonymous #12333 : en/reference/apc/functions/apc-add.xml * (update) On 2011-11-15 11:46:45 by anonymous #12333 : en/reference/apc/functions/apc-bin-dump.xml * (update) On 2011-11-15 11:47:47 by anonymous #12333 : en/reference/apc/functions/apc-cache-info.xml * (update) On 2011-11-15 11:48:46 by anonymous #12333 : en/reference/apc/functions/apc-clear-cache.xml * (update) On 2011-11-27 19:57:45 by joey : en/reference/apc/ini.xml * (update) On 2011-11-28 12:39:10 by anonymous #12769 : en/reference/exec/functions/shell-exec.xml -- https://edit.php.net/ This email is send automatically by the Php Docbook Online Editor.
Re: [PHP-DOC] Git support in PHPDoE
Now I'm confused. Is there a translation using git already? That is a big fat fat fat no no no no no. The PHP VCS infrastructure is about to move to git soon (https://wiki.php.net/rfc/dvcs), yes, but there will be no translation hosted out side of the PHP VCS infrastructure for any reason whatso ever. When the conversion have finished, all translations, english and doc-base will all be in the same git infrastructure. I wonder if PhDOE could start using individual git clones? Currently all patches and all work is stored up on a single shared checkout.. which brings its own bag of problems.. If a user could commit work to his local clone on PhDOE ( == WIP) and then push upstream? that would be cool I believe. Then anonymous users could also file a merge request so people wouldn't have to literally login to the OE and commit patches from there? -Hannes On Sun, Dec 11, 2011 at 17:29, Yannick Torrès yannick.tor...@gmail.com wrote: PhDOE is based on a VCS like Cvs or Svn. The major difficulty is that EN documentation will be steel on Svn, and translation, on Git. I'm worried about this change and the consequence on the PhDOE tools... Is there a treahd who explain why we must do this change ? Or it's just for fun with Git I really need to understand this change. Svn just works fine according to me to handle the documentation. Regards, Yannick 2011/12/11 Александр Москалёв ir...@irker.net 2011/12/11 Ferenc Kovacs tyr...@gmail.com http://linux.die.net/man/1/git-commit see --author From https://wiki.php.net/rfc/dvcs : Git can use HTTP Basic auth to verify whether a user is allowed to login. We can use HTTP Digest for authentication and an update hook to check whether the user is authorized to push to that directory. It will work with http basic auth? With regards, Alexander Moskaliov ir...@irker.net
Re: [PHP-DOC] Git support in PHPDoE
2011/12/13 Hannes Magnusson hannes.magnus...@gmail.com: Now I'm confused. Is there a translation using git already? That is a big fat fat fat no no no no no. No, it doesn't. The PHP VCS infrastructure is about to move to git soon (https://wiki.php.net/rfc/dvcs), yes, but there will be no translation hosted out side of the PHP VCS infrastructure for any reason whatso There's really some misunderstood going on. First of all, (it is a known fact, I just repeat it for clearance) *all* PHP infrastructure will go to git. There was a vote and it was decided (see Hannes's link), the work is already in progress . Docs (and translations) according to Philip willl be migrated last. When the conversion have finished, all translations, english and doc-base will all be in the same git infrastructure. I wonder if PhDOE could start using individual git clones? Currently all patches and all work is stored up on a single shared checkout.. which brings its own bag of problems.. If a user could commit work to his local clone on PhDOE ( == WIP) and then push upstream? that would be cool I believe. Then anonymous users could also file a merge request so people wouldn't have to literally login to the OE and commit patches from there? It could be local branches instead of full-fledged clones. Often anonymous patches (at least in translations) need review from a translation team member, so they rarely get commited as is, i.e. they need edit, so users still have to login to OE. -Hannes On Sun, Dec 11, 2011 at 17:29, Yannick Torrès yannick.tor...@gmail.com wrote: PhDOE is based on a VCS like Cvs or Svn. The major difficulty is that EN documentation will be steel on Svn, and translation, on Git. I'm worried about this change and the consequence on the PhDOE tools... Is there a treahd who explain why we must do this change ? Or it's just for fun with Git I really need to understand this change. Svn just works fine according to me to handle the documentation. Regards, Yannick 2011/12/11 Александр Москалёв ir...@irker.net 2011/12/11 Ferenc Kovacs tyr...@gmail.com http://linux.die.net/man/1/git-commit see --author From https://wiki.php.net/rfc/dvcs : Git can use HTTP Basic auth to verify whether a user is allowed to login. We can use HTTP Digest for authentication and an update hook to check whether the user is authorized to push to that directory. It will work with http basic auth? With regards, Alexander Moskaliov ir...@irker.net -- Regards, Shein Alexey
