Additions:
~-Bug tracker: [[http://mantis.phplist.com/]]
Deletions:
Additions:
- [[PhplistSVN phplist code repository]]
Deletions:
Additions:
Phplist currently doesn't really have a very organised plan about direction of development. Most new features are added because someone requests the feature and is prepared to pay for it. If you find anyone who wants to pay you to add something, don't hesitate and go ahead. Probably best is to work on it in your own code branch, and then merge it into the main development branch. However, make sure not to take too long, otherwise merging becomes a nightmare.
When you start coding on your local system and make sure that it all works ok, you can either try to get write access to the Subversion repository, or submit a patch. As usual with open source development, getting write access to the repository will require a bit of kudos, which will take time to build up. So while you're not in that stage you can [[HowtoSubmitAPatch submit a patch]] instead. Once you've managed to submit a few patches that were clean to apply and did something nice to the system that didn't break anything, it should be easy to get write access.
- [[PhplistSVN phplist code repository]
When you start coding on your local system and make sure that it all works ok, you can either try to get write access to the Subversion repository, or submit a patch. As usual with open source development, getting write access to the repository will require a bit of kudos, which will take time to build up. So while you're not in that stage you can [[HowtoSubmitAPatch submit a patch]] instead. Once you've managed to submit a few patches that were clean to apply and did something nice to the system that didn't break anything, it should be easy to get write access.
- [[PhplistSVN phplist code repository]
Deletions:
When you start coding on your local system and make sure that it all works ok, you can either try to get write access to the CVS, or submit a patch. As usual with open source development, getting write access to CVS will require a bit of kudos, which will take time to build up. So while you're not in that stage you can [[HowtoSubmitAPatch submit a patch]] instead. Once you've managed to submit a few patches that were clean to apply and did something nice to the system that didn't break anything, it should be easy to get CVS write access.
There are some files in the "devdocs" module of the CVS on sourceforge, that I will gradually move to this Wiki, so it's all in one place, for now, please refer to those documents.
- [[PhplistCVS phplist CVS]]
Additions:
~-Most wanted [[FeatureRequest feature requests]].
Additions:
[[PhplistDevelopment phplist Development]]
- [[PhplistCVS phplist CVS]]
- phplist Architecture (These are pages that explain how phplist is constructed, the ideas behind the functionality)
- [[PHPlistRssConceptualSetup phplistRSSConceptualSetup]] : explains the behind-lying idea both for users and developers
- [[PhplistCVS phplist CVS]]
- phplist Architecture (These are pages that explain how phplist is constructed, the ideas behind the functionality)
- [[PHPlistRssConceptualSetup phplistRSSConceptualSetup]] : explains the behind-lying idea both for users and developers
Deletions:
- PhplistCVS
- PHPlist Architecture (These are pages that explain how PHPlist is constructed, the ideas behind the functionality)
- PHPlistRssConceptualSetup : explains the behind-lying idea both for users and developers
Additions:
When you start coding on your local system and make sure that it all works ok, you can either try to get write access to the CVS, or submit a patch. As usual with open source development, getting write access to CVS will require a bit of kudos, which will take time to build up. So while you're not in that stage you can [[HowtoSubmitAPatch submit a patch]] instead. Once you've managed to submit a few patches that were clean to apply and did something nice to the system that didn't break anything, it should be easy to get CVS write access.
Additions:
Miscellania about this wiki: [[AboutThisWiki click here]].
Additions:
**Important**: if you want to create a new wiki page for Development, please use the [[DevelopmentTemplate Development page Template]].
- Developer Howto's
===Translation Project===
Everything on [[PhpListTranslation translation of phplist]]
- Developer Howto's
===Translation Project===
Everything on [[PhpListTranslation translation of phplist]]
Deletions:
- **Developer Howto's**
Additions:
- **Developer Howto's**
===Add-ons, plugins, tricks, MODs===
- [[PhplistHacks Hacks]]: Tricks, code modifs and add-ons that are not part of the actual phplist distribution, but can simplify life a lot. Some php or system knowledge required.
===Editor===
How to use different HTML editors with PHPList.
- [[UsingFCKEditor FCKEditor]]
- TinyMCE
===Add-ons, plugins, tricks, MODs===
- [[PhplistHacks Hacks]]: Tricks, code modifs and add-ons that are not part of the actual phplist distribution, but can simplify life a lot. Some php or system knowledge required.
===Editor===
How to use different HTML editors with PHPList.
- [[UsingFCKEditor FCKEditor]]
- TinyMCE
Deletions:
Additions:
- PHPlistRssConceptualSetup : explains the behind-lying idea both for users and developers
Additions:
- ProcessQueueWorkFlowDescription
Deletions:
Additions:
===Overview:===
- Developer Howto's
- CodingStyle
- DevelopmentEnvironment
- PhplistCVS
- HowToSubmitPatches
- PHPlist Architecture (These are pages that explain how PHPlist is constructed, the ideas behind the functionality)
- ProcessQueueDescription
- Developer's sandbox (These are pages quickly scribbled together, needing to be incorporated in the overall structure)
- RecentFeatureAdditions
- Developer Howto's
- CodingStyle
- DevelopmentEnvironment
- PhplistCVS
- HowToSubmitPatches
- PHPlist Architecture (These are pages that explain how PHPlist is constructed, the ideas behind the functionality)
- ProcessQueueDescription
- Developer's sandbox (These are pages quickly scribbled together, needing to be incorporated in the overall structure)
- RecentFeatureAdditions
