# more ftp functions

- Thread: https://externals.io/message/13991
- Original archive: https://news-web.php.net/php.internals/13991
- Started by Binam on 2004-12-03T06:50:10+00:00
- Messages: 4
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #13991 — Binam — 2004-12-03T06:50:10+00:00

URL: https://externals.io/message/13991#13991

Let me rephrase that. This is my first contribution to php or any open
source project for that matter, and I have no idea what the process is.
Do I need to write the code first and submit a patch to someone? Do I
need to work with someone since I assume don't have CVS write access? Is
the process in the comments or documented somewhere and I am going to
get flamed for not reading them? ;)
 
Thanks,
Jess

---

## #13997 — Adam Maccabee Trachtenberg — 2004-12-03T16:35:43+00:00

URL: https://externals.io/message/13991#13997 · In reply to: #13991

> Let me rephrase that. This is my first contribution to php or any open
> source project for that matter, and I have no idea what the process is.
> Do I need to write the code first and submit a patch to someone? Do I
> need to work with someone since I assume don't have CVS write access? Is
> the process in the comments or documented somewhere and I am going to
> get flamed for not reading them? ;)

I would suggest you create a patch and post it to the mailing list. If
it's accepted, someone will commit it for you.

Regardless of what you do, I can't predict whether you will or will
not get flamed. :)

-adam

-- 
adam@trachtenberg.com | http://www.trachtenberg.com
author of o'reilly's "upgrading to php 5" and "php cookbook"
avoid the holiday rush, buy your copies today!

---

## #14011 — Wez Furlong — 2004-12-07T14:05:57+00:00

URL: https://externals.io/message/13991#14011 · In reply to: #13991

There's a README.SUBMITTING-PATCH file in the PHP source that gives a
fair amount detail on the preferred way to contribute to the project.

It boils down to submitting a patch (unified diff) against HEAD of CVS
to the internals list and CC'ing it to the appropriate extension
maintainer(s) (there is an EXTENSIONS file that should be more or less
up to date with who is looking after what).

Welcome :)

--Wez.



>  
> Let me rephrase that. This is my first contribution to php or any open
> source project for that matter, and I have no idea what the process is. Do I
> need to write the code first and submit a patch to someone? Do I need to
> work with someone since I assume don't have CVS write access? Is the process
> in the comments or documented somewhere and I am going to get flamed for not
> reading them? ;)

---

## #14016 — Andi Gutmans — 2004-12-08T00:37:42+00:00

URL: https://externals.io/message/13991#14016 · In reply to: #13991

You can lower the changes by supplying a unified diff :)

Andi

At 11:35 AM 12/3/2004 -0500, Adam Maccabee Trachtenberg wrote:
>
>
> > […]
>
>I would suggest you create a patch and post it to the mailing list. If
>it's accepted, someone will commit it for you.
>
>Regardless of what you do, I can't predict whether you will or will
>not get flamed. :)
>
>-adam
>
>--
>adam@trachtenberg.com | http://www.trachtenberg.com
>author of o'reilly's "upgrading to php 5" and "php cookbook"
>avoid the holiday rush, buy your copies today!