On Feb 29, 2008, at 1:18 PM, Thomas Tempelmann wrote:
> On 22.02.2008 0:17 Uhr, "Joe Strout" <jo...@st...> wrote:
>
>> I've created a simple folder hierarchy in subversion, with "main" and
>> "prototype" at the root level. Under prototype, I've checked in
>> Seth's work for BKeeney Software.
>
> Assuming one of us would update the Lexer, would we update it in
> the main
> dir only, or should we update the prototype folder as well?
>
> I guess I do not understand the idea of the prototype folder yet.
Well, the idea behind the prototype folder is a place to store things
that may or may not turn out to be generally useful enough to be
incorporated into the main project. We may have several different
lexers, parsers, etc. hanging out under prototypes, and we make no
claims about them (other than they're available under the MIT
License). The main project, as I see it, is where we collect the
code that we have generally found to be most useful for the project
aims (i.e. RB code analysis) -- ideally, just one lexer, one parser,
one project reader, and so on, and that's the code we try to keep up
to date and always working with the latest version of RB and so on.
But the prototype folder could also serve as a place for side
projects -- things which are actively maintained by one or more
members of the group, but not by the group as a whole. So, for
example, if Bob and Seth want to continue updating their
BKeeneyProjReader project and making those updates available via the
SourceForge project, that's fine too.
I realize this is a bit nebulous, since our main project isn't really
a product in itself, but just a collection of code that would be
useful for making a variety of projects. But it's the best
distinction I could come up with. I'm open to suggestions if anybody
has them.
Best,
- Joe
|
