Simone Gianni wrote: > Hi Bernd, > I'm happy you asked me about Magma, even if it is only because of a > problem with a commit :D. I've had a task "Write about Magma" on my RTM > for quite a long time, and probably this is a good opportunity to start.
Probably, yes. Sorry for not replying earlier, I was too busy and hat to set away some dedicated time for it. > Regarding the commit, that is a Dojo layer, which is Dojo javascript > code packed in a single file. There has been some discussion about > whether Dojo can be included or not inside Apache SVN, cause while it is > okay to include a dependency binary version, Javascript does not have a > binary version of its own. Some projects are committing the entire Dojo > sources (incubator/XAP, Lenya, Tapestry and a few others), I just > committed the "compiled" (that is single file, specifically trimmed > down) version needed to achieve better runtime performances, but I can > remove it if you (the PMC) decide it's not a good idea to have it on > Labs SVN. Unfortunately I didn't find a way to build those Dojo layers > from the Maven build, but this could be a good opportunity to write a > mojo for that task that would benefit a lot of other people. The question as always is, what's the license? > Regarding Magma itself, I work on it on a daily basis. It started as a > mere experiment, then I started to use it on internal projects in my > company, then managed to persuade a couple of brave customers to have me > use it for real-life purposes. On one side this happenend because I > believe in it, on the other side because I needed the challenges of real > life scenarios so that I can work on it a lot more than in spare free > time. It was quite a good experience, Magma worked out quite well, and > there are currently two (relatively small, but real) intranets done with > Magma in production excluding our internal stuff, and a website that > will be completed soon. So Magma currently has 1 developer and 3 happy > users : me and two employees of mine. > > As it often happens, when it comes to deadlines and customers, a lot of > good practices like "document first" and TDD tend to fade in background, > that's probably why I procrastinated the work of "public relations" so > much about my lab : it is there, it is (mostly :D) working, it is > evolving a lot like a lab should do, but I'm still the only one able to > manage and run it properly. The documents I posted on CWiki when the Lab > was opened were specifically written to build some interest, but are > unfortunately terribly outdated, and that is really blocking me from > presenting it and other people to join. > > With it's year of development, 131 resolved issues and 154 classes, > Magma is still a one-man-show, and I must admit I don't have such > incredible community building skills :) Well, I learned it's more about visibility, creating initial interest and having an easy and accessible way to tell the project's story, what it is, what it does and how. Then, people will come to you at some point. That means: Writing on the ML, on a blog maybe (we can have a Labs blog if you want!), having docs, an overview, tutorials, examples. > However I'm already working to overcome this problem, improving > documentation and developer friendliness. In the last few weeks I > started really working on javadocs (see LABS-285), I'm already working > on a "Pet store" demo of it, and hope to update all documentation, write > some introduction to motivations and concept behind it and howtos for > other developers to join the effort. +1 > I think I'll manage to do this before summer, in the meanwhile if > someone wants to have more details, help me out, or the PMC wants to be > kept updated, I'll be more than glad to answer, introduce, explain, > report, demo, discuss or whatever else. Well, of course we like updates, that'd be great. Bernd > > Simone > > Bernd Fondermann wrote: >> Hi Simone, >> >> can you please elaborate on this commit, where the code is coming from >> etc.? >> >> We (the Labs PMC) still need to execute oversight and you are working >> very silently and in a lights out way. >> >> So (at least) when you do large commits and add third party code please >> share some thoughts with the list (but even better for small commits, >> too). >> >> Actually, I don't know very much about your lab, what it does, where it >> is now and what the plans for the future are... >> >> Thanks, >> >> Bernd >> >> [email protected] wrote: >> >>> Author: simoneg >>> Date: Thu May 21 14:55:54 2009 >>> New Revision: 777140 >>> >>> URL: http://svn.apache.org/viewvc?rev=777140&view=rev >>> Log: >>> LABS-350 : datewidget profile for dojo 1.3.0 >>> <snip/> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
