The new [[m:Developer]] page talk about people initially contributing patches here on the mailing list and only after some time being given CVA access.
I don't consider myself up-to-speed enough in PHP to contribute actual code, but I would like to help in documenting what's there.
What would be an appropriate forum for posting proposed comments?
Phil Boswell wrote:
I don't consider myself up-to-speed enough in PHP to contribute actual code, but I would like to help in documenting what's there.
If you're talking about commenting the source code, you can submit patches for that here.
If you're talking about helping with writing the User Manual, that's at http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide.
Greetings, Timwi
Timwi wrote:
Phil Boswell wrote:
I don't consider myself up-to-speed enough in PHP to contribute actual code, but I would like to help in documenting what's there.
If you're talking about commenting the source code, you can submit patches for that here.
This is the one. What is the preferred format?
If you're talking about helping with writing the User Manual, that's at http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide.
That can wait until I figure out what's going on :-)
Phil Boswell wrote:
Timwi wrote:
Phil Boswell wrote:
I don't consider myself up-to-speed enough in PHP to contribute actual code, but I would like to help in documenting what's there.
If you're talking about commenting the source code, you can submit patches for that here.
This is the one. What is the preferred format?
Anything the 'patch' tool will accept. (The easiest way for you to create these patches is to use the 'cvs diff -u' command-line command.)
Timwi wrote:
Phil Boswell wrote:
Timwi wrote:
Phil Boswell wrote:
I don't consider myself up-to-speed enough in PHP to contribute actual code, but I would like to help in documenting what's there.
If you're talking about commenting the source code, you can submit patches for that here.
This is the one. What is the preferred format?
Anything the 'patch' tool will accept. (The easiest way for you to create these patches is to use the 'cvs diff -u' command-line command.)
Except I'm working on Windows. I have Cygwin but haven't installed the cvs stuff.
What is the least complicated route to follow? Should I install something like WinCVS? Do I need to soup up my account at SourceForge (which ATM merely knows who I am and remembers a few bookmarks for me)?
Once I have the correct software installed, which branch of the project would I want to look at? It seems that there's new changes going through every day, and I don't know whether I could keep up :-)
On Mar 31, 2004, at 07:05, Phil Boswell wrote:
Except I'm working on Windows. I have Cygwin but haven't installed the cvs stuff.
What is the least complicated route to follow? Should I install something like WinCVS?
Cygwin's command-line CVS works just fine. (Be careful about line endings, though, I don't recall whether it prefers Unix-style or DOS-style, but whatever it uses make sure your editor sticks with them!) It may be a little cryptic, but my eyes completely glaze over when looking at WinCVS.
Somebody (Tim?) has recommended TortoiseCVS: http://www.tortoisecvs.org/index.shtml
Do I need to soup up my account at SourceForge (which ATM merely knows who I am and remembers a few bookmarks for me)?
To commit directly to the repository you'd need to be added to the project, but you can check out files and makes diffs against them via anonymous CVS.
Once I have the correct software installed, which branch of the project would I want to look at? It seems that there's new changes going through every day, and I don't know whether I could keep up :-)
Don't do any development in the 1.2 branch! Work on 1.3, in the main head branch. Many things are changing.
-- brion vibber (brion @ pobox.com)
wikitech-l@lists.wikimedia.org