|
Replies:
15
-
Last Post:
Jan 12, 2006 10:39 PM
by: mditto
|
|
|
Derek Cicero
derek.cicero@sun.com
|
|
|
|
The 1.2.1 release of the website is complete
Posted:
Dec 13, 2005 5:27 PM
|
|
All,
The changes in this version of the site are detailed below. Please move
all follow-up discussion website-discuss.
----------------
Added Projects
----------------
The "basic" projects feature is now live. For information on how to get
your projects on the site, please see this thread on cab-discuss:
http://www.opensolaris.org/jive/thread.jspa?threadID=4267&tstart=0
Projects currently work the same way as communities, with some
additional features such as a "files" page and support for "affiliations".
To see a live project, go to:
http://www.opensolaris.org/os/project/opengrok/
Throughout 2006, we will be adding additional features to provide a
centralized way to manage user roles, issues, communications and code
within projects.
+ At this stage, each project can have:
- A primary mailing list: PROJECT1-discuss at opensolaris dot org and N
secondary lists.
-- Mailing lists will link with Jive using existing current tree structure.
- A web document subtree: "http://www.opensolaris.org/os/project/PROJECT1/"
-- This is the root of their web pages in the application.
- A static files area:
-- Location: http://opensolaris.org/project/PROJECT1/files/
-- The files area will only be for files that have been uploaded. It
will not support linking to files.
-- There is no hierarchy within the files section.
-- There is no versioning of files.
-- File names will be forced to be unique based on the name of the
uploaded files (not a user defined name).
--- Uniqueness is enforced on a per-page basis (i.e. example.txt can
exist on separate pages, but not on the same page).
--- Downloads will be ordered by date uploaded.
--- User can sort data by header row.
-- Mime-types for the downloads page will be supported based on the
current [Edit Community >> Attachment Content Types] process.
Each Project also has the option of:
- A News area
- A Blog aggregator
- An Announcements area
- An Events area
- Projects cannot be nested.
- Projects have a "Project Leader" with same rights as a Community Leader.
-------------------------
Added Affiliations
-------------------------
- Individuals can declare interest in a Project by affiliating with it
and becoming an "Observer".
- Individuals can declare interest in a Community by affiliating with it
and becoming an "Observer".
- An individual becomes an observer by navigating to the community or
project home page and clicking the "Affiliate with this
community/project" link
+ A community or project leader will not see the affiliation links on
their home pages.
+ There is no way to to do a mass affiliation with N projects.
+ User profile pages show all the communities and projects that a user
is affiliated with, separated out by type. (Project/Community)
- Communities can endorse a project.
+ This is done by the community leader on the community home page.
[Endorse Projects >> Project Check Boxes]
+ All community leaders can issue or revoke a communities endorsement
of a project.
+ An endorsement appears on both the community page and the project page.
- Changes in affiliates do not result in a any type of notification to a
project or community
- There is no limit to number of communities/projects to which a user
can be affiliated.
- Affiliations do not carry over from one project to a community.
+ Affiliating with a "Zones"-related project does not mean I am
affiliated with "Zones" community, even thought the "Zones" community
has sponsored the "Zones" project.
--------------------------------------
Additional Site Changes
--------------------------------------
+ Site administrators can edit the list of categories used in the bug
report form.
+ The events page now shows events that end today or in the future
instead of events that start today or in the future.
+ Replaced the Informa RSS/ATOM feed parser with a parser based on ROME
due to ROME's better supports the various RSS and ATOM specs.
+ Fixed a minor TML bug where markup could be interpreted in simple anchors
+ "Integrated" site search with results from Jive. (6346477)
+ Modified the homepage for Jive to display all of the second-level
categories and forums. (6334610)
+ Added the maximum content size for a page to the Add/Edit page forms.
(6328414)
+ Split bug report categories/subcategories into two inter-dependent lists
+ Added "Files" functionality to Communities
+ Added revised Terms of Use
+ Added new Copyright Policy/ link from footer
+ Added Website Guidelines page / link from footer
----------------
Bug Fixes RFEs
----------------
+ 6334446 - update the bug filing form to include a pointer to
'request-sponsor' process
+ 6328414 - page content limit must be raised or removed
+ 6329735 - change default values in bug logging for on opensolaris.org
+ 6334610 - bugs.opensolaris.org reporting web interface makes me cry
+ 6346477 - Need to include Jive content in opensolaris search results
Also fixed:
+ Problem with moving a page
+ Problem where currently-occurring events are not displayed
+ Improved handling of RSS feeds with non-standard date formats
+ Modified the handling of the "author" attribute of RSS feeds. Changed
the parsing algorithm to parse the author field and remove the email
address, if present.
+ Removed File Locking
--
Derek Cicero
Program Manager
Solaris Kernel Group, Software Division
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
Posts:
812
From:
US
Registered:
3/9/05
|
|
|
|
Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 2:27 PM
in response to: Derek Cicero
|
|
On Tue 13 Dec 2005 at 05:27PM, Derek Cicero wrote:
> -------------------------
> Added Affiliations
> -------------------------
>
> - Individuals can declare interest in a Project by affiliating with it
> and becoming an "Observer".
>
> - Individuals can declare interest in a Community by affiliating with it
> and becoming an "Observer".
>
> - An individual becomes an observer by navigating to the community or
> project home page and clicking the "Affiliate with this
> community/project" link
> + A community or project leader will not see the affiliation links on
> their home pages.
> + There is no way to to do a mass affiliation with N projects.
> + User profile pages show all the communities and projects that a user
> is affiliated with, separated out by type. (Project/Community)
I have to say that I am utterly baffled by this functionality. What is
the *result* of being an observer? Why would I want to be one? Why are
we mixing together the terms "affiliate" and "observer"? In the
future, will you be sending me some kind of emails based on my
observer-ship? Why should I bother to care?
And on top of that, I can't seem to actually *become* an observer
for, say, the laptop community. I never get a link which tells
me I can become an affiliate; I am properly signed in.
> - Communities can endorse a project.
> + This is done by the community leader on the community home page.
> [Endorse Projects >> Project Check Boxes]
> + All community leaders can issue or revoke a communities endorsement
> of a project.
> + An endorsement appears on both the community page and the project page.
What does endorsement imply? "Endorse" means something rather different
than "observe" or "link". Does a community have to have rules about
deciding what projects it will or won't endorse?
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng dot sun dot com - blogs.sun.com/dp
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Stephen Hahn
sch@eng.sun.com
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 3:02 PM
in response to: dp
|
|
* Dan Price <dp at eng dot sun dot com> [2005-12-14 14:27]:
> On Tue 13 Dec 2005 at 05:27PM, Derek Cicero wrote:
> > -------------------------
> > Added Affiliations
> > -------------------------
> >
> > - Individuals can declare interest in a Project by affiliating with it
> > and becoming an "Observer".
> >
> > - Individuals can declare interest in a Community by affiliating with it
> > and becoming an "Observer".
> >
> > - An individual becomes an observer by navigating to the community or
> > project home page and clicking the "Affiliate with this
> > community/project" link
> > + A community or project leader will not see the affiliation links on
> > their home pages.
> > + There is no way to to do a mass affiliation with N projects.
> > + User profile pages show all the communities and projects that a user
> > is affiliated with, separated out by type. (Project/Community)
>
> I have to say that I am utterly baffled by this functionality. What is
> the *result* of being an observer? Why would I want to be one? Why are
> we mixing together the terms "affiliate" and "observer"? In the
> future, will you be sending me some kind of emails based on my
> observer-ship? Why should I bother to care?
>
> And on top of that, I can't seem to actually *become* an observer
> for, say, the laptop community. I never get a link which tells
> me I can become an affiliate; I am properly signed in.
>
> > - Communities can endorse a project.
> > + This is done by the community leader on the community home page.
> > [Endorse Projects >> Project Check Boxes]
> > + All community leaders can issue or revoke a communities endorsement
> > of a project.
> > + An endorsement appears on both the community page and the project page.
>
> What does endorsement imply? "Endorse" means something rather different
> than "observe" or "link". Does a community have to have rules about
> deciding what projects it will or won't endorse?
I asked for this functionality in the hopes of having some chance of
identifying the significance of communities and projects as the
numbers of each of those things becomes large. The number of
communities has already exceeded the capacity of the initial portal
design. I would agree that the consistency of the terms is not
present in the current implementation.
The ability to endorse a community or affiliate with a project is
too hidden. (Is this link suppressed if you have additional
privileges?) This is a bug.
The introduction of the affiliate versus observer terminology split is
a bug.
A community's choices about what it endorses are its own to make. The
point is that the projects it endorses are significant to it in a way
that unendorsed projects are not. You may or may not choose to treat
the statement of a community as significant, but it now has the
ability to make that statement.
The reporting changes to the portals to make queries/sorting based on
number of publicly associated (endorsing or affiliated) entities is
not in the current delivery.
- Stephen
--
Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems
stephen dot hahn at sun dot com http://blogs.sun.com/sch/
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Derek Cicero
derek.cicero@sun.com
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 3:14 PM
in response to: Stephen Hahn
|
|
Stephen Hahn wrote:
> * Dan Price <dp at eng dot sun dot com> [2005-12-14 14:27]:
>
>> On Tue 13 Dec 2005 at 05:27PM, Derek Cicero wrote:
>>
>>> -------------------------
>>> Added Affiliations
>>> -------------------------
>>>
>>> - Individuals can declare interest in a Project by affiliating with it
>>> and becoming an "Observer".
>>>
>>> - Individuals can declare interest in a Community by affiliating
>>> with it
>>> and becoming an "Observer".
>>>
>>> - An individual becomes an observer by navigating to the community or
>>> project home page and clicking the "Affiliate with this
>>> community/project" link
>>> + A community or project leader will not see the affiliation links on
>>> their home pages.
>>> + There is no way to to do a mass affiliation with N projects.
>>> + User profile pages show all the communities and projects that a user
>>> is affiliated with, separated out by type. (Project/Community)
>>
>> I have to say that I am utterly baffled by this functionality. What is
>> the *result* of being an observer? Why would I want to be one? Why are
>> we mixing together the terms "affiliate" and "observer"? In the
>> future, will you be sending me some kind of emails based on my
>> observer-ship? Why should I bother to care?
>>
>> And on top of that, I can't seem to actually *become* an observer
>> for, say, the laptop community. I never get a link which tells
>> me I can become an affiliate; I am properly signed in.
>>
>>> - Communities can endorse a project.
>>> + This is done by the community leader on the community home page.
>>> [Endorse Projects >> Project Check Boxes]
>>> + All community leaders can issue or revoke a communities endorsement
>>> of a project.
>>> + An endorsement appears on both the community page and the project
>>> page.
>>
>> What does endorsement imply? "Endorse" means something rather different
>> than "observe" or "link". Does a community have to have rules about
>> deciding what projects it will or won't endorse?
>
>
> I asked for this functionality in the hopes of having some chance of
> identifying the significance of communities and projects as the
> numbers of each of those things becomes large. The number of
> communities has already exceeded the capacity of the initial portal
> design. I would agree that the consistency of the terms is not
> present in the current implementation.
>
> The ability to endorse a community or affiliate with a project is
> too hidden. (Is this link suppressed if you have additional
> privileges?) This is a bug.
It is suppressed if you are an Admin/Site Editor. This was intentional,
but upon further review it should be changed. I have already put in the
request.
Derek
>
> The introduction of the affiliate versus observer terminology split is
> a bug.
>
> A community's choices about what it endorses are its own to make. The
> point is that the projects it endorses are significant to it in a way
> that unendorsed projects are not. You may or may not choose to treat
> the statement of a community as significant, but it now has the
> ability to make that statement.
>
> The reporting changes to the portals to make queries/sorting based on
> number of publicly associated (endorsing or affiliated) entities is
> not in the current delivery.
>
> - Stephen
>
--
Derek Cicero
Program Manager
Solaris Kernel Group, Software Division
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Posts:
812
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:10 PM
in response to: Derek Cicero
|
|
|
|
On Wed 14 Dec 2005 at 03:14PM, Derek Cicero wrote:
> >The ability to endorse a community or affiliate with a project is
> >too hidden. (Is this link suppressed if you have additional
> >privileges?) This is a bug.
>
> It is suppressed if you are an Admin/Site Editor. This was intentional,
> but upon further review it should be changed. I have already put in the
> request.
> Derek
What is "site editor", anyway? I am one, but I just get an annoying
empty box on every page. See attached.
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng dot sun dot com - blogs.sun.com/dp
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Posts:
812
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:11 PM
in response to: dp
|
|
On Wed 14 Dec 2005 at 04:10PM, Dan Price wrote:
> On Wed 14 Dec 2005 at 03:14PM, Derek Cicero wrote:
> > >The ability to endorse a community or affiliate with a project is
> > >too hidden. (Is this link suppressed if you have additional
> > >privileges?) This is a bug.
> >
> > It is suppressed if you are an Admin/Site Editor. This was intentional,
> > but upon further review it should be changed. I have already put in the
> > request.
> > Derek
>
> What is "site editor", anyway? I am one, but I just get an annoying
> empty box on every page. See attached.
(err, I was one; Stephen just deleted that right from my account to see
what would happen; indeed, I can now "affiliate" myself).
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng dot sun dot com - blogs.sun.com/dp
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Derek Cicero
derek.cicero@sun.com
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:38 PM
in response to: dp
|
|
Dan Price wrote:
> On Wed 14 Dec 2005 at 03:14PM, Derek Cicero wrote:
>
>>> The ability to endorse a community or affiliate with a project is
>>> too hidden. (Is this link suppressed if you have additional
>>> privileges?) This is a bug.
>>
>> It is suppressed if you are an Admin/Site Editor. This was intentional,
>> but upon further review it should be changed. I have already put in the
>> request.
>> Derek
>
>
> What is "site editor", anyway? I am one, but I just get an annoying
> empty box on every page. See attached.
It is a role that allows certain folks to add news, announcements, etc.
without having admin rights.
We can make it so it only appears on applicable pages.
Derek
>
> -dp
>
>
>
> ------------------------------------------------------------------------
>
--
Derek Cicero
Program Manager
Solaris Kernel Group, Software Division
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,901
From:
NZ
Registered:
6/16/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:18 PM
in response to: Derek Cicero
|
|
Hey,
On Wed, 2005-12-14 at 15:14 -0800, Derek Cicero wrote:
> > The ability to endorse a community or affiliate with a project is
> > too hidden. (Is this link suppressed if you have additional
> > privileges?) This is a bug.
>
> It is suppressed if you are an Admin/Site Editor. This was intentional,
> but upon further review it should be changed. I have already put in the
> request.
Hrm, I'm a community leader, but I still don't see any way of adding
myself as an observer.
Glynn
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Posts:
812
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:21 PM
in response to: gman
|
|
On Thu 15 Dec 2005 at 01:19PM, Glynn Foster wrote:
> Hey,
>
> On Wed, 2005-12-14 at 15:14 -0800, Derek Cicero wrote:
> > > The ability to endorse a community or affiliate with a project is
> > > too hidden. (Is this link suppressed if you have additional
> > > privileges?) This is a bug.
> >
> > It is suppressed if you are an Admin/Site Editor. This was intentional,
> > but upon further review it should be changed. I have already put in the
> > request.
>
> Hrm, I'm a community leader, but I still don't see any way of adding
> myself as an observer.
I think you can't be both. Maybe this should be refactored into:
[Community Members]
[Affiliate with this community] [(what is this?)]
And then the Community Members link would take you to a page:
Community Leaders:
Foo Bar, III
Quux Bazley
Affiliated with this Community:
...
...
...
Just a thought to simplify things a bit.
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng dot sun dot com - blogs.sun.com/dp
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,901
From:
NZ
Registered:
6/16/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:21 PM
in response to: gman
|
|
On Thu, 2005-12-15 at 13:19 +1300, Glynn Foster wrote:
> Hrm, I'm a community leader, but I still don't see any way of adding
> myself as an observer.
Nevermind, I guess I can't be an observer as well as a leader :)
I just wonder if the 'Affiliate with this community/project' should
actually be in the sidebar rather than somewhat lost in the main page
layout.
Glynn
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Derek Cicero
derek.cicero@sun.com
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:35 PM
in response to: gman
|
|
Glynn Foster wrote:
> On Thu, 2005-12-15 at 13:19 +1300, Glynn Foster wrote:
>
>> Hrm, I'm a community leader, but I still don't see any way of adding
>> myself as an observer.
>
>
> Nevermind, I guess I can't be an observer as well as a leader :)
Yes, a leader is already affiliated with the project.
>
> I just wonder if the 'Affiliate with this community/project' should
> actually be in the sidebar rather than somewhat lost in the main page
> layout.
That was something Jim G suggested as well. I will propose an alternate
solution.
Derek
>
>
>
> Glynn
>
> _______________________________________________
> website-discuss mailing list
> website-discuss at opensolaris dot org
>
--
Derek Cicero
Program Manager
Solaris Kernel Group, Software Division
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Posts:
110
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Jan 12, 2006 10:39 PM
in response to: Derek Cicero
|
|
> Yes, a leader is already affiliated with the project.
This needs to be reflected in the user profile page; currently it's not.
|
|
|
|
|
Posts:
110
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 6:15 PM
in response to: gman
|
|
> Nevermind, I guess I can't be an observer as well as a leader :)
Isn't that a bit like: "Lead, follow, or get out of the way"? :)
|
|
|
|
|
Derek Cicero
derek.cicero@Sun.COM
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 20, 2005 3:29 PM
in response to: Derek Cicero
|
|
>>
>>
>> I asked for this functionality in the hopes of having some chance of
>> identifying the significance of communities and projects as the
>> numbers of each of those things becomes large. The number of
>> communities has already exceeded the capacity of the initial portal
>> design. I would agree that the consistency of the terms is not
>> present in the current implementation.
>>
>> The ability to endorse a community or affiliate with a project is
>> too hidden. (Is this link suppressed if you have additional
>> privileges?) This is a bug.
>
>
> It is suppressed if you are an Admin/Site Editor. This was
> intentional, but upon further review it should be changed. I have
> already put in the request.
> Derek
This has been changed. Site Admins and Site Editors now have the
"affiliate" option.
Derek
>
>>
>
--
Derek Cicero
Program Manager
Solaris Kernel Group, Software Division
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Posts:
812
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:17 PM
in response to: Stephen Hahn
|
|
On Wed 14 Dec 2005 at 03:02PM, Stephen Hahn wrote:
> > What does endorsement imply? "Endorse" means something rather different
> > than "observe" or "link". Does a community have to have rules about
> > deciding what projects it will or won't endorse?
>
> I asked for this functionality in the hopes of having some chance of
> identifying the significance of communities and projects as the
> numbers of each of those things becomes large. The number of
> communities has already exceeded the capacity of the initial portal
> design. I would agree that the consistency of the terms is not
> present in the current implementation.
>
> The ability to endorse a community or affiliate with a project is
> too hidden. (Is this link suppressed if you have additional
> privileges?) This is a bug.
>
> The introduction of the affiliate versus observer terminology split is
> a bug.
>
> A community's choices about what it endorses are its own to make. The
> point is that the projects it endorses are significant to it in a way
> that unendorsed projects are not. You may or may not choose to treat
> the statement of a community as significant, but it now has the
> ability to make that statement.
>
> The reporting changes to the portals to make queries/sorting based on
> number of publicly associated (endorsing or affiliated) entities is
> not in the current delivery.
Ok, that helps to clarify things. I guess I'm wishing that somehow the
action I take (affiliation, endorsing, etc.) would lead to some more
tangible effect-- in other words, making it worth my effort. Maybe
in the future we could make... a customized portal page which aggregates
the transient artifacts (announcements/blogs/news/bugs/etc). of the
projects I am observing??
A "(what is this?)" help link next to the button that establishes
affiliation 'splaining this would be cool.
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng dot sun dot com - blogs.sun.com/dp
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
Stephen Hahn
sch@eng.sun.com
|
|
|
|
Re: Re: [osol-discuss] The 1.2.1 release of the
website is complete
Posted:
Dec 14, 2005 4:22 PM
in response to: dp
|
|
* Dan Price <dp at eng dot sun dot com> [2005-12-14 16:17]:
> On Wed 14 Dec 2005 at 03:02PM, Stephen Hahn wrote:
> > > What does endorsement imply? "Endorse" means something rather different
> > > than "observe" or "link". Does a community have to have rules about
> > > deciding what projects it will or won't endorse?
> >
> > I asked for this functionality in the hopes of having some chance of
> > identifying the significance of communities and projects as the
> > numbers of each of those things becomes large. The number of
> > communities has already exceeded the capacity of the initial portal
> > design. I would agree that the consistency of the terms is not
> > present in the current implementation.
> >
> > The ability to endorse a community or affiliate with a project is
> > too hidden. (Is this link suppressed if you have additional
> > privileges?) This is a bug.
> >
> > The introduction of the affiliate versus observer terminology split is
> > a bug.
> >
> > A community's choices about what it endorses are its own to make. The
> > point is that the projects it endorses are significant to it in a way
> > that unendorsed projects are not. You may or may not choose to treat
> > the statement of a community as significant, but it now has the
> > ability to make that statement.
> >
> > The reporting changes to the portals to make queries/sorting based on
> > number of publicly associated (endorsing or affiliated) entities is
> > not in the current delivery.
>
> Ok, that helps to clarify things. I guess I'm wishing that somehow the
> action I take (affiliation, endorsing, etc.) would lead to some more
> tangible effect-- in other words, making it worth my effort. Maybe
> in the future we could make... a customized portal page which aggregates
> the transient artifacts (announcements/blogs/news/bugs/etc). of the
> projects I am observing??
>
> A "(what is this?)" help link next to the button that establishes
> affiliation 'splaining this would be cool.
I just fired up Bugster to get a few of these points filed for
tracking. Expect a followup with IDs shortly...
- Stephen
--
Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems
stephen dot hahn at sun dot com http://blogs.sun.com/sch/
_______________________________________________
website-discuss mailing list
website-discuss at opensolaris dot org
|
|
|
|
|
