Re: stuff for hhh

On 09/03/2004, at 10:14 PM, Adam Megacz wrote:
> The ibex core will be GPL.  All subprojects (org.ibex.*, org.ibex.js,
> org.ibex.mips2java, and org.ibex.widgets) will be LGPL or BSDL

+1

> Each project will have a subdirectory in /var/www:
>
>    /var/www/
>             org/
>                 ibex/
>                      www/      (web site "subproject")
>                      widgets/
>                      core/
                       ...

+1

> Each project's Makefile will assume the following variables:
>
>   $(usr)      -- points to the stuff that's currently in
>                  upstream/install
>
>   $(build)    -- build directory [we need to discuss this]

+1

> I'd also like to try to standardize the top-level directory layout for
> projects like this:
>
>    Makefile
>    README
>    src/
>    web/   (more on this later)
>    doc/
>        AUTHORS
>        COPYING
>        ...

Looks good.

> And so forth.  The Makefiles have the required patches *built in*
> (using <<EOF).  In general I think we can trim down the amount of
> patching we're doing.

Can we do some kind of testing for when a patch fails? It's happened to 
me a few times when we were trying new versions of gcc a while back, 
and it's a real pain.

> This way you can build something like org.ibex.mips2java standalone,
> or as a "usr" package of the core.  But they'll share a common
> $(usr)/src/gcc/ source download.

Nice.

> Anyways, back to the repositories.  The cool part is that each
> ..www.. directory *is* the darcs repo!

Very cool.

>    repo.project.ibex.org

Few too many sub-domains for me.

>    project.ibex.org/repo/

This one's fine for layout but,

>    repo.ibex.org/project/

This might have an added benefit that we could either move the repo 
server to different hardware, or have mirrors setup with multiple DNS A 
records for repo.ibex.org.

> Should web be a subdirectory of doc?  Probably...

Probably, but it's different enough that I think it deserves it's own 
top-level dir.

> This is one point I'm not completely happy with; I'd prefer to have a
> single darcs repo for each project.  I'm actually thinking it might be
> better to give each developer his/her own "$USERID.users.ibex.org"
> (and the ability to make subdomains thereof).

Definitely, but I'd prefer users.ibex.org/$USER.

> If you want to test a new website layout, you just push it to one of 
> your personal subdomains.

+1, especially if it keeps us with one repo per-project.

> Lastly, although darcs' commit-via-patches thing is ubercool, I think
> the overhead of getting PGP working as well as having to maintain a
> duplicate set of ssh/pgp keys is just too much of a pain.  So,
> henceforth, once you get approval, just 'push --and-apply' via ssh.

This is fine by me, but I do like the idea of having PGP keys and using 
them for SSH.

> Which brings me to mailing lists.  I'd like to further streamline the
> whole system by having exactly one mailing list per subproject.

+1000. It's so simple it just might work.

> I think the only problem remaining is that there's no separation
> between the core list and the newbies list.

Ditch the users list.

> It's a big step forward.

Very much so.

> Oh yeah, one more thing.  People might not be happy about this, but
> I'd like to use jsp to limit all html documents to valid XML using a
> very restricted set of tags (mostly equivalent to guidexml or wiki).

Please. HTML is dead, long live XHTML.

> Styling will be site-wide, possibly with some color-scheme variations
> to distinguish the subprojects.  I guess it's sort of a branding
> thing.

Agreed, colours and logos is all that should vary (with the ibex logo 
being ever-present).

Have to say, very nice plan.

-- d