[kepler-dev] Getting rid of CreateModulesBundle

[Aaron Schultz]

I second David's suggestion that any developer should be allowed to edit 
any document in the developer area of the plone site.

I came across this recently where I did not have permission to edit a 
page that needed editing and so I didn't edit it because it was more 
trouble than it was worth to ask for permission to edit that page.   The 
whole idea of a wiki is that anyone can edit it, and people who care 
about specific content are notified of the change, all the history is 
recorded and so it can be rolled back if deemed inappropriate.

If we can't trust each other than who can we trust?

Aaron


David Welker wrote:
> Hi Daniel,
>  
> Nice work! I will update that documentation. I think we should fix the 
> permissions on the plone site so that everyone can edit anything, 
> unless it is extra sensitive or something. I think if you have access 
> to the site at all, you probably can be trusted to not edit it 
> maliciously.
>  
> David
>
> On Fri, May 15, 2009 at 2:36 PM, Daniel Crawl <crawl at sdsc.edu 
> <mailto:crawl at sdsc.edu>> wrote:
>
>
>     Hi David,
>
>     Done!
>
>     I fixed all the references to org.kepler.core.loader.Loader
>     in the source code that I could find; let me know if I
>     missed any.
>
>     I also fixed the references on the Kepler web site, except
>     the following (I don't have permission):
>
>     https://kepler-project.org/developers/teams/build/developing-a-hello-world-actor-using-the-kepler-build-system-and-eclipse
>     https://kepler-project.org/developers/teams/build/documentation/build-system-instructions
>
>
>
>     Thanks,
>
>      --dan
>
>
>
>
>     David Welker wrote:
>
>         Hi Daniel,
>
>         The loader module is no longer used for 1.0. We have an older
>         version of
>         loader that is used now. I think it would be a great idea to
>         merge the
>         functionality of the two classes so we have only one startup
>         class. While we
>         are at it, we should just go ahead and refactor it so that it is
>         org.kepler.Kepler or even just Kepler (with no package). I do
>         not recall any
>         objections when that was suggested several days ago.
>
>         David
>
>         On Tue, May 12, 2009 at 1:13 PM, Chad Berkley
>         <berkley at nceas.ucsb.edu <mailto:berkley at nceas.ucsb.edu>>wrote:
>
>          
>
>             If you extend ModulesTask, you can use the local variable
>             modulesTree and
>             increment through that.  If you need to access that in
>             kepler, we might need
>             to make a singleton instance or something that you can get at.
>
>             chad
>
>
>             Daniel Crawl wrote:
>
>                
>
>                 Hi David,
>
>                 I'm happy to remove it, if you can please suggest an
>                 alternative: how can I get a list of modules used
>                 (inside a running Kepler)?
>
>                 Thanks,
>
>                  --dan
>
>
>                 David Welker wrote:
>
>                      
>
>                     Hi Daniel,
>
>                     I was wondering whether, since CreateModulesBundle
>                     is not really
>                     necessary, whether or not you could remove it in
>                     the near future?
>
>                     Thanks!
>                     David
>
>                            
>
>                 _______________________________________________
>                 Kepler-dev mailing list
>                 Kepler-dev at kepler-project.org
>                 <mailto:Kepler-dev at kepler-project.org>
>                 http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
>
>                      
>
>
>          
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>