Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Django-avatar and markdown2 are somebody else's modules, so there is no guarantee that the changes will be merged into the respective main projects - it is up to the people who are in charge.

As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?

Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.

Django-avatar and markdown2 Warkdown2 are somebody else's modules, module, so there is no guarantee that the changes will be merged into the respective main projects - it is up to the people who are in charge.

As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?

Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.

Warkdown2 Markdown2 are somebody else's module, so there is no guarantee that the changes will be merged into the respective main projects - it is up to the people who are in charge.

As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?

Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.

Markdown2 are is somebody else's module, so there is no guarantee that the changes will be merged into the respective main projects project - it is up to the people person who are is in charge.

As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?

Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.