Hi all-
A hypothetical question for all of you add-on product developers out there...
I am doing some high-level thinking (which I will be sharing soon)
about the future architecture for add-on product data in plone.org,
and one question that's occurred to me is whether we are at a point
where
I still use them but would rather not. If you put a deprecation date up,
it'd help force me to more more of my packages to github and startup the
tracker there also.
+1 for github hosted. Very nice to have it coupled with the code repo.
On Wed, Feb 8, 2012 at 1:42 PM, Jon Stahl
On Wed, Feb 8, 2012 at 4:41 PM, derek aus...@pointerstop.ca wrote:
On Feb 8, 3:48 pm, Nathan Van Gheem vangh...@gmail.com wrote:
I still use them but would rather not. If you put a deprecation date up,
it'd help force me to more more of my packages to github and startup the
tracker there also.
Hi all!
In preparation for the upcoming Cioppino Sprint, which will likely
focus largely on improving plone.org, I took a bit of time to think
about what a roadmap for improving the infrastructure of our docs +
products sections could look like. My thinking is grounded in two key
assumptions:
I wouldn't need them exported. We could just close them to new submissions
for a period before completely shutting em down.
On Wed, Feb 8, 2012 at 9:57 PM, Jon Stahl jonst...@gmail.com wrote:
On Wed, Feb 8, 2012 at 4:41 PM, derek aus...@pointerstop.ca wrote:
On Feb 8, 3:48 pm, Nathan Van
Maybe we just always keep them read-only then.
On Wed, Feb 8, 2012 at 11:35 PM, T Kim Nguyen ngu...@uwosh.edu wrote:
What about the history we would be losing? Or bugs that have been
lingering, still unclosed?
I know I'm not a power coder but I still use Poi.
How many products have not
If you need to override only the template then use z3.jbot.
-aj
Gilles Lenfant-2 wrote
Hi,
Sorry for the disturbance, but I'm actually stuck overriding a standard
viewlet of Plone (4.1): The plone.links.RSS that goes in the HTML head.
Though I carefully read and practiced the tutorial
On 09/02/2012, at 6:42 AM, Jon Stahl wrote:
Hi all-
A hypothetical question for all of you add-on product developers out
there...
I am doing some high-level thinking (which I will be sharing soon)
about the future architecture for add-on product data in plone.org,
and one question that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry guys but once again: you can not force a project to move to
Github (sources and trackers) without explicit agreement of the
package owner or current package maintainer - at least not
for active packages where let's say the issue tracker is
Am 08.02.2012 20:48, schrieb Nathan Van Gheem:
I still use them but would rather not. If you put a deprecation date up,
it'd help force me to more more of my packages to github and startup the
tracker there also.
+1 for github hosted. Very nice to have it coupled with the code repo.
+1
10 matches
Mail list logo
