coWiki 0.3.4
Current user:   guest   Change Preferences
   List directory   Similar   Print version 
Diff: Development
 Legend:   Removed   Changed   Added 
 Ownership:  rw-rw-r-- iezzip users
 Modified:  28 Apr 04, 10:53
 Modified by:  Philip Iezzi (iezzip)
Rev.:  5 (Old)
 
 Ownership:  rw-rw-r-- iezzip users
 Modified:  12 Mar 06, 14:57
 Modified by:  Philip Iezzi (iezzip)
Rev.:  11 (Current)


+ %TITLE%

---
+ %TITLE%

---

<plugin com.recent cutoff="30" title="Recent comments" style="float:right; margin-left:10px;">
++ Interested in Helping out?

<q>
There are many ways to help out with PHPee.com projects. If you're not a developer you can submit bug reports or feature suggestions. When doing this please make sure to include all the information you can while reporting, including: Operating System, PHP version, and project version. Also include any files your having problems generating docs from.


* *Sourdough framework* ((http://sourceforge.net/tracker/?group_id=107716&atid=648509)([bug reports])) ((http://sourceforge.net/tracker/?group_id=107716&atid=648512)([feature requests]))
* *Pigalle* ((http://sourceforge.net/tracker/?group_id=70477&atid=527929)([bug reports])) ((http://sourceforge.net/tracker/?group_id=70477&atid=527932)([feature requests]))
* *YaBook* ((http://sourceforge.net/tracker/?group_id=107713&atid=648501)([bug reports])) ((http://sourceforge.net/tracker/?group_id=107713&atid=648504)([feature requests]))
* *PPhlogger* ((http://sourceforge.net/tracker/?group_id=54850&atid=475071)([bug reports])) ((http://sourceforge.net/tracker/?group_id=54850&atid=475074)([feature requests]))


++ Interested in Helping out?

<q>
There are many ways to help out with PHPee.com projects. If you're not a developer you can submit bug reports or feature suggestions. When doing this please make sure to include all the information you can while reporting, including: Operating System, PHP version, and project version. Also include any files your having problems generating docs from.


* *Sourdough framework* ((http://sourceforge.net/tracker/?group_id=107716&atid=648509)([bug reports])) ((http://sourceforge.net/tracker/?group_id=107716&atid=648512)([feature requests]))
* *Pigalle* ((http://sourceforge.net/tracker/?group_id=70477&atid=527929)([bug reports])) ((http://sourceforge.net/tracker/?group_id=70477&atid=527932)([feature requests]))
* *YaBook* ((http://sourceforge.net/tracker/?group_id=107713&atid=648501)([bug reports])) ((http://sourceforge.net/tracker/?group_id=107713&atid=648504)([feature requests]))
* *PPhlogger* ((http://sourceforge.net/tracker/?group_id=54850&atid=475071)([bug reports])) ((http://sourceforge.net/tracker/?group_id=54850&atid=475074)([feature requests]))



Please do NOT file any feature requests of planned features that are already listed on each project's status page: ((Pigalle|Status)(Pigalle Status)), ((YaBook|Status)(YaBook Status))

You might also want to checkout the other information on the SourceForge project pages.
</q>

---

You might also want to checkout the other information on the SourceForge project pages.
</q>

---

++ CVS access
++ Language localization

<q>
<q>
You can obtain a current copy of the source code of each project using CVS. Here is how to check out the latest HEAD:
We are still looking for translators. Currently Pigalle and YaBook do only support *en*<noop>/</noop>English and *de*<noop>/</noop>German. PowerPhlogger does currently support 20 different languages. Those 20 languages are also planned to be supported in the future release of PowerPhlogger, Phlogger3.

<code>
$>
cvs -d :pserver:anonymous@cvs.phpee.com:/repository login
Password:
[anonymous]
$>
cvs -z3 -d :pserver:anonymous@cvs.phpee.com:/repository co modulename
</code>

If you find some time doing a translation, please join the ((Forum / Mailing lists)(development mailing lists)) (*pigalle-devel*, *yabook-devel*) and let us know. Existing translators of PowerPhlogger will be notified as soon as the first alpha release of Phlogger3 is out.

Thanks
a lot for your great help!
</q>

---

++
So you want to contribute?

<q>
There
are several ways you can start contributing to PHPee.com projects. As first steps you should:

*1.
Get the code.*

...whereas /modulename/ is one of the following: *sourdough*, *pigalle*, *yabook*, *pphlogger*
Either install a ((Downloads)(snapshot)) or do a ((Subversion access)(SVN checkout)).

Note: If you get an error from cvs when using the login command (=cvs login: warning: failed to open <noop>/username/.cvspass</noop> for reading: No such file or directory=) then repeat the login command.
*2. Find a bug to solve or a feature to implement.*

If you already have an existing version of any module and want to update:
If you decide to implement a new feature, it might be worth discussing it in the ((Forum / Mailing lists)(lists)) first, to test water, get feedback from lead developers and see if anybody is already working on it or if it fits at all into the general direction of the project.

*3.
Submit a patch.*

There
are two ways to do a patch. You could make a copy of file you edit beforehand, and create a patch with:

<code>
<code>
$> cd <your module directory>
$>
cvs -z3 -d :pserver:anonymous@cvs.phpee.com:/repository update -APd
diff -u file.php.orig file.php > file.php.patch
</code>

</code>

For Windows users, there are a number of graphical CVS clients available such as the very capable and easy-to-use ((http://www.tortoisecvs.org/)(TortoiseCVS)). You should also try a current beta version of ((http://www.wincvs.org/)(WinCVS)).
</q>

or do it with Subversion:

<code>
svn
diff file.php > file.php.patch
</code>

Submit
your patch to the project's ((Forum / Mailing lists)(development mailing list)). Please include your patch as a text/plain attachment. Be prepared to be met with a critical analysis of your patch. In case your patch is refused, ask why and either correct your patch or constructively argue your point. In case you receive no feedback, try bumping the issue once after a day or three. If you still do not receive an answer, maybe your patch is not worthwhile. Keep it in case someone raises the issue in the list sometime in the future, but otherwise sleep on it.


---

---

++ Browse CVS Repository

<q>
We
also provide a web-based interface to view CVS repositories. Browsing the CVS tree gives you a great view into the current status of each project's code. You may also view the complete histories of any file in the repository.
As general points to remember:


*
Respect the project coding standards, otherwise your patches will not be commited. You can find the coding standards in your sourdough directory under sourdough/doc/CODING_STANDARDS or directly from ((https://svn.phpee.com/public/sourdough/trunk/doc/CODING_STANDARDS)(SVN)).
*
Work within the framework, that is use the available classes and mechanisms.
*
Monitor the ((Forum / Mailing lists)(development mailing lists)), the ((http://forum.phpee.com/)(discussion board)), and those of the apps you work on.


Lastly,
remember that, although you work on the project on your own goodwill, this does not grant you any specific privileges. The lead developers make the final call. Sometimes, they may make decisions that you may not agree with. Obviously, you are entitled to voice your opinion and argue your point, but stay civil, do not drag it out and respect their decisions.

* *((http://cvs.phpee.com/)(Browse CVS Repository))*
That is pretty much it. One last thing: do not do it for an ego boost, do it for the love of coding. The unfortunate truth is that contributing to an OSS project will most likely never get you the kind of fame Linus Torvalds or RMS enjoy, nonetheless, as with any Open Source project, your contribution will be greatly appreciated by the community.
</q>
</q>


Home | Pigalle | YaBook | PPhlogger | Sourdough | RSS 1.0 | GEO URL

Driven by coWiki 0.3.4 (Boron) web collaboration tool.