Re: [Embedlets-dev] Re:[Ant] Build vs Deployment vs Management processes
Status: Alpha
Brought to you by:
tkosan
|
From: Nicola K. B. <nic...@ap...> - 2003-02-07 08:42:57
|
Ted Kosan wrote, On 07/02/2003 9.21: > Topic tags:[AR][GW][DO][HW][PM] > _______________________________________________ > > Nicola, > > >>All this discussion on Ant... why don't you all just >>try it and ditch it with the speed of light if there >>is a better alternative or it doesn't work? > > > This hits on a question I have been thinking about with regards to open source > development. Since Andrzej will probably be the first committer for the > Embedlet Container, and I will probably be the first committer for the Wiring > Tool, is it acceptable for us to kind of force an issue like this by submitting > these initial code bases with Ant build scripts and a directory structure > optimized for use with Ant? Somehow this does not 'feel' quite right and yet > perhaps allowing the initial 'doers' to make decisions like this is open > source's practical solution to a tough problem? [snipped cool explanation of cross-skill interaction] Wow, very well said. Flag this, it will make a good project-goals page :-) BTW, I'm also an almost-mechanical-engineer (stopped my studies nar the end because of health problems, but now I'm restarting while I work). I liked playing with simple circuits when I was a kid (the eversturdy NE555), and I work in an automation firm, so I know the basics and the latest PLC advances, but have never really actively done anything with my hands. Probably this could help me somewhat. >>I am *very* ignorant about embedded devices, but >>this is inversely propositional to my interest >>in it and in my knowledge of Ant ;-) > > > And of course I am just getting started with Ant but know much about embedded > systems. ;-) ;-) > I have a couple of ideas here: > > 1) What does everyone think about us setting up a CS-oriented > developer/Embedded Systems developer list within this project where people from > both areas can ask hand-holding level questions to each other? I know that > there are a lot of CS-oriented questions I would like to know the answers to > but the main developer list does not seem to be the best forum for doing this. > If we are going to try to integrate these two areas, a 'no question is too > stupid' list like this might prove to be helpful. Usually creating separate mailing lists is not something I encourage at Apache, since it usually divides discussions more than one would want. Why not simply prepending each of these with [newbie] or [ant] ? Those not interested can filter. > 2) Are you interested in learning how to start playing with a Java based > embedded system like TINI? If so I will send you a free TINI and help you to > get up and running with it. This should help for gaining a feel for what the > embedded systems side of 'the great divide' is like. ;-) :-D Yeah! +1 >>I want to help in this great project and don't really get >>it just yet ;-) > > > Well, you already have started to help! I downloaded Forrest this week and > started playing with it (I even forced myself to download the source version > and build it from scratch in order to learn how to do this better). I must say > that Forrest is an amazing piece of work and I am in the process of setting it > up for an experimental version of the Embedlets.org main web site. Cool! > I am firmly convinced that at least 50% of the benefits derived from this > Embedlets project is an open source community where the CS-oriented world and > the Embedded Systems world can be brought together and synthesized. If this is > true then it is going to be very important for use to develop, publish and > maintain a significant number of documents which explain exactly what we are > doing and how each area relates to the other. After studying this problem for > the past couple of months I have not found a system that even comes close to > Forrest for solving it (thanks for the tip!). Call it by its name, "shameless plug" ;-) > Let me know about the TINI, yeeessss!!! :-) -- Nicola Ken Barozzi nic...@ap... - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- |