[haiku-web] Re: Community Documentation Collaboration (Was: Add Comunity Project)
- From: Urias McCullough <umccullough@xxxxxxxxx>
- To: haiku-web@xxxxxxxxxxxxx
- Date: Wed, 15 Apr 2009 10:15:20 -0700
On Wed, Apr 15, 2009 at 9:42 AM, Jorge G. Mare <koki@xxxxxxxxxxxxx> wrote:
> But that's the way it was setup! Here is a copy and paste from the
> content types admin section in the Drupal 4.7 installation:
>
> - About pages: Use to create pages that go under the About section of
> the website.
> - Team Pages: Use this to add information about teams and/or areas of
> development.
> - Document for developers: Use this to create documentation for developers.
> - Document for users: Use this to create documentation for end users.
> - Community pages: Use to create pages under the Community section.
> - Conference: Use to enter conferences and Haiku related events
> - News post: Use this form to submit news to the Haiku website.
> - RFC: Use for Request for Comment documents in Glass Elevator
>
> It is not an identical breakdown to the one that you describe, but it is
> essentially the same in that you have distinct areas of the website and
> you can specify which roles have what permissions to each of them. In
> summary, you can do what you are asking for by simply defining roles and
> adjusting the permissions.
>
> I do notice now that in the upgraded D5 installation the content types
> have changed. For example, the "About pages" content type seems to be
> gone. I don't know if this was accidental or by design; perhaps Nielx
> can tell us. :)
Right, I understand that the website is mostly configured that way,
but i don't believe there are associated roles with each of those
areas (we were talking about security roles and granting edit/admin
access to various areas of the site, not necessarily how the website
was organized content-wise)
But really, I think I've said what I can on this topic.
On another note:
I thought it was a bit ironic that someone has chosen to post another
slightly-modified, slightly incomplete guide on how to build Haiku
(hybrid this time) over at haikuware this morning...
It's not even up-to-date, as it completely ignores the new requirement
that yasm be installed :P
http://www.haikuware.com/latest/haiku-gcc4-and-hybrid-insructions
This is the very type of issue I would hope we could mitigate, even if
we can't eliminate it, rather than having someone post an entire
guide, I would prefer if they updated one of the guides already on
haiku-os.org and then posted links to it.
- Urias
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List
Other related posts:
