-
-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coordinate PLIP process with documenting the PLIP's #14
Comments
add this to docs |
Sure. Happy to talk about it sooner too. On 18 Aug 2014, at 5:16, sven wrote:
|
Make it clear that 97% of the readme is not about papyrus as a while but...
Hi @svx is this issue about updating http://docs.plone.org/develop/plone-coredev/plips.html etc.? |
@tkimnguyen partly yes, but in the first case it is more about making sure that a plip has proper documentation before the plip gets merged. This of course can be differ a lot, depending on the plip. The idea is/was to 'assign a docs buddy' to the developer, we sadly still forgetting quite often to document. |
The big issue I noticed is that the docs still refer to the old dev.plone.org for PLIPping; I was looking it up to see how to create a PLIP. |
Well this has to be fixed in the docs of buildout.coredev [https://github.com/plone/buildout.coredev], once it is fixed there we will pull it into the docs. |
Superseded by plone/buildout.coredev#840 and #1278 |
The text was updated successfully, but these errors were encountered: