Welcome to The Hive Group! Be sure to subscribe, and don't forget to click "my subscription" if you want to subscribe to the mailing list.
See also:
The Hive Project
The Hive Project Issue Tracker
The Hive Group Forum
Performance Measurement & Testing
Thu, 2006-10-05 18:49 — tamhasMany sites become concerned about the performance of their ABL application at some time in the history of the site. While a big performance boost can often be achieved by simply moving to newer (and probably cheaper) hardware, this is not always an option, either because a reasonably powerful machine is already in use or there isn't sufficient budget for a change. The following links have been collected to provide some help for those concerned with performance.
Projects vs. "project nodes"
Wed, 2006-10-04 21:17 — john2You aren't required to have a project node in order to have a project!
A project on the Hive is anything that is active, growing, and being maintained. Even a library of web resources, or a library of articles, can be considered a valid project on the Hive.
If you want your project to be listed, just tell us which node to add to the list. It can be any kind of a node, like a "page" node, a "group" node, or even a "project" node. :)
A project node provides an issue tracking system. That's it. It's also supposed to provide a "releases" system, but that seems to be currently broken in the Drupal "Projects" module. Hopefully they will fix it soon.
mandatory category fields in Groups and Project
Mon, 2006-10-02 23:24 — jurjenIn nodes of type "Group" and "Project", it is mandatory to pick 1 or more categories.
For Groups I think this is a left-over from the time when we had groups and projects coupled to each other.
For Projects it is especially annoying because when you click a category term, that is displayed next to the project name, you browse to the projects page which is very different than the other taxonomy pages. It seems to me that projects disturb our plans with categories.
Perhaps we should just dump the projects module and try this new stand-alone Case Tracker module instead?
Get started with creating new content
Mon, 2006-10-02 00:56 — johnDo you remember subscribing to the Sandbox group, when you first registered? If you don't remember, then you can click the navigation tab in the header and find the list of groups. If you visit the Sandbox group, you will see if you are subscribed, or if you need to subscribe.
You must be subscribed to the Sandbox group in order to use it for playing or for tentative "draft" work. We use this group because all nodes require a group "audience". If you are just playing or working on your first draft, you might not want a big audience. :)
The Sandbox is ideal if you want to play with creating different node types before settling on which node types to use for your new Hive content.
border around images from img_assist
Sun, 2006-10-01 21:31 — jurjenAll the images (added through img_assist) had a border around them. I did not like that, so I have removed the border.
I have edited file modules/img_assist/img_assist.css :
original:
.inline img{
border: 1px solid #000; /* put a thin border around inline images */
}
new:
.inline img{
border: none;
}
Unpublished nodes
Sun, 2006-10-01 21:25 — johnThere is currently a problem with Drupal, in that it does not allow authors to *view* their own unpublished nodes. They can edit them, but not view them.
See http://drupal.org/node/41188.
This is a shame, because otherwise, we could use a combination of the Workflow module (with workflow between published and unpublished) and the Workspace module (to view a list of all my own nodes, including the unpublished ones), to create "sandbox" type nodes, for playing or for tentative editing prior to publishing.
Hopefully there will soon be a relase of Drupal which resolves this issue.
In the meant
User access to node's "publishing information"
Sun, 2006-10-01 17:22 — johnShould be able to edit "publishing information", but not: "promoted to front page" or "sticky at top of lists". Those two should be up the Hive editors. Every user should be able to specify "published" or not for their node, and whether or not to "create new revision".
Some logo attempts
Sat, 2006-09-30 09:54 — jurjenpicture 1: the current logo
I like this shape, but don't like its color
picture 2: the current logo, colored
changed the hue to match the orange background. Well it does not match exactly, but you get the idea
picture 3:
fading background, combined with a resized logo on the foreground
picture 4:
fading background alone
picture 5:
fading background with a forgeround image that sucks
picture 6:
site tools
Thu, 2006-09-28 21:20 — jurjenOn "The Hive" you can find Progress related projects, discuss and collaborate, or start your own project and invite others to join you.
Several site tools are available to you:
Project
A project is a database for issues, bugtracking, and feature requests.
"releases" is currently broken, hopefully fixed with next version of this optional module. Fortunately, you can add attachments to almost everything.
Group
Group is a tool that facilitates collaboration among people that share an interest. Each group has:
Login difficulties, continued
Wed, 2006-09-27 17:22 — tamhasThis morning I had the same problem of just getting a refresh of the page when I tried to log in ... and now I am using FireFox. I had to get a fresh password to get in.
Boring ...
- Login to post comments
member names
Sat, 2006-09-23 10:35 — jurjenMy name is Jurjen Dijkstra. I always use my real name for login codes, this works well because my real name happens to be pretty much unique.
There are however member codes that I cannot easily associate with real people. Funny acronyms, letters with numbers.
I don't know how you feel about that, but I like to have a tiny little bit more info... get to know our members a little bit. A real name, a peg identity, whatever.
Add a few public non-mandatory fields to the account info?
