[SM-Discuss] SCM tools...
Andrew "ruskie" Levstik
ruskie at mages.ath.cx
Sat Mar 11 03:13:47 EST 2006
Andrew wrote :
> Since this topic seems to come up from time to time, I'll recap where
> it last left off.
> Theres a couple ways to organize stuff:
> 1) by maintainer
> 2) by code-reusage
> 3) by some other random category like language, type, or usage
> Option 1 has the advantage that developers can own spells they actually
> maintain, rather than an entire section where they might not use
> everything. Its clear whats owned by someone, or by a group of people,
> and what isnt.
> Option 2 fits naturally with the grimoire/section inheritence we have
> setup, eg devel-python. Re-using code across sections makes it
> significantly harder to have portable spells.
> Option 3 makes the most sense from a users perspective since they could
> (in theory) find stuff because its well organized.
> Theres no reason we can't just use searchable keywords to help users
> find spells, and possibly to organize them into a multi-level symlinked
> hierarchy. That would accomplish the goals of option 3 *without* having
> to move spells around in the repository. Also, as evidenced from past
> grimoire re-org discussions, categorial organizations that make sense
> are different for every person. Trying to come up with one that satisfies
> everyone isnt going to happen. Its a loosing proposition.
> In other words, lets not bother trying to find the one true categorial
> organization scheme. Organize by code-reuse first, then by
> maintainership. Then use keywords to accomplish categorizing things (as
> opposed to picking one of a half dozen categories something could fit in).
> As an aside, I also wrote some scripts to re-arrange or build the
> grimoire on its way from the repository to the tree we are all familiar
> with. Basically spells can get organized in the repository based on who
> owns them. Then the scripts collate them into sections where they best
> share code with other spells.
> Perhaps the grimoire lead candidates can speak their thoughts on this
> topic :-)
Well since I started this one I'll comment no this ideas...
Per maintainer would be nice if we had enough maintainers to
Per code reuse+keywords is a nice idea for us developers but it makes it
harder to track end-user <-> code reuse section for bugs. There's also
always that hmm this spell doesn't werk but it works if used here not
there problem that might popup. Which would in turn give us more bugs
The current imho is quite well... reuse code where possible but make
the basic organization end-user friendly...
Also on a side note KEYWORDS[X] should be implemented in any case. They
could make searching for things easier for people starting with source mage
and gaze should default to it.
IF the keyword idea is utilized in a proper way and if our users find it
better than what we have currently then we could start debating on using
code-reusable grimoires and views of them.
Hope I didn't make much goofups... I did just woke up...
Andrew "ruskie" Levstik
Source Mage GNU/Linux Games grimoire guru
Hacker FAQ: http://www.plethora.net/%7eseebs/faqs/hacker.html
Key id = A7A9E461
Key fingerprint = 757E C16B F5B7 DC27 B003 CCED CF95 3A77 A7A9 E461
More information about the SM-Discuss