[beports] Re: PortLogPlugin and the new host

On Thu, Jun 5, 2008 at 3:26 AM, Brecht Machiels <brecht@xxxxxxxxxxx> wrote:
> Hello all,
>
> I have installed Trac together with a preliminary version of the PortLog
> plugin at http://ports.haiku-files.org/ The Trac content (and svn repo)
> is an old backup of the Assembla Trac site. It is only meant for
> evaluating and debugging the plugin for now. Once we are happy with the
> way things work, we can move over the latest content from Assembla and
> migrate. I'll send account information to Andreas and Scott. Others who
> would like to evaluate the plugin, please send me an email.
>
> The plugin basically stores port information in the Trac database and
> adds forms to the wiki pages to change it. I'll try to summarize what
> this changes to the way things work.
>
> Before a portlog entry can be written, the port needs to be added to the
> database. Use the form at
> http://ports.haiku-files.org/wiki/PortLog/AddPort to do this. Once this
> is done, you can add a version. Once a version is added, port revisions
> of this version can be added.
>
> As you will see, the PortLog is now more fine-grained. The log of one
> port are no longer on one wiki page. Instead, each port revision has its
> own wiki page. Along with this, the http address to a port's log got a
> bit longer. It now looks like this:
> http://ports.haiku-files.org/wiki/<category>/<port>/<version>/<revision>
> Here's an example: http://ports.haiku-files.org/wiki/dev-lang/perl
>
> The plugin now auto-generates headings and part of the 'wiki content'
> for each of the wiki pages in this hierarchy:
> * the category page list all ports that belong to it. There is also room
> to add a description for each category
> * the port page displays information about the port: description,
> homepage, license (I though this might be interesting in view of the
> recent discussions about including license information in Haiku
> packages). The page also lists all versions and port revisions of that
> port.
> * the version page lists all dependencies and revisions.
> * the revision page lists the maintainer(s) and the status of the port
> on each of the three platforms.
> Additionally, The PortLog page now includes a macro that lists all
> categories.
>
> Each entry in the database (a category, a port, a version, ...) has a
> wiki page associated to it. The actual port log text will be included in
> the revision wiki pages. The other wiki pages can be used to include
> more general information. For example, some information might be common
> to all versions of a port and could thus be included in the port's wiki
> page. This also means that the current port logs will all be displayed
> on the port's wiki page. We should move these to the appropriate
> version/revision pages.
>
> When a port is added to the database, a component will be created for
> it. Tickets can thus be assigned to a specific port. It is no longer
> necessary to add "[portname]" to each ticket description. I realize the
> list of ports will eventually grow very large, so I have included the
> javascript that is used on the Haiku Trac site to transform the
> component select menu into two select menus. There seems to be a problem
> with this on the haiku-files server, so it is not functional at the
> moment. I will look into that later.
>
> I will import the PortLog code into the repository so that anyone who
> wants can have a look (beware though, it's not very pretty in its
> current state).
>
> I'm awaiting suggestions :)
>
> Cheers,
> Brecht
>

I've only done a few tests so far, but it seems that the status drop
down selectors don't always take, sometimes I have to try it a few
times before they are actually saved.  And when they do stick I see a
warning saying that the page isn't saved, but it really was.  Also
with the version and revision being shown after the portname is there
a way to make the left hand column wider on the front page so that
most of them will only take up a single line instead of breaking in
two, and will fit in the shaded background area nicer as well.
Overall looks like a nice improvement over the current setup.  Give us
a warning a day or two before you snapshot the assembla sight so that
we don't add info during the time you are migrating the live image
over.
I'll play around with it a bit more and see what else i uncover.
-scottmc

--
BePorts homepage - http://tools.assembla.com/BePorts
List archives: http://www.freelists.org/archives/beports
Administrative contact: brecht@xxxxxxxxxxx

Other related posts: